zalando / zalando/postgres-operator
New Persistent Volume on Configuration Change
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.13.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS EKS
- Are you running Postgres Operator in production? [yes | no] yes
- Type of issue? [Bug report, question, feature request, etc.] question
I am currently running multiple clusters using the operator. When I perform an update to the cluster manifest a new PV and gets created. I want my data to persist across configuration changes, how can I achieve this?
Thanks in advance
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. Start by reproducing a cluster-manifest update with postgres-operator:v1.13.0 on EKS and inspect the resulting PersistentVolume resources and operator logs; done means identifying the configuration or behavior that controls data persistence across updates and documenting the supported outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100