Felix Kunde

Changing the version in the manifest does nothing. In-place version upgrade is not supported yet. See [docs](https://github.com/zalando/postgres-operator/blob/master/docs/administrator.md#minor-and-major-version-upgrade). The version in the docker image name only refers to the latest Postgres...

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

Yeah, I have updated min required K8s version to 1.27 in the README :smiley: No, seriously, I would still suggest to add a simple if that checks the server version....

sounds like a good PR to me :) You can define another [global config option](https://github.com/zalando/postgres-operator/blob/master/docs/developer.md#introduce-additional-configuration-parameters) to specify the class where the default is empty. Type should be *string then.

Update your K8s folks, c'mon! 1.27 is already old. Or somebody come up with proper PR where operator checks the server version.

We released 1.12.2 today :partying_face:

Sorry to keep you waiting. Let me get some focus time on this topic next week so we can include into the upcoming release.

You've selected the Backups tab in UI. If you have neither configured a backup location nor set the required environment variable for UI deployment these errors are expected.

Sorry, I cannot replicate this. I tested in minikube adding the operator and ui using the provided kustomizations. No matter if I create a cluster with kubectl create or via...

@devops-matriz are you maybe still on helm 2? That has been an issue when I [last saw](https://github.com/zalando/postgres-operator/issues/760#issuecomment-579278642) this type of error.