Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Persistent Volume on Configuration Change #2794

Open
holgerson97 opened this issue Oct 27, 2024 · 1 comment
Open

New Persistent Volume on Configuration Change #2794

holgerson97 opened this issue Oct 27, 2024 · 1 comment

Comments

@holgerson97
Copy link

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

@FxKu
Copy link
Member

FxKu commented Nov 26, 2024

This sounds very odd. What changes do you do to the manifest? For pod rotations your K8s should make sure they re-attach to the existing volumes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants