zalando / zalando/postgres-operator
[Feature Request] Option to choose a PriorityClassName for the pooler pods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Kubenetes on cloud (GKE) and metal
- Are you running Postgres Operator in production? yes
- Type of issue? Feature request
Hello,
We utilize multiple postgres-operator instances for various purposes and criticality levels (e.g., production, pre-production, testing) on the same cluster and, in some cases, in the same namespace. We would like to set a different priority class for the poolers across different releases of the postgres-operators and postgres clusters.
Is it possible to add the priorityClassName in the pooler configuration ?
I am working on a PR to present a possible solution.
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 tracing the pooler configuration into the Kubernetes pod specification and identify how configuration differs across releases and clusters. Check the repository's relevant tests or Kubernetes validation; done means pooler pods accept the requested priorityClassName independently without changing unrelated pods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100