zalando / zalando/postgres-operator
Operator not loading Configmap
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 - Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
It runs in the cloud (Digital Ocean) - Are you running Postgres Operator in production? [yes | no]
Not yet - Type of issue? [Bug report, question, feature request, etc.]
Question ~ Bug
I'm trying to set up the AWS S3 backup. To do so, I have used the ConfigMap from this URL -> https://github.com/zalando/postgres-operator/blob/master/manifests/configmap.yaml. It seems the operator doesn't take anything from the configMap file, even after a restart. Furthermore, the logs show those loaded default variables are not from the applied ConfigMap.
FYI, the operator was installed with 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 manifests/configmap.yaml and the Helm installation configuration, then compare the applied ConfigMap with the operator logs after a restart. Check how the AWS S3 backup settings are supplied and loaded; done means the operator uses the applied values rather than its defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes, postgresql
- Domain
- cloud, databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100