GCP Release Note: July 23, 2025

API Gateway

Announcement

On July 23, 2025, we released an updated version of API Gateway.

Deprecated

Deprecation of Transport Layer Security (TLS) v1.0 and v1.1 protocols

API Gateway now enforces TLS v1.2+. You can opt out of enforcing TLS v1.2+ for your API Gateway’s new security settings by reaching out to Google Cloud Support to continue using your current protocol.

AlloyDB Omni

Announcement

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

• AlloyDB Omni supports PostgreSQL version
  16.8.
• AlloyDB Omni supports the
  pg_squeeze extension
  that addresses table bloat and improves data locality.
• You can set up the columnar engine storage cache on dedicated devices. For
  more information, see
  Configure the columnar engine in AlloyDB Omni.
• Improved I/O acceleration
  due to bug fixes in libaio.
• Active Directory authentication integration is generally available (GA), providing robust user authentication for your database clusters. For more information, see Integrate Active Directory with AlloyDB Omni.
• Active Directory group-based authorization is available in Preview, enabling granular permission management based on your Active Directory groups. For more information, see Integrate Active Directory group support with AlloyDB Omni.

Announcement

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

• AlloyDB Omni supports PostgreSQL version
  15.12.
• AlloyDB Omni supports the
  pg_squeeze extension
  that addresses table bloat and improves data locality.
• You can set up the columnar engine storage cache on dedicated devices. For
  more information, see
  Configure the columnar engine in AlloyDB Omni.

Announcement

The AlloyDB Omni Kubernetes operator version 1.5.0 is generally available (GA) and includes the following features and bug fixes:

• You can install the operator using the Operator Lifecycle Manager (OLM) for Kubernetes and OpenShift environments. See “Install the AlloyDB Omni operator” for AlloyDB Omni 15.12.0 and 16.8.0 for details.

• Low downtime, minor version upgrades for a database cluster in a high availability setup are available in Preview. For more information, see “Perform a minor database version upgrade for AlloyDB Omni on Kubernetes” in the documentation for AlloyDB Omni 15.12.0 and 16.8.0.

• Active Directory authentication integration on your Kubernetes-based AlloyDB Omni database cluster is generally available (GA). For more information, see Integrate Active Directory with AlloyDB Omni on Kubernetes.

• Active Directory group-based authorization on your Kubernetes-based AlloyDB Omni database cluster is available in Preview. For more information, see Integrate Active Directory group support on Kubernetes.

• You can configure backups to be taken directly from a standby Kubernetes cluster in a high availability (HA) setup to offload backup operations from your primary instance. See “Backup and restore in Kubernetes” for AlloyDB Omni 15.12.0 and 16.8.0 for details.

• The operator fully automatically replicates replication slots for cross-data-center replication to work with primary database clusters that have high availability (HA) enabled. You still need to make sure you have reliable and low latency network connectivity between the primary and secondary data centers, which is crucial for cross-data-center replication to function effectively. For more information, see “Work with cross-data-center replication” for AlloyDB Omni 15.12.0 and 16.8.0.

• AlloyDB Omni Kubernetes images are now built on Red Hat’s Universal Base Image (UBI) 9. For more information, see “Install AlloyDB Omni on Kubernetes” for AlloyDB Omni 15.12.0 and 16.8.0.

• AlloyDB AI requires AlloyDB Omni version 15.5.5 or later.

Issue

When upgrading your AlloyDB Omni database clusters, be aware of specific upgrade paths and prerequisites depending on your current controlPlaneAgentsVersion and environment:

• If your database cluster’s controlPlaneAgentsVersion is 1.0.0, you must first upgrade to 1.1.1 before you upgrade to 1.5.0 or higher. You can directly upgrade database clusters with controlPlaneAgentsVersion 1.1.0 or later to 1.5.0.

• If you use an OpenShift database cluster that runs controlPlaneAgentsVersion 1.4.1 or earlier, you must run prerequisite steps before updating to 1.5.0. For more information, see “Update OpenShift database clusters from version 1.4.1 or earlier” for AlloyDB Omni 15.12.0 and 16.8.0.

AlloyDB for PostgreSQL

Announcement

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

• AlloyDB Omni supports PostgreSQL version
  16.8.
• AlloyDB Omni supports the
  pg_squeeze extension
  that addresses table bloat and improves data locality.
• You can set up the columnar engine storage cache on dedicated devices. For
  more information, see
  Configure the columnar engine in AlloyDB Omni.
• Improved I/O acceleration
  due to bug fixes in libaio.
• Active Directory authentication integration is generally available (GA), providing robust user authentication for your database clusters. For more information, see Integrate Active Directory with AlloyDB Omni.
• Active Directory group-based authorization is available in Preview, enabling granular permission management based on your Active Directory groups. For more information, see Integrate Active Directory group support with AlloyDB Omni.

Announcement

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

• AlloyDB Omni supports PostgreSQL version
  15.12.
• AlloyDB Omni supports the
  pg_squeeze extension
  that addresses table bloat and improves data locality.
• You can set up the columnar engine storage cache on dedicated devices. For
  more information, see
  Configure the columnar engine in AlloyDB Omni.

Announcement

The AlloyDB Omni Kubernetes operator version 1.5.0 is generally available (GA) and includes the following features and bug fixes:

• You can install the operator using the Operator Lifecycle Manager (OLM) for Kubernetes and OpenShift environments. See “Install the AlloyDB Omni operator” for AlloyDB Omni 15.12.0 and 16.8.0 for details.

• Low downtime, minor version upgrades for a database cluster in a high availability setup are available in Preview. For more information, see “Perform a minor database version upgrade for AlloyDB Omni on Kubernetes” in the documentation for AlloyDB Omni 15.12.0 and 16.8.0.

• Active Directory authentication integration on your Kubernetes-based AlloyDB Omni database cluster is generally available (GA). For more information, see Integrate Active Directory with AlloyDB Omni on Kubernetes.

• Active Directory group-based authorization on your Kubernetes-based AlloyDB Omni database cluster is available in Preview. For more information, see Integrate Active Directory group support on Kubernetes.

• You can configure backups to be taken directly from a standby Kubernetes cluster in a high availability (HA) setup to offload backup operations from your primary instance. See “Backup and restore in Kubernetes” for AlloyDB Omni 15.12.0 and 16.8.0 for details.

• The operator fully automatically replicates replication slots for cross-data-center replication to work with primary database clusters that have high availability (HA) enabled. You still need to make sure you have reliable and low latency network connectivity between the primary and secondary data centers, which is crucial for cross-data-center replication to function effectively. For more information, see “Work with cross-data-center replication” for AlloyDB Omni 15.12.0 and 16.8.0.

• AlloyDB Omni Kubernetes images are now built on Red Hat’s Universal Base Image (UBI) 9. For more information, see “Install AlloyDB Omni on Kubernetes” for AlloyDB Omni 15.12.0 and 16.8.0.

• AlloyDB AI requires AlloyDB Omni version 15.5.5 or later.

Issue

When upgrading your AlloyDB Omni database clusters, be aware of specific upgrade paths and prerequisites depending on your current controlPlaneAgentsVersion and environment:

• If your database cluster’s controlPlaneAgentsVersion is 1.0.0, you must first upgrade to 1.1.1 before you upgrade to 1.5.0 or higher. You can directly upgrade database clusters with controlPlaneAgentsVersion 1.1.0 or later to 1.5.0.

• If you use an OpenShift database cluster that runs controlPlaneAgentsVersion 1.4.1 or earlier, you must run prerequisite steps before updating to 1.5.0. For more information, see “Update OpenShift database clusters from version 1.4.1 or earlier” for AlloyDB Omni 15.12.0 and 16.8.0.

Cloud Composer

Announcement

If your environment uses dag-factory package version 0.22, then you might
experience DAG failures in Cloud Composer versions that have
apache-airflow-providers-cncf-kubernetes package version 10.4.2 or later. At
the same time, upgrading the dag-factory package to version 0.23 might require
you to update your DAG code to make it compatible.

If your environment uses dag-factory version 0.22, we recommend to do the
following:

• Temporarily postpone upgrading your environment until you’re ready to switch
  to dag-factory version 0.23. Last versions of Cloud Composer that support
  version 0.22 are composer-3-airflow-2.10.5-build.3,
  composer-3-airflow-2.9.3-build.23, composer-2.13.1-airflow-2.10.5, and
  composer-2.13.1-airflow-2.9.3 released on May 14, 2025.
• When you are ready to upgrade, update your DAGs for compatibility with 0.23.
  We recommend to do this in a development environment first.
  Install
  dag-factory version 0.23, then check that your DAGs are parsed and are
  working correctly, and update them if needed. After your DAGs are
  compatible, install dag-factory version 0.23 in your production
  environment and transfer the updated DAGs. Your environment can now be
  upgraded to a later version of Cloud Composer or Airflow.
• If your environment is already upgraded to a later version of Cloud Composer
  and you experience problems, then update dag-factory to version 0.23 and
  update your DAGs for compatibility with 0.23.

Cloud Data Fusion

Fixed

The Cloud Data Fusion version 6.10.1.5 patch revision is generally available (GA). 6.10.1.5 includes reliability fixes.

Compute Engine

Changed

When a regional Persistent Disk volume is fully replicated, Compute Engine now refreshes its replica recovery checkpoint every 15 minutes.

Learn more about Regional Persistent Disk replica recovery checkpoints and how to use checkpoints to recover a degraded disk.

Generative AI on Vertex AI

Changed

Grounding with Google Maps is available in all regions (except for the EEA) as a Preview (Pre-GA) feature.

Google Cloud Armor

Feature

Cloud Armor supports internal service security policies for the service mesh to enforce global server-side rate limiting per client in Preview.

Google SecOps Marketplace

Feature

Siemplify: Version 94.0

• The following new actions have been added:

  • Get Custom Field Values

  • Resume Case SLA

  • Pause Case SLA

Changed

Sophos: Version 18.0

Added ability to work with new authentication method in the following action:

• Get Events Log

Source: Google Cloud Platform