zalando / zalando/postgres-operator
Feature Request: separate settings for the replica connection pooler
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? the internally deployed one :)
- 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
With one master and three replicas, I want to set different maxDBConnections and mode for the replica connection pooler, similar to the connectionPooler settings, but just dedicated to the replica pooler. Setting the maxDBConnections to what we could use one the replicas, would be too much for the one master.
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 existing connectionPooler settings and the replica connection pooler configuration in the operator. Check how maxDBConnections and mode are currently applied to master and replica pools, then verify that separate replica values can be configured and are rendered correctly for a cluster with one master and three replicas.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100