zalando / zalando/postgres-operator
Helm: Can't set ImagePullSecrets for Logical Backup image
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
When deploying operator via Helm, it is not possible to specify local container repository for Logical Backup image. It does not inherit ImagePullSecrets specified for operator itself, and there is no such setting in values.yaml.
My bigger "problem" is that my local minio instance I'm using to write backups to does not have a valid certificate and Logical Backup can't backup to it unless I patch the image. I can't do that in any sane way if operator was installed through Helm.
For aws s3 cli that is used in Logical Backup image, there exists a parameter --no-verify-ssl, however there is no way to pass it through to the entrypoint script. Alternatively, I could pass a certificate into the cronjob pod as an init container, but again, there is no way to specify any of it via Helm.
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 with values.yaml and the Logical Backup entrypoint script, then trace how Helm renders the logical-backup cronjob pod. Define the configuration needed for image pull secrets and the S3 SSL or certificate options, and verify that a Helm deployment can pass those settings through without manual patching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes, postgresql
- Domain
- cloud, database, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100