zalando / zalando/postgres-operator
Option to use zookeeper as DCS when using CRD
Open
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.8.2
- Where do you run it? - K8s on AWS VMs
- Are you running Postgres Operator in production? not yet.
- Type of issue? Question
I have a spare zookeeper (for Kafka) running in my K8s which want to use as DCS. I cant seem to figure our the configuration option for the same looking at the docs. I saw there is a SPILO_CONFIGURATION in Spilo, but not sure how to override in the operator ?
How to specify endpoints for non etcd/K8s API DCS ?
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
No files or tests are named in the issue. Start by reviewing the operator's CRD and DCS configuration documentation, then trace how non-etcd and non-Kubernetes API endpoints are configured; done means the supported configuration path is established and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100