zalando / zalando/postgres-operator
[kustomize] use configMapGenerator instead of ConfigMap resource
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
When making changes to the postgres-operator ConfigMap, the operator doesn't appear to detect the changes (at least judging by the logs).
If configMapGenerator was used instead, the ConfigMap name would be given a suffix of the hash of the contents (so as the contents change, the hash changes, and so do the references used in Deployments/StatefulSets for example, which in-turn are reconciled (likely restarting the pods).
I haven't taken a close look, so perhaps the operator is constantly watching for changes via the k8s API.
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
Locate the manifests that define the postgres-operator ConfigMap and its references in Deployments or StatefulSets, then inspect how the operator watches ConfigMap changes through the Kubernetes API. Compare the current behavior with configMapGenerator and verify through operator logs that changing the configuration causes the affected workloads to be reconciled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100