Open bo0ts opened 5 months ago
Observing the same. We are on GKE 1.26 .
Setting configuration to
persistent_volume_claim_retention_policy: {}
or even completely removing it has no effect and behaves same way as described in this issue.
I have the same problem.
Hi, same issue here :(
any update?
Update your K8s folks, c'mon! 1.27 is already old. Or somebody come up with proper PR where operator checks the server version.
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.