zalando / zalando/postgres-operator
Fix PDB Behavior for Single-Instance PostgreSQL Deployments
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
When the controller deployed with enable_pod_disruption_budget, it applies the same configuration to all PostgreSQL deployments, including those with numberOfInstances = 1.
For single-instance PostgreSQL setups, this results in a PDB that requires at least one pod to be available at all times.
Because the deployment only has one pod, Kubernetes blocks node draining and node rotation operations, causing operational friction.
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
Locate the controller logic handling enable_pod_disruption_budget and compare PodDisruptionBudget generation for deployments with numberOfInstances = 1 versus larger deployments. Verify the resulting Kubernetes behavior during node draining or rotation, while preserving the existing behavior for multi-instance PostgreSQL deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100