zalando / zalando/postgres-operator
Additional Read-only replicas
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.8.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Kubernetes on Cloud
- Are you running Postgres Operator in production? yes
- Type of issue? Question
I want to create a cluster on multi-zone cluster. Zone A is the core zone and I want to make sure the master pod (and stand-by pods) to stay in zone A while deploying read-only replicas on zone B.
I can specify nodeSelector to create cluster but cannot create read-only replicas on zone B. Is adding read-only instances possible?
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 reviewing the operator documentation and configuration related to node selection and replica placement. Compare the requested core-zone master and standby placement with read-only replicas in another zone, then determine the expected configuration and acceptance criteria for multi-zone scheduling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, 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