zalando / zalando/postgres-operator
[Question] Loosing login role on cluster update
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hello everyone,
When updating our cluster or moving pods from one node to another, our user looses the login role which causes service interruption. The role comes back after a while (time range vary)
I am probably missing some configuration, feeling like a "minimum replica policy" might be the thing (we have two replicas).
Any idea that might help ? 🙏
Thank you
Hugo
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.10.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS EKS
- Are you running Postgres Operator in production? yes
- Type of issue? question
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 by reproducing the cluster update or pod move with Postgres Operator v1.10.0 on AWS EKS, using the reported two-replica setup. Inspect the operator behavior around the login role during failover or rescheduling. Done means identifying the relevant configuration or producing a clearly reproducible operator defect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100