zalando / zalando/postgres-operator
Create k8s Service pointing to synchronous replicas
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 - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
Hi team!
The operator is creating foo-test-cluster-repl Service pointing to all replicas. When one wants to use synchronous replication, could the operator create the Service pointing only to synchronous replicas? E.g. foo-test-cluster-sync-repl pointing to replicas with Sync Standby role (patroni notation), foo-test-cluster-repl pointing to all replicas (it seems to me it's a valid case when total_replicas > sync_replicas).
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 how the operator creates the existing replica Service and how it identifies Patroni replica roles. Confirm how synchronous replicas are represented, then define the additional Service behavior while preserving the existing all-replica Service. Done means the synchronous-replica Service selects only replicas with the Sync Standby role and the existing Service still selects all 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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100