zalando / zalando/postgres-operator
Use a secret for logical backup credentials
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Is it possible at the moment to use a secret for logical backup credentials?
Reason why I am asking is because we setup the postgres operator and its config using flux, which means that all the config is stored in git. We can hardly store the credentials in the configmap in clear text in git.
For physical backups it is already possible to use secrets with credentials in there, it would make sense in my opinion to do the same for logical backups?
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.6.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Any platform [AKS, EKS, bare metal, OpenShift,...]
- Are you running Postgres Operator in production? [yes ]
- Type of issue? feature request
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
No file, test, or entry point is named. Start by comparing the existing physical-backup Secret support with the logical-backup credential configuration. Done means logical-backup credentials can be supplied through a Kubernetes Secret instead of plaintext ConfigMap data, with the relevant behavior covered by project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100