zalando / zalando/postgres-operator
Operator ignores OperatorConfiguration changes
Open
Nobody has claimed this yet.
wontfix
- 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? - registry.opensource.zalan.do/acid/postgres-operator:v1.6.0
- Where do you run it - cloud or metal? - Bare Metal K8s (microk8s)
- Are you running Postgres Operator in production? - yes
- Type of issue? - Bug report
Operator successfully read own OperatorConfiguration resource on start and ignores subsequent updates to it. I can't find any params/env to configure this behavior in docs.
As workaround we are forced to delete operator pod.
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 or test is named in the report. Start by tracing how the Kubernetes OperatorConfiguration resource is read and whether updates trigger reconciliation; reproduce the behavior on the reported operator version. Done means configuration changes take effect without deleting the operator pod, with regression coverage if the project has a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100