-
Notifications
You must be signed in to change notification settings - Fork 948
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
PersistentVolumeClaim retention is feature-gated and should be handled conditionally #2599
Comments
Observing the same. We are on GKE 1.26 . |
Setting configuration to |
bo0ts
added a commit
to bo0ts/postgres-operator
that referenced
this issue
Apr 16, 2024
I have the same problem. |
Hi, same issue here :( |
any update? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After upgrading to v1.11.0 I noticed the following messages for every postgres cluster on every start up of the operator:
After that nothing happens. The sts is neither deleted nor fixed and the messages show up on every start of the operator.
The cluster is running version k8s 1.25. It is my understanding that PersistentVolumeClaims are behind a feature-gate even in version 1.27 and that those parts of the sts spec can never be set. Indeed, trying to set them manually fails. See: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention
The operator should not attempt to set those values if the feature is not available.
The text was updated successfully, but these errors were encountered: