zalando / zalando/postgres-operator
Discussion notes on: 1 Statefulset per node
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Yesterday evening we found out that we arrived at similar need for different reason:
-
Controlled scale down to not terminate master node during scale down
-
Allow per replica/node different configuration, e.g. slaves with less resources
As a remark to the statefulset should scale down in a deterministic fashion thus the highest number of pod will be terminated(removed).
For 1) I also don't feel this is warrant enough for rewrite to multiple statefulsets, as failing over should be a no brainer combined with the probably very low times people actually scale up and down. Maybe Patroni can even prefer to fail over to lowest number pod.
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
No file, test, or implementation entry point is named. Start by reviewing the StatefulSet scale-down behavior and the stated needs for controlled termination and per-replica configuration, then determine whether Patroni or multiple StatefulSets are in scope; done requires an agreed design and explicitly defined behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100