zalando / zalando/postgres-operator
Scaling in k8s cloud.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hello. Thanks a lot for this pretty operator.
I could not find info about scaling pods with a postgres operator!
I have operator in my k8s cluster and CRD postgres, configured to be 3-instancies pg-cluster. So, if I want to enable autoscaling, what shall i do? Is it built in? I meen to auto-scale statefulset pod count.
I know, that k8s have a HPA for example, but... postgres operator has some checking feature to "repare" pg-cluster and if i change statefulset pods count manualy, then operator will "fix" to mainfest default value = 3. What do i need to do? Create pg-cluster with some other way that crd? Or maybe some patrony configuration? Maybe will find answer soon and will close issue, but i think, it may be question that interests not only me.
best regards, Piter.
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 reviewing the operator's CRD and StatefulSet behavior in relation to Kubernetes HPA and Patroni, as named in the issue. Determine whether autoscaling pod count is supported or needs a defined design, then document the expected configuration and how reconciliation should behave when scaling occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100