GCP Release Notes: September 15, 2025

Bigtable

Libraries

A weekly digest of client library updates from across the Cloud SDK.

Cloud Database Migration Service

Announcement

Gemini-powered conversion features for heterogeneous migrations in Database Migration Service are now generally available (GA).

For more information, see Accelerate code and schema conversion with Gemini.

Cloud Monitoring

Feature

When viewing a chart, you can now open a flyout that displays the chart and related log entries. To explore your metric and log data in more detail, you can then use the toolbars and menus in the flyout. To learn more, see the following:

• Correlate metric and log data
• Explore application telemetry

Google Distributed Cloud (software only) for VMware

Announcement

Google Distributed Cloud (software only) for VMware 1.31.900-gke.38 is now available for download. To upgrade, see Upgrade a cluster. Google Distributed Cloud 1.31.900-gke.38 runs on Kubernetes v1.31.12-gke.200.

If you are using a third-party storage vendor, check the GDC Ready storage partners document to make sure the storage vendor has already passed the qualification for this release.

After a release, it takes approximately 7 to 14 days for the version to become available for use with GKE On-Prem API clients: the Google Cloud console, the gcloud CLI, and Terraform.

Fixed

The following issues were fixed in 1.31.900-gke.38:

• Fixed vulnerabilities listed in Vulnerability fixes.

Google Distributed Cloud (software only) for bare metal

Announcement

Google Distributed Cloud for bare metal 1.31.900-gke.38 is now available for download. To upgrade, see Upgrade clusters. Google Distributed Cloud for bare metal 1.31.900-gke.38 runs on Kubernetes v1.31.10-gke.300.

After a release, it takes approximately 7 to 14 days for the version to become available for installations or upgrades with the GKE On-Prem API clients: the Google Cloud console, the gcloud CLI, and Terraform.

If you use a third-party storage vendor, check the Ready storage partners document to make sure the storage vendor has already passed the qualification for this release of Google Distributed Cloud for bare metal.

Fixed

The following issues were fixed in 1.31.900-gke.38:

• Fixed vulnerabilities listed in Vulnerability fixes.

Issue

For information about the latest known issues, see Google Distributed Cloud for bare metal known issues in the Troubleshooting section.

Google Distributed Cloud connected

Announcement

This is a minor release of Google Distributed Cloud connected (version 1.11.0).

Feature

The following new functionality has been introduced in this release of Google Distributed Cloud connected:

• Backup for VM workloads on GDC connected servers. You can now backup and restore virtual machine workloads on your Google Distributed Cloud connected servers deployment, including scheduling. For more information, see Back up a virtual machine.

• Configurable runtime class for container workloads. As part of gVisor integration in Google Distributed Cloud connected, you can now specify the default runtime class for container workloads at both Pod and cluster level. Cluster-level runtime class selection is a preview-level feature. For more information, see Configure the runtime class for a Pod.

• Island mode networking. Google Distributed Cloud connected now supports island mode networking on secondary network interfaces. For more information, see (Optional) Configure island mode.

• AppArmor sandboxing audit logs for VM workloads. Google Distributed Cloud connected now lets you enable audit logs for virtual machine workloads sandboxed using AppArmor policies. To enable audit log emission on an existing virtual machine workload, restart the corresponding virtual machine. For more information, see View AppArmor sandboxing audit logs.

• CoreDNS resolution for secondary networks. Google Distributed Cloud connected now supports specifying a CIDR block for use with secondary networks at both Pod and cluster level. This allows for CoreDNS resolution on secondary network interfaces. For more information, see Network resource.

• Access clusters through Connect Gateway. You can now access your Google Distributed Cloud connected clusters through Connect Gateway. For more information, see Obtain cluster credentials through Connect Gateway.

• VNC support for accessing VM workloads through Connect Gateway. You can now use VNC to access your virtual machine workloads through Connect Gateway.

Security

Security mitigations for the following vulnerabilities have been implemented in this release of Google Distributed Cloud connected:

• OS layer security mitigations: CVE-2025-31498, CVE-2024-48615, CVE-2016-1585.

• GDC software-only security mitigations: All mitigations listed in the GDC software-only release notes up to version 1.32.100 (inclusive).

Libraries

The following Google Distributed Cloud connected components have been updated:

• GDC software-only has been updated to version 1.32.100. (This component was formerly known as GKE on Bare Metal and as Anthos Clusters on Bare Metal.)

• Kubernetes has been updated to version 1.32.4-gke.200.

Fixed

The following issues have been resolved in this release of Google Distributed Cloud connected:

• Machines no longer experience intermittent connectivity loss. Google Distributed Cloud connected machines no longer experience intermittent connectivity loss; the underlying rare condition that can occur with fleet credential management has been resolved.

• VNC sessions through Connect Gateway are now more resilient. The stability of VNC sessions to virtual machine workloads through Connect Gateway has been improved.

Issue

This release of Google Distributed Cloud connected contains the following known issues:

• The gvisor runtime class is incompatible with Symcloud Storage persistent volumes in block mode. If you set a workload that uses Symcloud Storage persistent volumes in block mode to use the gvisor runtime class, the workload fails. Symcloud Storage persistent volumes in filesystem mode are not affected.

• Cilium does not differentiate between TCP and UDP protocols. Cilium does not differentiate between TCP and UDP protocols for services that use both protocols on the same port number and routes traffic for both protocols to the same backend pods. This can render such services non-functional. To work around this issue, use a different port for each protocol.

• Overlapping the Pod and cluster CIDR blocks for secondary networks causes network failure. If you specify overlapping CIDR blocks for Pods and clusters using the annotations.networking.gke.io/gdce-pod-cidr and annotations.networking.gke.io/gke-gateway-clusterip-cidr annotations in the Network resource, the Google Distributed Cloud connected virtual networking subsystem might behave erratically, including loss of connectivity. Follow the guidelines in (Optional) Configure island mode to prevent this issue.

• The anthos-multinet container might take up to two hours to fully start. You might intermittently experience a slower than normal startup for the anthos-multinet container (up to two hours). To remedy this issue, contact Google Support.

Service Extensions

Feature

To protect AI workloads, you can configure traffic extensions to call the Model Armor service on supported Application Load Balancers. This feature is in General Availability.

Source: Google Cloud Platform