AlloyDB Omni release notes

Stay organized with collections Save and categorize content based on your preferences.

The AlloyDB Omni Kubernetes operator version 1.3.0 is generally available (GA). Version 1.3.0 includes the following new features and changes:

• The Kubernetes operator 1.3.0 supports connection pooling (Preview).

• You can put the database in maintenance mode to make a maintenance update or repair a pod.

• You can create replication slots and users for logical replication via the Operator API from your database instance to subscribed applications.

• This release of the Kubernetes operator adds support for kube-state-metrics so that you can use Prometheus or a Prometheus-compatible scraper to consume and display custom resource metrics like DBCluster Backup, and DBInstance. For more information, see Monitor AlloyDB Omni Kubernetes operator custom resources.

• When you create a new database cluster, this version of the Kubernetes operator creates read-only (RO) and read-write (RW) load balancers concurrently, which reduces the time that it takes for the database cluster to be ready for connections and queries.

• Configurable log rotation has a default retention time of seven days, and each archived file is individually compressed using Gzip. For more information, see Configure AlloyDB Omni log rotation.

• Various bug fixes and performance improvements.

AlloyDB Omni version 15.7.0 is generally available (GA). Version 15.7.0 includes the following features and changes:

• AlloyDB Omni supports PostgreSQL version 15.7.

• The alloydb_scann extension—previously named postgres_scann—is generally available (GA). For more information about storing vector embeddings, creating indexes, and tuning indexes to achieve faster query performance and better recall, see Work with vectors.

• Support for Red Hat Enterprise Linux (RHEL) 8 is generally available (GA).

• The AlloyDB Omni columnar engine is available in Preview on ARM.

• Disk cache and columnar storage cache are available to improve AlloyDB Omni performance by accelerating data access for AlloyDB Omni in a container and on a Kubernetes cluster.

• Security fixes for CVE-2023-50387 and CVE-2024-7348 have been implemented.

• The AlloyDB Omni Reference documentation is available. This includes metrics, database flags, model endpoint management reference, and extensions documentation for AlloyDB Omni 15.7.0.

• AlloyDB Omni supports the pg_ivm extension, which provides incremental view maintenance for materialized views.

• Various bug fixes and performance improvements.

The AlloyDB Omni Kubernetes operator version 1.2.0 is generally available (GA). Version 1.2.0 includes the following new features:

• The healthcheckPeriodSeconds parameter lets you specify the number of seconds to wait between health checks. For more information, see Adjust automatic failover trigger settings.

• The following metrics help you monitor the performance of your database container. Each of these metrics is of type gauge. For more information, see Database container-level metrics.

  • alloydb_omni_memory_limit_byte shows the memory limit of a database container.

  • alloydb_omni_instance_postgresql_replication_state shows the state of each replica that's connected to the AlloyDB Omni primary node.

  • alloydb_omni_memory_used_byte shows the memory used by the database container in bytes.

• An issue that caused a brief interruption to all database clusters when the following is true is fixed:

  • You're upgrading the AlloyDB Omni Kubernetes operator version 1.1.1 to a newer version.

  • You're using the AlloyDB Omni database version 15.5.5 or later.

  • AlloyDB AI is not enabled.

• High availability is supported on a secondary database cluster after it's promoted. For more information, see Promote a secondary database cluster and Manage high availability in Kubernetes.

• You can enable or disable model endpoint management through Kubernetes manifests. For more information, see Install AlloyDB Omni with AlloyDB AI.

• You can configure when logs rotate using thresholds that are based on the size of the log files, the time since the log file last rotated, or both. For more information, see Configure AlloyDB Omni log rotation.

• You can create a snapshot of the memory heap of AlloyDB Omni Kubernetes operator to help you analyze and debug its memory performance. For more information, see Analyze AlloyDB Omni Kubernetes operator memory heap usage.

AlloyDB for PostgreSQL minor versions are upgraded to 15.7 and 14.12. For more information, see AlloyDB and AlloyDB Omni version policies.

AlloyDB Omni is in Limited Availability on the Aiven Platform. Aiven provides managed AlloyDB Omni as a service on multiple public clouds. For more information, see Store your data on any major cloud.