Upgrade
Upgrading to a new version of Crunchy Postgres for Kubernetes (CPK) depends on the tool used during the initial install, as well as the version being upgraded to. This section provides detailed instructions for upgrading CPK 5.x using Kustomize, Helm or OperatorHub, along with information for upgrading from CPK v4 to CPK v5.
Info
Depending on version updates, upgrading CPK may automatically rollout changes to managed Postgres clusters. This could result in downtime--we cannot guarantee no interruption of service, though CPK attempts graceful incremental rollouts of affected pods, with the goal of zero downtime.
Registering CPK Prior to Upgrading
A registration token is required when upgrading Certified and Marketplace OperatorHub installations. Therefore, if you have installed CPK using these either of these installation methods, be sure to register your CPK installation prior to upgrading.