Major Version Upgrade of Standby Clusters?

[thoro]

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.11.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
• Are you running Postgres Operator in production? yes
• Type of issue? Question / Feature Request

How are major version upgrades envisioned to function together with Standby Clusters? We have a master and multiple StandbyClusters which are completely separated.

Is there already some manual to handle these kind of upgrades? Postgres rsync suggestion will not work since the operator immediately restarts the new major version.

[FxKu]

So far major version upgrade across standby clusters is not supported. You would have to recreate the K8s resource - especially when you create it from S3. Not sure if there would be a way when using host address.

[thoro]

Currently they are running via host-address.

To automate, I guess a wait point needs to be implemented in Patroni and use the postgres-operator to execute the rsync at the correct point in time.

Would you have a pointer where those 2 operstions could be implemented?

Maybe there's a post-upgrade script oppurtunity?