zalando / zalando/postgres-operator
Supporting HPA for Zalando postgres
Open
Nobody has claimed this yet.
idea
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi,
We can eaily support the HPA by adding few parameters on CRD.
subresources:
status: {}
scale:
labelSelectorPath: .status.selector
specReplicasPath: .spec.numberOfInstances
statusReplicasPath: .status.replicas
- Which image of the operator are you using? - registry.opensource.zalan.do/acid/postgres-operator:v1.7.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? K8s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
we can scale Up the postgres CRD based on the number of Read Request and so on...
Thanks,
Kannan V
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 locating the operator's PostgreSQL CRD definition and reviewing Kubernetes HPA scale subresource requirements. Check how .status.selector, .spec.numberOfInstances, and .status.replicas are represented, then verify that HPA can scale the CRD based on read-request metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100