Alauda support for PostgreSQL

Upgrade

NOTE

This document provides the upgrade path principles and supported version compatibility for Alauda Support for PostgreSQL.

WARNING

New PostgreSQL 11/12 instances will no longer be supported and will be completely removed from future versions. Please upgrade to a higher version of PostgreSOL as soon as possible.

TOC

Compatibility Matrix

The table below lists supported versions of the Alauda Support for PostgreSQL and its key components:

Alauda PostgreSQL package versionPostgreSQL server versionKubernetes version
v4.1.x14, 161.25+
v4.0.x11, 12, 141.25+

Please refer to Release Notes for version-specific changes, new features and deprecations information.

Prerequisites

Before initiating an upgrade, please ensure the following:

  1. Version Compatibility: The current server version can be supported by the upgrade target version of the operator.
  2. Component Health: PostgreSQL instances are in a Ready state.
  3. Resource Availability: The cluster has sufficient resources to support the upgrade process.

Upgrade Path Guidelines

Consecutive Minor Upgrade

  • Description: Upgrade version-by-version through consecutive minor versions.
  • Example: 4.1.x → 4.2.x → 4.3.x

Patch-Level Upgrade

  • Description: Any upgrade between patch versions of the same minor version are supported.
  • Example: 4.1.3 → 4.1.7

PostgreSQL Version Alignment

  • Description: Ensure PostgreSQL server version upgrades follow the operator's compatibility matrix.
  • Example: Manually upgrade PostgreSQL server version to v14 (v16 work too) before upgrade Alauda Support for PostgreSQL to v4.1.0.
NOTE

If your current PostgreSQL server version is being removed in the next Alauda PostgreSQL package version, you must manually upgrade your PostgreSQL server version to a supported one before upgrading to the next Alauda PostgreSQL package version. This ensures compatibility and prevents upgrade failures.

Upgrade Strategy

Alauda Support for PostgreSQL will execute upgrades based on the configured upgrade strategy:

  • Automatic : Auto-upgrades are triggered immediately upon detecting new component versions.
  • Manual : Requires manual approval before initiating the upgrade process.