AlloyDB Omni (Container orchestrator) release notes

This page contains release notes for features and updates to AlloyDB Omni.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.

June 18, 2026

Feature

AlloyDB Omni documentation now includes documentation for the following AlloyDB AI features available in GA:

  • Auto vector embeddings automate the lifecycle of vector embeddings for large datasets, keeping them in sync with transactional data using real-time or batch updates. This feature includes a bulk mode that performs refreshes and migrations up to 130x faster than row-by-row processing."

  • AI functions integrate LLMs like Gemini to bring world knowledge to your AlloyDB data and incorporate advanced semantic search and ranking capabilities directly into your SQL workflows.

  • Use array-based AI functions to improve the efficiency of large-scale AI operations by enabling batch processing of natural language prompts in your SQL queries. For more information, see Perform intelligent SQL queries using AI functions.

Feature

AlloyDB Omni documentation now includes documentation for the following AlloyDB AI features, which are available in Preview:

  • The AlloyDB columnar engine provides a read-optimized, in-memory cache for HNSW indexes, increasing the number of queries per second (QPS) that your database can handle for vector search workloads. For more information, see Accelerate vector search with the columnar engine.
  • Hybrid search supports Elasticsearch, which lets you use the external_search_fdw extension to connect to Elasticsearch and perform hybrid searches in AlloyDB. For more information, see Access Elasticsearch data from AlloyDB.
  • The sentiment analysis and summarization functions let you process and analyze unstructured data in your database. For more information, see Analyze text sentiment and Summarize content.
  • You can defer ScaNN index creation on an empty table or a table with insufficient rows until the table has sufficient data. For more information, see Create a ScaNN index.
  • The alloydb_scann extension now supports four-level tree indexes, providing support for tables with up to 10 billion vector rows. For more information, see Four-level ScaNN tree indexes.

June 03, 2026

Announcement

The AlloyDB Omni Kubernetes operator version 1.7.1 is generally available (GA) and includes the following vulnerability fixes:

May 08, 2026

Announcement

The AlloyDB Omni Kubernetes operator (version 1.7.0) is officially certified for Red Hat OpenShift. The operator and its associated database images are validated to run optimally and securely on Red Hat OpenShift.

This release includes the following:

  • OpenShift Certified Catalog: the AlloyDB Omni Operator is now officially listed on the OpenShift Certified Catalog.
  • Built-in management: discover, install, and manage the operator using OpenShift's built-in Operator Lifecycle Manager (OLM) user interface.
  • OLM support: support for OLM bundles is available, facilitating a seamless, one-click installation experience and automated management for enterprise deployments. For more information, see Install the AlloyDB Omni operator.
  • This certification is supported by AlloyDB Omni versions starting with 16.11.0, 17.7.0, and 18.1.0.

April 22, 2026

Change

The naming conventions for AlloyDB Omni deployment options are updated to more accurately reflect their respective installation and orchestration methods.
The following table summarizes the primary name changes:

Original name New name
AlloyDB Omni for containers AlloyDB Omni using containers
AlloyDB Omni for Kubernetes AlloyDB Omni using the container orchestrator
AlloyDB Omni for Linux AlloyDB Omni using RPM
Red Hat RPM orchestrator AlloyDB Omni using the RPM orchestrator

This update clarifies the distinction between AlloyDB Omni deployment environments (such as Kubernetes or standalone Linux) and the packaging and orchestration technologies used to manage them. For more information, see Choose your deployment environment.

April 09, 2026

Announcement

The AlloyDB Omni Kubernetes operator version 1.7.0 is generally available (GA) and includes the following features and changes:

  • AlloyDB Omni supports PostgreSQL 18.1.0. For more information, see AlloyDB Omni Kubernetes operator. This operator version also supports AlloyDB Omni minor versions 15.15.0, 16.11.0, and 17.7.0.
  • Enterprise readiness for AlloyDB Omni on Google Distributed Cloud Software Only lets the operator manage the full database lifecycle, including provisioning, high availability, and disaster recovery, directly on your own physical bare metal infrastructure.
  • Database pods feature a hardened security posture with restricted Kubernetes securityContext settings enabled by default, including non-root execution and read-only root filesystems.
  • Added support for Transparent Data Encryption (TDE) (Preview), providing at-rest encryption for database clusters. This is available beginning with AlloyDB Omni 18.1.0. For more information, see Transparent Data Encryption.
  • Added support for custom configuration of database port numbers for your clusters. For more information, see Configure custom ports.
  • Introduced a framework for defining and collecting custom database metrics to enhance monitoring capabilities. For more information, see Configure custom metrics.
  • Added detailed memory allocation metrics for improved memory and performance monitoring. For more information, see AlloyDB Omni metrics.
  • Improved Active Directory integration with support for hostssl connection types, multi-domain LDAP base DNs, and customizable LDAP search attributes. For more information, see Integrate Active Directory.
  • Added support for rewind trigger functionality in symmetric disaster recovery configurations. For more information, see Work with cross-data-center replication.
  • You can perform CPU and memory scaling operations with minimal downtime using Low Downtime Maintenance (Preview). For more information, see Scale a database cluster.
  • Additional database flags are supported.
  • All current and earlier versions of Helm charts are available in the Artifact Registry. However, Helm charts are no longer available in Cloud Storage.
  • Updated manual major version upgrade instructions to use versioned data directory paths. For more information, see Upgrade database major version.
  • Updated Choose compatible Kubernetes operator and database cluster versions with latest versions.
Change

The AlloyDB Omni Kubernetes operator now automatically scales the wal_keep_size and max_wal_size database flags based on your configured storage size to optimize storage and checkpointing behavior. If you manually configure these flags, your custom values are respected and override the system-selected defaults.

Fixed

Reliability improvement for backups from standby instances: Fixed an issue in the AlloyDB Omni Kubernetes operator version 1.7.0 where backups taken from a standby instance could be incomplete if the primary instance were under heavy load. The backup process now performs a checkpoint before starting to ensure data integrity.

Upgrade required: If you use the backup from standby feature, upgrade to the latest versions of the AlloyDB Omni control plane and data plane. After you perform the upgrade, take a new backup to make sure that your data is fully protected.

Issue

Restore operations might fail if a database backup is running at the same time. If this occurs, retry the restore operation after some delay.

September 18, 2024

Feature

The AlloyDB Omni operator is now available in Preview on Google Distributed Cloud (GDC) connected. For more information, see Install AlloyDB Omni on Kubernetes.

September 16, 2024

Breaking

The postgres_ann extension has been renamed to alloydb_scann. Before you upgrade to AlloyDB Omni Kubernetes operator version 1.1.1, you must drop any indexes created using the earlier postgres_ann version, then upgrade AlloyDB Omni, and then create the indexes again using the alloydb_scann extension.

Fixed

AlloyDB Omni Kubernetes operator version 1.1.1 is now available. This patch fixes the following issues:

  • Fixed a regression for the AlloyDB Vertex AI integration.
  • Fixed a bug in which upgrading from version 1.0.0 to version 1.1.0 failed when using injected sidecars.
  • Fixed a bug in which backups weren't reestablished correctly across failovers when using the Commvault sidecar with high availability (HA) configurations.
  • Fixed a bug that caused a status to be incorrectly set by the load balancer, resulting in erroneous reports that the database cluster wasn't ready.
Feature

Added a tutorial that shows you how to set up a connection from an application running in a Google Kubernetes Engine autopilot cluster to an AlloyDB instance.

Issue

Upgrading to version 1.1.1 of the AlloyDB Omni Kubernetes operator might result in a brief interruption to all database clusters. No data loss is expected.

August 22, 2024

Feature

AlloyDB Omni now offers in-depth documentation that describes how to install and use AlloyDB Omni in virtual machine (VM) environments. The information in these documents is in addition to the AlloyDB Omni documentation that describes how to install and use AlloyDB Omni in VM and Kubernetes environments. For more information, see Get started with AlloyDB Omni on VMs.

Change

The extension temporal_tables version 1.2.2 has been added to extensions supported by AlloyDB.

The following extensions are updated:

  • Updated pg_partman to version 4.7.4.
  • Updated pgtt to version 3.0.0.

August 16, 2024

Feature

August 05, 2024

Feature

AlloyDB Omni version 15.5.5 is now generally available (GA). This version includes the following features and changes: