Upgrade

Upgrading to a new version of Crunchy Postgres for Kubernetes depends on the tool used during the initial install, as well as the version being upgraded to. This section provides detailed instructions for upgrading Crunchy Postgres for Kubernetes 5.x using Kustomize, Helm or OperatorHub, along with information for upgrading from Crunchy Postgres for Kubernetes v4 to Crunchy Postgres for Kubernetes v5.

Info

Depending on version updates, upgrading PGO may automatically rollout changes to managed Postgres clusters. This could result in downtime--we cannot guarantee no interruption of service, though PGO attempts graceful incremental rollouts of affected pods, with the goal of zero downtime.

Registering Crunchy Postgres for Kubernetes Prior to Upgrading

A registration token is required when upgrading Certified and Marketplace OperatorHub installations. Therefore, if you have installed Crunchy Postgres for Kubernetes using these either of these installation methods, be sure to register your Crunchy Postgres for Kubernetes installation prior to upgrading.

Upgrading Crunchy Postgres for Kubernetes 5.x

Upgrading from Crunchy Postgres for Kubernetes v4 to Crunchy Postgres for Kubernetes v5