dapr / dapr/kubernetes-operator
dapr-control-panel - Image Registry Override
- Dominant language
- Go
- Stars
- 18
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Hi guys,
Is there anyway to override the image registry for the dapr-control-panel to use an internal registry instead of ghcr.io? We are having some challenges with the upgrade right with the pod not starting becuase it cannot pull the image. We might be able to override it manually but we'd like to control it within the configuration somehow if possible.
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the repository for the dapr-control-panel image reference and the Kubernetes configuration or deployment manifests that define it. Determine whether an internal registry can be set through existing configuration; done means the image source is configurable and the pod can pull the configured image instead of ghcr.io.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100