zalando / zalando/postgres-operator
Statefulset not marking any replicas as current
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
I just deployed a postgres cluster using the operator on EKS and noticed the db statefulset never marks any of its replicas as current. It's still entirely functional, but confuses some of our application health checking which relies on the statefulset status field to declare the entire app as ready.
I also have enabled a monitoring sidecar which might be affecting things but I somewhat doubt it.
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS EKS
- Are you running Postgres Operator in production? no
- Type of issue? Bug report
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 PostgreSQL cluster deployment on AWS EKS with operator image v1.6.3, then inspect the StatefulSet status and the effect of the monitoring sidecar. Trace why no replicas are marked current and compare the observed status with the readiness check that consumes it. Done means the StatefulSet reports current replicas for a functional cluster and the application health check can declare it ready.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100