zalando / zalando/postgres-operator
Major Version Upgrade of Standby Clusters?
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? ghcr.io/zalando/postgres-operator:v1.11.0
- 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? Question / Feature Request
How are major version upgrades envisioned to function together with Standby Clusters? We have a master and multiple StandbyClusters which are completely separated.
Is there already some manual to handle these kind of upgrades? Postgres rsync suggestion will not work since the operator immediately restarts the new major version.
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 file, test, or entry point is named. Start by tracing the operator's standby-cluster and major-version upgrade handling, then consult any existing upgrade documentation. Done would require a documented, supported procedure or a clearly scoped implementation path for upgrading the master and separated standby clusters.
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