zalando / zalando/postgres-operator
readiness probe failure when using /readiness
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. acid/postgres-operator:v1.8.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Openshift
- Are you running Postgres Operator in production? yes
- Type of issue? Bug
readiness probe fails for the postgres pods when using /readiness as the path
It works fine if i update the path to /patroni
Have opened an issue with spilo as well. but no response there
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 comparing the failing /readiness probe with the working /patroni path in the PostgreSQL operator setup on OpenShift. Read the linked Spilo issue 892 for related context, then verify the behavior on PostgreSQL pods; done means /readiness succeeds without switching to /patroni.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- database, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100