zalando / zalando/postgres-operator
Postgresql service timeout 3 of 5 requests without selector for master
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
ghcr.io/zalando/postgres-operator:v1.12.2
Runned in 1.25 k8s by vmware tanzu for dev/stage envs
It's seems like a bug without an added selector for service for master pod
labels:
application: spilo
cluster-name: stage-psql
spilo-role: master
service response to a request 1 of 2-3 times.
30 requests - 10 response, other 20 - timeout. Fully fixed with setting selector. Is there option of adding a selector by default to service, or any thougths how to fix it without adding a selector?
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 intermittent service timeouts in Kubernetes with postgres-operator v1.12.2 and compare the service behavior with and without a selector targeting the master pod labels shown in the issue. Trace how the operator generates the PostgreSQL service and verify that the completed change consistently routes requests to the master without requiring a manually added selector.
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
- Mostly clear
- Newbie friendliness
- 35/100