zalando / zalando/postgres-operator
switchover instead of failover
Open
Nobody has claimed this yet.
patroni
question
technical issue
- 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.5.0
- Where do you run it? Bare Metal K8s
- Are you running Postgres Operator in production? no
- Type of issue? question
Why you use /failover route instead /switchover. How about using /switchover for rolling upgrade to remove down time?
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
Read pkg/util/patroni/patroni.go at the linked route and compare the requested switchover behavior with the current failover path. Done would require a decided upgrade and availability policy plus validated operator behavior; the issue does not identify tests or acceptance criteria.
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