Compatibility with Kubernetes v1.29

zalando / postgres-operator

Postgres operator creates and manages PostgreSQL clusters running in Kubernetes

https://postgres-operator.readthedocs.io/

MIT License

4.35k stars 980 forks source link

Compatibility with Kubernetes v1.29 #2603

Closed toabi closed 4 months ago

toabi commented 6 months ago

The table in the readme currently only lists v1.28 as max version.

Is there really anything blocking the use of the operator in a kubernetes 1.29 cluster?

FxKu commented 6 months ago

I have only noticed one incompatibility when changing libraries to 1.29. But it's only the go-client (it must be VolumeResourceRequirements now). Would be happy if you can test out operator on 1.29. We are just moving to 1.28 here.

minimax75 commented 6 months ago

Hi @FxKu , I ran an update from EKS 1.28 to 1.29 on our test-box with Operator version 1.10.1 and observed following problem. Leader-Pods are not evicted automatically from a cordoned and draining node. I need to manually switchover and then the pod gets evicted. I did not observe this behavior during the upgrade from 1.27 to 1.28.

FxKu commented 6 months ago

@minimax75 sounds unrelated to 1.29. Maybe you're using a newer Spilo/Patroni version? I would update to 1.11 to be sure you include this fix: https://github.com/zalando/postgres-operator/pull/2515

98jan commented 6 months ago

installed today in my kubeadm provisioned Kubernetes Cluster with version 1.29.0 and everything was working as expected for my use case.

minimax75 commented 6 months ago

updated to 1.11 and the issue is gone, so looks like it is related to spilo-15 3.2-p1 and operator 1.10.1

FxKu commented 4 months ago

I have updated the README. You can run the operator on K8s 1.29 and higher without any problems.