Upgrade path for VMware Postgres for Kubernetes version 2.3.0 to 4.3.0

Products

• VMware Tanzu Data Suite

Issue/Introduction

We are currently running Postgres for Kubernetes version 2.3.0 and would like to upgrade to the latest version. Is this possible?

Resolution

Due to extensive software changes in Postgres for Kubernetes you cannot upgrade directly from version 2.3.0 to 4.3.0.

You will need to plan on:

1. Upgrading from version 2.3.0 to version 3.0
2. Migrate from version 3.0 to version 4.2.4
3. Then upgrade to the latest version of Postgres for Kubernetes

 

Upgrade to Tanzu for Postgres on Kubernetes 3.0

Upgrading the VMware Tanzu for Postgres on Kubernetes Operator and Instances

Important upgrade notes:

• If you have been manually modifying the pg_hba.conf file, remove those entries from the pg_hba.conf file and transition to the supported workflow.
• Ensure glibc library has been upgraded from version 2.27 to 2.35
• When upgrading the VMware Postgres Operator, the Operator will ensure that existing Postgres instances have the appropriate version reference added to the object. Specifically, the Operator will set 'spec.postgresVersion.name' to 'postgres-15'. If you are tracking manifest files in source control, update those manifest files to reflect the change. Note that existing Postgres instances cannot be upgraded to a different major version.

 

NOTE: Use Helm CLI 3.8.0  and later

Accessing the Resources

Accessing the resources using two different methods:

1. Use Setup VMware Postgres Operator via Broadcom Support Portal Registry for a faster installation process, and if your server hosts have access to the internet.
2. Use Setup VMware Postgres Operator via Downloadable Archive File if your server hosts do not have access to the internet, or if you want to install from a private registry.

 

Upgrading the Operator using Helm

Steps can be found in the link above.

 

Upgrading the Operator using the Tanzu CLI

Steps can be found in the link above.

 

Upgrade to Tanzu for Postgres on Kubernetes 4.2.4

Important upgrade notes:

Version 4.0.0 represents a significant architectural evolution in the Postgres Operator, transition from pg_auto_failover to Patroni as the high availability practices.

Due to the fundamental nature of this architectural transformation, direct upgrades to version 4.0.0 from previous versions are currently not supported. This limitation is a result of the comprehensive changes in how database clusters are managed and orchestrated.

WARNING: Once a major version upgrade process is concluded, it becomes irreversible and you can't downgrade to the source version of the Postgres instance.

 

Upgrading Tanzu Postgres on Kubernetes Operator from v.3.0 to v4.2.4

Steps can be found in the link above.

NOTE: The upgrade process changes the underlying architecture and requires downtime. It is mandatory to take a full backup of all instances before proceeding with the migration.