zalando / zalando/postgres-operator
Feature request: support for more Patroni options
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.6.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal with rancher
- Are you running Postgres Operator in production? yes
- Type of issue? Feature request
The documentation for patroni parameters has a link to the full list. However, not all of them are supported.
In my case, I'd like to disable replication's sslmode as I'm using Zalando with Istio and is not needed. But patroni.postgresql.authentication is not defined in the manifest
My question is: would it be enough to just add this to the CRD definition or does Zalando not support for other reasons?
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 the cluster manifest's Patroni parameters documentation and compare its linked full Patroni settings list with the CRD definition. Trace how patroni.postgresql.authentication is handled by the operator, especially the requested replication sslmode setting. Done means the supported scope is established and the manifest, operator behavior, and documentation consistently reflect the result.
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