Kubernetes upgrade overview

Select a documentation version:

This page describes options and use cases for upgrading the AlloyDB Omni Kubernetes operator and the AlloyDB Omni database on Kubernetes. Keeping your AlloyDB Omni installation up to date is essential for security, stability, and access to new features.

The upgrade process involves the following components:

  • The AlloyDB Omni Kubernetes operator
  • The database cluster

Upgrade options

Depending on your needs and environment, you have the following upgrade options:

Upgrade type Description When to use it
Operator upgrade Upgrade the version of the AlloyDB Omni Kubernetes operator, for example, from 1.4.0 to 1.5.0. You must upgrade your AlloyDB Omni Kubernetes operator before you can perform database version upgrades. You also must upgrade your operator to get the latest features and fixes for the AlloyDB Omni Kubernetes operator.
Minor database version upgrade Upgrade your database to a newer minor version, for example, from PostgreSQL 15.7.1 to 15.12.0. These upgrades include bug fixes, security patches, and performance improvements. The minor database upgrade is part of regular maintenance that keeps your database clusters healthy and secure. For high availability (HA) clusters, this process is designed to be low-downtime.
Major database version upgrade Upgrade your database to a new major version, for example, from PostgreSQL 15 to 16. You perform a major version upgrade to take advantage of significant new features and capabilities introduced in the new database version. The major database version upgrade requires careful planning.