zalando / zalando/postgres-operator
Ability to provide imagePullSecret for internal Spilo images
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
- v1.8.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
- Bare Metal K8s
- Are you running Postgres Operator in production? [yes | no]
- no
- Type of issue? [Bug report, question, feature request, etc.]
- feature request
When override the default spilo docker_image parameter there is no option to provide any imagePullSecrets for fetching this image. As a result, if you try to pull from a private registry then the Postgres pods end up in ImagePullBackOff
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the docker_image parameter is handled when the operator creates PostgreSQL pods, then inspect where Kubernetes image pull configuration is assembled. Done means a custom private Spilo image can be pulled with supplied imagePullSecrets instead of leaving pods in ImagePullBackOff; add or update coverage for that configuration if the repository provides a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100