zalando / zalando/postgres-operator
Pod Priority Class for configConnectionPooler is missing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using?: registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
- **Where do you run it - cloud or metal? Kubernetes or OpenShift?: Kubernetes on AKS, EKS
- Are you running Postgres Operator in production?: yes
- Type of issue?: feature request
It is not possible to specify priorityClassName for pooler Deployment under configConnectionPooler in values.yaml Pooler deployment is created without priority class assigned and gets kicked out on production environments with priority classes.
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 with charts/postgres-operator/values.yaml, especially the configConnectionPooler section referenced in the issue, and trace how pooler Deployments are rendered. Add support for configuring a priority class on the pooler Deployment, then verify the rendered Kubernetes manifest includes the requested setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100