The following release notes cover the most recent changes over the last 60 days. For a comprehensive list of product-specific release notes, see the individual product release note pages.
You can also see and filter all release notes in the Google Cloud console or you can 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.
May 30, 2025
Apigee XOn May 30, 2025 we released an updated version of Apigee.
Announcing the general availability of Gemini Code Assist API development features in Apigee
With this functionality, you can accelerate your API development lifecycle within VS Code using Gemini Code Assist in Apigee. This feature allows you to use natural language prompts to design, create, iterate, and manage OpenAPI specifications with the following capabilities:
- AI-Powered API Design: Generate high-quality OpenAPI specifications from natural language prompts to the Apigee tool in Gemini Code Assist Chat, leveraging the Gemini model and the enterprise context of your API hub.
- Effortless Iteration: Refine existing or newly generated specifications using the intuitive Gemini chat interface.
- Integrated Testing: Quickly validate your APIs by deploying them to a local or Google Cloud-hosted mock server.
- Streamlined Workflow: Publish your completed API specifications directly to Apigee API hub and kick-start proxy development by creating Apigee proxy bundles from your API specifications.
- Duplicate Endpoint Detection: Proactively identify and prevent the creation of duplicate API endpoints already registered in your API hub.
For more information and usage instructions, see Designing and editing APIs, Tutorial: Use Gemini Code Assist to design, develop, and test APIs in Apigee, and Setting up Apigee API Management in Cloud Code for VS Code.
New Dataproc Serverless for Spark runtime versions:
- 1.1.106
- 1.2.50
- 2.2.50
- 2.3.1
The support dates for Dataproc on Compute Engine image versions 2.0
, 2.1
, and 2.2
have been extended, as follows:
- Image version
2.2
: Supported until 03/31/2027 - Image version
2.1
: Supported until 03/31/2026 - Image version
2.0
Supported until 09/30/2025
(2025-R22) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- Version 1.33.0-gke.2248000 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.12-gke.1086000
- 1.31.9-gke.1005000
- 1.33.0-gke.1868000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.12-gke.1151000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.12-gke.1151000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.33 to version 1.33.0-gke.2248000 with this release.
Regular channel
- Version 1.32.4-gke.1106006 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.11-gke.1217000
- 1.31.7-gke.1390000
- 1.32.3-gke.1927009
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.8-gke.1045000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.32.4-gke.1106006 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.8-gke.1045000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.4-gke.1106006 with this release.
Stable channel
- The following versions are now available in the Stable channel:
- The following versions are no longer available in the Stable channel:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
Extended channel
- Version 1.32.4-gke.1106006 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2703000
- 1.27.16-gke.2810000
- 1.28.15-gke.2169000
- 1.28.15-gke.2287000
- 1.29.15-gke.1240000
- 1.29.15-gke.1395000
- 1.30.11-gke.1217000
- 1.31.7-gke.1390000
- 1.32.3-gke.1927009
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2192000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2732000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2192000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.15-gke.1274000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.8-gke.1045000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.4-gke.1106006 with this release.
No channel
- Version 1.32.4-gke.1106006 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.31.9-gke.1005000
- 1.32.3-gke.1785003
- 1.32.4-gke.1106000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.4-gke.1106006 with this release.
The insecure kubelet read-only port (10255
) is disabled by default in all new clusters that run GKE version 1.32 and later. If you created your cluster using a GKE version earlier than 1.32, we recommend that you disable the insecure kubelet read-only port. For more information see Disable the kubelet read-only port in GKE clusters.
(2025-R21) Version updates
There are no version updates for 2025-R21.
(2025-R22) Version updates
- The following versions are now available in the Stable channel:
- The following versions are no longer available in the Stable channel:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
(2025-R22) Version updates
- Version 1.32.4-gke.1106006 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2703000
- 1.27.16-gke.2810000
- 1.28.15-gke.2169000
- 1.28.15-gke.2287000
- 1.29.15-gke.1240000
- 1.29.15-gke.1395000
- 1.30.11-gke.1217000
- 1.31.7-gke.1390000
- 1.32.3-gke.1927009
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2192000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2732000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2192000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.15-gke.1274000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.8-gke.1045000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.4-gke.1106006 with this release.
GKE now provides insights and recommendations that help you to identify and remediate clusters where the etcd cluster state database size is approaching the limit. Implementing the recommendation helps you to keep your clusters stable and performant.
May 29, 2025
AI ApplicationsVertex AI Search: Adjust autocomplete settings to reduce risk of PII leaks (Public preview)
If you use either the search history or user events model for autocomplete suggestions and you have concerns about your users entering their personally identifiable information (PII) as search queries, then see Reduce the risk of returning suggestions that contain PII.
This feature is in Public preview.
You can now start, stop, and restart your primary and read pool AlloyDB instances using the Google Cloud console and the Google Cloud CLI. This feature is generally available (GA).
On May 29, 2025 we released a new version of the Apigee integrated portal.
GA: Apigee Integrated Developer Portal Admin UI in the Google Cloud console.
This release adds the Apigee Integrated Developer Portal Admin UI from the Classic Apigee UI into the Google Cloud console.
Leveraging Google Cloud console components provides API providers and Portal Admins with a centralized platform to efficiently configure, publish, and manage your API consumer portals, eliminating the need to switch between different UIs.
No new APIs have been introduced in this release.
See Publishing overview to get started.
On May 29, 2025 we announced the shutdown schedule for the Apigee Classic UI.
The Apigee Classic UI will be shutdown as of August 29, 2025.
This is the final phase of moving Apigee to the Google Cloud console. Apigee in the Google Cloud console gives you the ability to manage all of your Apigee functionality in one place.
To prepare for the shutdown of the Apigee Classic UI, familiarize yourself with the new Apigee UI in Google Cloud console by reviewing UI overview.
See Apigee Classic UI shutdown for details on shutdown dates and exception request.
On May 29, 2025, we released an updated version of Apigee.
Public Preview: Apigee Extension Processor support for request and response body processing
When creating a load balancer service extension, you can customize the behavior of the extension processor proxy to support request body processing, response body processing, or a combination of the two.
For more information, see Get started with the Apigee Extension Processor.
You can now use the dbt-bigquery
adapter to run Python code that's defined in BigQuery DataFrames. For more information, see Use BigQuery DataFrames in dbt. This feature is in preview.
You can now use your Google Account user credentials to authorize the creation, scheduling, and running of pipelines as well as the scheduling of notebooks and data preparations. For more information, see Create a pipeline schedule. This feature is in preview.
You can now create event-driven transfers when transferring data from Cloud Storage to BigQuery. Event-driven transfers can automatically trigger transfer runs when data in your Cloud Storage bucket has been modified or added. This feature is generally available (GA).
The Bigtable Spark connector supports Scala versions 2.12 and 2.13 in all connector versions and has been updated as follows:
- Connector versions 0.5.0 and later support dynamic columns.
- Connector versions 0.6.0 and later support custom authentication providers and efficient joins with data sources.
You can now configure the observability scope or set the default log scope by using the Google Cloud CLI. You must use version 254.0 or higher. For more information, see Configure observability scopes and Set the default log scope.
Conversational Insights offers a merged analysis, which displays the previous results of each analysis type alongside your most recent analysis result. Merged analysis eliminates the need to run every analysis multiple times.
Public preview: Google Managed Service for Apache Kafka now offers schema registry support. For more information about the feature, see the schema registry overview or get started with an Avro producer in Java.
Google SecOps has updated the list of supported default parsers. Parsers are updated gradually, so it might take one to four days before you see the changes reflected in your region.
The following supported default parsers have changed. Each parser is listed by product name and log_type
value, if applicable. This list now includes both released default parsers and pending parser updates.
- AIX system (
AIX_SYSTEM
) - Akamai WAF (
AKAMAI_WAF
) - Apache (
APACHE
) - Appian Cloud (
APPIAN_CLOUD
) - Auth0 (
AUTH_ZERO
) - AWS CloudFront (
AWS_CLOUDFRONT
) - AWS Cloudtrail (
AWS_CLOUDTRAIL
) - AWS GuardDuty (
GUARDDUTY
) - AWS Macie (
AWS_MACIE
) - AWS Session Manager (
AWS_SESSION_MANAGER
) - AWS VPC Flow (
AWS_VPC_FLOW
) - AWS VPC Flow (CSV) (
AWS_VPC_FLOW_CSV
) - Azure AD (
AZURE_AD
) - Azure AD Organizational Context (
AZURE_AD_CONTEXT
) - Azure Firewall (
AZURE_FIREWALL
) - Azure Storage Audit (
AZURE_STORAGE_AUDIT
) - Barracuda Firewall (
BARRACUDA_FIREWALL
) - BeyondTrust BeyondInsight (
BEYONDTRUST_BEYONDINSIGHT
) - BIND (
BIND_DNS
) - Bitdefender (
BITDEFENDER
) - Blue Coat Proxy (
BLUECOAT_WEBPROXY
) - Brocade Switch (
BROCADE_SWITCH
) - Carbon Black (
CB_EDR
) - CircleCI (
CIRCLECI
) - Cisco ASA (
CISCO_ASA_FIREWALL
) - Cisco Firepower NGFW (
CISCO_FIREPOWER_FIREWALL
) - Cisco Internetwork Operating System (
CISCO_IOS
) - Cisco ISE (
CISCO_ISE
) - Cisco NX-OS (
CISCO_NX_OS
) - Cisco Prime (
CISCO_PRIME
) - Cisco Switch (
CISCO_SWITCH
) - Cisco Unity Connection (
CISCO_UNITY_CONNECTION
) - Cloud Audit Logs (
N/A
) - CrowdStrike Alerts API (
CS_ALERTS
) - CrowdStrike Falcon (
CS_EDR
) - CyberArk Endpoint Privilege Manager (EPM) (
CYBERARK_EPM
) - CyberArk Privileged Access Manager (PAM) (
CYBERARK_PAM
) - Cylance Protect (
CYLANCE_PROTECT
) - Darktrace (
DARKTRACE
) - Dell OpenManage (
DELL_OPENMANAGE
) - EfficientIP DDI (
EFFICIENTIP_DDI
) - Elastic Defend (
ELASTIC_DEFEND
) - Elastic Windows Event Log Beats (
ELASTIC_WINLOGBEAT
) - ExtraHop RevealX (
EXTRAHOP
) - F5 ASM (
F5_ASM
) - F5 BIGIP LTM (
F5_BIGIP_LTM
) - F5 DNS (
F5_DNS
) - Fastly WAF (
FASTLY_WAF
) - FireEye HX (
FIREEYE_HX
) - FortiGate (
FORTINET_FIREWALL
) - Fortinet FortiAnalyzer (
FORTINET_FORTIANALYZER
) - Fortinet FortiAuthenticator (
FORTINET_FORTIAUTHENTICATOR
) - Fortinet FortiNAC (
FORTINET_FORTINAC
) - Fortinet Web Application Firewall (
FORTINET_FORTIWEB
) - GitHub (
GITHUB
) - Gitlab (
GITLAB
) - HP Aruba (ClearPass) (
CLEARPASS
) - Ipswitch SFTP (
IPSWITCH_SFTP
) - Juniper (
JUNIPER_FIREWALL
) - Linux Auditing System (AuditD) (
AUDITD
) - ManageEngine ADManager Plus (
ADMANAGER_PLUS
) - McAfee ePolicy Orchestrator (
MCAFEE_EPO
) - Microsoft AD FS (
ADFS
) - Microsoft Defender for Endpoint (
MICROSOFT_DEFENDER_ENDPOINT
) - Microsoft Defender for Identity (
MICROSOFT_DEFENDER_IDENTITY
) - Microsoft IIS (
IIS
) - Microsoft PowerShell (
POWERSHELL
) - Netskope Web Proxy (
NETSKOPE_WEBPROXY
) - Nokia Router (
NOKIA_ROUTER
) - Office 365 (
OFFICE_365
) - Oracle (
ORACLE_DB
) - Palo Alto Cortex XDR Events (
PAN_CORTEX_XDR_EVENTS
) - Palo Alto Prisma Access (
PAN_CASB
) - Ping Federate (
PING_FEDERATE
) - Ping Identity (
PING
) - Proofpoint Tap Alerts (
PROOFPOINT_MAIL
) - Radware Web Application Firewall (
RADWARE_FIREWALL
) - ServiceNow Audit (
SERVICENOW_AUDIT
) - Snare System Diagnostic Logs (
SNARE_SOLUTIONS
) - Symantec DLP (
SYMANTEC_DLP
) - Symantec Security Analytics (
SYMANTEC_SA
) - Sysdig (
SYSDIG
) - Tanium Question (
TANIUM_QUESTION
) - Trend Micro Vision One (
TRENDMICRO_VISION_ONE
) - Trend Micro Vision One Workbench (
TRENDMICRO_VISION_ONE_WORKBENCH
) - TrendMicro Deep Discovery Inspector (
TRENDMICRO_DDI
) - VanDyke SFTP (
VANDYKE_SFTP
) - Vectra Detect (
VECTRA_DETECT
) - Vectra Stream (
VECTRA_STREAM
) - Vectra XDR (
VECTRA_XDR
) - VMware ESXi (
VMWARE_ESX
) - VMWare VSphere (
VMWARE_VSPHERE
) - WatchGuard (
WATCHGUARD
) - Windows Event (XML) (
WINEVTLOG_XML
) - Workspace Activities (
WORKSPACE_ACTIVITY
) - Zscaler (
ZSCALER_WEBPROXY
) - Zscaler CASB (
ZSCALER_CASB
) - Zscaler DLP (
ZSCALER_DLP
) - ZScaler DNS (
ZSCALER_DNS
) - Zscaler Internet Access Audit Logs (
ZSCALER_INTERNET_ACCESS
) - ZScaler NGFW (
ZSCALER_FIREWALL
) - Zscaler Private Access (
ZSCALER_ZPA
) - Zscaler Secure Private Access Audit Logs (
ZSCALER_ZPA_AUDIT
) - Zscaler Tunnel (
ZSCALER_TUNNEL
)
The following log types were added without a default parser. Each parser is listed by product name and log_type
value, if applicable.
- Azure App Configuration (
AZURE_APPCONFIGURATION
) - Azure App Platform (
AZURE_APPPLATFORM
) - Azure ArcData (
AZURE_ARCDATA
) - Azure Authorization (
AZURE_AUTHORIZATION
) - Azure Change Analysis (
AZURE_CHANGEANALYSIS
) - Azure DataFactory (
AZURE_DATAFACTORY
) - Doppel (
DOPPEL
) - Genian NAC (
GENIAN_NAC
) - Penta Security Wapples (
PENTA_WAPPLES
) - Redmine (
REDMINE
) - S2W Quaxar (
S2W_QUAXAR
) - SecurityBridge Dev (
SECURITYBRIDGE_DEV
) - TeamT5 ThreatSonar EDR (
TEAMT5_THREATSONAR_EDR
) - WorkDay User Sign In (
WORKDAY_USER_SIGNIN
)
For a list of supported log types and details about default parser changes, see Supported log types and default parsers.
Google SecOps has updated the list of supported default parsers. Parsers are updated gradually, so it might take one to four days before you see the changes reflected in your region.
The following supported default parsers have changed. Each parser is listed by product name and log_type
value, if applicable. This list now includes both released default parsers and pending parser updates.
- AIX system (
AIX_SYSTEM
) - Akamai WAF (
AKAMAI_WAF
) - Apache (
APACHE
) - Appian Cloud (
APPIAN_CLOUD
) - Auth0 (
AUTH_ZERO
) - AWS CloudFront (
AWS_CLOUDFRONT
) - AWS Cloudtrail (
AWS_CLOUDTRAIL
) - AWS GuardDuty (
GUARDDUTY
) - AWS Macie (
AWS_MACIE
) - AWS Session Manager (
AWS_SESSION_MANAGER
) - AWS VPC Flow (
AWS_VPC_FLOW
) - AWS VPC Flow (CSV) (
AWS_VPC_FLOW_CSV
) - Azure AD (
AZURE_AD
) - Azure AD Organizational Context (
AZURE_AD_CONTEXT
) - Azure Firewall (
AZURE_FIREWALL
) - Azure Storage Audit (
AZURE_STORAGE_AUDIT
) - Barracuda Firewall (
BARRACUDA_FIREWALL
) - BeyondTrust BeyondInsight (
BEYONDTRUST_BEYONDINSIGHT
) - BIND (
BIND_DNS
) - Bitdefender (
BITDEFENDER
) - Blue Coat Proxy (
BLUECOAT_WEBPROXY
) - Brocade Switch (
BROCADE_SWITCH
) - Carbon Black (
CB_EDR
) - CircleCI (
CIRCLECI
) - Cisco ASA (
CISCO_ASA_FIREWALL
) - Cisco Firepower NGFW (
CISCO_FIREPOWER_FIREWALL
) - Cisco Internetwork Operating System (
CISCO_IOS
) - Cisco ISE (
CISCO_ISE
) - Cisco NX-OS (
CISCO_NX_OS
) - Cisco Prime (
CISCO_PRIME
) - Cisco Switch (
CISCO_SWITCH
) - Cisco Unity Connection (
CISCO_UNITY_CONNECTION
) - Cloud Audit Logs (
N/A
) - CrowdStrike Alerts API (
CS_ALERTS
) - CrowdStrike Falcon (
CS_EDR
) - CyberArk Endpoint Privilege Manager (EPM) (
CYBERARK_EPM
) - CyberArk Privileged Access Manager (PAM) (
CYBERARK_PAM
) - Cylance Protect (
CYLANCE_PROTECT
) - Darktrace (
DARKTRACE
) - Dell OpenManage (
DELL_OPENMANAGE
) - EfficientIP DDI (
EFFICIENTIP_DDI
) - Elastic Defend (
ELASTIC_DEFEND
) - Elastic Windows Event Log Beats (
ELASTIC_WINLOGBEAT
) - ExtraHop RevealX (
EXTRAHOP
) - F5 ASM (
F5_ASM
) - F5 BIGIP LTM (
F5_BIGIP_LTM
) - F5 DNS (
F5_DNS
) - Fastly WAF (
FASTLY_WAF
) - FireEye HX (
FIREEYE_HX
) - FortiGate (
FORTINET_FIREWALL
) - Fortinet FortiAnalyzer (
FORTINET_FORTIANALYZER
) - Fortinet FortiAuthenticator (
FORTINET_FORTIAUTHENTICATOR
) - Fortinet FortiNAC (
FORTINET_FORTINAC
) - Fortinet Web Application Firewall (
FORTINET_FORTIWEB
) - GitHub (
GITHUB
) - Gitlab (
GITLAB
) - HP Aruba (ClearPass) (
CLEARPASS
) - Ipswitch SFTP (
IPSWITCH_SFTP
) - Juniper (
JUNIPER_FIREWALL
) - Linux Auditing System (AuditD) (
AUDITD
) - ManageEngine ADManager Plus (
ADMANAGER_PLUS
) - McAfee ePolicy Orchestrator (
MCAFEE_EPO
) - Microsoft AD FS (
ADFS
) - Microsoft Defender for Endpoint (
MICROSOFT_DEFENDER_ENDPOINT
) - Microsoft Defender for Identity (
MICROSOFT_DEFENDER_IDENTITY
) - Microsoft IIS (
IIS
) - Microsoft PowerShell (
POWERSHELL
) - Netskope Web Proxy (
NETSKOPE_WEBPROXY
) - Nokia Router (
NOKIA_ROUTER
) - Office 365 (
OFFICE_365
) - Oracle (
ORACLE_DB
) - Palo Alto Cortex XDR Events (
PAN_CORTEX_XDR_EVENTS
) - Palo Alto Prisma Access (
PAN_CASB
) - Ping Federate (
PING_FEDERATE
) - Ping Identity (
PING
) - Proofpoint Tap Alerts (
PROOFPOINT_MAIL
) - Radware Web Application Firewall (
RADWARE_FIREWALL
) - ServiceNow Audit (
SERVICENOW_AUDIT
) - Snare System Diagnostic Logs (
SNARE_SOLUTIONS
) - Symantec DLP (
SYMANTEC_DLP
) - Symantec Security Analytics (
SYMANTEC_SA
) - Sysdig (
SYSDIG
) - Tanium Question (
TANIUM_QUESTION
) - Trend Micro Vision One (
TRENDMICRO_VISION_ONE
) - Trend Micro Vision One Workbench (
TRENDMICRO_VISION_ONE_WORKBENCH
) - TrendMicro Deep Discovery Inspector (
TRENDMICRO_DDI
) - VanDyke SFTP (
VANDYKE_SFTP
) - Vectra Detect (
VECTRA_DETECT
) - Vectra Stream (
VECTRA_STREAM
) - Vectra XDR (
VECTRA_XDR
) - VMware ESXi (
VMWARE_ESX
) - VMWare VSphere (
VMWARE_VSPHERE
) - WatchGuard (
WATCHGUARD
) - Windows Event (XML) (
WINEVTLOG_XML
) - Workspace Activities (
WORKSPACE_ACTIVITY
) - Zscaler (
ZSCALER_WEBPROXY
) - Zscaler CASB (
ZSCALER_CASB
) - Zscaler DLP (
ZSCALER_DLP
) - ZScaler DNS (
ZSCALER_DNS
) - Zscaler Internet Access Audit Logs (
ZSCALER_INTERNET_ACCESS
) - ZScaler NGFW (
ZSCALER_FIREWALL
) - Zscaler Private Access (
ZSCALER_ZPA
) - Zscaler Secure Private Access Audit Logs (
ZSCALER_ZPA_AUDIT
) - Zscaler Tunnel (
ZSCALER_TUNNEL
)
The following log types were added without a default parser. Each parser is listed by product name and log_type
value, if applicable.
- Azure App Configuration (
AZURE_APPCONFIGURATION
) - Azure App Platform (
AZURE_APPPLATFORM
) - Azure ArcData (
AZURE_ARCDATA
) - Azure Authorization (
AZURE_AUTHORIZATION
) - Azure Change Analysis (
AZURE_CHANGEANALYSIS
) - Azure DataFactory (
AZURE_DATAFACTORY
) - Doppel (
DOPPEL
) - Genian NAC (
GENIAN_NAC
) - Penta Security Wapples (
PENTA_WAPPLES
) - Redmine (
REDMINE
) - S2W Quaxar (
S2W_QUAXAR
) - SecurityBridge Dev (
SECURITYBRIDGE_DEV
) - TeamT5 ThreatSonar EDR (
TEAMT5_THREATSONAR_EDR
) - WorkDay User Sign In (
WORKDAY_USER_SIGNIN
)
For a list of supported log types and details about default parser changes, see Supported log types and default parsers.
Pro feature: Code Interpreter is enabled by default
The Code Interpreter for Conversational Analytics is now enabled by default when the Gemini in Looker and Trusted Tester features settings are enabled for the Google Cloud project that is associated with a Looker Studio Pro subscription. The Code Interpreter in Conversational Analytics is a Preview feature that translates your natural language questions into Python code and executes that code to provide advanced analysis and visualizations.
Looker Studio users with the appropriate permissions can manage enablement on the Gemini in Looker page under User Settings.
Domain tagging for toxic combinations and chokepoints has been improved to be more precise. The following filters are available for issues:
- CVE Vulnerabilities
- Identity
- Data
- AI Security
May 28, 2025
BigQueryYou can now create a serverless Spark session and run PySpark code in a BigQuery notebook. This feature is generally available (GA).
Column metadata indexing is now available for both BigQuery tables and external tables. This feature is generally available (GA).
Multiple regions now benefit from enhanced responsiveness for latency-sensitive applications for Cloud Run service URLs.
Cloud SQL for SQL Server now offers the maximum server memory recommender.
Database instances running with an allocation of memory that's either too low or too high might experience performance issues.
The max server memory (mb)
flag limits the amount of memory that Cloud SQL can allocate for its internal pools. You can manually set a value for this flag, or omit the flag and let Cloud SQL manage memory limits for you automatically.
For more information, see Optimize maximum server memory usage.
Python 3.11 is now available in Colab Enterprise. Existing runtimes and runtime templates will remain using Python 3.10. For more information, see Python versions.
When you create a runtime template, you can now configure it to use the latest Python version available to Colab Enterprise, or you can specify the Python version. Using Latest
is a new option that means when a new version of Python is introduced to Colab Enterprise, runtimes that you create will use the latest Python version.
Existing runtime templates and runtimes remain using their current Python version (Python 3.10). This includes existing auto-generated default runtime templates. To create default runtime templates that use Latest
, you must do one of the following:
- Delete the existing default runtime templates. Then, when a new default runtime template is created, the Python version will be set to Latest.
- Change a runtime template's Python version by using the REST API.
You can now use strict act-as mode to enable an additional security check for certain user actions in Dataform. For more information, see Use strict act-as mode. This feature is in preview.
Announcing the General Availability release of Spark on BigQuery, which lets you create a serverless Spark session in a BigQuery Studio notebook. Use this feature to create, run, and test Spark jobs quickly and easily. For more information, see Run PySpark code in BigQuery Studio notebooks.
New Dataproc Serverless for Spark runtime versions:
- 1.1.105
- 1.2.49
- 2.2.49
- 2.3.0
Announcing the General Availability (GA) release of Dataproc Serverless for Spark runtime versions 2.3, which include the following components:
- Spark 3.5.1
- BigQuery Spark Connector 0.42.3
- Cloud Storage Connector 3.1.2
- Java 17
- Python 3.11
- R 4.3
- Scala 2.13
Manage files and folders in the Context Drawer
You can now view and manage files and folders requested to be included in Gemini Code Assist's context, using the Context Drawer. After you specify a file or folder to be used as context for your Gemini Code Assist prompts, these files and folders are placed in the Context Drawer, where you can review and remove them from the prompt context.
This gives you more control over which information Gemini Code Assist considers when responding to your prompts.
AI and ML perspective: Cost optimization: Major update to expand the cost optimization recommendations in the AI and ML perspective.
Workforce Identity Federation supports detailed audit logging, which you can use to troubleshoot attribute mapping issues. This feature is generally available.
You can assign IPv6 bring your own IP (BYOIP) addresses to a subnet's external address range. These subnet ranges can only be used by VM instances, either as ephemeral or reserved addresses. To reserve addresses from these ranges, create a static regional external IPv6 address with the VM endpoint type. This feature is available in General Availability.
For more information, see Create and use IPv6 sub-prefixes.
May 27, 2025
AlloyDB OmniThe AlloyDB Omni Kubernetes operator version 1.4.1 is generally available (GA) and includes the following bug fixes:
- Fix for overriding replication related parameters. This fix lets you override the
wal_keep_size
value. For more information, see Work with cross-data-center replication. This fix requires database version 15.7.1 or later. - 63-character DBCluster names are supported, which lets you define clearer and more descriptive cluster names.
- Various bug fixes are implemented to enhance stability and the user experience.
The AlloyDB Omni Kubernetes operator version 1.4.1 is generally available (GA) and includes the following bug fixes:
- Fix for overriding replication related parameters. This fix lets you override the
wal_keep_size
value. For more information, see Work with cross-data-center replication. This fix requires database version 15.7.1 or later. - 63-character DBCluster names are supported, which lets you define clearer and more descriptive cluster names.
- Various bug fixes are implemented to enhance stability and the user experience.
On May 27, 2025 we released an updated version of Apigee Advanced API Security.
With this release, Advanced API Security expands its runtime region support to include africa-south1
(Johannesburg).
For a list of supported regions, see Apigee locations.
You can now share Pub/Sub streaming data through BigQuery sharing with additional client libraries support and provider usage metrics. This feature is generally available (GA).
BigQuery offers optional job creation mode to speed up small queries that you use in your dashboards, data exploration, and other workflows. This mode automatically optimizes eligible queries and uses a cache to improve latency. This feature is generally available (GA).
You can delete logical and continuous materialized views in the Google Cloud console. For more information, see Delete a logical view or Delete a continuous materialized view.
You can now create build triggers that build from repositories connected to Developer Connect.
The Healthcare Natural Language API is deprecated and will be shut down on May 27, 2026. For more information, see Deprecations.
Learn how to instrument your generative AI applications by using OpenTelemetry and the LangGraph framework to collect information about the actions taken by your AI agent. You can view generative AI events by using the Trace Explorer:
cos-121-18867-90-32
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
Support NVIDIA MFT Tools on COS.
Inject IMEX channel char device for GB200 GPUs.
Fixed CVE-2025-46836 in sys-apps/net-tools.
Fixed CVE-20250-3198 in sys-libs/bintuils-libs.
Fixed KCTF-b3bf8f6 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811834 -> 811792
cos-117-18613-263-19
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v24.0.9 | v1.7.27 | See List |
Support NVIDIA MFT Tools on COS.
Inject IMEX channel char device for GB200 GPUs.
Fixed CVE-2025-46836 in sys-apps/net-tools.
Fixed CVE-20250-3198 in sys-libs/bintuils-libs.
Fixed KCTF-b3bf8f6 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811793 -> 811830
cos-113-18244-382-22
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.134 | v24.0.9 | v1.7.27 | See List |
Support NVIDIA MFT Tools on COS.
Fixed CVE-2025-46836 in sys-apps/net-tools.
Fixed CVE-20250-3198 in sys-libs/bintuils-libs.
Fixed KCTF-b3bf8f6 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812054 -> 812045
cos-109-17800-519-12
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.135 | v24.0.9 | v1.7.27 | See List |
Support NVIDIA MFT Tools on COS.
Fixed CVE-2025-46836 in sys-apps/net-tools.
Fixed CVE-20250-3198 in sys-libs/bintuils-libs.
Runtime sysctl changes:
- Changed: fs.file-max: 812270 -> 812274
You can now use the Filestore CSI driver to create Filestore instances with the NFSv4.1 protocol from the Google Kubernetes Engine (GKE) cluster. This feature is available for zonal, regional, and enterprise service tiers.
Version 3.35 is released
All release notes published on this date are part of version 3.35.
The timing of the update to your instance depends on the deployment schedule that you have chosen. For more information, see Deployment schedules.
QM integration now includes chat session events
You can now export chat session events to an external quality management (QM) system. After you configure the endpoint of your QM system in Google Cloud CCaaS, your chat session events can be streamed to the endpoint in real time.
User experience change:
- The QM Integration dialog at Settings > Developer Settings > Session Data Export > QM Integration has a new QM Chat Events - send chat sessions events checkbox.
For more information, see QM, SIPREC, and WFM integration.
Remove email subject lines from interaction data
We now support removing email subject lines when you delete interaction data from your instance for specified end-users. The email subjects are removed when you delete data for an end-user in the Consumer Privacy dialog at Settings > Consumer Management > Consumer Privacy. To completely remove an end-user's data, you must also delete their emails from your mail server. You must also delete chat transcripts, call recordings, and other session-related files from your CRM or external storage, depending on your configuration.
For more information, see Remove subject lines from end-user email interactions.
New sender email with auto-response emails
You can now configure an outbound-only email address and use it as the sender address for auto-response emails. The outbound-only address is a "no-reply" email address that prevents the receiver from responding.
User experience changes:
- The Auto-response dialog at Settings > Queue > Email > [your-email-queue] > Auto-response has a new Sender email field.
- The Add an email dialog at Settings > Developer Settings > Email Account Management > Email account list > Add email account has a new This is an outbound only email account checkbox.
For more information, see Configure an outbound-only email account and Configure an auto-response email.
Include images in outbound emails
You can now include images in outbound emails. This includes emails from an agent in an email session and outbound auto-response emails.
User experience change:
- The Auto-response dialog at Settings > Queue > Email > [your-email-queue] > Auto-response has a new Insert Image button.
- The email adapter has a new Insert Image button.
For more information, see Agent email adapter and Configure an auto-response email.
The following issues were addressed in this release:
- Fixed an issue where calls were were being logged as Call with unknown contact in HubSpot instead of under the correct contact name.
- Fixed an issue where the client secret couldn't be saved when a user attempted to set up authentication (using either basic authentication or OAuth) for a custom CRM with the Generic API CRM lookup method.
- Fixed an issue where the setup dialog for Find an account by query endpoint could not be reached due to an authentication error when configuring OAuth for a custom CRM.
- Fixed an issue where calls were being passed to a custom CRM with the incorrect phone number format.
- Fixed an issue for ServiceNow users where records were created for outbound calls despite the agent selecting Do not create a record in the call adapter.
- Fixed an issue where a queue did not have access to the global contact list even though it was configured to have access to it.
- Fixed an issue where the Directory tab didn't appear when an agent was transferring a call.
- Fixed an issue where the Voice Campaign checkbox didn't appear for Select Call Types in the Create Reports pane, despite the user having the appropriate report access permissions.
- Fixed an issue where agent extension deflection recordings didn't upload after appearing to be successfully uploaded.
- Fixed an issue that occurred when the
@{NEXT_REOPEN_HOUR}
dynamic variable was put in the Message field for After Hour Messaging in the Web & Mobile Messages pane. The variable always resolved as the next time the chat queue opened on the following day. This happened even when the next time the chat queue opened was on the current day. - Fixed an issue that occurred when an end-user on the global contact list placed an inbound call to a queue with access to the global contact list turned off. The agent adapter displayed the destination name of the caller, despite access to the global contact list being turned off.
- Extended the search conditions for the Directory tab in the agent adapter to include search by an extension number.
- Fixed an issue where the "next open hours" message was incorrect when a chat ended after midnight.
- Fixed an issue where the call transcript failed to continue after an agent returned from hold.
- Fixed an issue where the default disposition list appeared in the agent adapter instead of the custom disposition list, which was configured to appear.
- Fixed an issue where a user with a manager role received a "Not Authorized" error when attempting to use the Operation Management and Disposition Codes pages.
- Fixed an issue where the
failReason
andafterHours
fields in the session metadata file were incorrect for chats that failed because they were attempted after hours. - Fixed an issue where the Assign agents button wasn't working for custom after hours deflection and automatic redirection.
- Fixed an issue where the client secret was not saved when configuring OAuth for a custom CRM.
- Fixed an issue where calling the current queue status endpoint of the Manager API intermittently returned a 404 error.
- Fixed an issue where the wrong disposition code list appeared for an agent after transferring a chat to an agent in a different queue.
- Fixed an issue where chat shortcuts were not working in the agent adapter for mobile chats.
- Fixed issues where agents were unable to successfully move beyond the wrap-up state to handle the next call.
In GKE version 1.32.2-gke.1297000 and later, you can run GPU workloads on Confidential GKE Nodes with the A3 High machine type and NVIDIA H100 GPUs. This enables stronger data protection and integrity for GPU-accelerated computations running within GKE clusters and nodes. This feature is available in Preview. For more information, see Encrypt GPU workload data in use with Confidential GKE Nodes.
In GKE version 1.32.2-gke.1297000 and later, you can use the Intel TDX and AMD SEV-SNP Confidential Computing technologies with Confidential GKE Nodes. This feature is in General Availability. Use Confidential GKE Nodes to encrypt your workload data in-use through Compute Engine Confidential VMs for data and code confidentiality and integrity. For more information, see Encrypt workload data in-use with Confidential GKE Nodes.
Policy Controller version 1.20.3 is now available.
Enhanced data residency support in the European Union and United States is in General Availability.
May 26, 2025
BigQueryA weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-bigquery
2.50.1 (2025-05-16)
Dependencies
- Update dependency com.google.cloud:sdk-platform-java-config to v3.48.0 (#3790) (206f06d)
- Update netty.version to v4.2.1.final (#3780) (6dcd858)
Documentation
Python
Changes for google-cloud-bigquery
3.33.0 (2025-05-19)
Features
- Add ability to set autodetect_schema query param in update_table (#2171) (57f940d)
- Add dtype parameters to to_geodataframe functions (#2176) (ebfd0a8)
- Support job reservation (#2186) (cb646ce)
Bug Fixes
A weekly digest of client library updates from across the Cloud SDK.
Cloud Logging begins enforcement of the new volume-based regional quotas. These quotas replace the single, global quota for the number of calls to write log entries. For more information, see Logging API quotas and limits.
A weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-logging
3.22.4 (2025-05-20)
Bug Fixes
- deps: Update the Java code generator (gapic-generator-java) to 2.58.0 (45b4878)
Dependencies
Generally Available: A3 Ultra accelerator-optimized machine types are now available in the following additional regions and zones:
APAC
- Mumbai, India:
asia-south1-b
- Delhi, India:
asia-south2-c
Europe:
- St. Ghislain, Belgium:
europe-west1-b
- Eemshaven, Netherlands:
europe-west4-b
North America:
- Council Bluffs, Iowa:
us-central1-b
- Moncks Corner, South Carolina:
us-east1-d
- Ashburn, Virginia,:
us-east4-b
- The Dalles, Oregon:
us-west1-c
- Dallas, Texas:
us-south1-b
For a complete list of A3 Ultra regions and zones, see GPU regions and zones.
Datastream now supports MongoDB as a source. The feature is in Preview.
For more information, see the Datastream documentation.
New Storage Transfer Service (STS) based feeds
This feature is currently in Preview.
Existing tenants are now able to create new feeds using STS, whereas existing feeds will remain unaffected. Customers will be separately notified about the required steps and timelines for the migration of existing feeds to STS. The following new feeds are available:
- GOOGLE_CLOUD_STORAGE_V2
- GOOGLE_CLOUD_STORAGE_EVENT_DRIVEN
- AMAZON_S3_V2
- AMAZON_SQS_V2
- AZURE_BLOBSTORE_V2
The following feed types are replaced by the new STS-based feeds:
- GOOGLE_CLOUD_STORAGE replaced by GOOGLE_CLOUD_STORAGE_V2
- AMAZON_S3 replaced by AMAZON_S3_V2
- AMAZON_SQS replaced by AMAZON_SQS_V2
- AZURE_BLOBSTORE replaced by AZURE_BLOBSTORE_V2
For more information, see Storage Transfer Service and its benefits and Configuration by source type.
New Storage Transfer Service (STS) based feeds
This feature is currently in Preview.
Existing tenants are now able to create new feeds using STS, whereas existing feeds will remain unaffected. Customers will be separately notified about the required steps and timelines for the migration of existing feeds to STS. The following new feeds are available:
- GOOGLE_CLOUD_STORAGE_V2
- GOOGLE_CLOUD_STORAGE_EVENT_DRIVEN
- AMAZON_S3_V2
- AMAZON_SQS_V2
- AZURE_BLOBSTORE_V2
The following feed types are replaced by the new STS-based feeds:
- GOOGLE_CLOUD_STORAGE replaced by GOOGLE_CLOUD_STORAGE_V2
- AMAZON_S3 replaced by AMAZON_S3_V2
- AMAZON_SQS replaced by AMAZON_SQS_V2
- AZURE_BLOBSTORE replaced by AZURE_BLOBSTORE_V2
For more information, see Storage Transfer Service and its benefits and Configuration by source type.
The Flex service level now supports auto-tiering feature in Preview, and available only for custom-performance Flex zonal pools. For more information, see Manage auto-tiering.
The cross-region backup vaults feature is now generally available. For more information, see Backup vaults.
Efficient backup copying is now enabled for incremental backups. When you copy an incremental backup, Spanner also copies all the older backups in the chain required to restore the copied backup. If the destination instance already contains a backup chain that ends with an older backup copied from the same source chain, Spanner now avoids creating redundant copies of existing backups to save storage and network costs. Spanner copies only the incremental backup and any older backups not present in the destination chain, and appends these backups to the existing chain.
While Spanner aims to avoid redundant copies, in rare situations, Spanner might need to copy all the older backups in the chain, even if previously copied backups already exist in the destination instance.
For more information, see Incremental backups.
May 25, 2025
Google SecOps SOARRelease 6.3.46 is now available for all regions.
May 24, 2025
Google SecOps SOARRelease 6.3.47 is being rolled out to the first phase of regions as listed here.
Environment load balancing
The environment load balancing feature offers improved stability and fair resource sharing in multi-tenant environments. It uses a lottery algorithm for resource allocation and lets administrators prioritize environments via API-based weighting.
For more information, see Manage environment load balancing.
May 23, 2025
Assured WorkloadsThe Canada Protected B control package is now generally available.
Preview: You can view and export usage and forecast data of the machine types and TPUs in your project, folder, or organization. This information helps you analyze usage trends and plan for future capacity needs. For more information, see the following:
Cloud Deploy now uses Skaffold 2.16 as the default Skaffold version, as of May 23, 2025, for all target types.
Cloud SQL for SQL Server now extends query insights and index advisor support to read replicas.
Generally available: Resource-based committed use discounts (CUDs) are available for M4 machine types that come with 6 TB of memory. Learn more about how to purchase commitments for M4 6 TB machine types.
Dataproc now supports the creation of zero-scale clusters, available in preview. This feature provides a cost-effective way to use Dataproc clusters, as they utilize only secondary workers that can be scaled down to zero when not in use.
Mistral OCR is an Optical Character Recognition API for document understanding. It is GA on Vertex AI. For more information, see the Mistral OCR model card in Model Garden.
(2025-R20) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- Version 1.32.4-gke.1236006 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.12-gke.1033000
- 1.31.7-gke.1390000
- 1.31.8-gke.1045000
- 1.32.3-gke.1927002
- 1.32.4-gke.1106000
- 1.32.4-gke.1236000
- 1.33.0-gke.1552000
- 1.33.0-gke.1712000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.12-gke.1086000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.8-gke.1113000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.4-gke.1236006 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.12-gke.1086000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.8-gke.1113000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.4-gke.1236006 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.33 to version 1.33.0-gke.1868000 with this release.
Regular channel
- Version 1.32.3-gke.1927009 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.11-gke.1157000
- 1.31.7-gke.1265000
- 1.32.3-gke.1785003
- 1.32.3-gke.1927002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.32.3-gke.1927009 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.3-gke.1927009 with this release.
Stable channel
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Stable channel.
- The following versions are now available in the Stable channel:
- The following versions are no longer available in the Stable channel:
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
Extended channel
- Version 1.32.3-gke.1927009 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2682000
- 1.27.16-gke.2771000
- 1.28.15-gke.2142000
- 1.28.15-gke.2239000
- 1.29.15-gke.1193000
- 1.29.15-gke.1325000
- 1.30.11-gke.1157000
- 1.31.7-gke.1265000
- 1.32.3-gke.1785003
- 1.32.3-gke.1927002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2169000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2703000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2169000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.15-gke.1240000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.3-gke.1927009 with this release.
No channel
- Version 1.32.3-gke.1927009 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.3-gke.1927002
- 1.32.4-gke.1236000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.3-gke.1927009 with this release.
(2025-R20) Version updates
- Version 1.32.4-gke.1236006 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.12-gke.1033000
- 1.31.7-gke.1390000
- 1.31.8-gke.1045000
- 1.32.3-gke.1927002
- 1.32.4-gke.1106000
- 1.32.4-gke.1236000
- 1.33.0-gke.1552000
- 1.33.0-gke.1712000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.12-gke.1086000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.8-gke.1113000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.4-gke.1236006 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.12-gke.1086000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.8-gke.1113000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.4-gke.1236006 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.33 to version 1.33.0-gke.1868000 with this release.
(2025-R20) Version updates
- Version 1.32.3-gke.1927009 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.11-gke.1157000
- 1.31.7-gke.1265000
- 1.32.3-gke.1785003
- 1.32.3-gke.1927002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.32.3-gke.1927009 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.3-gke.1927009 with this release.
(2025-R20) Version updates
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Stable channel.
- The following versions are now available in the Stable channel:
- The following versions are no longer available in the Stable channel:
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
(2025-R20) Version updates
- Version 1.32.3-gke.1927009 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2682000
- 1.27.16-gke.2771000
- 1.28.15-gke.2142000
- 1.28.15-gke.2239000
- 1.29.15-gke.1193000
- 1.29.15-gke.1325000
- 1.30.11-gke.1157000
- 1.31.7-gke.1265000
- 1.32.3-gke.1785003
- 1.32.3-gke.1927002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2169000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2703000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2169000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.15-gke.1240000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.3-gke.1927009 with this release.
(2025-R20) Version updates
- Version 1.32.3-gke.1927009 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.3-gke.1927002
- 1.32.4-gke.1236000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.11-gke.1217000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.3-gke.1927009 with this release.
In the Google Cloud console, the GKE security posture dashboard now uses Security Command Center to show the top threats that affect your GKE workloads. This feature is in General Availability.
Starting May 26, 2025, the findings retention period for new activations of Security Command Center will change from 13 months to 90 days.
The retention period for findings for existing customers prior to May 26, 2025, remains unchanged.
For more information on retention periods, see Data retention.
May 22, 2025
AI HypercomputerGenerally available: You can proactively manage upcoming maintenance host events on your reserved blocks of capacity, whether VMs are running on them or not. This approach helps you minimize disruptions and maintain optimal performance. For more information, see Manage host events across reservations.
AlloyDB for PostgreSQL supports the
pg_ivm
extension,
which provides incremental view maintenance for materialized views.
On May 22, 2025, we released an updated version of Apigee.
Public preview of server-sent events
Apigee now supports continuous response streaming from server-sent event (SSE) endpoints to clients in real time. The Apigee SSE feature is useful for handling large language model (LLM) APIs that operate most effectively by streaming their responses back to the client. SSE streaming reduces latency, and clients can receive response data as soon as it is generated by an LLM. This feature supports the use of AI agents that operate in real time environments, such as customer service bots or workflow orchestrators. For more information, see Streaming server-sent events.
Public Preview of Apigee policies for LLM/GenAI workloads
Four new Apigee policies supporting LLM/GenAI workloads are now available in Public Preview:
The Apigee semantic caching policies enable intelligent response reuse based on semantic similarity. Using these policies in your Apigee API proxies can minimize redundant backend API calls, reduce latency, and lower operational costs.
The Model Armor policies protect your AI applications by sanitizing user prompts to and responses from large language models (LLMs). Using these policies in your Apigee API proxies can mitigate the risks associated with LLM usage by leveraging Model Armor to detect prompt injection, prevent jailbreak attacks, apply responsible AI filters, filter malicious URLs, and protect sensitive data.
For more information on using these policies in your Apigee API proxies, see:
Backup for GKE is now available in two new regions: europe-north2 and northamerica-south1
When you migrate Teradata data to BigQuery using the BigQuery Data Transfer Service, you can now specify the outputs of the BigQuery translation engine to use as schema mapping. This feature is in preview.
You can use custom constraints with Organization Policy to provide more granular control over specific fields for some BigQuery resources. This feature is available in Preview.
Starting September 15 2025, the bigquery.datasets.getIamPolicy
IAM permission is required to view a dataset's access controls and to query the
INFORMATION_SCHEMA.OBJECT_PRIVILEGES
view. The bigquery.datasets.setIamPolicy
permission is required to update a
dataset's access controls or to create a dataset with access controls using the
API. For more information on this change and how to opt into early enforcement, see Changes to dataset-level access controls.
When you Set up Gemini in BigQuery you are now prompted to grant the BigQuery Studio User and BigQuery Studio Admin roles. These roles now include permission to use Gemini in BigQuery features. This feature is generally available (GA).
You can select multiple columns and perform data preparation tasks on them, including dropping columns. For more information, see Prepare data with Gemini. This feature is generally available (GA).
Database Migration Service now supports MySQL minor version 8.0.42 for homogeneous MySQL migrations. For more information, see Supported source and destination databases in Cloud SQL for MySQL migrations.
You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).
For more information, see Configure both private services access and Private Service Connect.
The rollout of the following minor versions, extension versions, and plugin versions is complete:
Minor versions
- 13.20 is upgraded to 13.21.
- 14.17 is upgraded to 14.18.
- 15.12 is upgraded to 15.13.
- 16.8 is upgraded to 16.9.
- 17.4 is upgraded to 17.5.
Extensions and plugins
- pg_squeeze is upgraded from 1.5 to 1.8 for all PostgreSQL versions 12 and above.
To use these versions of the extensions, update your instance to [PostgreSQL version].R20250302.00_19
.
If you use a maintenance window, then the updates to the minor, extension, and plugin versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks.
For more information on checking your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.
You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).
For more information, see Configure both private services access and Private Service Connect.
You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).
For more information, see Configure both private services access and Private Service Connect.
Public preview: You can request Cloud TPUs using future reservations in calendar mode. This mode, powered by the Dynamic Workload Scheduler, lets you check TPU availability up to 120 days in advance and request capacity based on your schedule. You can use calendar mode to reserve TPUs for 1 to 90 days. Requesting a short-term reservation with calendar mode is a good fit for training and experimentation workloads that require precise start times and have a defined duration. For more information, see Request a short-term reservation using calendar mode.
Public preview: You can enable reservation sharing for Cloud TPU. This feature lets you share a reservation across multiple projects. You can also share a reservation with Vertex AI for training or serving workloads. For more information, see Share a Cloud TPU reservation.
Public preview: The general-purpose C4D machine series offers Local SSD (-lssd
) machine types with up to 12 TiB of Titanium SSD. Learn more about C4D machine series and the available C4D Local SSD machine types.
New Dataproc Serverless for Spark runtime versions:
- 1.1.104
- 1.2.48
- 2.2.48
Gemini Code Assist now uses Gemini 2.5. These models are now used in the following experiences:
- Chat
- Code generation
- Code transformation
Anthropic's Claude Opus 4 and Claude Sonnet 4 are GA on Vertex AI and support Provision Throughput. For more information, see the Claude Opus 4 or Claude Sonnet 4 model card in Model Garden.
All new VMware Engine private clouds now deploy with the following versions:
- VMware vSphere version 8.0 update 3
- NSX-T 4.2.1.2
Existing private clouds will be upgraded starting June 2025. See Service announcements for more details on the contents of this update.
Google Distributed Cloud (software only) for VMware 1.31.500-gke.68 is now available for download. To upgrade, see Upgrade a cluster. Google Distributed Cloud 1.31.500-gke.68 runs on Kubernetes v1.31.7-gke.1000.
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.
The following functional changes were made in 1.31.500-gke.68:
- Upgraded etcd to v3.4.33.
The following issues were fixed in 1.31.500-gke.68:
- Fixed vulnerabilities listed in Vulnerability fixes.
Release 1.31.500-gke.68
Google Distributed Cloud for bare metal 1.31.500-gke.68 is now available for download. To upgrade, see Upgrade clusters. Google Distributed Cloud for bare metal 1.31.500-gke.68 runs on Kubernetes v1.31.7-gke.1000.
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.
The following functional changes were made in 1.31.500-gke.68:
- Upgraded etcd to v3.4.33-0-gke.3.
The following issues were fixed in 1.31.500-gke.68:
- Fixed vulnerabilities listed in Vulnerability fixes.
For information about the latest known issues, see Google Distributed Cloud for bare metal known issues in the Troubleshooting section.
The May 13, 2025 issue in which GKE Autopilot clusters failed to update the cgroup_mode
field is fixed in all GKE versions.
Environment load balancing
The environment load balancing feature offers improved stability and fair resource sharing in multi-tenant environments. It uses a lottery algorithm for resource allocation and lets administrators prioritize SOAR environments via API-based weighting.
For more information, see Manage environment load balancing.
Chart Properties panel improvements
New improvements to the Properties panel Setup and Style tabs let users customize charts with a more organized and user-friendly flow.
New user consent flow for BigQuery data sources
When you're querying BigQuery data sources with Viewer credentials, a new user consent flow is available to verify that your email credentials can be logged.
The Google Kubernetes Engine (GKE) security posture dashboard shows the top threats, but not the top software vulnerabilities, detected by Security Command Center.
In the Google Cloud console, the Google Kubernetes Engine (GKE) security posture dashboard shows the top threats and software vulnerabilities that affect your GKE workloads. This feature is in General Availability.
Standalone VTT outputs are now supported.
Preview stage support for the following integration:
May 21, 2025
AlloyDB for PostgreSQLAlloyDB AI query engine
(Preview) lets you combine natural language with
SQL using operators like ai.if
, ai.rank
, and ai.generate
.
You can generate embeddings on images, videos, and text using multimodal embedding models, and
you can use Google DeepMind's latest text embedding model into model endpoint
management.
Apigee API hub is now available in the following regions:
- europe-west10 (Berlin)
- us-east5 (Columbus)
- us-south1 (Dallas)
- me-central2 (Dammam)
- asia-south2 (Delhi)
- me-central1 (Doha)
- europe-north1 (Finland)
- europe-west3 (Frankfurt)
- asia-east2 (Hong Kong)
- asia-southeast2 (Jakarta)
- africa-south1 (Johannesburg)
- us-west4 (Las Vegas)
- us-west2 (Los Angeles)
- europe-southwest1 (Madrid)
- australia-southeast2 (Melbourne)
- europe-west8 (Milan)
- northamerica-northeast1 (Montréal)
- europe-west4 (Netherlands)
- asia-northeast2 (Osaka)
- us-west3 (Salt Lake City)
- southamerica-west1 (Santiago)
- asia-northeast3 (Seoul)
- us-east1 (South Carolina)
- asia-east1 (Taiwan)
- me-west1 (Tel Aviv)
- asia-northeast1 (Tokyo)
- northamerica-northeast2 (Toronto)
- europe-west12 (Turin)
- europe-central2 (Warsaw)
- europe-west6 (Zürich)
For more information, see API hub locations.
The names for some Assured Workloads control packages are changing. For information about the name change, see Control package renaming notice.
Backup and DR Service 11.0.15.226 is now available to update your backup/recovery appliance. Refer to these instructions to update your appliance.
There is a new committed use discount (CUD) for customers using Backup and DR Service to protect Oracle databases into a backup vault. This is a way to lower backup costs in consideration of a 1-year or 3-year commitment. You can purchase CUDs from Google Cloud Marketplace via the standard process.
Backup and DR Service now supports backup and restore of Db2 databases using persistent disk snapshots. This is typically faster and simpler than previous methods and in some cases may also reduce costs.
These issues have been fixed:
- An issue in which multiple snapshot/Direct OnVault jobs became stuck in an unresponsive state after attempting to connect to vCenter with an openssl command.
- An issue in which database persistent disk snapshot backup jobs failed with the unhelpful error message
resource not found
now has a useful error message. - An issue in which Log explorer was showing some spurious "read error, check permissions" results on backup/recovery appliances.
- An issue in which a backup/recovery appliance could come out of synchronization with a management console following a
Trying to release lock
orFailed to acquire lock
error. - A rare issue in which a backup/recovery appliance became unresponsive after a very heavy load exhausted all job threads and /var/log/ was 100% full. Thread management is now more efficient.
- An issue in which persistent disk database snapshot images were failing to import log backups, and the recovery range was missing on imported backups.
- An issue in which some backups of PostgreSQL version 15 failed due to a premature timeout.
- An issue in which some mount jobs failed if the host's lvmconfig has global/system_id_source set to
uname
. - An issue in which database names provided in mount screen were not honored correctly when creating child applications on the target host.
- The
Staging disk is full
error message has been made more useful.
Vulnerabilities CVE-2024-42301, CVE-2024-42284, and CVE-2024-41092 have been fixed at kernel version 4.18.0-553.33.1.el8_10.
This release introduces enhanced logging and alerting capabilities for backup/recovery appliances, enabling proactive monitoring of their health and status. You can now configure email notifications via Cloud Logging to receive timely alerts on appliance status changes or potential issues, and five new events have been added for more granular monitoring:
- 10237: Jobs running over 6 hours.
- 11001: Backup/recovery appliance certificate expires in X days.
- 11004: Backup/recovery appliance system components are down.
- 11006: Backup/recovery appliance unable to sync with host.
- 90003: A new backup/recovery appliance update is available.
You are now able to set access controls on routines. This feature is in Preview.
You can now perform supervised tuning on a BigQuery ML remote model based on a Vertex AI gemini-2.0-flash-001
or gemini-2.0-flash-lite-001
model.
1.25.2-asm.3 is now available for in-cluster Cloud Service Mesh.
You can now download 1.25.2-asm.3 for in-cluster Cloud Service Mesh. It includes the features of Istio 1.25.2 subject to the list of supported features. Cloud Service Mesh version 1.25.2-asm.3 uses envoy v1.33.1-dev..
For details on upgrading Cloud Service Mesh, see Upgrade Cloud Service Mesh.
1.24.5-asm.3 is now available for in-cluster Cloud Service Mesh.
You can now download 1.24.5-asm.3 for in-cluster Cloud Service Mesh. It includes the features of Istio 1.24.5 subject to the list of supported features. Cloud Service Mesh version 1.24.5-asm.3 uses envoy v1.32.6-dev.
For details on upgrading Cloud Service Mesh, see Upgrade Cloud Service Mesh.
1.23.6-asm.3 is now available for in-cluster Cloud Service Mesh.
You can now download 1.23.6-asm.3 for in-cluster Cloud Service Mesh. It includes the features of Istio 1.23.6 subject to the list of supported features. Cloud Service Mesh version 1.23.6-asm.3 uses envoy v1.31.6.
For details on upgrading Cloud Service Mesh, see Upgrade Cloud Service Mesh.
In-cluster Cloud Service Mesh 1.22 is no longer supported. For more information and to view the earliest end-of-life dates for other versions, see Supported versions.
The following parser documentation is now available.
Collect Automation Anywhere logs
Collect ManageEngine ADAudit Plus logs
Collect Nasuni File Services Platform logs
Collect McAfee Web Gateway logs
Collect Microsoft Defender for Identity logs
The following parser documentation is now available.
Collect Automation Anywhere logs
Collect ManageEngine ADAudit Plus logs
Collect Nasuni File Services Platform logs
Collect McAfee Web Gateway logs
Collect Microsoft Defender for Identity logs
Google Cloud NetApp Volumes now supports volume replication for large capacity volumes. This feature is now generally available for allow-listed users.
The backup vault now allows users to specify a minimum retention period for backups, which prevents the backup deletion before the specified number of days. This feature is generally available for allow-listed users. For more information, see Backup vaults.
The Flex service level of Google Cloud NetApp Volumes that supports the independent provisioning of capacity and performance with zonal pools in selected regions is now generally available. For more information, see NetApp Volumes key features and Supported regions.
May 20, 2025
AI ApplicationsVertex AI Search: Media search automatically chooses the results mode
Media search can respond to queries as full queries or as partial (search-as-you-type) queries. You can specify which query mode to use or you can specify the auto mode.
With auto mode, Media search makes the choice for you by assessing and weighting various signals such as query length and content. Use the auto mode if you have one search box that some users expect to respond with search-as-you-type suggestions and others expect to respond as a full query search.
Auto mode is the default mode. For more information, see Get search results for media.
On May 20, 2025 we released a new version of Advanced API Security Abuse Detection.
Advanced API Security Abuse Detection incident reports now include the ability to view raw data
With this new functionality, you can view raw data underlying an incident report, including client IP address, API proxy, developer app, and other attributes.
For usage information, see the Abuse Detection customer documentation.
Introducing preview of a simplified one-step procedure for changing backup plans assigned to your Compute Engine VMs. Previously, changing the backup plan for a VM required removing the existing plan and then applying the new plan. With this update, you can now change the backup plan for a VM in a single operation. This enhancement streamlines your workflow, making it quicker and more efficient to ensure your VMs are protected by the desired backup strategy.
Preview: You can use future reservation requests in calendar mode to reserve capacity for creating VMs with TPUs attached. This feature helps you obtain and reserve high-demand resources to run generative artificial intelligence (AI), machine learning (ML), or high performance computing (HPC) workloads.
For more information, see the following pages:
Vertex AI Agent Engine
The following features are now available in Preview:
Gemini 2.5 Flash's public preview version has been updated to gemini-2.5-flash-preview-5-20
.
See Gemini 2.5 Flash for model details.
The model is available in the API and Vertex AI Studio.
Audio-to-audio support for Gemini 2.5 Flash with Live API is now available as a private preview. Users must be allowlisted to use this new feature.
The model is available in the API and Vertex AI Studio.
See Live API for details.
MedGemma models are available in Model Garden.
Thought summaries are now available as an experimental feature for Gemini 2.5 Pro and 2.5 Flash.
For details, see Thinking.
The model is available in the API and Vertex AI Studio.
Lyria 2, our latest music generation model, is now generally available.
See our music generation prompt guide and our user guide for more information.
The model is available in the API and Vertex AI Studio.
Imagen 4
Imagen 4 offers two Preview models: Imagen 4 Generate Preview 05-20, and Imagen 4 Ultra Generate Experimental 05-20.
For more information, see Generate images using text prompts and the Generate images API.
The model is available in the API and Vertex AI Studio.
Veo 3
Veo 3 is available in Preview for allowlisted accounts.
For more information about Veo 3, see Veo | AI Video Generator and Veo on Vertex AI API.
The model is available in the API and Vertex AI Studio.
New stable text embeddings models are now generally available:
gemini-embedding-001
text-embedding-005
For more information, see Get text embeddings.
In GKE version 1.32.3-gke.1927002 and later, GKE uses a container-optimized compute platform for the general-purpose Autopilot compute class. This platform improves Pod scheduling latency, especially during autoscaling operations. The container-optimized compute platform provides benefits like faster scaling reaction times and more precise capacity right-sizing. For more information about the general-purpose compute class, see About built-in compute classes in Autopilot clusters.
Self-Service Deprovisioning for Google SecOps
You can now deprovision your Google SecOps tenant and associated data directly. For more information, see Self-service deprovisioning.
The following features have been added to Studio in Looker, which is available in preview:
- Some Looker permissions now apply to Studio in Looker reports. See Overview of Studio in Looker permissions for more information.
- Studio in Looker reports now support some download and export capabilities. See Download charts and reports for more information.
May 19, 2025
BigQueryContinuous queries let you build long-lived, continuously processing SQL statements that can analyze, process, and perform machine learning (ML) inference on incoming data in BigQuery in real time.
- To monitor your continuous queries, you can use a custom job ID prefix to simplify filtering or view metrics specific to continuous queries in Cloud Monitoring.
- Continuous queries can use slot autoscaling to dynamically scale allocated capacity to accommodate your workload.
This feature is generally available (GA).
Spanner now supports cross regional federated queries from BigQuery which allow BigQuery users to query Spanner tables from regions other than their BigQuery region. Users don't incur Spanner network egress charges during the preview period. This feature is in preview.
A weekly digest of client library updates from across the Cloud SDK.
Go
Changes for bigquery/storage/apiv1beta1
1.68.0 (2025-05-12)
Features
- bigquery/analyticshub: Support new feature Sharing Cloud Pubsub Streams via AH (GA) and Subscriber Email logging feature (#11908) (a21d596)
- bigquery/storage: Increased the number of partitions can be written in a single request (43bc515)
- bigquery: Add performance insights (#12101) (aef68ab)
- bigquery: Add some missing fields to BigQuery stats (#12212) (77b08e8)
- bigquery: Add WriteTruncateData write disposition (#12013) (b1126a3)
- bigquery: New client(s) (#12228) (f229bd9)
- bigquery: Support managed iceberg tables (#11931) (35e0774)
- bigquery: Support per-job reservation assignment (#12078) (c9cebcc)
Bug Fixes
- bigquery: Cache total rows count (#12230) (202dce0), refs #11874 #11873
- bigquery: Parse timestamps with timezone info (#11950) (530d522)
- bigquery: Update google.golang.org/api to 0.229.0 (3319672)
- bigquery: Upgrade gRPC service registration func (7c01015)
Documentation
- bigquery/storage: Updated the number of partitions (from 100 to 900) can be inserted, updated and deleted in a single request (43bc515)
Python
Changes for google-cloud-bigquery
3.32.0 (2025-05-12)
Features
- Add dataset access policy version attribute (#2169) (b7656b9)
- Adds preview support for incremental results (#2145) (22b80bb)
- Add WRITE_TRUNCATE_DATA enum (#2166) (4692747)
- Adds condition class and assoc. unit tests (#2159) (a69d6b7)
- Support BigLakeConfiguration (managed Iceberg tables) (#2162) (a1c8e9a)
- Update the AccessEntry class with a new condition attribute and unit tests (#2163) (7301667)
Bug Fixes
A weekly digest of client library updates from across the Cloud SDK.
Cloud CDN supports content targeting, which helps you cache and deliver assets that are customized for your end-user contexts. It enables device characterization and geo-targeting, which are useful for implementing responsive websites, language customization, and currency settings. This feature is now Generally Available.
Cross-Site Interconnect (Preview) support is available in the following colocation facilities:
- Taipei, Taiwan
For more information, see the Locations table and Global Locations.
To take advantage of the new features of the global external Application Load Balancer, you can now migrate your classic Application Load Balancer resources to the global external Application Load Balancer infrastructure.
To migrate to the global external Application Load Balancer, you change the load balancing scheme of your load balancing resources—specifically, the backend services and forwarding rules—from EXTERNAL
to EXTERNAL_MANAGED
. You can also rollback resources to the classic Application Load Balancer infrastructure, as long as you do so within 90 days of changing the load balancing scheme.
Cloud Console support is also available to help you complete the migration process.
For more details on the migration process, see the following pages:
- Migration overview
- Migrate resources from classic to global external Application Load Balancer
- Roll back migrated resources to classic Application Load Balancer
This capability is available in General availability.
cos-121-18867-90-27
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
Fixed docker MTU mismatch.
Increased kdump memory reservation.
cos-117-18613-263-14
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v24.0.9 | v1.7.27 | See List |
Increased kdump memory reservation.
Previously, Dataplex data profile scans were limited to 300 columns per BigQuery table. You can now run data profile scans on all 10,000 columns in a BigQuery table.
File storage on Compute Engine:
- Added information about Google Cloud Managed Lustre and DDN Infinia.
- Updated the protocol specifications for Filestore.
- Updated the protocol and performance specifications for NetApp Volumes.
Parallel file systems for HPC workloads: Added information about Google Cloud Managed Lustre and DDN Infinia.
This is a minor release of Google Distributed Cloud connected (version 1.9.0).
The following new functionality has been introduced in this release of Google Distributed Cloud connected:
Workload network traffic tagging on GDCc servers. VLAN ID tagging on the kube0 network interface is now supported on GDC connected servers. This lets you tag your GDC connected workload traffic with a specific VLAN ID. You must request this feature when ordering your GDC connected servers deployment. For more information, see Workload network traffic tagging.
Performance-optimized Network Function operator on GDCc servers. The Network Function operator functionality has been streamlined on GDC connected server deployments to reduce vCPU and RAM consumption. For more information, see Network Function operator profiles.
L2 MetalLB load balancing for secondary networks. You can now specify an annotation in your Network resource and Pod configuration that triggers automatic configuration of L2 MetalLB load balancing on secondary Pod networks. For more information, see Configure a secondary interface on a Pod using Distributed Cloud multi-networking.
The following changes to existing functionality have been introduced in this release of Google Distributed Cloud connected:
IPv4/IPv6 dual-stack networking GA. This release of Google Distributed Cloud connected promotes the dual-stack IPv4/IPv6 networking feature to General Availability. For more information, see IPv4/IPv6 dual-stack networking.
Configurable local storage schemas GA. This release of Google Distributed Cloud connected promotes the configurable local storage schemas feature to General Availability. For more information, see Configure local storage schemas.
Load balancer address pool support GA. This release of Google Distributed Cloud connected promotes the load balancer address pool networking feature to General Availability. For more information, see Create a cluster.
Optimized BGP peering for multi-network Pods. The BGP peering functionality has been optimized for workload Pods using both primary and secondary network interfaces. For more information, see Networking features.
Virtual machine workload support is now enabled by default on GDCc servers. The VMRuntime virtual machine subsystem is now enabled by default on GDC connected servers deployments. You can manually disable it by modifying the
VMRuntime
custom resource. For more information, see Enable VM Runtime on GDC support on Distributed Cloud connected.Default downtime for virtual machine workloads has changed. The default value of the maxDowntime parameter for virtual machine workloads has been changed to 5 seconds. This lets a virtual machine workload pause for 5 seconds to complete live migration. To override this default with a value of your choice, see Migration Policies.
Virtual machine workloads stuck in abnormal state now automatically restart. The auto-recovery feature in the VMRuntime virtual machine subsystem now automatically restarts virtual machine workloads that have remained in an abnormal state for more than 3 minutes.
Security mitigations for the following vulnerabilities have been implemented in this release of Google Distributed Cloud connected:
OS layer security mitigations: CVE-2024-53227, CVE-2024-38589, CVE-2024-56770, CVE-2024-56779, CVE-2024-56724, CVE-2024-56723, CVE-2024-56720, CVE-2024-56688, CVE-2024-56642, CVE-2024-56606, CVE-2024-35925, CVE-2024-35933, CVE-2024-35930, CVE-2024-35895, CVE-2024-35855, CVE-2024-35852, CVE-2024-35847, CVE-2024-42145, CVE-2024-53066, CVE-2024-53061, CVE-2024-53057, CVE-2024-50151, CVE-2024-50142, CVE-2024-46771, CVE-2024-50202, CVE-2024-50143, CVE-2024-50251, CVE-2024-50237, CVE-2024-50234, CVE-2024-49968, CVE-2024-43846, CVE-2024-50058, CVE-2024-47696, CVE-2024-47671, CVE-2024-47668, CVE-2024-47667, CVE-2024-47663, CVE-2024-46840, CVE-2024-46854, CVE-2024-46844, CVE-2024-46829, CVE-2024-46822, CVE-2024-46750, CVE-2024-46744, CVE-2024-40905, CVE-2024-38588, CVE-2024-46707, CVE-2021-47619
GDC software-only security mitigations: CVE-2022-36227, CVE-2024-45491, CVE-2024-45492, CVE-2020-16156, CVE-2021-33194, CVE-2022-1304, CVE-2022-27664, CVE-2022-41723, CVE-2022-48733, CVE-2023-3676, CVE-2023-3955, CVE-2023-5528, CVE-2023-7104, CVE-2023-39325, CVE-2023-49083, CVE-2023-52425, CVE-2024-0743, CVE-2024-0793, CVE-2024-6609, CVE-2024-20696, CVE-2024-38577, CVE-2024-41011, CVE-2024-42228, CVE-2024-42280, CVE-2024-42284, CVE-2024-42285, CVE-2024-42301, CVE-2024-42302, CVE-2024-42313, CVE-2024-43839, CVE-2024-43858, CVE-2024-43882, CVE-2024-44974, CVE-2024-44987, CVE-2024-44998, CVE-2024-44999, CVE-2024-45490, CVE-2024-46673, CVE-2024-46674, CVE-2024-46722, CVE-2024-46723, CVE-2024-46724, CVE-2024-46725, CVE-2024-46731, CVE-2024-46738, CVE-2024-46740, CVE-2024-46743, CVE-2024-46744, CVE-2024-46747, CVE-2024-46756, CVE-2024-46757, CVE-2024-46758, CVE-2024-46759, CVE-2024-46782, CVE-2024-46798, CVE-2024-46800, CVE-2024-46804, CVE-2024-46814, CVE-2024-46815, CVE-2024-46818, CVE-2024-46828, CVE-2024-46844, GHSA-m425-mq94-257g, CVE-2021-31525, CVE-2021-3669, CVE-2021-36976, CVE-2022-26280, CVE-2022-41717, CVE-2023-2431, CVE-2023-2727, CVE-2023-2728, CVE-2023-3978, , CVE-2023-23931, CVE-2023-31083, CVE-2023-44487, CVE-2023-52889, CVE-2024-24557, CVE-2024-29018, CVE-2024-41098, CVE-2024-42114, CVE-2024-42246, CVE-2024-42259, CVE-2024-42272, CVE-2024-42283, CVE-2024-42286, CVE-2024-42287, CVE-2024-42288, CVE-2024-42289, CVE-2024-42297, CVE-2024-42309, CVE-2024-42310, CVE-2024-42311, CVE-2024-43828, CVE-2024-43829, CVE-2024-43834, CVE-2024-43835, CVE-2024-43846, CVE-2024-43849, CVE-2024-43853, CVE-2024-43854, CVE-2024-43856, CVE-2024-43860, CVE-2024-43861, CVE-2024-43871, CVE-2024-43884, CVE-2024-43889, CVE-2024-43890, CVE-2024-43892, CVE-2024-43893, CVE-2024-43894, CVE-2024-43905, CVE-2024-43907, CVE-2024-43908, CVE-2024-43914, CVE-2024-44935, CVE-2024-44944, CVE-2024-44946, CVE-2024-44947, CVE-2024-44954, CVE-2024-44960, CVE-2024-44965, CVE-2024-44968, CVE-2024-44971, CVE-2024-44988, CVE-2024-44989, CVE-2024-44990, CVE-2024-44995, CVE-2024-45003, CVE-2024-45006, CVE-2024-45016, CVE-2024-45018, CVE-2024-45021, CVE-2024-45025, CVE-2024-45028 CVE-2024-46675, CVE-2024-46676, CVE-2024-46677, CVE-2024-46679, CVE-2024-46685, CVE-2024-46689, CVE-2024-46702, CVE-2024-46707, CVE-2024-46714, CVE-2024-46719, CVE-2024-46721, CVE-2024-46737, CVE-2024-46739, CVE-2024-46750, CVE-2024-46755, CVE-2024-46763, CVE-2024-46771, CVE-2024-46777, CVE-2024-46780, CVE-2024-46781, CVE-2024-46783, CVE-2024-46791, CVE-2024-46817, CVE-2024-46819, CVE-2024-46822, CVE-2024-46829, CVE-2024-46840, CVE-2024-47663, GHSA-jq35-85cj-fj4p, CVE-2024-43167, CVE-2024-43168, CVE-2024-3177, CVE-2021-36084, CVE-2021-36085, CVE-2021-36086, CVE-2021-36087, CVE-2021-36690, CVE-2024-43841
The following Google Distributed Cloud connected components have been updated:
GDC software-only has been updated from version 1.29.800-gke.111 to version 1.30.400-gke.136. (This component was formerly known as GKE on Bare Metal and as Anthos Clusters on Bare Metal.)
Symcloud Storage has been updated from version 5.4.8 to version 5.4.14-63.
The following documentation updates have been implemented in this release of Google Distributed Cloud connected:
Survivability mode. We have clarified how a cluster enters survivability, what happens when a cluster enters survivability mode, and how Google supports clusters that have entered survivability mode. For more information, see Survivability mode.
Offline cluster credential generation. We have updated the "Create and manage clusters" page with steps for generating offline cluster credentials. For more information, see Obtain credentials for a cluster.
The following issues have been resolved in this release of Google Distributed Cloud connected:
Reallocating a GPU resource from a VM to a container no longer causes an initialization error. An NVML initialization error no longer occurs when you reallocate a GPU from a virtual machine workload to a container workload.
After a network disruption, Symcloud Storage volumes no loner fail to mount or dismount. Symcloud Storage volumes now mount and dismount reliably after network connectivity is restored after a node that uses Symcloud Storage volumes experiences a network disconnection.
Virtual machines using file-based Symcloud Storage volumes no longer experience CDI import errors. Intermittent CDI import failures no longer occur when creating a virtual machine that uses a file-based Symcloud Storage volume.
You no longer have to manually copy storage secrets for corresponding buckets to the target clusters in a zone. For Google Distributed Cloud connected zones with more than one cluster deployed on refreshed rack hardware, management of storage buckets for all clusters must be done through the first cluster in the zone, also known as the Storage Infrastructure Cluster (SIC). This is because bucket access is granted through roles to users on the SIC. When access to a bucket is granted, a secret is generated on the SIC for the associated user. Google Distributed Cloud connected now automatically synchronizes storage secrets across clusters, and you no longer have to manually copy those secrets to each target cluster.
This release of Google Distributed Cloud connected contains the following known issues:
Storage is not freed immediately upon cluster deletion. After deleting a cluster, the storage used by that cluster is not freed up immediately. This is because storage clean-up is part of a garbage collection task that runs infrequently. To work around this issue, manually delete all of a cluster's persistent volumes before deleting the cluster itself.
The Storage Infrastructure Cluster cannot be deleted. On refreshed rack hardware deployments, the first cluster in a Google Distributed Cloud connected zone, also known as the Storage Infrastructure Cluster (SIC) cannot be deleted. Doing so would render Google Distributed Cloud connected storage inoperable. This is intentional behavior. Legacy Google Distributed Cloud connected rack hardware deployments and Google Distributed Cloud connected server deployments are not affected by this issue.
Machines can experience intermittent connectivity loss. Google Distributed Cloud connected machines can experience intermittent connectivity loss due to a rare condition that can occur with fleet credential management. To remedy this issue, contact Google Support.
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.Virtual machine workloads fail to restart or migrate if DHCP server address changes. If you are using DHCP to assign IP addresses to your virtual machine workloads and the IP address of your DHCP server changes, your virtual machine workloads cannot restart or complete migration. To remedy this issue, remove the stale network interface resource from the cluster and restart the affected virtual machine workloads.
Virtual machine workloads cannot coexist on the same virtual network with Pods that use DHCP for IP address assignment. This is because virtual machine workloads need the
IPAMMode
parameter set toexternal
to use DHCP, while Pods need theIPAMMode
parameter set tointernal
to use DHCP. Pods with static IP address are not affected by this. This behavior is by design.
Simplified provisioning and onboarding
The process for customer self provisioning and onboarding has been streamlined, significantly reducing the time required to onboard to Google SecOps.
For more information, see Onboard a Google SecOps instance.
Preview stage support for the following integration:
Service producers can publish services that are hosted on cross-region internal Application Load Balancers. This feature is available in Preview. For more information, see Publish services by using Private Service Connect.
May 18, 2025
Google SecOps SOARRelease 6.3.45 is now available for all regions.
May 17, 2025
Google SecOps SOARRelease 6.3.46 is is being rolled out to the first phase of regions.
Create playbooks with Gemini
This feature is now in General Availability. For more information, see Create playbooks with Gemini.
May 16, 2025
Apigee API hubAPI overview and metrics
The Get Started with API hub page now includes new charts and scorecards to provide a quick overview of your API landscape.
For more information see Get started with API hub.
Attach and manage Tags
You can now add custom tags to your APIs and API deployments, making it easier to organize, categorize, and discover your API resources in API hub. Tags can also be used to conditionally allow or deny policies to a specific resource.
For more information see Attach and manage tags.
Updated UI for API hub
The API hub user interface is now updated to Google Material Design 2. This update provides a more consistent and modern look and feel, enhancing the overall user experience and aligning the UI with other Google Cloud products.
hybrid 1.14.2-hotfix.1
On May 16, 2025 we released an updated version of the Apigee hybrid software, 1.14.2-hotfix.1.
Apply this hotfix with the following steps:
Download the
apigee-org
andapigee-env
charts with the1.14.2-hotfix.1
version tag:export CHART_REPO=oci://us-docker.pkg.dev/apigee-release/apigee-hybrid-helm-charts
export CHART_VERSION=1.14.2-hotfix.1
helm pull $CHART_REPO/apigee-env --version $CHART_VERSION --untar
helm pull $CHART_REPO/apigee-org --version $CHART_VERSION --untar
Optional: Perform this step if you need to allow use of the
allOf
combinator along with settingadditionalProperties: true
in your OAS spec. See fixed bug 393615439.Add the following stanza to your
overrides.yaml
:runtime: cwcAppend: conf_message-processor-communication_oas.disable.resolve.combinator: true
Install the hotfix release:
Update the
apigee-env
chart with thehelm upgrade
command and your current overrides file for each environment in your Apigee org:Dry run:
helm upgrade ENV_RELEASE_NAME apigee-env/ \ --namespace APIGEE_NAMESPACE \ --set env=ENV_NAME \ --atomic \ -f OVERRIDES_FILE \ --dry-run=server
- ENV_RELEASE_NAME is a name used to keep track of installation and upgrades of the
apigee-env chart
. This name must be unique from the other Helm release names in your installation. Usually this is the same as ENV_NAME. However, if your environment has the same name as your environment group, you must use different release names for the environment and environment group, for exampledev-env-release
anddev-envgroup-release
. For more information on releases in Helm, see Three big concepts in the Helm documentation. - APIGEE_NAMESPACE is your installation's namespace. The default is
apigee
. - ENV_NAME is the name of the environment you are upgrading.
- OVERRIDES_FILE is your edited overrides file.
Install the changes:
helm upgrade ENV_RELEASE_NAME apigee-env/ \ --namespace APIGEE_NAMESPACE \ --set env=ENV_NAME \ --atomic \ -f OVERRIDES_FILE
- ENV_RELEASE_NAME is a name used to keep track of installation and upgrades of the
Update the
apigee-org
chart:Dry run:
helm upgrade ORG_NAME apigee-org/ \ --namespace APIGEE_NAMESPACE \ -f OVERRIDES_FILE \ --dry-run=server
Install the changes:
helm upgrade ORG_NAME apigee-org/ \ --namespace APIGEE_NAMESPACE \ -f OVERRIDES_FILE
Verify the installation:
Ensure runtime and udca pods are up and running by checking their state:
kubectl -n APIGEE_NAMESPACE get pods -l app=apigee-runtime
kubectl -n APIGEE_NAMESPACE get pods -l app=apigee-udca
- For information on upgrading, see Upgrading Apigee hybrid to version 1.14.
- For information on new installations, see The big picture.
Bug ID | Description |
---|---|
393615439 | OASValidation behavior for allOf with additionalProperties: true .
Issue
The OASValidation policy in Apigee Hybrid versions 1.12 and later may incorrectly reject requests when validating against an OpenAPI Specification (OAS) that uses combinator keywords ( ResolutionA configuration flag has been introduced to control this behavior. By setting this flag, you can disable the pre-validation combinator resolution step, reverting to the behavior consistent with Apigee Edge and older Hybrid versions. Validation errors in Apigee hybridIf you encounter the validation errors described above, particularly for specs that worked correctly in Apigee Edge or Hybrid versions prior to 1.12, you can revert to the previous validation behavior by setting the following flag for the apigee-runtime container: conf_message-processor-communication_oas.disable.resolve.combinator = true |
Bug ID | Description |
---|---|
N/A | Incorporated an updated base image for stackdriver-logging-agent , improving the overall security of the service. This addresses the following vulnerabilities (among others and not limited to): |
The DB plugin versions 1.11.7 and 1.12.2 are available in Cloud Data Fusion versions 6.10.1 and 6.11.0 respectively. This release includes the following change:
- Added the
TRANSACTION_ISOLATION_LEVEL
property to DB Plugins (PostgreSQL, MySQL, and MSSQL).
A security vulnerability was detected in the classic Application Load Balancer service prior to April 26, 2025.
CVE-2025-4600 allowed attackers to smuggle requests to classic Application Load Balancers due to incorrect parsing of oversized chunk bodies. This vulnerability was addressed within the classic Application Load Balancer service on April 26, 2025 through improved input validation and parsing logic.
No action is needed. For more information, see the GCP-2025-027 security bulletin.
The latency and quality of Translation LLM has been improved.
Translation LLM now supports even more languages.
See our documentation for a list of all supported languages.
Google Distributed Cloud (software only) for VMware 1.30.900-gke.57 is now available for download. To upgrade, see Upgrade a cluster. Google Distributed Cloud 1.30.900-gke.57 runs on Kubernetes v1.30.11-gke.700.
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.
The following functional changes were made in 1.30.900-gke.57:
- Upgraded etcd to v3.4.33-0-gke.3.
The following issues were fixed in 1.30.900-gke.57:
- Fixed vulnerabilities listed in Vulnerability fixes.
Release 1.30.900-gke.57
Google Distributed Cloud for bare metal 1.30.900-gke.57 is now available for download. To upgrade, see Upgrade clusters. Google Distributed Cloud for bare metal 1.30.900-gke.57 runs on Kubernetes v1.30.11-gke.700.
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.
The following functional change was made in 1.30.900-gke.57:
- Upgraded etcd to v3.4.33-0-gke.3.
The following issues are fixed in 1.30.900-gke.57:
Fixed an issue where network interfaces are being leaked, preventing namespace deletion.
The 1.30.900-gke.57 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
For information about the latest known issues, see Google Distributed Cloud for bare metal known issues in the Troubleshooting section.
(2025-R19) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- Version 1.32.4-gke.1106000 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.11-gke.1157000
- 1.30.11-gke.1217000
- 1.31.7-gke.1265000
- 1.32.3-gke.1785003
- 1.33.0-gke.1582000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.3-gke.1927002 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.3-gke.1927002 with this release.
Regular channel
- Version 1.32.3-gke.1785003 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.32.2-gke.1297002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.32.3-gke.1785003 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
Stable channel
- The following versions are now available in the Stable channel:
Extended channel
- Version 1.32.3-gke.1785003 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2664000
- 1.27.16-gke.2732000
- 1.28.15-gke.2121000
- 1.28.15-gke.2192000
- 1.29.14-gke.1067000
- 1.29.15-gke.1274000
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.32.2-gke.1297002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2142000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2682000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2142000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.15-gke.1193000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
No channel
- Version 1.32.3-gke.1785003 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
(2025-R19) Version updates
- Version 1.32.4-gke.1106000 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.11-gke.1157000
- 1.30.11-gke.1217000
- 1.31.7-gke.1265000
- 1.32.3-gke.1785003
- 1.33.0-gke.1582000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.3-gke.1927002 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.12-gke.1033000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.7-gke.1390000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.3-gke.1927002 with this release.
(2025-R19) Version updates
- Version 1.32.3-gke.1785003 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.32.2-gke.1297002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.32.3-gke.1785003 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
(2025-R19) Version updates
- The following versions are now available in the Stable channel:
(2025-R19) Version updates
- Version 1.32.3-gke.1785003 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2664000
- 1.27.16-gke.2732000
- 1.28.15-gke.2121000
- 1.28.15-gke.2192000
- 1.29.14-gke.1067000
- 1.29.15-gke.1274000
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.32.2-gke.1297002
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2142000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2682000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2142000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.15-gke.1193000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
(2025-R19) Version updates
- Version 1.32.3-gke.1785003 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
May 15, 2025
AI HypercomputerPreview: You can use the Flex-start consumption option to obtain resources for up to seven days. Flex-start provisions capacity from a secured resource pool. Using this feature increases your chance to obtain high-demand resources like GPUs. For more information, see Choose a consumption option.
The region selector when creating a service or a job from the Google Cloud console now defaults to europe-west1
.
Cloud SQL for MySQL now supports minor version 8.0.42. To upgrade your existing instance to the new version, see Upgrade the database minor version.
You can now use advanced disaster recovery (DR) for your Private Service Connect (PSC) enabled Cloud SQL Enterprise Plus edition instances. With advanced DR, you can:
- Designate a cross-region disaster recovery (DR) replica
- Perform a cross-region replica failover for disaster recovery
- Restore your original deployment by using zero-data loss switchover
You can also use switchover to simulate disaster recovery without data loss. For more information, see Use advanced disaster recovery (DR). This feature is generally available (GA).
You can now use advanced disaster recovery (DR) for your Private Service Connect (PSC) enabled Cloud SQL Enterprise Plus edition instances. With advanced DR, you can:
- Designate a cross-region disaster recovery (DR) replica
- Perform a cross-region replica failover for disaster recovery
- Restore your original deployment by using zero-data loss switchover
You can also use switchover to simulate disaster recovery without data loss. For more information, see Use advanced disaster recovery (DR). This feature is generally available (GA).
Public Preview: You can use the flex-start provisioning model to increase your chances of obtaining GPUs for short-duration workloads. You can use flex-start with resize requests in managed instance groups (MIGs).
For more information, see the following:
New Dataproc Serverless for Spark runtime versions:
- 1.1.103
- 1.2.47
- 2.2.47
New Dataproc on Compute Engine subminor image versions:
- 2.0.141-debian10, 2.0.141-rocky8, 2.0.141-ubuntu18
- 2.1.89-debian11, 2.1.89-rocky8, 2.1.89-ubuntu20, 2.1.89-ubuntu20-arm
- 2.2.57-debian12, 2.2.57-rocky9, 2.2.57-ubuntu22
Global transaction identifier (GTID)-based replication for MySQL sources is now generally available (GA).
Support for creating custom organization policy constraints in Eventarc Advanced and in Eventarc Standard is generally available for some Eventarc resources.
Create playbooks with Gemini
This feature is now in General Availability. For more information, see Create playbooks with Gemini.
The predefined role reference and the permissions reference have been reorganized to improve performance and searchability. To see the new experience, visit the IAM roles and permissions index.
Set links to open in new tabs for pivot tables and table charts
The new Open links in new tab option lets report editors specify whether hyperlinks that are included in the data will open in a new tab.
Open links in new tab option is available only for pivot tables and table charts in reports that have modern charts enabled.
Looker connector filter enhancements
The Looker connector now supports the Matches (advanced) filter condition for text and number filter types, in addition to the data and time filter type. This support applies to filters from Looker data sources that are defined in LookML models with the conditionally_filter
and always_filter
parameters.
Learn more about how Looker Studio interprets LookML filters.
Limiting inappropriate content in schedules
Looker Studio now checks for potentially inappropriate content in the subject and message fields while creating and updating schedules. You won't be able to save a schedule until the flagged content is removed.
Partner connection launch update
The following partner connectors have been added to the Looker Studio Connector Gallery:
- Sitechecker by Sitechecker
- Smart Copilot by Make Me Win
- Odoo Contacts AppiWorks by Jivrus Technologies
- Odoo Documents AppiWorks By Jivrus Technologies
- ChurchSuite by Growing Healthier Churches
- Lumar by Lumar
- Yandex Metrica by Windsor.ai
- Everflow by Windsor.ai
Support for creating custom organization policy constraints in Eventarc Advanced and for creating custom organization policy constraints in Eventarc Standard is generally available for some Eventarc resources.
The GA release of enhanced data residency support in the European Union and United States is temporarily delayed.
When you enable Security Command Center for the first time in an organization, and you enable data residency in the European Union or United States, data residency controls are enforced at rest, in use, and in transit. This feature is in General Availability.
For details, see Planning for data residency and Security Command Center regional endpoints.
You can now create a pre-filtered vector index that indexes only rows in your database that match a specific filter condition. Using a pre-filtered vector index improves both the performance and recall of approximate nearest neighbor (ANN) searchers by restricting the search to only apply to rows that satisfy the filtering condition. For more information, see Filter a vector index.
Vertex AI custom training supports the following accelerators:
- A3 Ultra
- A4
Vertex AI online prediction supports the following accelerators:
- A3 Mega
- A4
For regional availability of accelerators, see Using accelerators.
May 14, 2025
AlloyDB for PostgreSQLThe default major version of PostgreSQL compatibility for new AlloyDB clusters is now PostgreSQL 16.
On May 14, 2025, we released an updated version of Apigee (1-15-0-apigee-4).
Large message payload support in Apigee
Apigee now supports message payloads up to 30MB. For more information, see:
- Message payload size.
Properties
in the ProxyEndpoint configuration elements reference.Properties
in the TargetEndpoint configuration elements reference.
Improvements to the AppGroups functionality
Scopes and attributes can now be added to the AppGroup App Key via a POST operation on the key using the appGroupAppKey. See the updateAppGroupAppKey API for details.
Improvements to the PublishMessage policy
The PublishMessage policy now supports two new elements:
The <UseMessageAsSource> element uses request or response message content as the source of data to be written to Pub/Sub. For more information, see <UseMessageAsSource>.
The <Attributes> element lets you specify string attributes (key/value pairs) to include with the request or response message that is written to Pub/Sub. For more information, see <Attributes>.
Bug ID | Description |
---|---|
391140293 | Resolved scaling issue resulting in 503 errors Added |
391862684 | Resolved issue with requests stuck at Message Processor causing timeouts. |
N/A | Updates to security infrastructure and libraries. |
You can now schedule automated data transfers from Snowflake to BigQuery using the BigQuery Data Transfer Service. This feature is in preview.
BigQuery now supports cross-region transfers for batch loading and exporting data. You can load or export your data from any region or multi-region to any other region or multi-region using a single bq load
, LOAD DATA
, bq extract
, or EXPORT DATA
statement. This feature is generally available (GA).
Vector indexes support the TreeAH index type, which uses Google's ScaNN algorithm. The TreeAH index is optimized for efficient batch processing, capable of handling anywhere from a few thousand to hundreds of thousands of embeddings at once. This feature is generally available (GA).
A new Cloud Composer release has started on May 14, 2025. Get ready for upcoming changes and features as we roll out the new release to all regions. This release is in progress at the moment. Listed changes and features might not be available in some regions yet.
It is now possible to migrate from Cloud Composer 1 to Cloud Composer 3 using snapshots in all regions supported by Cloud Composer 3. The gradual rollout of this feature is finished.
It is now possible to restart the Airflow web server through Cloud Composer API by using the RestartWebServer method.
The default value of the [scheduler]max_tis_per_query
Airflow configuration option is set to 128
. This change fixes the issue with DAGs remaining in the scheduled state in some cases.
Cloud Composer 3 and Cloud Composer 2 no longer support files with gzip encoding (content-type=gzip
).
Before this change, all files that had gzip encoding, including .py
and .zip
files, were processed inconsistently by the DAG processor. After this change, the DAG processor skips all files with gzip encoding. This change doesn't apply to regular .zip
archives. Airflow still decompresses and processes DAG files contained in archives that have no specified encoding.
This change is gradually rolled out to all regions supported by Cloud Composer, except us-central1, us-east4 and europe-west1. It will be rolled out to the remaining regions in one of the future releases.
(Cloud Composer 3) Fixed an issue where the Airflow scheduler failed to initialize and work properly if a custom email backend was enabled. The Airflow scheduler now supports the following email backends:
- airflow.providers.sendgrid.utils.emailer.send_email
- airflow.utils.email.send_email_smtp
This issue affected only the Airflow scheduler. Airflow workers already support these and other backends. If you use an email backend that isn't supported by the scheduler, you can still send email from Airflow workers.
(Cloud Composer 3) Improved the computation of metrics related to snapshots. This change reduces the number of calls made by Cloud Composer to the Cloud Storage API.
(Cloud Composer 2) In Cloud Composer versions 2.11.5 and later, log processing is switching to using OpenTelemetry instead of Fluentd.
This change is gradually rolled out to the asia-south1 and africa-south1 regions. It will be rolled out to more regions in future releases. New and upgraded Cloud Composer 2 environments in the listed regions will get this change.
(Airflow 2.9.3) The apache-airflow-providers-google
package was upgraded to version 15.1.0 in Cloud Composer 2 images and Cloud Composer 3 builds.
For more information about changes, see the apache-airflow-providers-google changelog from version 14.0.0 to version 15.1.0.
(Airflow 2.9.3) Changes in preinstalled packages:
apache-airflow-providers-standard
was upgraded to 1.0.0 from 0.4.0.aiosqlite
was removed from preinstalled packages.json-merge-patch
was removed from preinstalled packages.time-machine
was removed from preinstalled packages.pyjwt
was downgraded to 2.9.0 from 2.10.1.
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.5-build.3 (default)
- composer-3-airflow-2.9.3-build.23
New images are available in Cloud Composer 2:
- composer-2.13.1-airflow-2.10.5 (default)
- composer-2.13.1-airflow-2.9.3
Cloud Composer version 2.8.0 has reached its end of support period.
Global and cross-region load balancers now support enabling traffic isolation on the service load balancing policy. By default, these load balancers use the WATERFALL_BY_REGION
algorithm which allows traffic overflow to other regions when backends in the region closest to the user are either full or unhealthy. Enabling traffic isolation lets the load balancer route traffic only to the region closest to the user, even if all the backends in that region are running at their configured capacity limit. You can also choose to prevent traffic overflow entirely by enabling this feature in STRICT
mode.
For details, see Traffic isolation.
This feature is in Preview.
Cloud SQL for SQL Server now supports TLS connections to Active Directory endpoints without requiring server certificate trust or the use of IP addresses. Existing server certificates will need to be rotated to use this feature.
Release 6.3.1
- A dedicated Cortex-specific Cloud Build Service Account will now be automatically created during the deployment process for both the standard Quickstart demo and the Cortex for Meridian Quickstart demo.
- When executing
gcloud builds submit
command for Cortex Framework deployments, the_BUILD_ACCOUNT
parameter is now required. If you are updating an existing deployment, ensure you provide the appropriate build account in the following format:_BUILD_ACCOUNT='projects/SOURCE_PROJECT/serviceAccounts/SERVICE_ACCOUNT@SOURCE_PROJECT.iam.gserviceaccount.com'
.
- Resolved inconsistencies between the standard and Cortex for Meridian Quickstart demos related to Cloud Build Service Account behavior.
- The Quickstart demo now automatically enables the Data Catalog API during its execution.
- Oracle builds may time out when using a private worker pool created with default parameters.
Create custom commands
You can now configure and use custom commands with IntelliJ Gemini Code Assist (version 1.15.0
). Create, save, and execute your own pre-configured prompts to perform repetitive tasks faster and more easily in the IDE.
To view the custom commands settings, go to Settings > Tools > Gemini > Prompt Library.
Chat responses with error messages now have action buttons for IntelliJ Gemini Code Assist (version 1.15.0
).
MedLM is deprecated. Access to MedLM will no longer be available on or after September 29, 2025.
Mobile SDK 2.12 is released
Mobile SDK 2.12 includes the following updates:
- Added support for the following languages:
- Ukrainian
- English - India
- Hindi
- Romanian
- Croatian
- Russian
- Tagalog
- End-users can receive and download attachments during sessions. The following file types are supported:
- Images: JPEG, JPG, PNG, GIF, WebP
- Video: MP4, MOV, AVI, WMV, WebM
- Audio: MP3, WAV, M4A, WEBA
- Other file types: PDF, DOC, XLS, PPT, CSV, TXT
Preview: You can use the Google Cloud console to create admin clusters and view admin cluster details. For more information, see Create an admin cluster.
New premium versions of the following parsers are now available:
- ZSCALER_WEBPROXY
- ZSCALER_FIREWALL
- ZSCALER_DNS
- ZSCALER_INTERNET_ACCESS
- ZSCALER_VPN
- ZSCALER_ZPA
- ZSCALER_TUNNEL
- ZSCALER_CASB
- ZSCALER_DLP
- ZSCALER_ADMIN_AUDIT
We recommend using the documented topology for each parser.
New premium versions of the following parsers are now available:
- ZSCALER_WEBPROXY
- ZSCALER_FIREWALL
- ZSCALER_DNS
- ZSCALER_INTERNET_ACCESS
- ZSCALER_VPN
- ZSCALER_ZPA
- ZSCALER_TUNNEL
- ZSCALER_CASB
- ZSCALER_DLP
- ZSCALER_ADMIN_AUDIT
We recommend using the documented topology for each parser.
A new status dashboard provides status tracking for Google SecOps SOAR.
Looker 25.8 is expected to include the following changes, features, and fixes:
Expected Looker (original) deployment start: Monday, May 19, 2025
Expected Looker (original) final deployment and download available: Thursday, May 29, 2025
Expected Looker (Google Cloud core) deployment start: Monday, May 19, 2025
Expected Looker (Google Cloud core) final deployment: Monday, June 2, 2025
An issue has been fixed where HTML in a LookML dimension wasn't being applied to Y-axis labels. This feature now performs as expected.
SSL host validation is now enabled by default. If any of your SSL certificates are invalid, certain Looker workflows may break.
The Code Interpreter in Conversational Analytics is now available in Preview. The Code Interpreter translates your natural language questions into Python code and executes that code to provide advanced analysis and visualizations. The Code Interpreter is disabled by default. Admins of Looker (original) instances can manage enablement for the Code Interpreter on the Gemini in Looker admin page. (This release note was added on May 19, 2025.)
You can now create connections using the Amazon Redshift 2.1+ or Amazon Redshift Serverless 2.1+ SQL dialect, both of which use the Redshift JDBC driver. Connections with the original Amazon Redshift SQL dialect option use the Postgres JDBC driver.
The Presto JDBC driver version has been updated to 0.291.
You can now select the JDBC driver version when you create or edit a connection.
The sync_lookml_dashboard
API endpoint now accepts an optional dashboard_ids
parameter to specify a subset of dashboards to synchronize.
The gemini_in_looker
permission can now be applied to selected models on the Looker instance. The Gemini role still applies the gemini_in_looker
permission to all models on the Looker instance; however, if needed, Looker admins can manually restrict use of Gemini in Looker to specific models by creating and assigning a Looker role with gemini_in_looker
permissions on limited models.
When you create a custom measure, suggestions are now displayed for tier filters.
An issue has been fixed where some of the Project API endpoints wouldn't create a fresh dev mode copy of the LookML project files if no dev mode copy already existed. These endpoints now work as expected.
An issue has been fixed where Elite System Activity data could be delayed. This feature now performs as expected.
An issue has been fixed where navigating between Looks could cause the System Activity Explore to correlate an incorrect Look ID with a query ID. This feature now performs as expected.
An issue has been fixed where filtering on a pivoted field while Grid Layout by Row was enabled could return a server error. This feature now performs as expected.
An issue has been fixed where duplicating a dashboard tile and editing it could cause the tile to load indefinitely. This feature now performs as expected.
An issue has been fixed where scheduled reports could include limited columns even if All Results was enabled for the schedule. This feature now performs as expected.
An issue has been fixed where links in data tables couldn't be clicked. This feature now performs as expected.
An issue has been fixed where changes to the row limit and visualization configuration that were applied by custom visualizations were not saved in the System Activity query record. This feature now performs as expected.
An issue has been fixed where Looks could appear before dashboards in embedded folder navigation. This feature now performs as expected.
An issue has been fixed where running queries would not be canceled if a user navigated away from a dashboard, for example, by clicking an Explore from here link. This feature now performs as expected.
An issue has been fixed where all the folders in the IDE would collapse when a user toggled a folder on a new session. This feature now performs as expected.
An issue has been fixed where a scatterplot visualization could crash if there were less than three rows of data and clustering was enabled. This feature now performs as expected.
An issue has been fixed where additional queries that were used for totals and pivots would not include context comments. These queries now include context comments, and this feature performs as expected.
An issue has been fixed where blank measure filters could prevent Looker from correctly displaying subtotals in table visualizations. This feature now performs as expected.
An issue has been fixed where the BigQuery storage project ID could be set to a user attribute value, even though Looker doesn't support user attributes in this field. The user interface for the Connections page has been updated, and this feature now performs as expected.
Previously, using Application Default Credentials (ADC) with a BigQuery connection caused Looker to incorrectly display the service account file upload button on the PDT Override panel; this button has now been removed and this feature now performs as expected.
May 13, 2025
BigQueryThe following SQL features are now generally available (GA) in BigQuery:
GROUP BY STRUCT
and theSELECT DISTINCT
clause.GROUP BY ARRAY
and theSELECT DISTINCT
clause.GROUP BY ALL
clause.
You can export query results from Bigtable Studio. This feature is generally available (GA).
For more information, see Manage your data using Bigtable Studio.
The MariaDB Batch Source plugin versions 1.11.7 and 1.12.2 are available in Cloud Data Fusion versions 6.10.1 and 6.11.0 respectively. This release includes the following changes:
Fixed an issue related to the MariaDB
YEAR
data type causing pipeline failures when the date type was manually changed toDATE
. Validation for this specific scenario is now skipped (PLUGIN-1888).Fixed an issue that caused pipeline failures with a
java.lang.ClassNotFoundException: Class io.cdap.plugin.db.DBRecord not found
error, which was due to a class loading problem (PLUGIN-1874).Added a committer to Database plugins to manage committing or rolling back entire tasks, depending on whether the task completes successfully or is aborted (PLUGIN-1815).
Labels you previously set for your Cloud Run functions using either
gcloud functions
commands or the Cloud Functions v2 API propagate to Cloud Run when you deploy your functions in Cloud Run. For more information on creating labels in Cloud Run, see Configure labels for services.
Labels you previously set for your Cloud Run functions using either
gcloud functions
commands or the Cloud Functions v2 API propagate to Cloud Run when you deploy your functions in Cloud Run. For more information on creating labels in Cloud Run, see Configure labels for services.
Google has applied fixes for a vulnerability (CVE-2024-45332) affecting the following Intel processors: CascadeLake, Ice Lake XeonSP, Ice Lake XeonD, Sapphire Rapids and Emerald Rapids. For more information, see the GCP-2025-025 security bulletin.
Bulk export of universal catalog metadata is generally available (GA).
You can export universal catalog metadata into Cloud Storage and then use it for tasks that require comprehensive retrieval of metadata. You can also query and analyze the exported metadata in BigQuery.
For more information, see Export metadata.
Datastream is now available in the europe-north2
(Stockholm) region. For the list of all available regions, see IP allowlists and regions.
Version 3.34 is released
All release notes published on this date are part of version 3.34.
The timing of the update to your instance depends on the deployment schedule that you have chosen. For more information, see Deployment schedules.
Co-browse is renamed to Screen Share
We've renamed the Co-browse capability to Screen Share. We've made this change in the user interface and in the documentation. However, we haven't renamed any endpoint, property, object, or other programmatic element in the APIs or the SDKs for this update.
Manual wrap-up is automatically assigned to the last completed chat
When an agent manually enters wrap-up status, wrap-up is automatically assigned to the agent's last completed chat. For more information, see Manual wrap-up.
Spelling and grammar check is available for SMS and WhatsApp sessions
Spelling and grammar check is now available for SMS and WhatsApp chat sessions. For more information, see Agent Assist for chat.
Virtual agent to virtual agent chat transfers
A virtual agent can now transfer a chat session to another virtual agent by transferring to the queue that the destination virtual agent is assigned to. For more information, see Virtual agent to virtual agent transfers.
The following issues were addressed in this release:
- Fixed an issue that prevented agents from calling other agents using a phone number with an extension.
- Fixed an issue where a phone number with an extension and a comma separator was not displaying correctly.
- Fixed an issue where some properties in the session metadata file were not correct for a session that was monitored by another user.
- Fixed an issue where chat duration was incorrect in reporting.
- Fixed an issue where a user was unable to change from the wrap-up status to another status.
- Fixed an issue where call IDs mistakenly appeared in agent activity timeline reports.
- Fixed an issue where the scroll bar didn't appear in the chat navigation panel of the chat adapter. This prevented agents from scrolling to chats that were hidden from view.
- Fixed an issue where error messages were mistakenly sent to end-users while they were waiting for a virtual agent to connect to their session.
- Fixed an issue where the Performance Overview Dashboard was displaying incorrect information on the Chats > Queue Abandoned and Virtual Agent Chat > Total Escalations tiles.
- Fixed an issue where sessions that were escalated by a virtual agent arrived in the destination queue and were never assigned to an agent because of an error in prioritization.
- Fixed an issue where auto-generated session summaries for the virtual agent segments of a session were not appearing in the agent adapter.
- Fixed an issue where a Screen Share error message mistakenly appeared the next time Screen Share was attempted.
- Fixed an issue where links that agents sent to end-users in a chat session did not have underscores, despite rich messaging being turned on.
- Fixed an issue where email was causing abnormally high CPU usage.
- Fixed an issue where message preview was not working in the agent adapter for web SDK and chat.
- Fixed an issue where the incorrect error message appeared when SSO sign-in failed.
- Fixed an issue where manual wrap-up caused high CPU usage.
- Fixed an issue where Chat ID was not available as an incoming field type when adding a parameter for post-session chat transfers.
- Fixed an issue where agents were unable to send messages in the chat adapter.
- Fixed an issue where the chat shortcut list continued to display after the agent deleted the shortcut keyword from the chat text field.
- Fixed an issue where chat shortcut categories were appearing in the shortcut list in the chat adapter despite the fact that they contained no chat shortcuts.
- Fixed an issue in the chat adapter where the View original and View translation links where not translated into the language of the chat adapter.
- Fixed a Workforce Management issue where login durations for events that spanned multiple intervals were incorrectly reported.
- Fixed a Workforce Management issue where short abandoned chat counts were incorrectly reported.
- Fixed a Workforce Management issue where the historical or ready time values exceeded 900 seconds.
- Fixed an Workforce Management issue where reporting data was missing for sessions over 45 minutes.
- Fixed a Workforce Management issue where hold duration was counted multiple times in reporting.
- Fixed a Workforce Management issue where query performance was sub-optimal.
- Fixed a Workforce Management issue where the OutboundCount and OutboundHandleTime calculations were incorrect in the AgentSystem report.
- Fixed a Workforce Management issue where agent queue data was not given the same treatment for calls as it was for chats.
- Fixed an agent desktop issue where the calls waiting and chats waiting fields in the menu bar displayed incorrect text when the French language was selected.
- Fixed an agent desktop issue where the Insert summary button (for inserting a generated session summary) appeared during wrap-up even when session summarization was turned off.
- Fixed an agent desktop issue where a View Previous banner mistakenly appeared when clicking the chats field in the menu bar.
- Fixed an agent desktop issue in the session data feed, where the date and time were not formatted correctly in French.
- Fixed an agent desktop issue where an agent who transferred a session and then left it was unable to see the chat adapter after being re-added to the session.
GKE now provides insights and recommendations that help you to identify and troubleshoot clusters with Custom Resource Definitions that contain an invalid or malformed Certificate Authority bundle, which might disrupt cluster operations. Implementing the recommendation helps you to keep your clusters stable and performant.
GKE Autopilot clusters fail to update the cgroup_mode
field and display the following error:
ERROR: (gcloud.container.clusters.update)
ResponseError: code=400,
message=INVALID_ARGUMENT: invalid node_pool_auto_config.linux_node_config.
Allowed fields are: ["cgroup_mode"]
This issue occurs in all GKE versions. A fix for this issue is in progress. For more information, see Migrate nodes to Linux cgroupv2.
You can now create Looker (Google Cloud core) instances that use Private Service Connect with a hybrid network configuration. Instances that have this type of configuration will allow secure inbound access through a web URL and will connect to external services through a private network.
Spanner now supports the INTERVAL
data type in GoogleSQL and PostgreSQL, which represents a duration or an amount of time.
For more information, see Interval functions in GoogleSQL and PostgreSQL data types.
Spanner now supports the SPLIT_SUBSTR()
GoogleSQL function, which splits an input string using a delimiter and returns a substring composed of a specific number of segments, starting from a given segment index.
Spanner also supports the following GoogleSQL aliases:
ADDDATE()
: Alias forDATE_ADD()
SUBDATE()
: Alias forDATE_SUB()
LCASE()
: Alias forLOWER()
UCASE()
: Alias forUPPER()
May 12, 2025
BigQueryA weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-bigquery
2.50.0 (2025-05-06)
Features
- Add WRITE_TRUNCATE_DATA as an enum value for write disposition (#3752) (acea61c)
- bigquery: Add support for reservation field in jobs. (#3768) (3e97f7c)
Dependencies
- Update dependency com.google.api.grpc:proto-google-cloud-bigqueryconnection-v1 to v2.63.0 (#3770) (934389e)
- Update dependency com.google.apis:google-api-services-bigquery to v2-rev20250404-2.0.0 (#3754) (1381c8f)
- Update dependency com.google.apis:google-api-services-bigquery to v2-rev20250427-2.0.0 (#3773) (c0795fe)
- Update dependency com.google.cloud:sdk-platform-java-config to v3.46.3 (#3772) (ab166b6)
- Update dependency com.google.cloud:sdk-platform-java-config to v3.47.0 (#3779) (b27434b)
BigQuery resource utilization charts have the following changes:
- The default timeline shown in the event timeline chart has changed from one to six hours.
- Several improvements have been made to the views, including a new reservation slot usage view. This view helps monitor idle, baseline, and autoscaled slot usage.
This feature is in Preview.
You can now view the Query text section in a BigQuery execution graph to understand how the stage steps are related to the query text. This feature is in preview.
You can now use BigQuery and BigQuery DataFrames to enable multimodal analysis, transformation, and data engineering (ELT) workflows in both SQL and Python. Use multimodal data features to do the following:
Integrate unstructured data into standard tables by using
ObjectRef
values, and then work with this data in analysis and transformation workflows by usingObjectRefRuntime
values.Use generative AI to analyze multimodal data and generate embeddings by using BigQuery ML SQL functions or BigQuery DataFrames methods with Gemini and multimodal embedding models.
Create multimodal DataFrames in BigQuery DataFrames, and then use object transformation methods to transform images and chunk PDF files.
Use Python user-defined functions (UDFs) to transform images and chunk PDF files.
This feature is in Preview.
A weekly digest of client library updates from across the Cloud SDK.
A weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-logging
3.22.3 (2025-05-06)
Bug Fixes
- deps: Update the Java code generator (gapic-generator-java) to 2.56.3 (844f4fa)
Dependencies
A vulnerability (CVE-2024-28956) affecting Intel Cascade Lake processors and Intel Ice Lake processors was discovered and is being addressed. For more information, see the GCP-2025-024 security bulletin.
Public preview: In a managed instance group (MIG), you can use a health check to monitor your application health without triggering repairs of an unhealthy VM, if the application fails the health check. You can prevent the MIG from repairing an unhealthy VM by turning off autohealing. For more information, see Turn off repairs in a MIG.
cos-113-18244-382-15
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.134 | v24.0.9 | v1.7.27 | See List |
Fixed issue where modinfo could not display module signatures.
Updated apparmor to 3.1.6. This fixes CVE-2016-1585.
Upgraded containerd to 1.7.27. Fixes CVE-2024-40635.
Fixed CVE-2024-50063 in the Linux kernel.
Fixed CVE-2024-26739 in the Linux kernel.
Fixed CVE-2025-21853 in the Linux kernel.
Fixed KCTF-342debc in the Linux kernel.
Fixed KCTF-3df275e in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812040 -> 812054
cos-dev-125-19041-0-0
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.89 | v27.5.1 | v2.0.4 | See List |
Upgraded app-admin/google-guest-configs to v20250501.00.
Added support for 7th generation TPU devices.
Updated the Linux kernel to v6.6.89.
Increased kdump memory reservation.
Fixed issue where modinfo could not display module signatures.
Updated apparmor to 3.1.6. This fixes CVE-2016-1585.
Runtime sysctl changes:
- Changed: fs.file-max: 811773 -> 811729
cos-117-18613-263-13
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v24.0.9 | v1.7.27 | See List |
Upgraded app-admin/google-guest-configs to v20250501.00.
Added support for 7th generation TPU devices.
Fixed issue where modinfo could not display module signatures.
Updated apparmor to 3.1.6. This fixes CVE-2016-1585.
Upgraded containerd to 1.7.27. Fixes CVE-2024-40635.
Fixed KCTF-3df275e in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811816 -> 811830
cos-109-17800-519-7
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.135 | v24.0.9 | v1.7.27 | See List |
Fixed issue where modinfo could not display module signatures.
Updated apparmor to 3.1.6. This fixes CVE-2016-1585.
Upgraded containerd to 1.7.27. Fixes CVE-2024-40635.
Updated NVIDIA GPU drivers to v535.247.01 for default/ R535, v550.163.01 for R550 and v570.133.20 for latest/R570. This resolves CVE‑2025‑23244.
Fixed CVE-2024-26739 in the Linux kernel.
Fixed KCTF-3df275e in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812287 -> 812270
cos-121-18867-90-23
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
Upgraded app-admin/google-guest-configs to v20250501.00.
Added support for 7th generation TPU devices.
Fixed issue where modinfo could not display module signatures.
Updated apparmor to 3.1.6. This fixes CVE-2016-1585.
Fixed KCTF-3df275e in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811788 -> 811731
A weekly digest of client library updates from across the Cloud SDK.
Go
Changes for dataflow/apiv1beta3
0.11.0 (2025-05-06)
Features
- dataflow: A new enum
StreamingMode
is added (2f22244) - dataflow: A new field
bugs
is added to message.google.dataflow.v1beta3.SdkVersion
(2f22244) - dataflow: A new field
data_sampling
is added to message.google.dataflow.v1beta3.DebugOptions
(2f22244) - dataflow: A new field
default_streaming_mode
is added to message.google.dataflow.v1beta3.TemplateMetadata
(2f22244) - dataflow: A new field
default_value
is added to message.google.dataflow.v1beta3.ParameterMetadata
(2f22244) - dataflow: A new field
disk_size_gb
is added to message.google.dataflow.v1beta3.RuntimeEnvironment
(2f22244) - dataflow: A new field
dynamic_destinations
is added to message.google.dataflow.v1beta3.PubsubLocation
(2f22244) - dataflow: A new field
enable_launcher_vm_serial_port_logging
is added to message.google.dataflow.v1beta3.FlexTemplateRuntimeEnvironment
(2f22244) - dataflow: A new field
enum_options
is added to message.google.dataflow.v1beta3.ParameterMetadata
(2f22244) - dataflow: A new field
group_name
is added to message.google.dataflow.v1beta3.ParameterMetadata
(2f22244) - dataflow: A new field
hidden_ui
is added to message.google.dataflow.v1beta3.ParameterMetadata
(2f22244) - dataflow: A new field
image_repository_cert_path
is added to message.google.dataflow.v1beta3.ContainerSpec
(2f22244) - dataflow: A new field
image_repository_password_secret_id
is added to message.google.dataflow.v1beta3.ContainerSpec
(2f22244) - dataflow: A new field
image_repository_username_secret_id
is added to message.google.dataflow.v1beta3.ContainerSpec
(2f22244) - dataflow: A new field
name
is added to message.google.dataflow.v1beta3.ListJobsRequest
(2f22244) - dataflow: A new field
parent_name
is added to message.google.dataflow.v1beta3.ParameterMetadata
(2f22244) - dataflow: A new field
parent_trigger_values
is added to message.google.dataflow.v1beta3.ParameterMetadata
(2f22244) - dataflow: A new field
runtime_updatable_params
is added to message.google.dataflow.v1beta3.Job
(2f22244) - dataflow: A new field
satisfies_pzi
is added to message.google.dataflow.v1beta3.Job
(2f22244) - dataflow: A new field
service_resources
is added to message.google.dataflow.v1beta3.Job
(2f22244) - dataflow: A new field
step_names_hash
is added to message.google.dataflow.v1beta3.PipelineDescription
(2f22244) - dataflow: A new field
straggler_info
is added to message.google.dataflow.v1beta3.WorkItemDetails
(2f22244) - dataflow: A new field
straggler_summary
is added to message.google.dataflow.v1beta3.StageSummary
(2f22244) - dataflow: A new field
streaming_mode
is added to message.google.dataflow.v1beta3.Environment
(2f22244) - dataflow: A new field
streaming_mode
is added to message.google.dataflow.v1beta3.FlexTemplateRuntimeEnvironment
(2f22244) - dataflow: A new field
streaming_mode
is added to message.google.dataflow.v1beta3.RuntimeEnvironment
(2f22244) - dataflow: A new field
streaming
is added to message.google.dataflow.v1beta3.TemplateMetadata
(2f22244) - dataflow: A new field
supports_at_least_once
is added to message.google.dataflow.v1beta3.TemplateMetadata
(2f22244) - dataflow: A new field
supports_exactly_once
is added to message.google.dataflow.v1beta3.TemplateMetadata
(2f22244) - dataflow: A new field
trie
is added to message.google.dataflow.v1beta3.MetricUpdate
(2f22244) - dataflow: A new field
update_mask
is added to message.google.dataflow.v1beta3.UpdateJobRequest
(2f22244) - dataflow: A new field
use_streaming_engine_resource_based_billing
is added to message.google.dataflow.v1beta3.Environment
(2f22244) - dataflow: A new field
user_display_properties
is added to message.google.dataflow.v1beta3.JobMetadata
(2f22244) - dataflow: A new message
DataSamplingConfig
is added (2f22244) - dataflow: A new message
HotKeyDebuggingInfo
is added (2f22244) - dataflow: A new message
ParameterMetadataEnumOption
is added (2f22244) - dataflow: A new message
RuntimeUpdatableParams
is added (2f22244) - dataflow: A new message
SdkBug
is added (2f22244) - dataflow: A new message
ServiceResources
is added (2f22244) - dataflow: A new message
Straggler
is added (2f22244) - dataflow: A new message
StragglerInfo
is added (2f22244) - dataflow: A new message
StragglerSummary
is added (2f22244) - dataflow: A new message
StreamingStragglerInfo
is added (2f22244) - dataflow: A new method_signature
job,update_mask
is added to methodUpdateJob
in serviceJobsV1Beta3
(2f22244) - dataflow: A new value
BIGQUERY_TABLE
is added to enumParameterType
(2f22244) - dataflow: A new value
BOOLEAN
is added to enumParameterType
(2f22244) - dataflow: A new value
ENUM
is added to enumParameterType
(2f22244) - dataflow: A new value
GO
is added to enumLanguage
(2f22244) - dataflow: A new value
JAVASCRIPT_UDF_FILE
is added to enumParameterType
(2f22244) - dataflow: A new value
KAFKA_READ_TOPIC
is added to enumParameterType
(2f22244) - dataflow: A new value
KAFKA_TOPIC
is added to enumParameterType
(2f22244) - dataflow: A new value
KAFKA_WRITE_TOPIC
is added to enumParameterType
(2f22244) - dataflow: A new value
KMS_KEY_NAME
is added to enumParameterType
(2f22244) - dataflow: A new value
MACHINE_TYPE
is added to enumParameterType
(2f22244) - dataflow: A new value
NUMBER
is added to enumParameterType
(2f22244) - dataflow: A new value
SERVICE_ACCOUNT
is added to enumParameterType
(2f22244) - dataflow: A new value
WORKER_REGION
is added to enumParameterType
(2f22244) - dataflow: A new value
WORKER_ZONE
is added to enumParameterType
(2f22244)
Bug Fixes
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
- dataflow: An existing oauth_scope `https (2f22244)
Documentation
- dataflow: A comment for enum
JobState
is changed (2f22244) - dataflow: A comment for enum
WorkerIPAddressConfiguration
is changed (2f22244) - dataflow: A comment for enum value
JOB_VIEW_ALL
in enumJobView
is changed (2f22244) - dataflow: A comment for field
additional_experiments
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
additional_user_labels
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
bypass_temp_dir_validation
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
capabilities
in message.google.dataflow.v1beta3.SdkHarnessContainerImage
is changed (2f22244) - dataflow: A comment for field
current_state
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
dataset
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
debug_options
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
dump_heap_on_oom
in message.google.dataflow.v1beta3.FlexTemplateRuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
dynamic_template
in message.google.dataflow.v1beta3.LaunchTemplateRequest
is changed (2f22244) - dataflow: A comment for field
enable_hot_key_logging
in message.google.dataflow.v1beta3.DebugOptions
is changed (2f22244) - dataflow: A comment for field
enable_streaming_engine
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
environment
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
flex_resource_scheduling_goal
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
gcs_path
in message.google.dataflow.v1beta3.DynamicTemplateLaunchParams
is changed (2f22244) - dataflow: A comment for field
gcs_path
in message.google.dataflow.v1beta3.LaunchTemplateRequest
is changed (2f22244) - dataflow: A comment for field
id
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
ip_configuration
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
job_name
in message.google.dataflow.v1beta3.LaunchTemplateParameters
is changed (2f22244) - dataflow: A comment for field
kms_key_name
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
launch_parameters
in message.google.dataflow.v1beta3.LaunchTemplateRequest
is changed (2f22244) - dataflow: A comment for field
location
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
machine_type
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
max_workers
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
name
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
network
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
num_workers
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
project_id
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
requested_state
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
save_heap_dumps_to_gcs_path
in message.google.dataflow.v1beta3.FlexTemplateRuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
service_account_email
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
service_account_email
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
service_kms_key_name
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
service_options
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
set
in message.google.dataflow.v1beta3.MetricUpdate
is changed (2f22244) - dataflow: A comment for field
subnetwork
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
temp_location
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
transform_name_mapping
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
type
in message.google.dataflow.v1beta3.Job
is changed (2f22244) - dataflow: A comment for field
worker_region
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
worker_region
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
worker_zone
in message.google.dataflow.v1beta3.Environment
is changed (2f22244) - dataflow: A comment for field
worker_zone
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for field
zone
in message.google.dataflow.v1beta3.RuntimeEnvironment
is changed (2f22244) - dataflow: A comment for message
DynamicTemplateLaunchParams
is changed (2f22244) - dataflow: A comment for message
Job
is changed (2f22244) - dataflow: A comment for message
JobExecutionStageInfo
is changed (2f22244) - dataflow: A comment for message
JobMetrics
is changed (2f22244) - dataflow: A comment for message
LaunchTemplateParameters
is changed (2f22244) - dataflow: A comment for message
MetricUpdate
is changed (2f22244) - dataflow: A comment for message
SdkHarnessContainerImage
is changed (2f22244) - dataflow: A comment for message
Step
is changed (2f22244) - dataflow: A comment for method
AggregatedListJobs
in serviceJobsV1Beta3
is changed (2f22244) - dataflow: A comment for method
CreateJob
in serviceJobsV1Beta3
is changed (2f22244) - dataflow: A comment for method
CreateJobFromTemplate
in serviceTemplatesService
is changed (2f22244) - dataflow: A comment for method
GetTemplate
in serviceTemplatesService
is changed (2f22244) - dataflow: A comment for method
LaunchTemplate
in serviceTemplatesService
is changed (2f22244) - dataflow: A comment for method
ListJobs
in serviceJobsV1Beta3
is changed (2f22244) - dataflow: A comment for service
FlexTemplatesService
is changed (2f22244)
Dataproc Serverless for Spark: Spark UI for Dataproc Serverless batches and interactive sessions, which lets you monitor and debug your serverless Spark workloads, now features Event Timeline and Task Quantile views for enhanced troubleshooting.
In GKE version 1.33 and later, the Compute Engine persistent disk CSI Driver supports provisioning Hyperdisk Balanced High Availability volumes in the ReadWriteOnce
, ReadWriteOncePod
, and ReadWriteMany
access modes. For more information, see Provisioning Hyperdisk Balanced High Availability volumes.
A feature rollout on May 8, 2025, introduced new APIs that may require updated permissions for custom roles to access the detection UI page.
If you encounter access errors, update your permissions, as needed, or select Revert to Previous Detection Table on the detection page to revert to the previous UI.
YARA-L search with data tables updates
- Data tables are now accessible from the Investigation menu, instead of Detection, in the web interface.
- Data tables can now be used as a data source in search queries.
- Role-based access control (RBAC) has been added to manage access to data tables.
A feature rollout on May 8, 2025, introduced new APIs that may require updated permissions for custom roles to access the detection UI page.
If you encounter access errors, update your permissions, as needed, or select Revert to Previous Detection Table on the detection page to revert to the previous UI.
YARA-L search with data tables updates
- Data tables are now accessible from the Investigation menu, instead of Detection, in the web interface.
- Data tables can now be used as a data source in search queries.
- Role-based access control (RBAC) has been added to manage access to data tables.
A weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-pubsub
1.139.3 (2025-05-06)
Dependencies
- Update dependency com.google.cloud:sdk-platform-java-config to v3.47.0 (#2414) (d78823f)
- Update googleapis/sdk-platform-java action to v2.57.0 (#2415) (1ddf9b8)
1.139.2 (2025-05-05)
Bug Fixes
- deps: Update the Java code generator (gapic-generator-java) to 2.56.3 (2b928a8)
Dependencies
- Update dependency com.google.cloud:google-cloud-bigquery to v2.49.2 (#2399) (ff48708)
- Update dependency com.google.cloud:google-cloud-core to v2.54.3 (#2393) (0ffa26a)
- Update dependency com.google.cloud:google-cloud-storage to v2.52.1 (#2396) (283a6e1)
- Update dependency com.google.cloud:sdk-platform-java-config to v3.46.3 (#2406) (8963ed0)
You can use custom constraints with Organization Policy to provide more granular control over specific fields for some Cloud Quotas resources. For more information, see Use custom organization policies. This feature is available in Preview.
By default, scans for MAC_ADDRESS
findings now include MAC_ADDRESS_LOCAL
findings. Previously, you could only use this functionality if you set the InfoType.version
of MAC_ADDRESS
to latest
in your InspectConfig
.
You can still use the old version of MAC_ADDRESS
by setting its InfoType.version
to legacy
or by using the MAC_ADDRESS_UNIVERSAL
infoType. In 90 days, the new functionality will be promoted to legacy
.
You can exclude IP address ranges from being used for automatic IP address allocation for internal ranges. This feature is available in General Availability. For more information, see Reserve internal ranges.
reCAPTCHA Mobile SDK v18.7.1 is now available for Android
This version contains reliability improvements in the execute()
method.
May 11, 2025
Google SecOps SOARRelease 6.3.45 is being rolled out to the first phase of regions as listed here.
This release contains internal and customer bug fixes.
May 10, 2025
AlloyDB for PostgreSQLDue to a change to report replay_lsn
more accurately during parallel replay, metrics might show a slightly higher replication lag.
Release 6.3.44 is now available for all regions.
May 09, 2025
AlloyDB OmniAlloyDB Omni version 16.3.0 with Red Hat Universal Base Image (UBI) as a base image is generally available (GA). The image is RedHat certified and can also be accessed from the Red Hat Ecosystem Catalog. Version UBI 16.3.0 includes third-party extensions, including PostGIS and Orafce, which you can install on RPM-based Linux distributions. For more information about using UBI in AlloyDB Omni, see Install AlloyDB Omni on a VM.
AlloyDB Omni version 16.3.0 with Red Hat Universal Base Image (UBI) as a base image is generally available (GA). The image is RedHat certified and can also be accessed from the Red Hat Ecosystem Catalog. Version UBI 16.3.0 includes third-party extensions, including PostGIS and Orafce, which you can install on RPM-based Linux distributions. For more information about using UBI in AlloyDB Omni, see Install AlloyDB Omni on a VM.
Public preview: A Security Risk Overview dashboard for Compute Engine, available in the Google Cloud console, shows the top Security Command Center findings that affect your Compute Engine resources.
New Dataproc on Compute Engine subminor image versions:
- 2.0.140-debian10, 2.0.140-rocky8, 2.0.140-ubuntu18
- 2.1.88-debian11, 2.1.88-rocky8, 2.1.88-ubuntu20, 2.1.88-ubuntu20-arm
- 2.2.56-debian12, 2.2.56-rocky9, 2.2.56-ubuntu22
VMware Engine ve2
nodes are available in Montreal, Canada (northamerica-northeast1
).
(2025-R18) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- Version 1.32.3-gke.1927002 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.32.2-gke.1297002
- 1.32.3-gke.1785000
- 1.32.3-gke.1927000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.3-gke.1785003 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.33 to version 1.33.0-gke.1552000 with this release.
Regular channel
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
Stable channel
There are no new releases in the Stable channel.
Extended channel
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2650000
- 1.27.16-gke.2703000
- 1.28.15-gke.2097000
- 1.28.15-gke.2169000
- 1.29.15-gke.1240000
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2121000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2664000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2121000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
No channel
- Version 1.32.2-gke.1297002 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.31.6-gke.1020000
- 1.32.3-gke.1785000
- 1.32.3-gke.1927000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
1.33 is now available in the Rapid channel
Kubernetes 1.33 is now available in the Rapid channel. For more information about the content of Kubernetes 1.33, read the Kubernetes 1.33 Release Notes.
New features in 1.33
- New v1beta2 versions of the Kubernetes Dynamic Resource Allocation (DRA) APIs will be available (because this is a beta API, using it in GKE clusters requires opt-in). For more information about using DRA in GKE, see About dynamic resource allocation in GKE.
- In-Place Pod Resize (Public Preview) allows you to change the CPU and memory requests and limits assigned to containers within a running Pod (limitations apply) through the new
resize
pod subresource (on-by-default), often without requiring a container restart significantly decreasing service disruptions. For more information, see Resize CPU and Memory Resources assigned to Containers. - Sidecar Containers graduated to stable, enabling the "sidecar pattern". initContainers with
restartPolicy: Always
will start before application containers and remain running throughout the pod's lifecycle, terminating after the main containers exit. - Streaming List Response Encoding enables efficient handling of requests for large object collections, improving API server reliability and performance.
Multiple Service CIDRs is now generally available, allowing cluster administrators to dynamically increase the number of IP addresses available for
type: ClusterIP
Services (by creating new ServiceCIDR objects).
Deprecated in 1.33
The gitRepo volume driver is deprecated and disabled for security reasons. For more information, see KEP-5040.
Removed in 1.33
The status.nodeInfo.kubeProxyVersion
field in the Node API object is no longer populated in 1.33 and later. This field actually reported the kubelet version, not the kube-proxy
version. You can use status.nodeInfo.kubeletVersion
to get the kubelet version. For more information, see KEP-4004.
Other changes in 1.33
containerd 2.0 is supported. For more information, see Migrate nodes to containerd 2.
(2025-R18) Version updates
- Version 1.32.3-gke.1927002 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.11-gke.1131000
- 1.31.7-gke.1212000
- 1.32.2-gke.1297002
- 1.32.3-gke.1785000
- 1.32.3-gke.1927000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.3-gke.1785003 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.11-gke.1157000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.7-gke.1265000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.3-gke.1785003 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.33 to version 1.33.0-gke.1552000 with this release.
(2025-R18) Version updates
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
(2025-R18) Version updates
There are no new releases in the Stable channel.
(2025-R18) Version updates
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2650000
- 1.27.16-gke.2703000
- 1.28.15-gke.2097000
- 1.28.15-gke.2169000
- 1.29.15-gke.1240000
- 1.30.10-gke.1070000
- 1.31.6-gke.1064001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2121000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2664000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2121000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
(2025-R18) Version updates
- Version 1.32.2-gke.1297002 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.31.6-gke.1020000
- 1.32.3-gke.1785000
- 1.32.3-gke.1927000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
Google SecOps supports Self Service creation of custom log types. Self service custom log types let you create custom log types instantly instead of going through SecOps support, allowing quicker data onboarding. This feature will be available as a public preview starting the week of May 12, 2025.
Google SecOps supports Self Service creation of custom log types. Self service custom log types let you create custom log types instantly instead of going through SecOps support, allowing quicker data onboarding. This feature will be available as a public preview starting the week of May 12, 2025.
If the Force mobile authentication setting is enabled, mobile users will be logged out after 60 minutes, rather than 30 minutes, of inactivity.
Memorystore for Valkey now provides node-level metrics. This feature is Generally Available (GA). For more information, see Supported monitoring metrics.
A Security Risk Overview dashboard for Compute Engine is available in the Google Cloud console. The dashboard, available in Preview, shows the top Security Command Center findings that affect your Compute Engine resources.
May 08, 2025
AlloyDB for PostgreSQLAlloyDB supports IAM authentication in AlloyDB Studio. For more information, see Choose a database authentication method.
You can now use additional concurrency settings for heterogeneous SQL Server migration jobs with Database Migration Service. This lets you adjust the migration process to better align with your scenario.
For information about creating migration jobs using the new full dump configuration and maximum concurrent connection settings, see:
- Create a migration job in the SQL Server to Cloud SQL for PostgreSQL documentation
- Create a migration job in the SQL Server to AlloyDB for PostgreSQL documentation
A new release is available. This release may include some or all of the following: general performance improvements, bug fixes, and updates to the API reference documentation.
Global external Application Load Balancers that use HTTPS as the backend service protocol can now negotiate TLS 1.3 for the connection from the load balancer to the backend.
For more details, see TLS support.
This capability is available in General Availability.
Log Analytics can now automatically infer fields of a column when the data type is JSON. You can also view how often these inferred fields appear in your data.
If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA
) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.
For users of the Cloud SQL Auth Proxy:
- If the Cloud SQL instance to which you're connecting is using shared certificate authority (CA) for its
serverCaMode
setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later. - If the Cloud SQL instance to which you're connecting is using customer-managed CA for its
serverCaMode
setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.
If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA
) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.
For users of the Cloud SQL Auth Proxy:
- If the Cloud SQL instance to which you're connecting is using shared certificate authority (CA) for its
serverCaMode
setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later. - If the Cloud SQL instance to which you're connecting is using customer-managed CA for its
serverCaMode
setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.
If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA
) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.
For users of the Cloud SQL Auth Proxy:
- If the Cloud SQL instance to which you're connecting is using shared certificate authority (CA) for its
serverCaMode
setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later. - If the Cloud SQL instance to which you're connecting is using customer-managed CA for its
serverCaMode
setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.
New Dataproc Serverless for Spark runtime versions:
- 1.1.102
- 1.2.46
- 2.2.46
In GKE version 1.32 and later, GKE Sandbox (gVisor) can now be configured with SYS_ADMIN privileges in GKE Autopilot. This lets you use Docker-in-Docker with gVisor in GKE Autopilot.
ClusterProfile sync is now available to generate a cluster inventory for an existing fleet. A cluster inventory lets you work with open source and third party integrations that use the ClusterProfile specification.
New grid lines options for cartesian charts
New grid line options let you set colors and line styles for individual axis grid lines, which makes it easier to distinguish between left or right y-axis grid lines.
The new grid line options are available only for cartesian charts in reports that have modern charts enabled.
You can use custom constraints to define your own restrictions on Google Cloud services for Network Connectivity Center resources. To learn about which Network Connectivity Center resources support custom constraints, and some sample use cases, see Use custom organization policies for Network Connectivity Center.
This feature is available in General Availability for the following resources:
- Hubs
- Spokes
It is available in Public preview for the Groups resource.
The following Security Command Center Enterprise pages that you previously accessed through the Google Security Operations console are now under Security Command Center in the Google Cloud console:
- Risk Overview
- Issues
- Assets (previously called resources)
- Findings
The Security Command Center Enterprise left navigation also includes links to pages in the Google Security Operations console. For information about this navigation and accessing Google Security Operations pages, see Security Command Center Enterprise console.
Security Command Center Enterprise uses predefined security graph rules to identify issues. This feature is in Preview.
For more information, see Predefined security graph rules.
May 07, 2025
AlloyDB for PostgreSQLYou can migrate from Cloud SQL for PostgreSQL to AlloyDB for PostgreSQL using your Cloud SQL for PostgreSQL backup (GA). The Google Cloud CLI is also supported. For more information, see Migrate from Cloud SQL for PostgreSQL to AlloyDB.
AlloyDB lets you configure a deny maintenance period on clusters running the latest version. The feature is generally available (GA).
You can now build a vector embedding Extract, Transform, Load (ETL) pipeline that lets you generate and ingest embeddings from files or real time sources to AlloyDB using Google Cloud Dataflow. For more information, see Build realtime vector embedding pipeline for AlloyDB with Dataflow.
The following products are now supported by the following control packages. See supported products for more information:
- Cloud Build, Cloud SQL for PostgreSQL, Cloud Workstations, Document AI, Firebase Security Rules, Cloud OS Login API, Storage Transfer Service:
- Australia Regions
- Australia Regions with Assured Support
- Brazil Regions
- Canada Protected B
- Canada Regions
- Canada Regions and Support
- Chile Regions
- EU Regions
- EU Regions and Support
- Hong Kong Regions
- India Regions
- Indonesia Regions
- Israel Regions
- Israel Regions and Support
- Japan Regions
- Qatar Regions
- Singapore Regions
- South Africa Regions
- South Korea Regions
- Switzerland Regions
- Taiwan Regions
- UK Regions
- US Regions
- US Regions and Support
- Google Cloud NetApp Volumes:
- Canada Regions
- EU Regions
- Singapore Regions
- US Regions
- Google Security Operations (Google SecOps) SOAR
- Australia Regions:
- Australia Regions with Assured Support
- Brazil Regions
- Chile Regions
- Hong Kong Regions
- India Regions
- Indonesia Regions
- Israel Regions
- Israel Regions and Support
- Japan Regions
- Qatar Regions
- Singapore Regions
- South Africa Regions
- South Korea Regions
- Switzerland Regions
- Taiwan Regions
- UK Regions
- US Regions
- US Regions and Support
You can use Data Boost when you analyze your Bigtable data with BigQuery. This feature is available in Preview.
Data lineage in Cloud Composer now uses OpenLineage in all regions supported by Cloud Composer. For more information about this feature, see the previous announcement.
For newly created Cloud Composer 3 environments, the minimum amount of memory is changed to 2 GB.
For newly created environments, database retention policy is now enabled by default in Google Cloud CLI, API, and Terraform. Before this change, it was enabled by default only in Google Cloud Console.
Improved the environment liveness monitoring. This change addresses some cases of transient failures that caused "Liveness probe failed" warnings in the environment's logs.
(Airflow 2.10.5) The apache-airflow-providers-google
package was upgraded to version 15.1.0 in Cloud Composer 2 images and Cloud Composer 3 builds.
For more information about changes, see the apache-airflow-providers-google changelog from version 14.0.0 to version 15.1.0.
(Airflow 2.10.5) Changes in preinstalled packages:
apache-airflow-providers-standard
was upgraded to 1.0.0 from 0.4.0.aiosqlite
was removed from preinstalled packages.json-merge-patch
was removed from preinstalled packages.time-machine
was removed from preinstalled packages.
The default version of Airflow is changed to 2.10.5.
Airflow 2.10.2 is no longer included in Cloud Composer images and builds.
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.5-build.2 (default)
- composer-3-airflow-2.9.3-build.22
New images are available in Cloud Composer 2:
- composer-2.13.0-airflow-2.10.5 (default)
- composer-2.13.0-airflow-2.9.3
Cloud Composer versions 2.7.0 and 2.7.1 have reached their end of support period.
Version 2.56.0 of the Ops Agent using the Prometheus receiver can fail to send metrics and report negative start times. To resolve this issue, downgrade to version 2.55.0. For more information, see Known issue: Ops Agent version 2.56.0 fails to send metrics.
You can migrate to AlloyDB for PostgreSQL using your Cloud SQL for PostgreSQL backup (GA). The Google Cloud CLI is also supported. For more information, see Migrate from Cloud SQL for PostgreSQL to AlloyDB.
Custom connectors for managed connectivity pipelines are available for a variety of third-party data sources. These connectors are contributed by the community. For more information, see Community-contributed custom connectors.
Dataproc on Compute Engine: The default enabling of the following cluster properties previously announced to occur on May 10, 2025 (see the February 10, 2025 release note) has been postponed to a future date. The future date will be announced in a release note at least one month in advance of the change. Until then, these diagnostic properties will continue to be set to false by default unless set to true by the user.
dataproc:diagnostic.capture.enabled
dataproc:dataproc.logging.extended.enabled
dataproc:dataproc.logging.syslog.enabled
Gemini 2.0 Flash with image generation (gemini-2.0-flash-preview-image-generation
) is now available as a public preview offering.
For more information, see Generate images with Gemini.
Seed parameter is now in GA and supports Gemini 2.5 model family.
We are moving service health updates for Google Cloud Security products from the Cloud Status Dashboard to a new security-specific status dashboard.
This dashboard displays service status and incident history for the following products:
- Google SecOps
- Google Threat Intelligence
- Mandiant Advantage Threat Intelligence
- Mandiant Attack Surface Management
- Mandiant Digital Threat Monitoring
- Mandiant Hunt
- Mandiant Managed Defense
- Mandiant Security Validation
We are moving service health updates for Google Cloud Security products from the Cloud Status Dashboard to a new security-specific status dashboard.
This dashboard displays service status and incident history for the following products:
- Google SecOps
- Google Threat Intelligence
- Mandiant Advantage Threat Intelligence
- Mandiant Attack Surface Management
- Mandiant Digital Threat Monitoring
- Mandiant Hunt
- Mandiant Managed Defense
- Mandiant Security Validation
The following features have been added to Studio in Looker, which is available in preview:
- You can now create reports using the responsive layout.
- You can now use variables, including parameters and query result variables. However, the ability to modify parameters using the report link is not supported in Studio in Looker.
Migrate to Virtual Machines now introduces an expiration time for a migrating VM. A migrating VM is a VM that you create during the migration process to migrate your workloads to Google Cloud.
A migrating VM stays active for 100 days from the time that the VM appears in the VM Migrations tab. After 100 days, the VM is moved to the EXPIRED
state and stays in the EXPIRED
state for 30 days. If you need more time to complete your migration, you can extend the lifespan of the migrating VM by an additional 100 days. You can only extend the lifespan of a migrating VM two weeks before the VM expires and throughout the expiration period (between 86 to 130 days from the creation of the VM). If you don't extend the lifespan of the VM during this period, the VM expires.
We just released three new voice features for Chirp 3: HD Voices. Pace control is available across all locales; pause control is available across all locales; custom pronunciations is available across all locales except bn-in, gu-in, nl-be, sw-ke, th-th, uk-ua, ur-in, and vi-vn. Be sure to check our Chirp 3: HD Voices documentation for more information.
The following features of internal ranges are available in General Availability:
- Reserving internal ranges with IPv6 addresses
- Creating immutable ranges (ranges that can't be edited, except for the description)
- Editable descriptions
For more information, see Internal ranges overview.
When you reserve an internal range with an automatically allocated IPv4 CIDR block, you can specify the allocation strategy that is used to select a free block. This feature is available in Preview.
May 06, 2025
Apigee UIOn May 6, 2025, we released a new Apigee REST resource for debug sessions.
Apigee now offers a Management API that allows users to list all recent debug sessions for a given proxy, regardless of revision or environment and current deployment status. This API is available for use, and is now used to populate all recent debug sessions in the Apigee Debug UI.
For more information on this method, see: organizations.apis.debugsessions.list
On May 6, 2025, we released a new Apigee REST resource for debug sessions.
Apigee now offers a Management API that allows users to list all recent debug sessions for a given proxy, regardless of revision or environment and current deployment status. This API is available for use, and is now used to populate all recent debug sessions in the Apigee Debug UI.
For more information on this method, see: organizations.apis.debugsessions.list
In the Google Cloud console, Analytics Hub has been renamed BigQuery sharing (Analytics Hub).
The following resource types are now publicly available through the Search (SearchAllResources, SearchAllIamPolicies) APIs.
- Eventarc
eventarc.googleapis.com/Channel
eventarc.googleapis.com/ChannelConnection
The Deployment Manager API is no longer automatically enabled when you enable Cloud Composer API because this API isn't used by the Cloud Composer service.
Environments with Cloud Composer versions 2.0.* still rely on the Deployment Manager API for updates, upgrades, and environment deletion. It won't be possible to perform these operations if this API is disabled. We recommend to upgrade your 2.0.* environments to a later version to remove this dependency.
When you create a snooze for a single alerting policy, you can now use resource, metric, and metadata label types to filter applicable incidents. For more information, see Create a snooze.
Private NAT supports Cloud Run in Preview. For more information, see Supported resources.
Direct VPC egress supports Private NAT (Preview).
The following images are now rolling out for managed Cloud Service Mesh:
- 1.21.5-asm.42 is rolling out to the rapid release channel.
- 1.20.8-asm.33 is rolling out to the regular release channel.
- 1.19.10-asm.33 is rolling out to the stable release channel.
A behavioral change regarding user-provided credentials (private key and certificate) for TLS termination at ingress is now rolling out to the Rapid release channel. Subsequent announcements will appear for additional release channels.
The Kubernetes Secrets denoted by Gateway.servers.port.tls.credentialName
will be read by each ingress gateway pod directly instead of the Control Plane. This change enhances security because the user-provided secret is read directly by the workloads instead of passing any managed component.
This change is compatible with previous behavior aside from the propagation speed of the updated secrets. Previously, updated secrets would propagate immediately. Now, updated secrets will propagate within 60 minutes. If you need immediate secret rotation, restart the gateway pods.
Each gateway pod reads Kubernetes secrets, so the number of the gateway pods becomes a scalability factor. We recommend the following maximum number of gateway pods:
- If the GKE cluster is regional, 1500 or fewer pods
- If the GKE cluster is zonal or using autopilot, 500 or fewer pods
If this change in behavior doesn't work for you, consider using the deployment with mounted credentials.
This change only affects clusters using Traffic Director and version 1.21.5-asm.42 or later.
cos-113-18244-382-8
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.123 | v24.0.9 | v1.7.24 | See List |
Upgraded sys-apps/grep to v3.12.
Upgraded net-dns/libidn2 to v2.3.8.
Upgraded sys-apps/makedumpfile to v1.7.7.
Fixed CVE-2025-32414, CVE-2025-32415 in dev-libs/libxml2.
Fixed CVE-2025-1178,CVE-2025-1182 and CVE-2025-1181 in sys-libs/binutils-libs.
Updated dev-go/protobuf to v1.33.0. This fixes CVE-2024-24786.
Updated dev-go/net to v0.39.0. This fixes CVE-2025-22870.
Updated NVIDIA GPU drivers to v535.247.01 for default/ R535, v550.163.01 for R550 and v570.133.20 for latest/R570. This resolves CVE-2025-23244.
Added support for 7th generation TPU devices.
Prompt with folders in your local workspace (Preview)
You can now include folders from your local IDE project for IntelliJ Gemini Code Assist (version 1.14.0
) to use as context for your prompts, in Preview. To specify a folder in your chat prompt, type @ and select the folder you want to specify.
Directing Code Assist to add folders to your chat can improve responses by specifying use of the contents within your selected folder(s), with support up to a 1M token context window.
General availability: Managed Service for Apache Kafka now supports configuring standard Apache Kafka ACLs using REST, gRPC, and gcloud CLI. For more information, see Access control with IAM and Kafka ACLs.
Google Distributed Cloud (software only) for VMware 1.32.0-gke.1087 is now available for download. To upgrade, see Upgrade a cluster. Google Distributed Cloud 1.32.0-gke.1087 runs on Kubernetes v1.32.3-gke.1000.
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.
GA: Advanced clusters. By default, new clusters are created as advanced clusters. For more information, see Differences when running advanced clusters.
GKE Identity Service supports a new diagnosis mode that surfaces diagnostic information related to the login flow. This makes it easier to troubleshoot login and OIDC configuration issues. For details, see GKE Identity Service diagnostic utility.
Support configuring cluster-level default topology spread constraints when creating a cluster for use with topology domains. For details, see schedulerConfiguration.
Version changes in 1.32.0-gke.1087:
- The etcd version upgraded to 3.4.33
- COS upgraded to milestone 117
- containerd upgraded to 1.7
- Cilium upgraded to 1.15.6
Other changes in 1.32.0-gke.1087:
The following legacy features are blocked during cluster upgrade:
- Dataplane V1 (Calico)
- Integrated F5 Big IP load balancer configuration
- Non-HA admin cluster
- Kubeception user cluster
- Seesaw load balancer
You must migrate your clusters to recommended features before upgrading to 1.32.
The following changes to MetalLB address pools were made to behave the same as advanced clusters:
- Can't remove existing address pools
- Can't remove addresses in an existing address pool
- Can't change address pool name
The cert-manager component is available on advanced clusters.
Allow changing
stackdriver.projectID
to be the same asgkeconnect.projectID
.Removed support in the Konnectivity server (
konnectivity-server
) for the following weak cryptographic cipher suites: TLS_RSA_WITH_AES_256_GCM_SHA384 and TLS_RSA_WITH_AES_128_GCM_SHA256.
- Windows Server OS node pools are deprecated in version 1.32 and will be unavailable in version 1.33 and higher. Support for Windows Server OS node pools ends May 25, 2026. We recommend that you begin migration planning immediately to ensure a smooth transition before the support period ends.
The following issues were fixed in 1.32.0-gke.1087:
- Fixed an issue that prevented user cluster upgrades when Dataplane V2 was explicitly configured with forward mode.
Skip checking additional IP address requirements for HA admin cluster upgrade.
Fixed missing validators for HA admin cluster and Controlplane V2 user control plane.
Fixed an issue during non-HA to HA admin cluster migration that prevented the migration from completing.
Fixed an issue where the VM template wasn't updated when HA admin control-plane machines were recreated.
Fixed an issue where resource validation counted customer workloads and reported warnings when customers ran high resource request workloads.
The 1.32.0-gke.1087 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
Release 1.32.0-gke.1087
Google Distributed Cloud for bare metal 1.32.0-gke.1087 is now available for download. To upgrade, see Upgrade clusters. Google Distributed Cloud for bare metal 1.32.0-gke.1087 runs on Kubernetes v1.32.3-gke.1000.
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.
Version 1.29 end of life: In accordance with the Version Support Policy, version 1.29 (all patch releases) of Google Distributed Cloud for bare metal has reached its end of life and is no longer supported.
GA: Added support for new diagnosis utility for GKE Identity Service that provides diagnostics information related to the login flow. This makes it easier to troubleshoot login and OIDC configuration issues. For more information, see GKE Identity Service diagnostic utility.
GA: For high availability control planes, Google Distributed Cloud automatically configures the Keepalived virtual router redundancy protocol (VRRP) configuration to make failover behaviour deterministic and prevent interleaving of ARP replies with different MAC addresses:
- By default, each Keepalived instance is configured with a different
priority
value. - Each Keepalived instance is configured with
nopreempt
to avoid elections when a non-master instance is restarted.
- By default, each Keepalived instance is configured with a different
GA: Added support for a new field,
controlPlane.loadBalancer.keepalivedVRRPGARPMasterRepeat
, in the cluster configuration file that maps to thevrrp_garp_master_repeat
setting for Keepalived. This field specifies the number of gratuitous ARP (GARP) messages to send at a time after a control plane node transitions to the role of the master server. The default value is5
.GA: Added a new
controlPlane.loadBalancer.mode
, field for Layer 2 load balancing. This field lets you separate control plane load balancing from data plane load balancing:- At cluster creation, if you set
controlPlane.loadBalancer.mode
tobundled
andloadBalancer.nodePoolSpec
is configured, the control plane load balancer runs in the control plane node pool and the data plane load balancer runs in the load balancer node pool. - For an existing cluster where
controlPlane.loadBalancer.mode
isn't set andloadBalancer.nodePoolSpec
isn't specified, both the control plane load balancer and the data plane load balancer run in the control plane node pool. You can migrate the data plane load balancer to a load balancer node pool by updating the cluster spec to specify a load balancer node pool (loadBalancer.nodePoolSpec
) and to addcontrolPlane.loadBalancer.mode
set tobundled
.
- At cluster creation, if you set
Upgraded etcd to v3.4.33-0-gke.3.
Upgraded containerd to version 1.7.
Upgraded the SR-IOV operator,
sriov-network-operator
, to version 1.4.Added
Compress=yes
to/etc/systemd/journald.conf
to ensure that objects larger than 512 bytes are compressed before they are written to the file system.Added new, default periodic health checks to ensure that Kubernetes cluster resources are configured correctly and functioning properly.
Added more namespaces to the default snapshot scenarios.
Added preflight check for kernel
fsnotify
settings for Red Hat Enterprise Linux (RHEL) 8.x.Removed the leading timestamp from the
bmctl version
response. Temporarily, we've provided-t
and--timestamps
flags to revert to the old format.Added a check for the
FailedCgroupRemoval
node condition to the node problem detector (NPD) to look for orphan container processes on nodes. By default, a new plugin for NPD automatically fixes this condition on the node.Updated the cluster delete process to delete worker node pools prior to removing any control plane nodes. This change applies to supported cluster deletion flows, including
bmctl
, the Google Cloud CLI, and the Google Cloud console.Updated the log entries in the
backup.log
file created by thebmctl backup
command to improve readability.Updated the cluster upgrade operation to keep only the three latest
kubeadm
backups of etcd and configuration information for a node. Previously,kubeadm
kept node backups for every attempted upgrade.Added the kubelet config, CPU Manager state, and Memory Manager state to node snapshots.
Fixed an issue that resulted in an excessive creation of periodic
kube-proxy-cleanup
jobs on cluster nodes with high pod utilization.Fixed an issue that caused cluster creation to fail because kubelet restarted before required static pods are running.
Fixed an issue where node upgrades failed due to a missing super-admin.conf file.
Fixed an issue where the
bmctl update cluster
command fails for user clusters that were created with thecloudOperationsServiceAccountKeyPath
setting in the header section of the cluster configuration file.Fixed an issue where prompting during
bmctl update cluster
prevented use of automation. You can now use the --quiet flag to skip prompting.Fixed an issue where node machines didn't update when the registry mirror hosts field was updated.
The 1.32.0-gke.1086 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
For information about the latest known issues, see Google Distributed Cloud for bare metal known issues in the Troubleshooting section.
You can use custom constraints with Organization Policy to provide more granular control over specific fields for some Dataplex and data lineage resources. For more information, see Manage Dataplex resources using custom constraints and Manage data lineage resources using custom constraints. This feature is generally available (GA).
May 05, 2025
Apigee UIOn May 5, 2025, we released an updated version of the Apigee UI.
Bug ID | Description |
---|---|
402183688 | Resolved navigation issue when creating a new flow in the Apigee Proxy Editor In some instances, adding a flow to an Apigee endpoint using the Apigee Proxy Editor resulted in redirection to a |
Support for PHP 8.4 runtime is in Preview.
Support for Python 3.13 runtime is in General availability (GA).
Support for Ruby 3.4 runtime is in Preview.
Support for PHP 8.4 runtime is in Preview.
Support for Python 3.13 runtime is in General Availability (GA).
Support for Ruby 3.4 runtime is in Preview.
Cloud Function Task adds support for Cloud Functions v2 API
The Cloud Function task in Application Integration now lets you create, link, and run the latest generation of serverless functions, called Cloud Run functions, using the Cloud Functions v2 API.
For more information, see Cloud Function Task.
Control HTTP call access by region in Application Integration
Application Integration now offers a new control within the Regions page to enable or disable HTTP calls for integrations on a per-region basis.
For more information, see Manage regions.
A weekly digest of client library updates from across the Cloud SDK.
Node.js
Changes for @google-cloud/bigquery
8.0.0 (2025-04-23)
⚠ BREAKING CHANGES
- migrate to node 18 (#1458)
Miscellaneous Chores
Changes that you make to your saved queries are now automatically saved. This feature is in preview.
A weekly digest of client library updates from across the Cloud SDK.
Node.js
Changes for @google-cloud/bigtable
6.0.0 (2025-04-22)
⚠ BREAKING CHANGES
- Migrate to Node 18 (#1582)
Features
- Add fields and the BackupType proto for Hot Backups (#1439) (433a8e3)
- Add MergeToCell to Mutation APIs (433a8e3)
- Add min, max, hll aggregators and more types (433a8e3)
- Add plumbing PR for client side metrics to support the open telemetry instruments (#1569) (c37a451)
- Add the MetricsCollector for client side metrics (#1566) (d475ef2)
- Add the plumbing for application blocking latencies client side metrics (#1575) (967f440)
- Bigtable authorized views requests on the Data plane (#1509) (da373b5)
- Move the metrics handler fixture (#1570) (c97ebcc)
- Publish ProtoRows Message (433a8e3)
- Publish the Cloud Bigtable ExecuteQuery API (433a8e3)
- Update Go Bigtable import path (433a8e3)
- Update Go Datastore import path (433a8e3)
Bug Fixes
- Address assertion error in TestReadRows_Retry_LastScannedRow conformance test (#1521) (0552638)
- Check and mutate generic header conformance test (#1551) (7f1099a)
- Conformance test sample rowkeys generic deadline (#1562) (2fdf98f)
- Fix plumbing errors for client side metrics collection (#1583) (574c2f4)
- Fix TestReadRows_Generic_CloseClient conformance test by passing grpc status codes for closed client errors (#1524) (8524174)
- Fix paused scan test (#1539) (d009a8f)
- Sample rowkey generic header conformance test (#1550) (6ef7671)
- TestMutateRow_Generic_Headers (#1540) (f6176c1)
- Update owlbot.py to exculde sync repo (#1549) (f1ad565)
- Update sync-repo-settings.yaml to make owl bot optional (#1547) (d745412)
- Use the universe domain if it is provided by the user (#1563) (d26ecb8)
Miscellaneous Chores
Java
Changes for google-cloud-bigtable
2.58.1 (2025-04-28)
Bug Fixes
2.58.0 (2025-04-28)
Features
- Add deletion_protection support for LVs (43c97a3)
- bigtable: Add integration tests for Materialized/Logical Views (#2518) (4d3a7e6)
Bug Fixes
Invalidation using cache tags is Generally Available.
Cloud CDN now also offers faster performance and higher rate limits for invalidation requests using all invalidation matchers. For more information, see Cache validation overview.
It is now possible to migrate from Cloud Composer 1 to Cloud Composer 3 using snapshots. For more information, see the new migration guide.
This feature will gradually roll out to all regions supported by Cloud Composer 3. At the moment it is available in the africa-south1, asia-south1, me-central1, me-central2, me-west1, southamerica-east1, and southamerica-west1 regions.
Support for the Python 3.13 runtime is in General Availability (GA).
Support for the Ruby 3.4 runtime is in Preview.
Support for the PHP 8.4 runtime is in Preview.
Support for the Python 3.13 runtime is in General Availability (GA).
Support for the Ruby 3.4 runtime is in Preview.
Support for the PHP 8.4 runtime is in Preview.
Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.
cos-117-18613-263-4
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v24.0.9 | v1.7.24 | See List |
This is an LTS Refresh release.
Upgraded sys-apps/makedumpfile to v1.7.7.
Upgraded app-containers/docker-credential-helpers to v0.9.3.
Upgraded app-admin/google-guest-configs to v20250328.00.
Upgraded app-containers/cni-plugins to v1.6.2.
Upgraded dev-lang/go to v1.23.8.
Upgraded sys-apps/grep to v3.12.
Upgraded net-dns/libidn2 to v2.3.8.
Upgraded net-nds/rpcbind to v1.2.7.
Upgraded net-fs/cifs-utils to v7.3, Upgraded sys-libs/talloc to v2.4.2.
Upgraded sys-apps/acl to v2.3.2-r2.
Upgraded sys-libs/libseccomp to v2.6.0-r2.
Upgraded dev-libs/expat to v2.7.1.
Upgraded dev-db/sqlite to v3.49.1.
Upgraded dev-libs/double-conversion to v3.3.1.
Upgraded app-arch/unzip to v6.0_p29.
Upgraded app-admin/sudo to v1.9.16_p2-r1.
Upgraded net-libs/libnetfilter_conntrack to v1.1.0.
Upgraded net-libs/libtirpc to v1.3.6.
Upgraded sys-apps/gentoo-functions to v1.7.3.
Upgraded sys-libs/libcap to v2.71.
Upgraded dev-libs/nss to v3.109.
Updated NVIDIA GPU drivers to v535.247.01 for default/ R535, v550.163.01 for R550 and v570.133.20 for latest/R570. This resolves CVE‑2025‑23244.
Update dev-go/net in policy manager to v0.39.0. This fixes CVE-2025-22870.
Fix CVE-2025-32414, CVE-2025-32415 in dev-libs/libxml2.
Fixed CVE-2025-1178,CVE-2025-1182 and CVE-2025-1181 in sys-libs/binutils-libs.
Updated dev-vcs/git to version 2.49.0. This fixed CVE-2024-52006, CVE-2024-50349
Fixed KCTF-342debc in the Linux kernel.
Fixed CVE-2025-22097 in the Linux kernel.
Fixed CVE-2025-22035 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811753 -> 811816
cos-109-17800-519-1
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.135 | v24.0.9 | v1.7.24 | See List |
This is an LTS Refresh release.
Upgraded sys-apps/makedumpfile to v1.7.7.
Upgraded app-containers/docker-credential-helpers to v0.9.2.
Upgraded app-admin/google-guest-configs to v20250221.00.
Upgraded sys-auth/pambase to v20250228.
Upgraded app-admin/google-guest-configs to v20250124.00.
Upgraded dev-lang/go to v1.21.13.
Upgraded sys-apps/grep to v3.12.
Upgraded net-dns/libidn2 to v2.3.8.
Upgraded net-nds/rpcbind to v1.2.7.
Upgraded net-fs/cifs-utils to v7.3, Upgraded sys-libs/talloc to v2.4.2.
Upgraded net-firewall/iptables to v1.8.11-r1.
Upgraded app-arch/gzip to v1.13-r1.
Upgraded sys-apps/acl to v2.3.2-r2.
Upgraded dev-db/sqlite to v3.49.1.
Upgraded app-admin/sudo to v1.9.16_p2-r1.
Upgraded net-libs/libnetfilter_conntrack to v1.1.0.
Upgraded dev-libs/nss to v3.107.
Upgraded dev-python/configobj to v5.0.9.
Upgraded sys-libs/libcap to v2.71.
Upgraded net-libs/libtirpc to v1.3.6.
Upgraded dev-libs/expat to v2.6.4.
Updated dev-go/protobuf to v1.33.0. This fixes CVE-2024-24786.
Updated dev-go/net to v0.39.0. This fixes CVE-2025-22870.
Fixed CVE-2025-32414, CVE-2025-32415 in dev-libs/libxml2.
Fixed CVE-2025-1178,CVE-2025-1182 and CVE-2025-1181 in sys-libs/binutils-libs.
Fixed CVE-2025-32728 in net-misc/openssh.
Updated dev-vcs/git to version 2.49.0. This fixed CVE-2024-52006, CVE-2024-50349
Fixed CVE-2025-22035 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812262 -> 812287
cos-dev-125-19025-0-0
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.88 | v27.5.1 | v2.0.4 | See List |
Upgraded app-admin/google-guest-configs to v20250409.00.
Upgraded app-admin/google-guest-agent to v20250418.00.
Upgraded sys-apps/makedumpfile to v1.7.7.
Upgraded app-benchmarks/microbenchmarks to v0.0.1-r20.
Upgraded chromeos-base/minijail to v18-r167.
Upgraded chromeos-base/chromeos-common-script to v0.0.1-r664.
Upgraded chromeos-base/google-breakpad to v2025.04.09.155244-r236.
Upgraded chromeos-base/shill-client to v0.0.1-r4853.
Upgraded chromeos-base/power_manager-client to v0.0.1-r2968.
Upgraded chromeos-base/update_engine-client to v0.0.1-r2480.
Upgraded chromeos-base/session_manager-client to v0.0.1-r2829.
Upgraded chromeos-base/debugd-client to v0.0.1-r2733.
Upgraded app-arch/gzip to v1.14.
Upgraded net-dns/libidn2 to v2.3.8.
Upgraded sys-apps/grep to v3.12.
Updated NVIDIA GPU drivers to v535.247.01 for default/ R535 and v570.133.20 for latest/R570. This resolves CVE‑2025‑23244.
Fixed CVE-2025-32414, CVE-2025-32415 in dev-libs/libxml2.
Updated the Linux kernel to v6.6.88.
Updated the Linux kernel to v6.6.88.
Runtime sysctl changes:
- Changed: fs.file-max: 811785 -> 811773
cos-121-18867-90-15
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
Upgraded sys-apps/makedumpfile to v1.7.7.
Upgraded sys-apps/grep to v3.12.
Upgraded net-dns/libidn2 to v2.3.8.
Updated NVIDIA GPU drivers to v535.247.01 for default/ R535 and v570.133.20 for latest/R570. This resolves CVE‑2025‑23244.
Fixed CVE-2025-32414, CVE-2025-32415 in dev-libs/libxml2.
Fixed KCTF-342debc in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811806 -> 811788
You can use custom constraints with Organization Policy to provide more granular control over specific fields for some Dataplex and data lineage resources. For more information, see Manage Dataplex resources using custom constraints and Manage data lineage resources using custom constraints. This feature is generally available (GA).
You can now use Private Service Connect interfaces as a private connectivity method in Datastream. For more information, see the documentation.
Custom extractor model pretrained-foundation-model-v1.5-2025-04-25
powered by Gemini 2.5 Flash LLM is available as Public Preview in US regions. The custom extractor model supports a quota of up to 15 pages per minute for online process requests.
For more information about available models, see Custom extractor model versions.
Grounding
The following grounding features are generally available:
New Light Theme
Google SecOps has introduced a new light theme option in the platform. The light theme includes a color palette for visual clarity.
New Light Theme
Google SecOps has introduced a new light theme option in the platform. The light theme includes a color palette for visual clarity.
A new enforcement version, enforcement version 3, is available for principal access boundary policies. To learn more about enforcement versions and see the permissions that enforcement version 3 can block, see Permissions that principal access boundary policies can block.
A weekly digest of client library updates from across the Cloud SDK.
Node.js
Changes for @google-cloud/pubsub
5.0.0 (2025-04-28)
⚠ BREAKING CHANGES
- migrate to Node 18 (#2024)
- remove (broken) legacy OTel support
- remove legacy ack deadline options
- move maxExtension into subscriber options
Miscellaneous Chores
Web Security Scanner, a built-in service of Security Command Center, released new detectors. The following detectors, which are available with the Enterprise and Premium tiers of Security Command Center, detect misconfigurations in web applications:
HSTS_MISCONFIGURATION
CSP_MISSING
CSP_MISCONFIGURATION
COOP_MISSING
CLICKJACKING_PROTECTION_MISSING
For more information, see Web Security Scanner misconfiguration findings.
May 03, 2025
Google SecOps SOARRelease 6.3.44 is being rolled out to the first phase of regions as listed here.
Light Theme Enhancements
We've improved the color palette for the light theme to enhance visual clarity.
May 02, 2025
Apigee XOn May 2, 2025, we released an updated version of Apigee (1-15-0-apigee-3).
Large message payload support in Apigee
Apigee now supports message payloads up to 30MB. For more information, see:
- Message payload size.
Properties
in the ProxyEndpoint configuration elements reference.Properties
in the TargetEndpoint configuration elements reference.
Improvements to the PublishMessage policy
The PublishMessage policy now supports two new elements:
The <UseMessageAsSource> element uses request or response message content as the source of data to be written to Pub/Sub. For more information, see <UseMessageAsSource>.
The <Attributes> element lets you specify string attributes (key/value pairs) to include with the request or response message that is written to Pub/Sub. For more information, see <Attributes>.
Bug ID | Description |
---|---|
391140293 | Resolved scaling issue resulting in 503 errors Added |
391862684 | Resolved issue with requests stuck at Message Processor causing timeouts. |
N/A | Updates to security infrastructure and libraries. |
hybrid v1.14.2
On May 2, 2025 we released an updated version of the Apigee hybrid software, 1.14.2.
- For information on upgrading, see Upgrading Apigee hybrid to version 1.14.
- For information on new installations, see The big picture.
Large message payload support in Apigee hybrid
Apigee now supports message payloads up to 30MB. For information see:
- Message payload size
runtime.resources.limits.memory
in the Configuration property reference.runtime.resources.requests.memory
in the Configuration property reference.
Starting with v1.14.2, third-party container images will be labeled with a version tag that matches the Apigee hybrid image tag. This affects the image tags returned by the apigee-pull-push
command line tool. For more information, see:
Bug ID | Description |
---|---|
399447688 | API proxy deployment could become stuck in PROGRESSING state. |
396571537 | Rotating Cassandra credentials in Kubernetes secrets fixed for Multi-region deployments. |
368155212 | Auto Cassandra secret rotation could fail when Enhanced per-environment proxy limits are enabled. |
384937220 | Fixed ApigeeRoute name collision on internal chaining gateway for Enhanced Proxy Limits. |
412324617 | Fixed issue where Runtime container could spin at 100% cpu limit. |
Bug ID | Description |
---|---|
391923260 | Security fixes for apigee-udca . This addresses the following vulnerabilities: |
N/A | Security fixes for apigee-fluent-bit . This addresses the following vulnerabilities: |
N/A | Security fixes for apigee-hybrid-cassandra . This addresses the following vulnerability: |
N/A | Security fixes for apigee-hybrid-cassandra-client . This addresses the following vulnerability: |
N/A | Security fixes for apigee-mint-task-scheduler . This addresses the following vulnerability: |
N/A | Security fixes for apigee-open-telemetry-collector . This addresses the following vulnerabilities: |
N/A | Security fixes for apigee-operators . This addresses the following vulnerabilities: |
N/A | Security fixes for apigee-prometheus-adapter . This addresses the following vulnerability: |
N/A | Security fixes for apigee-redis . This addresses the following vulnerabilities: |
N/A | Security fixes for apigee-stackdriver-logging-agent . This addresses the following vulnerabilities: |
N/A | Security fixes for apigee-watcher . This addresses the following vulnerabilities: |
The Sovereign Controls for Kingdom of Saudi Arabia control package now supports the following products. See Supported products by control package for more information:
- Access Context Manager
- Certificate Authority Service
- Connect
- GKE Hub
- GKE Identity Service
The Sovereign Controls for EU control package now supports the following products. See Supported products by control package for more information:
- Access Context Manager
- Certificate Authority Service
- Cloud Service Mesh
- Connect
- GKE Hub
- MemoryStore for Redis
- Speech-to-Text
The ITAR control package now supports Service Directory.
The limit for the number of widgets on a custom dashboard has increased to 100, from 40. For information about dashboards, see the following:
You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA
) option as its server CA mode.
Custom SAN configuration for instances is generally available (GA).
You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA
) option as its server CA mode.
Custom SAN configuration for instances is generally available (GA).
You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA
) option as its server CA mode.
Custom SAN configuration for instances is generally available (GA).
New Dataproc on Compute Engine subminor image versions:
- 2.0.139-debian10, 2.0.139-rocky8, 2.0.139-ubuntu18
- 2.1.87-debian11, 2.1.87-rocky8, 2.1.87-ubuntu20, 2.1.87-ubuntu20-arm
- 2.2.55-debian12, 2.2.55-rocky9, 2.2.55-ubuntu22
Dataproc on Compute Engine: Upgraded NodeProblemDetector to 0.8.20 based version for 2.2 image.
Dataproc on Compute Engine: Upgraded oauth2l to v1.3.3 to address CVEs.
Dataproc on Compute Engine: Fixed an issue with Apache Hudi that caused failure in Hudi CLI.
The global endpoint is generally available (GA). For details, see Global endpoint.
(2025-R17) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.10-gke.1070000
- 1.30.10-gke.1102000
- 1.31.6-gke.1064001
- 1.31.6-gke.1099001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.2-gke.1297002 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
Regular channel
- The following versions are now available in the Regular channel:
Stable channel
- Version 1.32.1-gke.1357001 is no longer available in the Stable channel.
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
Extended channel
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2633000
- 1.27.16-gke.2682000
- 1.28.15-gke.2072000
- 1.28.15-gke.2142000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2097000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2650000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2097000 with this release.
No channel
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.30.10-gke.1102000
- 1.31.6-gke.1099001
- 1.32.1-gke.1357001
- 1.32.2-gke.1182001
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
(2025-R17) Version updates
- Version 1.32.2-gke.1297002 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.30.10-gke.1070000
- 1.30.10-gke.1102000
- 1.31.6-gke.1064001
- 1.31.6-gke.1099001
- 1.32.2-gke.1182003
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.29 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.2-gke.1297002 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.30.11-gke.1131000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.7-gke.1212000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.2-gke.1297002 with this release.
(2025-R17) Version updates
- The following versions are now available in the Regular channel:
(2025-R17) Version updates
- Version 1.32.1-gke.1357001 is no longer available in the Stable channel.
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
(2025-R17) Version updates
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2633000
- 1.27.16-gke.2682000
- 1.28.15-gke.2072000
- 1.28.15-gke.2142000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2097000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2650000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2097000 with this release.
(2025-R17) Version updates
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.30.10-gke.1102000
- 1.31.6-gke.1099001
- 1.32.1-gke.1357001
- 1.32.2-gke.1182001
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
Auto extraction of JSON logs
Google SecOps supports Auto Extraction of JSON logs. The auto extraction feature lets you use raw log fields directly in search, detection rules, and Native Dashboards, with or without a parser. Public preview for this feature begins the week of May 5, 2025.
Auto extraction of JSON logs
Google SecOps supports Auto Extraction of JSON logs. The auto extraction feature lets you use raw log fields directly in search, detection rules, and Native Dashboards, with or without a parser. Public preview for this feature begins the week of May 5, 2025.
Cloud Logging for agent-based transfers now logs skipped files. A skipped file is logged when the file already exists in the sink, and your transfer job is configured to ignore existing files.
See Cloud Logging for Storage Transfer Service for details.
May 01, 2025
Anthos Config ManagementInstalling Policy Controller through the ConfigManagement API is no longer supported. For instructions installing Policy Controller, see Installing Policy Controller. For instructions migrating existing Policy Controller instances, see Migrate from the ConfigManagement API to the PolicyController API. This note was added on May 16, 2025.
The Config Sync auto-upgrades feature is now unavailable. You can no longer configure auto-upgrade settings and must manually upgrade the Config Sync version. If you currently use auto-upgrades, you must first disable auto-upgrades before you can manually update Config Sync.
Upgraded the Open Telemetry Collector image from v0.103.0 to v0.118.0. This upgrade includes a breaking change where the default OTLP component endpoint is now localhost
instead of 0.0.0.0
. You will be impacted only if you use a customized configuration for the built-in Otel Collector within Config Sync, and you can explicitly specify 0.0.0.0
for endpoints to ensure that your monitoring solution continues to function correctly. To understand the changes in each release, review the full changelog for opentelemetry-collector-contrib.
The nomos vet
command now supports a --threshold
flag to proactively validate the number of objects in your Config Sync repository. You can use this flag in validation pipelines to prevent sync failures caused by exceeding the underlying etcd
size limits when your repository contains a large number of objects. For more information, see Enforce the maximum number of objects to sync.
Deleting a RootSync or RepoSync now removes its management metadata from all managed objects. This allows objects to be adopted by their new managers, simplifying the procedure for splitting a large configuration repository across multiple RootSync or RepoSync objects. For more information, see Break up a repository into multiple repositories.
Addressed multiple Common Vulnerabilities and Exposures (CVEs) by updating dependencies.
Fixed an issue impacting the Ignore object mutations feature. The client.lifecycle.config.k8s.io/mutation: ignore
annotation was not always effective, causing Config Sync to potentially overwrite changes made directly to annotated resources in the cluster. Config Sync now correctly ignores mutations on these resources.
Fixed an issue preventing ResourceGroup objects from being garbage collected when their corresponding RootSync or RepoSync objects were deleted.
Fixed several issues to improve ResourceGroup status reporting and reliability.
Fixed an issue where drift prevention incorrectly blocked modifications of abandoned resources.
App Hub supported resources are now generally available (GA).
A new release is available. This release may include some or all of the following: general performance improvements, bug fixes, and updates to the API reference documentation.
Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.
You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA
), the shared CA (GOOGLE_MANAGED_CAS_CA
), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA
) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA
), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA
) is the default configuration.
The shared CA and customer-managed CA options are now generally available (GA).
Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.
You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA
), the shared CA (GOOGLE_MANAGED_CAS_CA
), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA
) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA
), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA
) is the default configuration.
The shared CA and customer-managed CA options are now generally available (GA).
Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.
You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA
), the shared CA (GOOGLE_MANAGED_CAS_CA
), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA
) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA
), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA
) is the default configuration.
The shared CA and customer-managed CA options are now generally available (GA).
Config Connector version 1.131.0 is now available.
New Beta resources (direct reconciler)
New Alpha resources (direct reconciler)
ComputeNetworkAttachment
ComputeNetworkEdgeSecurityService
DataplexEntryGroup
DataplexEntryType
DataplexTask
DataplexZone
DatastreamRoute
DocumentAIVersion
GKEBackupBackup
GKEBackupRestore
PubSubSnapshot
SpeechCustomClass
VMwareEngineExternalAddress
MetastoreService
MetastoreFederation
MetastoreBackup
APIQuotaPreference
APIQuotaAdjusterSettings
EventarcGoogleChannelConfig
EventarcChannel
AssetSavedQuery
AssetFeed
EssentialContactsContact
DataCatalogEntryGroup
DataCatalogEntry
DataCatalogTagTemplate
DataCatalogTag
- Fixed an issue: excessive compute.firewallPolicies.patchRule Logs triggered by Config Connector direct reconciliation.
New Dataproc Serverless for Spark runtime versions:
- 1.1.101
- 1.2.45
- 2.2.45
Native Query Execution now supports reading Apache ORC complex types.
Dialogflow CX (Conversational Agents): Models gemini-2.0-flash-001
and gemini-2.0-flash-lite-001
are now GA. They are available in all supported regions.
This change applies to the following features:
- Playbooks
- Data store tools in playbooks
- Generators
Design an optimal storage strategy for your cloud workload: Added information about Filestore replication, Hyperdisk Balanced High Availability, Anywhere Cache, and capacity specifications for Google Cloud NetApp Volumes.
On or after September 30, 2025, you can no longer send inspection and discovery results from Sensitive Data Protection to Data Catalog. Data Catalog is deprecated and will be discontinued on January 30, 2026. For Sensitive Data Protection, no action is required from you. No inspection or discovery configuration will break.
For discovery operations, we recommend that you add Dataplex Catalog aspects based on insights from data profiles instead.
You can automatically attach aspects to Dataplex entries after profiling supported data resources. For more information, see Add Dataplex Catalog aspects based on insights from data profiles.
Spanner Graph now lets you model schemaless data with a dynamic label and properties. For more information, see Manage schemaless data with Spanner Graph.
April 30, 2025
Cloud ComposerStarting from 5 May, 2025, new Cloud Composer 3 environments will use 1 CPU and 4 GB of memory for the Airflow web server by default. The minimum and maximum values for these parameters will not change.
The rollout of the following extension versions and plugin versions is complete:
Extensions and plugins
pg_partman
is upgraded from 5.0.1 to 5.2.4 (for PostgreSQL versions 14 and later).
To use this version of the extension, update your instance to [PostgreSQL version].R20250302.00_10
.
If you use a maintenance window, then the updates to the minor, extension, and plugin versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks.
For more information on checking your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.
You can now include folders from your local IDE project for IntelliJ Gemini Code Assist (version 1.14.0
) to use as context for your prompts, in Preview.
- Llama 4 Maverick and Scout models are available in Model Garden with Model-as-a-Service API Service and self-hosted deployments.
- HiDream-I1, Llama Guard 4, Llama Prompt Guard 2, and Qwen3 are available in Model Garden.
- Additional materials are available for deploying a model in Model Garden by using the Python SDK, gcloud CLI, or API, which are available in Preview:
Multi-regional deployment on Compute Engine: Technical updates to align design recommendations with Google Cloud Well-Architected Framework core principles.
Single-zone deployment on Compute Engine: Technical updates to align design recommendations with Google Cloud Well-Architected Framework core principles.
Hub-and-spoke network architecture: Added Network Connectivity Center as a design option.
A monthly digest of client library updates from across the Cloud SDK.
Go
Changes for spanner/admin/database/apiv1
1.79.0 (2025-04-08)
Features
- spanner: Allow string values for Scan functions (#11898) (9989dd0)
- spanner: New client(s) (#11946) (c60f28d)
0.1.0 (2025-04-15)
Bug Fixes
- spanner/benchmarks: Update google.golang.org/api to 0.229.0 (3319672)
1.80.0 (2025-04-23)
Features
Bug Fixes
- spanner/benchmarks: Update google.golang.org/api to 0.229.0 (3319672)
- spanner/test/opentelemetry/test: Update google.golang.org/api to 0.229.0 (3319672)
- spanner: Retry INTERNAL retriable auth error (#12034) (65c7461)
- spanner: Update google.golang.org/api to 0.229.0 (3319672)
Performance Improvements
Java
Changes for google-cloud-spanner
6.90.0 (2025-03-31)
Features
- Add default_isolation_level connection property (#3702) (9472d23)
- Adds support for Interval datatype in Java client (#3416) (8be8f5e)
- Integration test for End to End tracing (#3691) (bf1a07a)
- Specify isolation level per transaction (#3704) (868f30f)
- Support PostgreSQL isolation level statements (#3706) (dda2e1d)
6.91.0 (2025-04-17)
Features
- [Internal] open telemetry built in metrics for GRPC (#3709) (cd76c73)
- Add java sample for the pre-splitting feature (#3713) (e97b92e)
- Add TransactionMutationLimitExceededException as cause to SpannerBatchUpdateException (#3723) (4cf5261)
- Built in metrics for afe latency and connectivity error (#3724) (e13a2f9)
- Support unnamed parameters (#3820) (1afd815)
Bug Fixes
- Add default implementations for Interval methods in AbstractStructReader (#3722) (97f4544)
- Set transaction isolation level had no effect (#3718) (b382999)
Performance Improvements
- Cache the key used for OTEL traces and metrics (#3814) (c5a2045)
- Optimize parsing in Connection API (#3800) (a2780ed)
- Qualify statements without removing comments (#3810) (d358cb9)
- Remove all calls to getSqlWithoutComments (#3822) (0e1e14c)
6.91.1 (2025-04-21)
Bug Fixes
Node.js
Changes for @google-cloud/spanner
7.20.0 (2025-04-11)
Features
- Add support for Interval (#2192) (8c886cb)
- debugging: Implement x-goog-spanner-request-id propagation per request (#2205) (e42caea)
- spanner: Add support for snapshot isolation (#2245) (b60a683)
- spanner: Support for Multiplexed Session Partitioned Ops (#2252) (e7ce471)
7.21.0 (2025-04-15)
Features
Bug Fixes
The enhance_query
option on the SEARCH, SCORE, and SNIPPET functions is now updated to provide automatic synonym matching and spell correction of single words, by default. Previously, if you provided a single word as the search string it would likely not return any matches and required a phrase with context to perform the enhanced search.
If you're a service producer that makes a service available through VPC Network Peering, you can migrate your service to Private Service Connect without changing the IPv4 address that consumers use to access the service. This feature is available in General Availability.
April 29, 2025
Apigee API hubOn April 29, 2025, we released an updated version of Apigee.
Apigee API hub is enabled for existing Apigee organizations in supported regions.
With this release, we are enabling Apigee API hub for existing Apigee organizations in regions where API hub is supported. All existing Apigee organizations, including hybrid organizations, that selected an API hub-supported region for their Apigee Analytics region will have access to API hub features at no additional cost.
API hub allows you to view, organize, and manage all of the APIs in your Apigee organization in one central location. To learn more, see What is Apigee API hub?
The process of enabling API hub for these organizations will continue over the next several weeks until all eligible organizations are updated. No action on your part is required to provision API hub for your organization, with the following exceptions:
- If your Apigee organization has Data Residency or VPC Service Controls enabled, you must configure your API hub instance manually to support these services. See VPC Service Controls for API hub and API hub and data residency for more information.
- If your Apigee organization uses Customer-Managed Encryption Keys (CMEK), you must deprovision the Apigee API hub instance provided by default and recreate it to support CMEK. See Deprovision Apigee API hub and Provision API hub in the Cloud console for step-by-step instructions.
Contact Google Cloud Support for questions or assistance.
On April 29, 2025, we released an updated version of Apigee.
Apigee API hub is enabled for existing Apigee organizations in supported regions.
With this release, we are enabling Apigee API hub for existing Apigee organizations in regions where API hub is supported. All existing Apigee organizations, including hybrid organizations, that selected an API hub-supported region for their Apigee Analytics region will have access to API hub features at no additional cost.
API hub allows you to view, organize, and manage all of the APIs in your Apigee organization in one central location. To learn more, see What is Apigee API hub?
The process of enabling API hub for these organizations will continue over the next several weeks until all eligible organizations are updated. No action on your part is required to provision API hub for your organization, with the following exceptions:
- If your Apigee organization has Data Residency or VPC Service Controls enabled, you must configure your API hub instance manually to support these services. See VPC Service Controls for API hub and API hub and data residency for more information.
- If your Apigee organization uses Customer-Managed Encryption Keys (CMEK), you must deprovision the Apigee API hub instance provided by default and recreate it to support CMEK. See Deprovision Apigee API hub and Provision API hub in the Cloud console for step-by-step instructions.
Contact Google Cloud Support for questions or assistance.
Similarity vector search in Bigtable by finding the K-nearest neighbors is generally available (GA).
The MCP Toolbox for Databases includes a Bigtable connector. This feature is available in Preview.
Find and eliminate waste using FinOps hub 2.0 with Gemini Cloud Assist (preview)
FinOps hub 2.0 adds a new dashboard, Utilization insights, designed to help you quickly identify and reduce cloud waste to get the most value from Google Cloud. You can do the following with FinOps hub's Utilization insights dashboard:
- Assess estimated costs from underutilized resources (for example, idle, overprovisioned, underprovisioned and suboptimal configurations).
- Use the visual Waste map to find the top waste drivers by projects and waste category, helping you focus your optimization efforts.
- Leverage data-driven recommendations to optimize key services (Compute Engine, Kubernetes Engine (GKE), Cloud SQL, and Cloud Run) and App Hub applications.
Use Gemini Cloud Assist in FinOps hub to save time and simplify collaboration. If you have enabled Gemini Cloud Assist in Billing, Gemini generates summaries of top wasted usage insights and drafts email reports of utilization insights that you can share with your engineering teams for quicker remediation.
For more information about the FinOps hub Utilization insights dashboard, see:
For more information about Gemini Cloud Assist features in FinOps hub, see:
App Hub applications are now integrated with billing reports and the FinOps hub, to let you analyze costs by application. This integration provides detailed cost analysis for your specific applications, so FinOps and DevOps can see the cost of their applications and get recommendations on how to optimize their cloud efficiency.
- In cost Reports, you can configure your report to Group by Application, or filter on Applications.
- In the Cost table report, you can filter on Applications.
- In the Cost breakdown report, you can filter on Applications.
- In the FinOps hub Utilization insights dashboard, you can view insights by App Hub Application, to see the estimated costs of potentially wasted usage, and find recommendations to reduce waste and optimize your costs.
A script for migrating from Cloud Composer 2 to Cloud Composer 3 is now available on GitHub.
For instructions about migrating with the script, see the new migration guide in Cloud Composer documentation.
All Application and Proxy Network Load Balancers now support deployments where the load balancer frontend and the load balancer backend use different VPC networks. This is supported without the use of a Shared VPC deployment.
For regional and cross-region load balancers, connectivity between the load balancer's VPC network and the backend VPC network must be configured using either VPC Network Peering, Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or a Network Connectivity Center framework.
For global and classic load balancers, the different VPC networks don't need to be connected using VPC Network Peering because GFEs communicate directly with backends in their respective VPC networks.
For more details, see the following pages:
Gemini in Colab Enterprise, which is a product in the Gemini for Google Cloud portfolio, now includes additional capabilities in Preview. See the following:
- Chat about your notebook with Gemini
- Explain code cells with Gemini assistance
- Explain and fix errors with Gemini assistance
To enable and activate Gemini in Colab Enterprise features, see Set up Gemini in Colab Enterprise.
cos-113-18244-382-3
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.134 | v24.0.9 | v1.7.24 | See List |
This is an LTS Refresh Release.
Upgraded app-admin/google-guest-configs to v20250221.00.
Upgraded sys-auth/pambase to v20250228.
Upgraded app-containers/docker-credential-helpers to v0.9.2.
Upgraded app-admin/google-guest-configs to v20250124.00.
Upgraded dev-lang/go to v1.21.13.
Upgraded app-arch/unzip to v6.0_p29.
Upgraded net-nds/rpcbind to v1.2.7.
Upgraded net-fs/cifs-utils to v7.3, Upgraded sys-libs/talloc to v2.4.2.
Upgraded dev-libs/double-conversion to v3.3.1.
Upgraded dev-db/sqlite to v3.49.1.
Upgraded sys-apps/acl to v2.3.2-r2.
Upgraded dev-libs/expat to v2.6.4.
Upgraded sys-process/procps to v4.0.4-r2.
Upgraded net-libs/libnetfilter_conntrack to v1.1.0.
Upgraded dev-libs/nss to v3.107.
Upgraded app-admin/sudo to v1.9.16_p2-r1.
Upgraded net-libs/libtirpc to v1.3.6.
Upgraded sys-libs/libcap to v2.71.
Fixed CVE-2025-32728 in net-misc/openssh.
Updated dev-vcs/git to version 2.49.0. This fixed CVE-2024-52006, CVE-2024-50349
Runtime sysctl changes:
- Changed: fs.file-max: 812031 -> 812035
cos-121-18867-90-4
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
This is an LTS Refresh Release.
Fixed an issue in containerd that potentially breaks metric collection
Fixed an issue in containerd that prevented some v2 shims from shutting down properly.
Upgraded sys-auth/pambase to v20250228.
Upgraded app-containers/docker-credential-helpers to v0.9.2.
Upgraded app-admin/google-guest-agent to v20250304.03.
Upgraded app-admin/google-guest-configs to v20250221.00.
Upgraded app-admin/google-guest-configs to v20250124.00.
Upgraded app-containers/docker-registry-test to v2.8.3.
Upgraded dev-lang/go to v1.23.8.
Upgraded dev-db/sqlite to v3.49.1.
Upgraded sys-apps/acl to v2.3.2-r2.
Upgraded dev-libs/double-conversion to v3.3.1.
Upgraded sys-libs/libseccomp to v2.6.0.
Updated dev-go/net in policy manager to v0.39.0. This fixes CVE-2025-22870.
Fixed CVE-2025-32728 in net-misc/openssh.
Updated dev-vcs/git to version 2.49.0. This fixed CVE-2024-52006, CVE-2024-50349
Runtime sysctl changes:
- Changed: fs.file-max: 811714 -> 811806
cos-dev-125-19014-0-0
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
Patched a null ptr exception bug in NVIDIA 570.124.06 OSS driver
Fixed an issue in containerd that potentially breaks metric collection
Fixed an issue in containerd that prevented some v2 shims from shutting down properly.
Updated dev-go/net in policy manager to v0.39.0. This fixes CVE-2025-22870.
Fixed CVE-2025-32728 in net-misc/openssh.
Fixed CVE-2025-31498 in net-dns/c-ares.
Runtime sysctl changes:
- Changed: fs.file-max: 811798 -> 811785
cos-117-18613-164-124
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.72 | v24.0.9 | v1.7.24 | See List |
Fixed CVE-2025-32728 in net-misc/openssh.
Runtime sysctl changes:
- Changed: fs.file-max: 811760 -> 811753
New Dataproc on Compute Engine subminor image versions:
2.0.138-debian10, 2.0.138-rocky8, 2.0.138-ubuntu18
2.1.86-debian11, 2.1.86-rocky8, 2.1.86-ubuntu20, 2.1.86-ubuntu20-arm
2.2.54-debian12, 2.2.54-rocky9, 2.2.54-ubuntu22
Dataproc on Compute Engine: Fixed Job ID retrieval in Dataproc job logs for clusters created with 2.0
, 2.1
image versions, by ignoring timestamp prefix.
Dataproc on Compute Engine: Added an temporary object hold on the spark-job-history
folder in Cloud Stroage to prevent deletion by Cloud Storage life cycling.
VS Code Gemini Code Assist (version 2.32.0
) now supports creation and management of multiple chats.
VS Code Gemini Code Assist (version 2.32.0
) now supports streamlined multi-part chat code suggestions. You have the option to accept a single code change or all suggested changes.
You can now specify and apply rules to each chat request with VS Code Gemini Code Assist (version 2.32.0
).
Gemini 1.5 Pro and Gemini 1.5 Flash models are not available in projects that have no prior usage of these models, including new projects. For details, see Model versions and lifecycle.
Advanced reporting dashboards are released for GA
Advanced reporting dashboards can help you gain insights into the performance of your contact center. You can create new custom dashboards based on tiles from other dashboards and use powerful editing capabilities to customize dashboards to suit your business needs. Advanced reporting dashboards are released for General Availability. For more information, see Advanced reporting dashboards.
For dialects that support period-over-period measures, Looker developers can create a measure
of type: period_over_period
to enable period-over-period analysis in the corresponding Looker Explores. See Period-over-period measures in Looker for more information.
For Looker connections with Google BigQuery, Looker admins can now specify a Temp Project that is used to write PDTs to your database and a PDT Override Billing Project ID that is used for billing for PDT build and maintenance queries.
In addition to automated 24-hour backups, Looker (Google Cloud core) now supports customer-initiated backups and self-service restore.
IPv4 address range filtering for VPC spokes is available in public preview.
This feature lets you change IPv4 address ranges for VPC spokes that are specified to be exported to hub.
Vulnerability Assessment for Google Cloud has been released to Preview. This feature helps to discover critical and high severity software vulnerabilities in your Compute Engine VM instances without installing agents.
Vulnerability Assessment for Google Cloud is on by default. Customers might see an increase in findings due to vulnerabilities in existing virtual machines that weren't previously detected.
Preview stage support for the following integration:
April 28, 2025
BigQueryA weekly digest of client library updates from across the Cloud SDK.
A weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-bigquery
2.49.2 (2025-04-26)
Dependencies
When you translate SQL queries from your source database, you can use configuration YAML files to optimize and improve the performance of your translated SQL. This feature is generally available (GA).
Dataplex automatic discovery in BigQuery scans your data in Cloud Storage buckets to extract and catalog metadata, creating BigLake, external, or object tables for analytics and AI for insights, security, and governance. This feature is generally available (GA).
The following resource types are now publicly available through the ExportAssets, ListAssets, BatchGetAssetsHistory, QueryAssets, Feed, and Search (SearchAllResources, SearchAllIamPolicies) APIs.
- Security Command Center
securitycenter.googleapis.com/BigQueryExport
securitycenter.googleapis.com/ContainerThreatDetectionSettings
securitycenter.googleapis.com/EventThreatDetectionSettings
securitycenter.googleapis.com/MuteConfig
securitycenter.googleapis.com/NotificationConfig
securitycenter.googleapis.com/ResourceValueConfig
securitycenter.googleapis.com/SecurityHealthAnalyticsSettings
securitycenter.googleapis.com/VirtualMachineThreatDetectionSettings
securitycenter.googleapis.com/WebSecurityScannerSettings
- Oracle Database@Google Cloud
oracledatabase.googleapis.com/AutonomousDatabase
oracledatabase.googleapis.com/CloudExadataInfrastructure
oracledatabase.googleapis.com/CloudVmCluster
Using a fully qualified domain name (FQDN) forwarding target is available for outbound DNS forwarding in Preview.
A weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-logging
3.22.2 (2025-04-25)
Dependencies
3.22.1 (2025-04-25)
Bug Fixes
- deps: Update the Java code generator (gapic-generator-java) to 2.56.2 (7cce5b5)
Python
Changes for google-cloud-logging
3.12.1 (2025-04-21)
Bug Fixes
A weekly digest of client library updates from across the Cloud SDK.
Go
Changes for storage/internal/apiv2
1.52.0 (2025-04-22)
Features
- storage/control: Add Anywhere cache control APIs (#11807) (12bfa98)
- storage: Add CurrentState function to determine state of stream in MRD (#11688) (14e8e13)
- storage: Add OwnerEntity to bucketAttrs (#11857) (4cd4a0c)
- storage: Takeover appendable object (#11977) (513b937)
- storage: Unfinalized appendable objects. (#11647) (52c0218)
Bug Fixes
- storage: Fix Attrs for append takeover (#11989) (6db35b1)
- storage: Fix panic when Flush called early (#11934) (7d0b8a7)
- storage: Fix unfinalized write size (#12016) (6217f8f)
- storage: Force first message on next sendBuffer when nothing sent on current (#11871) (a1a2292)
- storage: Populate Writer.Attrs after Flush() (#12021) (8e56f74)
- storage: Remove check for FinalizeOnClose (#11992) (2664b8c)
- storage: Wrap read response parsing errors (#11951) (d2e6583)
Java
Changes for google-cloud-storage
2.51.0 (2025-04-23)
Features
- Add @BetaApi Storage#blobAppendableUpload for gRPC Transport (#3020) (62b6248)
- Add @BetaApi Storage#blobReadSession for gRPC Transport (#3020) (62b6248)
- Implement improved retry context information (#3020) (62b6248)
Bug Fixes
- deps: Update the Java code generator (gapic-generator-java) to 2.56.0 (8f9f5ec)
- Ensure object generation is sent for Storage#update(BlobInfo) using HTTP Transport (#3006) (2a3e0e7), closes #2980
- Update 416 handling for ReadChannel (#3018) (4a9c3e4)
- Update gRPC Bidi resumable upload to have more robust error message generation (#2998) (79b5d85)
- Update gRPC implementation for storage.buckets.get to translate NOT_FOUND to null (#3005) (704af65)
Dependencies
- Remove explicit version declarations for packages that are in shared-dependencies (#3014) (61cdb30)
- Update dependency com.google.apis:google-api-services-storage to v1-rev20250312-2.0.0 (#3000) (78fc076)
- Update dependency com.google.cloud.opentelemetry:exporter-trace to v0.34.0 (#2938) (ff6f696)
- Update sdk-platform-java dependencies (#3046) (861f958)
- Update sdk-platform-java dependencies (#3053) (921d1ba)
Public preview: Resize request in a managed instance group (MIG) lets you specify the name of the VMs to create all at once. This feature helps if your orchestration mechanism or workload requires specific VM naming. For more information, see About resize requests in a MIG.
Generally available: The Memory-optimized machine family has added two new M4 machine types:
- m4-megamem-28
- m4-ultramem-224
The m4-megamem-28 offers 28 vCPUs with 372 GB of memory. The m4-ultramem-224 offers 224 vCPUs with 5,952 GB of memory.
Quality AI offers the following conversation filters:
- CSAT
- Sentiment score
- Silence duration
Dataplex automatic discovery scans your data in Cloud Storage buckets to extract and catalog metadata, creating BigLake, external, or object tables for analytics and AI for insights, security, and governance. This feature is generally available (GA).
Custom performance is now generally available for Filestore instances.
AI and ML perspective: Operational excellence: Major update to expand the operational excellence recommendations in the AI and ML perspective.
(2025-R16) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.29.14-gke.1067000
- 1.29.14-gke.1086000
- 1.29.15-gke.1170000
- 1.30.11-gke.1131000
- 1.31.7-gke.1013002
- 1.31.7-gke.1212000
- 1.32.3-gke.1717000
Regular channel
- The following versions are no longer available in the Regular channel:
- 1.29.14-gke.1018000
- 1.29.14-gke.1067000
Stable channel
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Stable channel.
- The following versions are no longer available in the Stable channel:
- 1.29.13-gke.1038000
- 1.29.13-gke.1169000
Extended channel
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2595000
- 1.27.16-gke.2664000
- 1.28.15-gke.2027000
- 1.28.15-gke.2121000
- 1.29.14-gke.1018000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2072000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2633000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2072000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.14-gke.1067000 with this release.
No channel
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.29.13-gke.1038000
- 1.29.13-gke.1169000
- 1.29.14-gke.1018000
- 1.29.14-gke.1067000
- 1.29.14-gke.1086000
- 1.29.15-gke.1170000
- 1.30.9-gke.1127000
- 1.30.11-gke.1131000
- 1.31.7-gke.1013002
- 1.31.7-gke.1212000
- 1.32.3-gke.1717000
(2025-R16) Version updates
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.29.14-gke.1067000
- 1.29.14-gke.1086000
- 1.29.15-gke.1170000
- 1.30.11-gke.1131000
- 1.31.7-gke.1013002
- 1.31.7-gke.1212000
- 1.32.3-gke.1717000
(2025-R16) Version updates
- The following versions are no longer available in the Regular channel:
- 1.29.14-gke.1018000
- 1.29.14-gke.1067000
(2025-R16) Version updates
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Stable channel.
- The following versions are no longer available in the Stable channel:
- 1.29.13-gke.1038000
- 1.29.13-gke.1169000
(2025-R16) Version updates
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2595000
- 1.27.16-gke.2664000
- 1.28.15-gke.2027000
- 1.28.15-gke.2121000
- 1.29.14-gke.1018000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.28.15-gke.2072000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2633000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2072000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.29 to version 1.29.14-gke.1067000 with this release.
(2025-R16) Version updates
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.29.13-gke.1038000
- 1.29.13-gke.1169000
- 1.29.14-gke.1018000
- 1.29.14-gke.1067000
- 1.29.14-gke.1086000
- 1.29.15-gke.1170000
- 1.30.9-gke.1127000
- 1.30.11-gke.1131000
- 1.31.7-gke.1013002
- 1.31.7-gke.1212000
- 1.32.3-gke.1717000
Google SecOps has updated the list of supported default parsers. Parsers are updated gradually, so changes may take one-to-four days to appear in your region.
The following supported default parsers have been updated. Each parser is listed by product name and log_type
value, if applicable. This list now includes both released default parsers and pending parser updates.
- 1Password Audit Events (
ONEPASSWORD_AUDIT_EVENTS
) - AIX system (
AIX_SYSTEM
) - Akamai DataStream 2 (
AKAMAI_DATASTREAM_2
) - Alveo Risk Data Management (
ALVEO_RDM
) - Amazon API Gateway (
AWS_API_GATEWAY
) - Apache Tomcat (
TOMCAT
) - Appian Cloud (
APPIAN_CLOUD
) - Arcsight CEF (
ARCSIGHT_CEF
) - Asset Panda (
ASSET_PANDA
) - Aware Audit (
AWARE_AUDIT
) - Aware Signals (
AWARE_SIGNALS
) - AWS Cloudtrail (
AWS_CLOUDTRAIL
) - AWS CloudWatch (
AWS_CLOUDWATCH
) - AWS ECS Metrics (
AWS_ECS_METRICS
) - AWS Elastic Load Balancer (
AWS_ELB
) - AWS GuardDuty (
GUARDDUTY
) - AWS Inspector (
AWS_INSPECTOR
) - AWS Lambda Function (
AWS_LAMBDA_FUNCTION
) - AWS RDS (
AWS_RDS
) - AWS Redshift (
AWS_REDSHIFT
) - AWS Route 53 DNS (
AWS_ROUTE_53
) - AWS Security Hub (
AWS_SECURITY_HUB
) - AWS VPC Flow (
AWS_VPC_FLOW
) - AWS WAF (
AWS_WAF
) - Azure AD Directory Audit (
AZURE_AD_AUDIT
) - Azure AD Organizational Context (
AZURE_AD_CONTEXT
) - Azure Application Gateway (
AZURE_GATEWAY
) - Azure Firewall (
AZURE_FIREWALL
) - Azure Key Vault logging (
AZURE_KEYVAULT_AUDIT
) - Barracuda CloudGen Firewall (
BARRACUDA_CLOUDGEN_FIREWALL
) - Barracuda WAF (
BARRACUDA_WAF
) - BeyondTrust BeyondInsight (
BEYONDTRUST_BEYONDINSIGHT
) - Blue Coat Proxy (
BLUECOAT_WEBPROXY
) - Broadcom Support Portal Audit Logs (
BROADCOM_SUPPORT_PORTAL
) - Cato Networks (
CATO_NETWORKS
) - Cequence Bot Defense (
CEQUENCE_BOT_DEFENSE
) - Check Point (
CHECKPOINT_FIREWALL
) - ChromeOS XDR (
CHROMEOS_XDR
) - Cisco Email Security (
CISCO_EMAIL_SECURITY
) - Cisco EStreamer (
CISCO_ESTREAMER
) - Cisco Firepower NGFW (
CISCO_FIREPOWER_FIREWALL
) - Cisco FireSIGHT Management Center (
CISCO_FIRESIGHT
) - Cisco Internetwork Operating System (
CISCO_IOS
) - Cisco IronPort (
CISCO_IRONPORT
) - Cisco ISE (
CISCO_ISE
) - Cisco NX-OS (
CISCO_NX_OS
) - Cisco Switch (
CISCO_SWITCH
) - Cisco Umbrella Cloud Firewall (
UMBRELLA_FIREWALL
) - Cisco vManage SD-WAN (
CISCO_SDWAN
) - Cisco VPN (
CISCO_VPN
) - Citrix Netscaler (
CITRIX_NETSCALER
) - Citrix Storefront (
CITRIX_STOREFRONT
) - Claroty Xdome (
CLAROTY_XDOME
) - Cloud Audit Logs (
N/A
) - Cloud Data Loss Prevention (
N/A
) - Cloudflare Network Analytics (
CLOUDFLARE_NETWORK_ANALYTICS
) - Cloudflare WAF (
CLOUDFLARE_WAF
) - Cloudflare Warp (
CLOUDFLARE_WARP
) - CommVault (
COMMVAULT
) - CrowdStrike Detection Monitoring (
CS_DETECTS
) - CrowdStrike Falcon (
CS_EDR
) - CrowdStrike Falcon Stream (
CS_STREAM
) - CrowdStrike Identity Protection Services (
CS_IDP
) - CrushFTP (
CRUSHFTP
) - Custom Application Access Logs (
CUSTOM_APPLICATION_ACCESS
) - CyberArk Privileged Access Manager (PAM) (
CYBERARK_PAM
) - Cybereason EDR (
CYBEREASON_EDR
) - Cyolo Secure Remote Access for OT (
CYOLO_OT
) - Datadog (
DATADOG
) - Delinea Secret Server (
DELINEA_SECRET_SERVER
) - Dell CyberSense (
DELL_CYBERSENSE
) - Digicert (
DIGICERT
) - Edgio WAF (
EDGIO_WAF
) - Elastic Packet Beats (
ELASTIC_PACKETBEATS
) - F5 ASM (
F5_ASM
) - F5 DNS (
F5_DNS
) - Forcepoint DLP (
FORCEPOINT_DLP
) - Forcepoint NGFW (
FORCEPOINT_FIREWALL
) - Forgerock OpenIdM (
FORGEROCK_OPENIDM
) - FortiGate (
FORTINET_FIREWALL
) - Fortinet FortiAnalyzer (
FORTINET_FORTIANALYZER
) - Fortinet Fortimanager (
FORTINET_FORTIMANAGER
) - Fortinet Web Application Firewall (
FORTINET_FORTIWEB
) - GitHub (
GITHUB
) - Gitlab (
GITLAB
) - Harness IO (
HARNESS_IO
) - Hashicorp Vault (
HASHICORP
) - Hillstone Firewall (
HILLSTONE_NGFW
) - Huawei Switches (
HUAWEI_SWITCH
) - IBM Guardium (
GUARDIUM
) - Imperva Database (
IMPERVA_DB
) - Intel Endpoint Management Assistant (
INTEL_EMA
) - JAMF Security Cloud (
JAMF_SECURITY_CLOUD
) - JFrog Artifactory (
JFROG_ARTIFACTORY
) - JumpCloud Directory Insights (
JUMPCLOUD_DIRECTORY_INSIGHTS
) - Juniper (
JUNIPER_FIREWALL
) - Kaspersky AV (
KASPERSKY_AV
) - Kaspersky Endpoint (
KASPERSKY_ENDPOINT
) - Kolide Endpoint Security (
KOLIDE
) - Kubernetes Audit (
KUBERNETES_AUDIT
) - Layer7 SiteMinder (
SITEMINDER_SSO
) - Linux Auditing System (AuditD) (
AUDITD
) - Looker Audit (
LOOKER_AUDIT
) - ManageEngine ADAudit Plus (
ADAUDIT_PLUS
) - ManageEngine ADManager Plus (
ADMANAGER_PLUS
) - McAfee Web Gateway (
MCAFEE_WEBPROXY
) - Metabase (
METABASE
) - Microsoft AD FS (
ADFS
) - Microsoft Azure Activity (
AZURE_ACTIVITY
) - Microsoft Azure NSG Flow (
AZURE_NSG_FLOW
) - Microsoft CyberX (
CYBERX
) - Microsoft Defender for Endpoint (
MICROSOFT_DEFENDER_ENDPOINT
) - Microsoft Defender for Identity (
MICROSOFT_DEFENDER_IDENTITY
) - Microsoft Defender for Office 365 (
MICROSOFT_DEFENDER_MAIL
) - Microsoft IIS (
IIS
) - Microsoft PowerShell (
POWERSHELL
) - Microsoft Sentinel (
MICROSOFT_SENTINEL
) - Microsoft System Center Endpoint Protection (
MICROSOFT_SCEP
) - Mikrotik Router (
MIKROTIK_ROUTER
) - Mimecast (
MIMECAST_MAIL
) - MISP Threat Intelligence (
MISP_IOC
) - NetIQ eDirectory (
NETIQ_EDIRECTORY
) - Netskope V2 (
NETSKOPE_ALERT_V2
) - Nozomi Networks Scada Guardian (
NOZOMI_GUARDIAN
) - Office 365 (
OFFICE_365
) - Okta (
OKTA
) - Okta User Context (
OKTA_USER_CONTEXT
) - One Identity Identity Manager (
ONE_IDENTITY_IDENTITY_MANAGER
) - Oort Security Tool (
OORT
) - Open Cybersecurity Schema Framework (OCSF) (
OCSF
) - Open LDAP (
OPENLDAP
) - Opnsense (
OPNSENSE
) - Ops Genie (
OPS_GENIE
) - Oracle (
ORACLE_DB
) - Oracle Cloud Guard (
OCI_CLOUDGUARD
) - Oracle Cloud Infrastructure Audit Logs (
OCI_AUDIT
) - Orca Cloud Security Platform (
ORCA
) - Palo Alto Cortex XDR Alerts (
CORTEX_XDR
) - Palo Alto Networks Firewall (
PAN_FIREWALL
) - Palo Alto Panorama (
PAN_PANORAMA
) - Palo Alto Prisma Access (
PAN_CASB
) - Palo Alto Prisma Cloud Alert payload (
PAN_PRISMA_CA
) - Pharos (
PHAROS
) - Privacy-I (
PRIVACY_I
) - Proofpoint On Demand (
PROOFPOINT_ON_DEMAND
) - Proofpoint Tap Alerts (
PROOFPOINT_MAIL
) - Proofpoint Threat Response (
PROOFPOINT_TRAP
) - Radware Web Application Firewall (
RADWARE_FIREWALL
) - ReviveSec (
REVIVESEC
) - Rubrik (
RUBRIK
) - Salesforce (
SALESFORCE
) - Sangfor Proxy (
SANGFOR_PROXY
) - Security Command Center Posture Violation (
GCP_SECURITYCENTER_POSTURE_VIOLATION
) - Security Command Center Threat (
N/A
) - Security Command Center Toxic Combination (
GCP_SECURITYCENTER_TOXIC_COMBINATION
) - ServiceNow CMDB (
SERVICENOW_CMDB
) - Snare System Diagnostic Logs (
SNARE_SOLUTIONS
) - Snipe-IT (
SNIPE_IT
) - Snyk Group level audit/issues logs (
SNYK_ISSUES
) - SonicWall (
SONIC_FIREWALL
) - Sophos Central (
SOPHOS_CENTRAL
) - Swimlane Platform (
SWIMLANE
) - Symantec DLP (
SYMANTEC_DLP
) - Symantec Event export (
SYMANTEC_EVENT_EXPORT
) - Symantec Web Security Service (
SYMANTEC_WSS
) - Tanium Question (
TANIUM_QUESTION
) - Tanium Threat Response (
TANIUM_THREAT_RESPONSE
) - Teleport Access Plane (
TELEPORT_ACCESS_PLANE
) - Tenable Active Directory Security (
TENABLE_ADS
) - Tenable CSPM (
TENABLE_CSPM
) - tenable.io (
TENABLE_IO
) - Terraform Enterprise Audit (
TERRAFORM_ENTERPRISE
) - Thinkst Canary (
THINKST_CANARY
) - ThreatX WAF (
THREATX_WAF
) - Trend Micro Email Security Advanced (
TRENDMICRO_EMAIL_SECURITY
) - Trend Micro Vision One (
TRENDMICRO_VISION_ONE
) - TrendMicro Apex Central (
TRENDMICRO_APEX_CENTRAL
) - TXOne Stellar (
TRENDMICRO_STELLAR
) - UKG (
UKG
) - Unix system (
NIX_SYSTEM
) - UPX AntiDDoS (
UPX_ANTIDDOS
) - VanDyke SFTP (
VANDYKE_SFTP
) - Varonis (
VARONIS
) - Vectra Alerts (
VECTRA_ALERTS
) - Vectra Stream (
VECTRA_STREAM
) - VMware AirWatch (
AIRWATCH
) - Vmware Avinetworks iWAF (
VMWARE_AVINETWORKS_IWAF
) - VMware ESXi (
VMWARE_ESX
) - VMware Horizon (
VMWARE_HORIZON
) - Watchguard EDR (
WATCHGUARD_EDR
) - Windows Defender AV (
WINDOWS_DEFENDER_AV
) - Windows DHCP (
WINDOWS_DHCP
) - Windows DNS (
WINDOWS_DNS
) - Windows Event (
WINEVTLOG
) - Windows Event (XML) (
WINEVTLOG_XML
) - Windows Sysmon (
WINDOWS_SYSMON
) - Workday Audit Logs (
WORKDAY_AUDIT
) - Workday User Activity (
WORKDAY_USER_ACTIVITY
) - WPEngine (
WPENGINE
) - Zimperium (
ZIMPERIUM
) - Zscaler (
ZSCALER_WEBPROXY
) - ZScaler DNS (
ZSCALER_DNS
) - Zscaler Internet Access Audit Logs (
ZSCALER_INTERNET_ACCESS
) - ZScaler NGFW (
ZSCALER_FIREWALL
)
The following log types were added without a default parser. Each parser is listed by product name and log_type
value, if applicable.
- Accenture Synthetic (
ACCENTURE_SYNTHETIC
) - Adyen Platform (
ADYEN
) - AliCloud ActionTrail (
ALICLOUD_ACTIONTRAIL
) - Apache LOG4J Java Application Log (
LOG4J
) - AppSmith Audit (
APPSMITH_AUDIT
) - Arctic Security Arctic Node (
ARCTIC_NODE
) - Arista CorvilNet DANZ Integration (
ARISTA_CORVILNET
) - Arista Extensible Operating System (
ARISTA_EOS
) - AvePoint EnPower (
AVEPOINT_ENPOWER
) - Avigilon Alta Cloud Security (
AVIGILON_ALTA_CLOUD_SECURITY
) - Avigilon Ava Security Camera (
AVIGILON_AVA_SECURITY_CAMERA
) - AWS Dasha (
AWS_DASHA
) - AWS Elastic Kubernetes Service (
AWS_EKS
) - Azure Network Security Group Event (
AZURE_NSG_EVENT
) - Azure Windows Virtual Desktop Connections Logs (
AZURE_WVD_CONNECTIONS
) - Azure Windows Virtual Desktop Management Logs (
AZURE_WVD_MANAGEMENT
) - Barracuda Load Balancer ADC (
BARRACUDA_LOAD_BALANCER
) - Broadcom Edge Secure Web Gateway (
BROADCOM_EDGE_SWG
) - Celonis Audit Logs (
CELONIS
) - Chopin PrePay Solutions (
CHOPIN_PPS
) - Cisco Duo Authentication Proxy (
DUO_AUTH_PROXY
) - Cloudflare CASB Findings (
CLOUDFLARE_CASB_FINDINGS
) - Cloudflare Device posture results (
CLOUDFLARE_DEVICE_POSTURE_RESULTS
) - Cloudflare DLP Forensic Copies (
CLOUDFLARE_DLP_FORENSIC_COPIES
) - Cloudflare DNS Firewall Logs (
CLOUDFLARE_DNS_FIREWALL_LOGS
) - Cloudflare DNS logs (
CLOUDFLARE_DNS_LOGS
) - Cloudflare Email Security Alerts (
CLOUDFLARE_EMAIL_SECURITY_ALERTS
) - Cloudflare Firewall Events (
CLOUDFLARE_FIREWALL_EVENTS
) - Cloudflare Gateway DNS (
CLOUDFLARE_GATEWAY_DNS
) - Cloudflare Gateway HTTP (
CLOUDFLARE_GATEWAY_HTTP
) - Cloudflare Gateway Network (
CLOUDFLARE_GATEWAY_NETWORK
) - Cloudflare HTTP requests (
CLOUDFLARE_HTTP_REQUESTS
) - Cloudflare Magic IDS Detections (
CLOUDFLARE_MAGIC_IDS_DETECTIONS
) - Cloudflare NEL reports (
CLOUDFLARE_NEL_REPORTS
) - Cloudflare Sinkhole HTTP Logs (
CLOUDFLARE_SINKHOLE_HTTP_LOGS
) - Cloudflare SSH Logs (
CLOUDFLARE_SSH_LOGS
) - Cloudflare Workers Trace Events (
CLOUDFLARE_WORKERS_TRACE_EVENTS
) - Cloudflare Zero Trust Network Session (
CLOUDFLARE_ZERO_TRUST_NETWORK_SESSION
) - CloudWave Honeypot (
CLOUDWAVE_HONEYPOT
) - ColorTokens (
COLORTOKENS
) - Contrast Security (
CONTRAST_SECURITY
) - Conversational Agents and Dialogflow (
CONVERSATIONAL_AGENT
) - Corero SmartWall One (
CORERO_SMARTWALL_ONE
) - Cytracom Control One (
CYTRACOM_CONTROL_ONE
) - Datadog Application Security Management (
DATADOG_ASM
) - Express NodeJS (
EXPRESS_NODEJS
) - F5 Distributed Cloud WAF (
F5_DCS_WAF
) - Figma Developers (
FIGMA
) - FIS Trax Payment Factory (
TRAX
) - Fortinet FortiDeceptor (
FORTINET_FORTIDECEPTOR
) - Fortinet FortiSASE (
FORTINET_FORTISASE
) - Gemini Code Assist (
GEMINI_CODE_ASSIST
) - Genea Access Control (
GENEA_ACCESS_CONTROL
) - Genetec Synergis (
GENETEC_SYNERGIS
) - GL TRADE (
GL_TRADE
) - HP Inc MFP (
HP_INC_MFP
) - HP Tandem (
HP_TANDEM
) - Huawei Versatile Routing Platform (
HUAWEI_VRP
) - Human Security (
HUMAN_SECURITY
) - iManage Threat Manager (
IMANAGE_THREAT_MANAGER
) - Indefend DLP (
INDEFEND_DLP
) - Invicti (
INVICTI
) - Isonline ISL Light (
ISL_LIGHT
) - Itential Pronghorn (
ITENTIAL_PRONGHORN
) - Jit (
JIT
) - Kodem Security (
KODEM_SECURITY
) - Konica Minolta YSoft SafeQ (
YSOFT_SAFEQ
) - LayerX (
LAYERX
) - LinOTP (
LIN_OTP
) - Magento Cloud (
MAGENTO_CLOUD
) - Mandiant Advantage Security Validation (
MA_SV
) - NetApp ONTAP Audit (
NETAPP_ONTAP_AUDIT
) - Netscout Arbor Threat Mitigation System (
NETSCOUT_TMS
) - Netwrix Privilege Secure (
NETWRIX_PRIVILEGE_SECURE
) - NeuVector SUSE (
NEUVECTOR
) - Novidea Insurance Management System (
NOVIDEA_CLAIM_HISTORY
) - OneTrust (
ONETRUST
) - Openpath Context (
OPENPATH_CONTEXT
) - Oracle Audit Vault Database Firewall (
ORACLE_AVDF
) - Oracle CPQ (
ORACLE_CPQ
) - Oracle Exadata Database Machine (
ORACLE_EXADATA
) - Palo Alto Prisma Cloud Workload Protection (
PAN_PRISMA_CWP
) - Palo Alto Prisma Dig Cloud DSPM (
PAN_PRISMA_DIG_CLOUD_DSPM
) - Panorays (
PANORAYS
) - Pathlock Identity Security Platform (
PATHLOCK
) - Procore (
PROCORE
) - ProofPoint Email Protection (
PROOFPOINT_EMAIL_PROTECTION
) - Radiantone (
RADIANTONE
) - Radware Cloud WAF Service Access (
RADWARE_ACCESS
) - Reblaze Web Application Firewall (
REBLAZE_WAF
) - Red Access Browsing Security (
RED_ACCESS
) - SafeNet Network HSM (
SAFENET_HSM
) - Salesforce Marketing Cloud Audit (
SALESFORCE_MARKETING_CLOUD_AUDIT
) - Salesforce Shield (
SALESFORCE_SHIELD
) - Sangfor IAG (
SANGFOR_IAG
) - SAP Leasing (
SAP_LEASING
) - SAS Institute (
SAS_INSTITUTE
) - Securden (
SECURDEN
) - SecurEnvoy SecurAccess (
SECURENVOY_MFA
) - Securesoft Sniper IPS (
SECURESOFT_SNIPER_IPS
) - Sentra Data Loss Prevention (
SENTRA_DLP
) - Shield IoT (
SHIELD_IOT
) - Siemens Simatic S7 PLC SNMP (
SIEMENS_S7_PLC_SNMP
) - Siemens Simatic S7 PLC SYSLOG (
SIEMENS_S7_PLC_SYSLOG
) - Smartsheet User Context (
SMARTSHEET_USER_CONTEXT
) - Snowflake Access (
SNOWFLAKE_ACCESS
) - SOCRadar Incidents (
SOCRADAR_INCIDENTS
) - Strata Maverics Identity Orchestration Platform (
STRATA_MAVERICS
) - Stripe Payments (
STRIPE
) - Suridata (
SURIDATA
) - Teradata Access (
TERADATA_ACCESS
) - Thales payShield 10K HSM (
THALES_PS10K_HSM
) - Trend Micro TippingPoint Security Management System (
TREND_MICRO_TIPPING_POINT
) - Valence Security (
VALENCE
) - Vertica Audit (
VERTICA_AUDIT
) - Windows NTP (
WINDOWS_NTP
) - Winget Autoupdate (
WINGET_AUTOUPDATE
) - Wiz Runtime Execution Data (
WIZ_RUNTIME_EXECUTION_DATA
) - Workiva Wdesk (
WORKIVA_WDESK
) - XL Release (
XLR
) - Yugabyte Database (
YUGABYTE_DATABASE
)
For a list of supported log types and details about default parser changes, see Supported log types and default parsers.
Google SecOps has updated the list of supported default parsers. Parsers are updated gradually, so changes may take one-to-four days to appear in your region.
The following supported default parsers have been updated. Each parser is listed by product name and log_type
value, if applicable. This list now includes both released default parsers and pending parser updates.
- 1Password Audit Events (
ONEPASSWORD_AUDIT_EVENTS
) - AIX system (
AIX_SYSTEM
) - Akamai DataStream 2 (
AKAMAI_DATASTREAM_2
) - Alveo Risk Data Management (
ALVEO_RDM
) - Amazon API Gateway (
AWS_API_GATEWAY
) - Apache Tomcat (
TOMCAT
) - Appian Cloud (
APPIAN_CLOUD
) - Arcsight CEF (
ARCSIGHT_CEF
) - Asset Panda (
ASSET_PANDA
) - Aware Audit (
AWARE_AUDIT
) - Aware Signals (
AWARE_SIGNALS
) - AWS Cloudtrail (
AWS_CLOUDTRAIL
) - AWS CloudWatch (
AWS_CLOUDWATCH
) - AWS ECS Metrics (
AWS_ECS_METRICS
) - AWS Elastic Load Balancer (
AWS_ELB
) - AWS GuardDuty (
GUARDDUTY
) - AWS Inspector (
AWS_INSPECTOR
) - AWS Lambda Function (
AWS_LAMBDA_FUNCTION
) - AWS RDS (
AWS_RDS
) - AWS Redshift (
AWS_REDSHIFT
) - AWS Route 53 DNS (
AWS_ROUTE_53
) - AWS Security Hub (
AWS_SECURITY_HUB
) - AWS VPC Flow (
AWS_VPC_FLOW
) - AWS WAF (
AWS_WAF
) - Azure AD Directory Audit (
AZURE_AD_AUDIT
) - Azure AD Organizational Context (
AZURE_AD_CONTEXT
) - Azure Application Gateway (
AZURE_GATEWAY
) - Azure Firewall (
AZURE_FIREWALL
) - Azure Key Vault logging (
AZURE_KEYVAULT_AUDIT
) - Barracuda CloudGen Firewall (
BARRACUDA_CLOUDGEN_FIREWALL
) - Barracuda WAF (
BARRACUDA_WAF
) - BeyondTrust BeyondInsight (
BEYONDTRUST_BEYONDINSIGHT
) - Blue Coat Proxy (
BLUECOAT_WEBPROXY
) - Broadcom Support Portal Audit Logs (
BROADCOM_SUPPORT_PORTAL
) - Cato Networks (
CATO_NETWORKS
) - Cequence Bot Defense (
CEQUENCE_BOT_DEFENSE
) - Check Point (
CHECKPOINT_FIREWALL
) - ChromeOS XDR (
CHROMEOS_XDR
) - Cisco Email Security (
CISCO_EMAIL_SECURITY
) - Cisco EStreamer (
CISCO_ESTREAMER
) - Cisco Firepower NGFW (
CISCO_FIREPOWER_FIREWALL
) - Cisco FireSIGHT Management Center (
CISCO_FIRESIGHT
) - Cisco Internetwork Operating System (
CISCO_IOS
) - Cisco IronPort (
CISCO_IRONPORT
) - Cisco ISE (
CISCO_ISE
) - Cisco NX-OS (
CISCO_NX_OS
) - Cisco Switch (
CISCO_SWITCH
) - Cisco Umbrella Cloud Firewall (
UMBRELLA_FIREWALL
) - Cisco vManage SD-WAN (
CISCO_SDWAN
) - Cisco VPN (
CISCO_VPN
) - Citrix Netscaler (
CITRIX_NETSCALER
) - Citrix Storefront (
CITRIX_STOREFRONT
) - Claroty Xdome (
CLAROTY_XDOME
) - Cloud Audit Logs (
N/A
) - Cloud Data Loss Prevention (
N/A
) - Cloudflare Network Analytics (
CLOUDFLARE_NETWORK_ANALYTICS
) - Cloudflare WAF (
CLOUDFLARE_WAF
) - Cloudflare Warp (
CLOUDFLARE_WARP
) - CommVault (
COMMVAULT
) - CrowdStrike Detection Monitoring (
CS_DETECTS
) - CrowdStrike Falcon (
CS_EDR
) - CrowdStrike Falcon Stream (
CS_STREAM
) - CrowdStrike Identity Protection Services (
CS_IDP
) - CrushFTP (
CRUSHFTP
) - Custom Application Access Logs (
CUSTOM_APPLICATION_ACCESS
) - CyberArk Privileged Access Manager (PAM) (
CYBERARK_PAM
) - Cybereason EDR (
CYBEREASON_EDR
) - Cyolo Secure Remote Access for OT (
CYOLO_OT
) - Datadog (
DATADOG
) - Delinea Secret Server (
DELINEA_SECRET_SERVER
) - Dell CyberSense (
DELL_CYBERSENSE
) - Digicert (
DIGICERT
) - Edgio WAF (
EDGIO_WAF
) - Elastic Packet Beats (
ELASTIC_PACKETBEATS
) - F5 ASM (
F5_ASM
) - F5 DNS (
F5_DNS
) - Forcepoint DLP (
FORCEPOINT_DLP
) - Forcepoint NGFW (
FORCEPOINT_FIREWALL
) - Forgerock OpenIdM (
FORGEROCK_OPENIDM
) - FortiGate (
FORTINET_FIREWALL
) - Fortinet FortiAnalyzer (
FORTINET_FORTIANALYZER
) - Fortinet Fortimanager (
FORTINET_FORTIMANAGER
) - Fortinet Web Application Firewall (
FORTINET_FORTIWEB
) - GitHub (
GITHUB
) - Gitlab (
GITLAB
) - Harness IO (
HARNESS_IO
) - Hashicorp Vault (
HASHICORP
) - Hillstone Firewall (
HILLSTONE_NGFW
) - Huawei Switches (
HUAWEI_SWITCH
) - IBM Guardium (
GUARDIUM
) - Imperva Database (
IMPERVA_DB
) - Intel Endpoint Management Assistant (
INTEL_EMA
) - JAMF Security Cloud (
JAMF_SECURITY_CLOUD
) - JFrog Artifactory (
JFROG_ARTIFACTORY
) - JumpCloud Directory Insights (
JUMPCLOUD_DIRECTORY_INSIGHTS
) - Juniper (
JUNIPER_FIREWALL
) - Kaspersky AV (
KASPERSKY_AV
) - Kaspersky Endpoint (
KASPERSKY_ENDPOINT
) - Kolide Endpoint Security (
KOLIDE
) - Kubernetes Audit (
KUBERNETES_AUDIT
) - Layer7 SiteMinder (
SITEMINDER_SSO
) - Linux Auditing System (AuditD) (
AUDITD
) - Looker Audit (
LOOKER_AUDIT
) - ManageEngine ADAudit Plus (
ADAUDIT_PLUS
) - ManageEngine ADManager Plus (
ADMANAGER_PLUS
) - McAfee Web Gateway (
MCAFEE_WEBPROXY
) - Metabase (
METABASE
) - Microsoft AD FS (
ADFS
) - Microsoft Azure Activity (
AZURE_ACTIVITY
) - Microsoft Azure NSG Flow (
AZURE_NSG_FLOW
) - Microsoft CyberX (
CYBERX
) - Microsoft Defender for Endpoint (
MICROSOFT_DEFENDER_ENDPOINT
) - Microsoft Defender for Identity (
MICROSOFT_DEFENDER_IDENTITY
) - Microsoft Defender for Office 365 (
MICROSOFT_DEFENDER_MAIL
) - Microsoft IIS (
IIS
) - Microsoft PowerShell (
POWERSHELL
) - Microsoft Sentinel (
MICROSOFT_SENTINEL
) - Microsoft System Center Endpoint Protection (
MICROSOFT_SCEP
) - Mikrotik Router (
MIKROTIK_ROUTER
) - Mimecast (
MIMECAST_MAIL
) - MISP Threat Intelligence (
MISP_IOC
) - NetIQ eDirectory (
NETIQ_EDIRECTORY
) - Netskope V2 (
NETSKOPE_ALERT_V2
) - Nozomi Networks Scada Guardian (
NOZOMI_GUARDIAN
) - Office 365 (
OFFICE_365
) - Okta (
OKTA
) - Okta User Context (
OKTA_USER_CONTEXT
) - One Identity Identity Manager (
ONE_IDENTITY_IDENTITY_MANAGER
) - Oort Security Tool (
OORT
) - Open Cybersecurity Schema Framework (OCSF) (
OCSF
) - Open LDAP (
OPENLDAP
) - Opnsense (
OPNSENSE
) - Ops Genie (
OPS_GENIE
) - Oracle (
ORACLE_DB
) - Oracle Cloud Guard (
OCI_CLOUDGUARD
) - Oracle Cloud Infrastructure Audit Logs (
OCI_AUDIT
) - Orca Cloud Security Platform (
ORCA
) - Palo Alto Cortex XDR Alerts (
CORTEX_XDR
) - Palo Alto Networks Firewall (
PAN_FIREWALL
) - Palo Alto Panorama (
PAN_PANORAMA
) - Palo Alto Prisma Access (
PAN_CASB
) - Palo Alto Prisma Cloud Alert payload (
PAN_PRISMA_CA
) - Pharos (
PHAROS
) - Privacy-I (
PRIVACY_I
) - Proofpoint On Demand (
PROOFPOINT_ON_DEMAND
) - Proofpoint Tap Alerts (
PROOFPOINT_MAIL
) - Proofpoint Threat Response (
PROOFPOINT_TRAP
) - Radware Web Application Firewall (
RADWARE_FIREWALL
) - ReviveSec (
REVIVESEC
) - Rubrik (
RUBRIK
) - Salesforce (
SALESFORCE
) - Sangfor Proxy (
SANGFOR_PROXY
) - Security Command Center Posture Violation (
GCP_SECURITYCENTER_POSTURE_VIOLATION
) - Security Command Center Threat (
N/A
) - Security Command Center Toxic Combination (
GCP_SECURITYCENTER_TOXIC_COMBINATION
) - ServiceNow CMDB (
SERVICENOW_CMDB
) - Snare System Diagnostic Logs (
SNARE_SOLUTIONS
) - Snipe-IT (
SNIPE_IT
) - Snyk Group level audit/issues logs (
SNYK_ISSUES
) - SonicWall (
SONIC_FIREWALL
) - Sophos Central (
SOPHOS_CENTRAL
) - Swimlane Platform (
SWIMLANE
) - Symantec DLP (
SYMANTEC_DLP
) - Symantec Event export (
SYMANTEC_EVENT_EXPORT
) - Symantec Web Security Service (
SYMANTEC_WSS
) - Tanium Question (
TANIUM_QUESTION
) - Tanium Threat Response (
TANIUM_THREAT_RESPONSE
) - Teleport Access Plane (
TELEPORT_ACCESS_PLANE
) - Tenable Active Directory Security (
TENABLE_ADS
) - Tenable CSPM (
TENABLE_CSPM
) - tenable.io (
TENABLE_IO
) - Terraform Enterprise Audit (
TERRAFORM_ENTERPRISE
) - Thinkst Canary (
THINKST_CANARY
) - ThreatX WAF (
THREATX_WAF
) - Trend Micro Email Security Advanced (
TRENDMICRO_EMAIL_SECURITY
) - Trend Micro Vision One (
TRENDMICRO_VISION_ONE
) - TrendMicro Apex Central (
TRENDMICRO_APEX_CENTRAL
) - TXOne Stellar (
TRENDMICRO_STELLAR
) - UKG (
UKG
) - Unix system (
NIX_SYSTEM
) - UPX AntiDDoS (
UPX_ANTIDDOS
) - VanDyke SFTP (
VANDYKE_SFTP
) - Varonis (
VARONIS
) - Vectra Alerts (
VECTRA_ALERTS
) - Vectra Stream (
VECTRA_STREAM
) - VMware AirWatch (
AIRWATCH
) - Vmware Avinetworks iWAF (
VMWARE_AVINETWORKS_IWAF
) - VMware ESXi (
VMWARE_ESX
) - VMware Horizon (
VMWARE_HORIZON
) - Watchguard EDR (
WATCHGUARD_EDR
) - Windows Defender AV (
WINDOWS_DEFENDER_AV
) - Windows DHCP (
WINDOWS_DHCP
) - Windows DNS (
WINDOWS_DNS
) - Windows Event (
WINEVTLOG
) - Windows Event (XML) (
WINEVTLOG_XML
) - Windows Sysmon (
WINDOWS_SYSMON
) - Workday Audit Logs (
WORKDAY_AUDIT
) - Workday User Activity (
WORKDAY_USER_ACTIVITY
) - WPEngine (
WPENGINE
) - Zimperium (
ZIMPERIUM
) - Zscaler (
ZSCALER_WEBPROXY
) - ZScaler DNS (
ZSCALER_DNS
) - Zscaler Internet Access Audit Logs (
ZSCALER_INTERNET_ACCESS
) - ZScaler NGFW (
ZSCALER_FIREWALL
)
The following log types were added without a default parser. Each parser is listed by product name and log_type
value, if applicable.
- Accenture Synthetic (
ACCENTURE_SYNTHETIC
) - Adyen Platform (
ADYEN
) - AliCloud ActionTrail (
ALICLOUD_ACTIONTRAIL
) - Apache LOG4J Java Application Log (
LOG4J
) - AppSmith Audit (
APPSMITH_AUDIT
) - Arctic Security Arctic Node (
ARCTIC_NODE
) - Arista CorvilNet DANZ Integration (
ARISTA_CORVILNET
) - Arista Extensible Operating System (
ARISTA_EOS
) - AvePoint EnPower (
AVEPOINT_ENPOWER
) - Avigilon Alta Cloud Security (
AVIGILON_ALTA_CLOUD_SECURITY
) - Avigilon Ava Security Camera (
AVIGILON_AVA_SECURITY_CAMERA
) - AWS Dasha (
AWS_DASHA
) - AWS Elastic Kubernetes Service (
AWS_EKS
) - Azure Network Security Group Event (
AZURE_NSG_EVENT
) - Azure Windows Virtual Desktop Connections Logs (
AZURE_WVD_CONNECTIONS
) - Azure Windows Virtual Desktop Management Logs (
AZURE_WVD_MANAGEMENT
) - Barracuda Load Balancer ADC (
BARRACUDA_LOAD_BALANCER
) - Broadcom Edge Secure Web Gateway (
BROADCOM_EDGE_SWG
) - Celonis Audit Logs (
CELONIS
) - Chopin PrePay Solutions (
CHOPIN_PPS
) - Cisco Duo Authentication Proxy (
DUO_AUTH_PROXY
) - Cloudflare CASB Findings (
CLOUDFLARE_CASB_FINDINGS
) - Cloudflare Device posture results (
CLOUDFLARE_DEVICE_POSTURE_RESULTS
) - Cloudflare DLP Forensic Copies (
CLOUDFLARE_DLP_FORENSIC_COPIES
) - Cloudflare DNS Firewall Logs (
CLOUDFLARE_DNS_FIREWALL_LOGS
) - Cloudflare DNS logs (
CLOUDFLARE_DNS_LOGS
) - Cloudflare Email Security Alerts (
CLOUDFLARE_EMAIL_SECURITY_ALERTS
) - Cloudflare Firewall Events (
CLOUDFLARE_FIREWALL_EVENTS
) - Cloudflare Gateway DNS (
CLOUDFLARE_GATEWAY_DNS
) - Cloudflare Gateway HTTP (
CLOUDFLARE_GATEWAY_HTTP
) - Cloudflare Gateway Network (
CLOUDFLARE_GATEWAY_NETWORK
) - Cloudflare HTTP requests (
CLOUDFLARE_HTTP_REQUESTS
) - Cloudflare Magic IDS Detections (
CLOUDFLARE_MAGIC_IDS_DETECTIONS
) - Cloudflare NEL reports (
CLOUDFLARE_NEL_REPORTS
) - Cloudflare Sinkhole HTTP Logs (
CLOUDFLARE_SINKHOLE_HTTP_LOGS
) - Cloudflare SSH Logs (
CLOUDFLARE_SSH_LOGS
) - Cloudflare Workers Trace Events (
CLOUDFLARE_WORKERS_TRACE_EVENTS
) - Cloudflare Zero Trust Network Session (
CLOUDFLARE_ZERO_TRUST_NETWORK_SESSION
) - CloudWave Honeypot (
CLOUDWAVE_HONEYPOT
) - ColorTokens (
COLORTOKENS
) - Contrast Security (
CONTRAST_SECURITY
) - Conversational Agents and Dialogflow (
CONVERSATIONAL_AGENT
) - Corero SmartWall One (
CORERO_SMARTWALL_ONE
) - Cytracom Control One (
CYTRACOM_CONTROL_ONE
) - Datadog Application Security Management (
DATADOG_ASM
) - Express NodeJS (
EXPRESS_NODEJS
) - F5 Distributed Cloud WAF (
F5_DCS_WAF
) - Figma Developers (
FIGMA
) - FIS Trax Payment Factory (
TRAX
) - Fortinet FortiDeceptor (
FORTINET_FORTIDECEPTOR
) - Fortinet FortiSASE (
FORTINET_FORTISASE
) - Gemini Code Assist (
GEMINI_CODE_ASSIST
) - Genea Access Control (
GENEA_ACCESS_CONTROL
) - Genetec Synergis (
GENETEC_SYNERGIS
) - GL TRADE (
GL_TRADE
) - HP Inc MFP (
HP_INC_MFP
) - HP Tandem (
HP_TANDEM
) - Huawei Versatile Routing Platform (
HUAWEI_VRP
) - Human Security (
HUMAN_SECURITY
) - iManage Threat Manager (
IMANAGE_THREAT_MANAGER
) - Indefend DLP (
INDEFEND_DLP
) - Invicti (
INVICTI
) - Isonline ISL Light (
ISL_LIGHT
) - Itential Pronghorn (
ITENTIAL_PRONGHORN
) - Jit (
JIT
) - Kodem Security (
KODEM_SECURITY
) - Konica Minolta YSoft SafeQ (
YSOFT_SAFEQ
) - LayerX (
LAYERX
) - LinOTP (
LIN_OTP
) - Magento Cloud (
MAGENTO_CLOUD
) - Mandiant Advantage Security Validation (
MA_SV
) - NetApp ONTAP Audit (
NETAPP_ONTAP_AUDIT
) - Netscout Arbor Threat Mitigation System (
NETSCOUT_TMS
) - Netwrix Privilege Secure (
NETWRIX_PRIVILEGE_SECURE
) - NeuVector SUSE (
NEUVECTOR
) - Novidea Insurance Management System (
NOVIDEA_CLAIM_HISTORY
) - OneTrust (
ONETRUST
) - Openpath Context (
OPENPATH_CONTEXT
) - Oracle Audit Vault Database Firewall (
ORACLE_AVDF
) - Oracle CPQ (
ORACLE_CPQ
) - Oracle Exadata Database Machine (
ORACLE_EXADATA
) - Palo Alto Prisma Cloud Workload Protection (
PAN_PRISMA_CWP
) - Palo Alto Prisma Dig Cloud DSPM (
PAN_PRISMA_DIG_CLOUD_DSPM
) - Panorays (
PANORAYS
) - Pathlock Identity Security Platform (
PATHLOCK
) - Procore (
PROCORE
) - ProofPoint Email Protection (
PROOFPOINT_EMAIL_PROTECTION
) - Radiantone (
RADIANTONE
) - Radware Cloud WAF Service Access (
RADWARE_ACCESS
) - Reblaze Web Application Firewall (
REBLAZE_WAF
) - Red Access Browsing Security (
RED_ACCESS
) - SafeNet Network HSM (
SAFENET_HSM
) - Salesforce Marketing Cloud Audit (
SALESFORCE_MARKETING_CLOUD_AUDIT
) - Salesforce Shield (
SALESFORCE_SHIELD
) - Sangfor IAG (
SANGFOR_IAG
) - SAP Leasing (
SAP_LEASING
) - SAS Institute (
SAS_INSTITUTE
) - Securden (
SECURDEN
) - SecurEnvoy SecurAccess (
SECURENVOY_MFA
) - Securesoft Sniper IPS (
SECURESOFT_SNIPER_IPS
) - Sentra Data Loss Prevention (
SENTRA_DLP
) - Shield IoT (
SHIELD_IOT
) - Siemens Simatic S7 PLC SNMP (
SIEMENS_S7_PLC_SNMP
) - Siemens Simatic S7 PLC SYSLOG (
SIEMENS_S7_PLC_SYSLOG
) - Smartsheet User Context (
SMARTSHEET_USER_CONTEXT
) - Snowflake Access (
SNOWFLAKE_ACCESS
) - SOCRadar Incidents (
SOCRADAR_INCIDENTS
) - Strata Maverics Identity Orchestration Platform (
STRATA_MAVERICS
) - Stripe Payments (
STRIPE
) - Suridata (
SURIDATA
) - Teradata Access (
TERADATA_ACCESS
) - Thales payShield 10K HSM (
THALES_PS10K_HSM
) - Trend Micro TippingPoint Security Management System (
TREND_MICRO_TIPPING_POINT
) - Valence Security (
VALENCE
) - Vertica Audit (
VERTICA_AUDIT
) - Windows NTP (
WINDOWS_NTP
) - Winget Autoupdate (
WINGET_AUTOUPDATE
) - Wiz Runtime Execution Data (
WIZ_RUNTIME_EXECUTION_DATA
) - Workiva Wdesk (
WORKIVA_WDESK
) - XL Release (
XLR
) - Yugabyte Database (
YUGABYTE_DATABASE
)
For a list of supported log types and details about default parser changes, see Supported log types and default parsers.
The new gcp.restrictTLSCipherSuites organization policy constraint can be applied to Looker (Google Cloud core) instances that use a public IP networking configuration. See the Restrict TLS cipher suites on a Looker (Google Cloud core) instance documentation page for more information.
For VM Clusters on Exadata Infrastructure, you can now select a guest OS version that is optimized for your VMs. This feature is generally available (GA). See Create VM Clusters.
A weekly digest of client library updates from across the Cloud SDK.
Java
Changes for google-cloud-pubsub
1.139.1 (2025-04-25)
Dependencies
1.139.0 (2025-04-25)
Features
- Generate renamed go pubsub admin clients (4472d7b)
Bug Fixes
- Add retries for ack and modack operations that don't return with a metadata map (#2385) (00070b7)
- deps: Update the Java code generator (gapic-generator-java) to 2.56.2 (4472d7b)
Dependencies
- Update dependency com.google.cloud:google-cloud-bigquery to v2.49.0 (#2380) (405e485)
- Update dependency com.google.cloud:google-cloud-core to v2.53.1 (#2365) (748058f)
- Update dependency com.google.cloud:google-cloud-storage to v2.50.0 (#2372) (b81164a)
- Update dependency com.google.protobuf:protobuf-java-util to v4.30.1 (#2364) (05eb9c0)
- Update dependency com.google.protobuf:protobuf-java-util to v4.30.2 (#2383) (4119cc0)
Documentation
- Update documentation for JavaScriptUDF to indicate that the
message_id
metadata field is optional instead of required (f904786)
Security Command Center provides increased support for Microsoft Azure data.
- Security Command Center can collect Microsoft Azure resource and configuration data.
- Risk Engine can discover toxic combinations, attack paths, and issues in your Microsoft Azure environment.
- The Sensitive Data Protection discovery service can profile your Azure Blob Storage data and identify vulnerabilities and misconfigurations that can expose sensitive data.
- Cloud Infrastructure Entitlement Management (CIEM) can analyze and generate misconfiguration findings for Azure role-assignments that grant principals excessive privileges beyond what they use. This capability is available in Preview.
Toxic Combinations for Amazon Web Services (AWS) has been released to General Availability.
The discovery service of Sensitive Data Protection now supports Azure Blob Storage. You can run discovery to generate data profiles of your Blob Storage containers. Data profiles provide metrics and insights about the sensitivity and risk levels of your data to help you plan your data protection and governance workflows.
This feature is available only to Security Command Center Enterprise customers. To use this feature, you need an Azure connector in Security Command Center that has permissions for Sensitive Data Protection discovery.
To get started on profiling Blob Storage data, see the following:
Manually adding split points to your Spanner database is now generally available. Spanner automatically splits, or partitions, data in response to traffic changes to spread load across all available resources in an instance. For large, anticipated traffic changes, such as for a product launch, you can now pre-split the database with split boundaries that represent future traffic. This warmup can yield significant performance benefits for large scaling events.
For more information about configuring split points for your database, see Pre-splitting overview.
April 27, 2025
Google SecOps SOARRelease 6.3.43 is now available for all regions.
April 25, 2025
Agent AssistSummarization with custom sections, generative knowledge assist, and proactive generative knowledge assist are available in the following regions:
- northamerica-northeast1 (Montreal)
- northamerica-northeast2 (Toronto)
- europe-west4 (Eemshaven)
- europe-west6 (Zurich)
- asia-southeast2 (Jakarta)
- me-west1 (Tel Aviv)
8 AlloyDB recommenders are now generally available (GA). For more information, see the following pages:
Bigtable is supported by Database Center, which is generally available (GA). The Database Center now provides performance, availability, and data protection in the form of recommender-related health issues. You can also view these performance recommendations in Recommendation Hub.
Starting April 28, 2025, the Global external Application Load Balancer and the Classic Application Load Balancer will no longer allow the use of custom request headers that reference connection-specific hop-by-hop headers.
This change applies only to HTTP/1.1 traffic. Connection-specific hop-by-hop headers are already disallowed by the HTTP/2 and HTTP/3 protocols.
This change is in accordance with RFC 2616 which states that these connection-specific hop-by-hop headers headers are meaningful only for a single transport-level connection and should not be forwarded by proxies.
The impacted hop-by-hop headers are: Connection
, Keep-Alive
, TE
, Trailer
, Transfer-Encoding
, and Upgrade
.
Starting April 28, 2025, connection-specific hop-by-hop headers that were configured by using custom headers will no longer be applied. These headers will only be set by the load balancer during normal connection handling.
Starting June 30, 2025, any configuration changes that reference the connection-specific hop-by-hop custom headers will no longer be accepted.
What you need to do
If you are an HTTP/1.1 user affected by this change, complete the following steps:
Determine if your application depends on the values of any hop-by-hop headers configured as custom headers. If any dependencies are found, replace them with an allowed custom header and modify your application accordingly.
Review your backend service and URL map
headerAction
configuration to remove any references to connection-specific hop-by-hop headers.
Public Preview: License Manager lets you subscribe, manage, and track your third-party license usage on Google Cloud. As an administrator, you can use License Manager to offer per-user licensing products, like Microsoft Office, to your users with no long-term commitments and no overhead of managing compliance.
For more information, see About License Manager.
Support for accelerator-optimized a3-highgpu-1g machine type for securely running AI and ML workloads is now available in Preview, with the following specifications:
- 4th Generation Intel Xeon Scalable processor (Sapphire Rapids)
- Intel TDX
- 1 NVIDIA H100 GPU
cos-117-18613-164-121
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.72 | v24.0.9 | v1.7.24 | See List |
Updated cos-gpu-installer to v2.5.0: Support IMEX Driver installation for NVIDIA_GB200 GPU device.
Upgraded app-admin/node-problem-detector to v0.8.20.
Reverted a change in the linux kernel which caused nfs directories to unexpectedly be mounted as ro instead of rw.
Fixed CVE-2024-48615 in app-arch/libarchive.
Fixed CVE-2025-21963 in the Linux kernel.
Fixed CVE-2025-21964 in the Linux kernel.
Fixed CVE-2025-21962 in the Linux kernel.
Fixed CVE-2025-21908 in the Linux kernel.
Fixed CVE-2025-21898 in the Linux kernel.
Fixed CVE-2025-21959 in the Linux kernel.
Fixed CVE-2025-21919 in the Linux kernel.
Fixed CVE-2025-21922 in the Linux kernel.
Fixed CVE-2025-21920 in the Linux kernel.
Fixed CVE-2025-21997 in the Linux kernel.
Fixed CVE-2025-22005 in the Linux kernel.
Fixed CVE-2025-21991 in the Linux kernel.
Fixed CVE-2025-21980 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811760 -> 811799
cos-121-18867-0-104
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.74 | v27.5.1 | v2.0.4 | See List |
Updated cos-gpu-installer to v2.5.0: Support IMEX Driver installation for NVIDIA_GB200 GPU device.
Reverted a change in the linux kernel which caused nfs directories to unexpectedly be mounted as ro instead of rw.
Fixed CVE-2025-31498 in net-dns/c-ares.
Fixed CVE-2024-48615 in app-arch/libarchive.
Fixed CVE-2025-21963 in the Linux kernel.
Fixed CVE-2025-21964 in the Linux kernel.
Fixed CVE-2025-21908 in the Linux kernel.
Fixed CVE-2025-21898 in the Linux kernel.
Fixed CVE-2025-21959 in the Linux kernel.
Fixed CVE-2025-21962 in the Linux kernel.
Fixed CVE-2025-21919 in the Linux kernel.
Fixed CVE-2025-21920 in the Linux kernel.
Fixed CVE-2025-21922 in the Linux kernel.
Fixed CVE-2025-21980 in the Linux kernel.
Fixed CVE-2025-22005 in the Linux kernel.
Fixed CVE-2025-21997 in the Linux kernel.
Fixed CVE-2025-21991 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811714 -> 811816
cos-109-17800-436-106
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.124 | v24.0.9 | v1.7.24 | See List |
Reverted a change in the linux kernel which caused nfs directories to unexpectedly be mounted as ro instead of rw.
Fixed CVE-2024-48615 in app-arch/libarchive.
Fixed CVE-2025-21962 in the Linux kernel.
Fixed CVE-2025-21964 in the Linux kernel.
Fixed CVE-2025-21963 in the Linux kernel.
Fixed CVE-2025-21959 in the Linux kernel.
Fixed CVE-2025-21898 in the Linux kernel.
Fixed CVE-2025-21980 in the Linux kernel.
Fixed CVE-2025-22005 in the Linux kernel.
Fixed CVE-2025-21997 in the Linux kernel.
Fixed CVE-2025-21999 in the Linux kernel.
Fixed CVE-2025-21922 in the Linux kernel.
Fixed CVE-2025-21920 in the Linux kernel.
Fixed CVE-2025-21919 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812288 -> 812262
cos-dev-125-19000-0-0
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.87 | v27.5.1 | v2.0.4 | See List |
Updated cos-gpu-installer to v2.5.0: Support IMEX Driver installation for NVIDIA_GB200 GPU device.
Updated the Linux kernel to v6.6.87.
Upgraded app-admin/google-guest-agent to v20250408.00.
Upgraded chromeos-base/update_engine-client to v0.0.1-r2479.
Upgraded chromeos-base/power_manager-client to v0.0.1-r2967.
Upgraded chromeos-base/shill-client to v0.0.1-r4850.
Upgraded chromeos-base/session_manager-client to v0.0.1-r2828.
Upgraded chromeos-base/debugd-client to v0.0.1-r2732.
Upgraded chromeos-base/chromeos-common-script to v0.0.1-r663.
Reverted a change in the linux kernel which caused nfs directories to unexpectedly be mounted as ro instead of rw.
Fixed CVE-2024-53427 in app-misc/jq.
Fixed CVE-2024-48615 in app-arch/libarchive.
Updated dev-vcs/git to version 2.49.0. This fixed CVE-2024-52006, CVE-2024-50349
Runtime sysctl changes:
- Changed: fs.file-max: 811798 -> 811749
cos-113-18244-291-109
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.123 | v24.0.9 | v1.7.24 | See List |
Reverted a change in the linux kernel which caused nfs directories to unexpectedly be mounted as ro instead of rw.
Fixed CVE-2024-48615 in app-arch/libarchive.
Fixed CVE-2025-21963 in the Linux kernel.
Fixed CVE-2025-21959 in the Linux kernel.
Fixed CVE-2025-21898 in the Linux kernel.
Fixed CVE-2025-21964 in the Linux kernel.
Fixed CVE-2025-21962 in the Linux kernel.
Fixed CVE-2025-21919 in the Linux kernel.
Fixed CVE-2025-21922 in the Linux kernel.
Fixed CVE-2025-21920 in the Linux kernel.
Fixed CVE-2025-21997 in the Linux kernel.
Fixed CVE-2025-21980 in the Linux kernel.
Fixed CVE-2025-22005 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812031 -> 812016
Google Distributed Cloud (software only) for VMware 1.31.400-gke.110 is now available for download. To upgrade, see Upgrade a cluster or a node pool. Google Distributed Cloud 1.31.400-gke.110 runs on Kubernetes v1.31.7-gke.800.
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.
Upgraded etcd to v3.4.33-0-gke.3.
Fixed an issue that prevented user cluster upgrades when Dataplane V2 was explicitly configured with forward mode.
The 1.31.400-gke.110 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
Release 1.31.400-gke.110
Google Distributed Cloud (software only) for VMware 1.31.400-gke.110 is now available for download. To upgrade, see Upgrade a cluster or a node pool. Google Distributed Cloud 1.31.400-gke.110 runs on Kubernetes v1.31.7-gke.800.
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.
The following functional change was made in 1.31.400-gke.110:
Updated the cluster upgrade operation to keep only the three latest
kubeadm
backups of etcd and configuration information for a node. Previously,kubeadm
kept node backups for every attempted upgrade.Upgraded etcd to v3.4.33-0-gke.3.
The following fixes were made in 1.31.400-gke.110:
Fixed an issue where network interfaces were being leaked, preventing namespace deletion.
Fixed an issue that resulted in an excessive creation of periodic
kube-proxy-cleanup
jobs on cluster nodes with high pod utilization.Fixed an issue that caused cluster creation to fail because kubelet restarted before required static pods are running.
Fixed an issue that allowed
bmctl reset
to run in situations where the reset resulted in the loss of quorum for control plane nodes. To run the command without enforcing the quorum, use the newly added--bypass-quorum-check
flag.
The 1.31.400-gke.110 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
For information about the latest known issues, see Google Distributed Cloud for bare metal known issues in the Troubleshooting section.
Google SecOps now supports native integration with Azure Event Hub through the feed management API or web interface. This enhancement enables real-time log ingestion without requiring Azure blob storage. For more information, see Create an Azure Event Hub feed.
Google SecOps now supports native integration with Azure Event Hub through the feed management API or web interface. This enhancement enables real-time log ingestion without requiring Azure blob storage. For more information, see Create an Azure Event Hub feed.
The maintenance feature for Memorystore for Valkey is now Generally Available (GA).
New SAP certifications: Additional M4 memory-optimized machine types
For use with SAP HANA scale-up (OLAP and OLTP) and SAP NetWeaver workloads, SAP has certified the following Compute Engine M4 memory-optimized machine types: 372 GB m4-megamem-28
and 6 TB m4-ultramem-224
.
For more information, see:
- For SAP HANA, M4 memory-optimized VM types
- For SAP NetWeaver, M4 memory-optimized VM types
New SAP certification: 3 TB m4-megamem-224
for SAP HANA scale-out workloads
For use with SAP HANA scale-out (OLAP and OLTP) workloads, SAP has certified the 3 TB m4-megamem-224
memory-optimized machine type.
For more information, see M4 memory-optimized VM types.
Updated the limitations for the following integration in the Supported products and limitations page:
- Firestore: using Firestore Enterprise edition with restricted VIP requires adding IP ranges to an allowlist.
April 24, 2025
AI ApplicationsVertex AI Search: Obtain claim-level grounding scores (GA)
Claim-level scores from the check grounding API is Generally available (GA). In addition to the answer-level support score, you can obtain a support score for each claim in an answer candidate.
For more information, see Obtain claim-level scores for an answer candidate.
You can now work with a Gemini powered assistant in a BigQuery data canvas. The data canvas assistant is an agent-like tool, capable of constructing and modifying a data canvas to answer data analytics questions from user prompting. This feature is now in Preview.
Starting from June 2025, the default version for new Cloud Composer environments changes from Cloud Composer 2 to Cloud Composer 3. New environments will use the latest default Airflow build (composer-3-airflow-2
). Currently, the default version is composer-2-airflow-2
.
Database Migration Service for heterogeneous migrations to PostgreSQL now supports migrating to PostgreSQL versions 16 and 17.
- PostgreSQL versions 16 and 17 are supported for migrations from Oracle and SQL Server to Cloud SQL for PostgreSQL.
- PostgreSQL version 16 is supported for migrations from Oracle and SQL Server to AlloyDB for PostgreSQL.
For more information, see Supported source and destination databases.
You can use a single request to batch update all the firewall policy rules for hierarchical and network firewall policies. For more information, see Overview of batch update to firewall policy rules. This feature is available in General Availability.
Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.
Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.
Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.
Dialogflow CX (Conversational Agents): You can now create personalized voice models with voice cloning.
Dialogflow CX (Conversational Agents): You can now use code blocks to get better control over playbooks.
Dialogflow CX (Conversational Agents): You can now use the console to test your tools.
Saxml on GKE is de-prioritized beginning April 24, 2025. This means the project won't get further updates. Existing Saxml deployments will continue to function as is without disruption. We strongly suggest that you migrate to JetStream, Google's up to date open source inference framework for high-performance LLM serving on TPUs and GPUs. JetStream offers continuous batching and quantization for better throughput and memory efficiency. For a migration example, see Serve Gemma using TPUs on GKE with JetStream.
After May 23, 2025, Gemini in Looker will be enabled by default for Looker (original) instances outside of the EMEA region.
Looker admins can opt out of automatic enablement by disabling the Automated Gemini in Looker enablement and user management setting on the Settings page in the Looker Admin panel, now available for Looker (original) instances on Looker 25.6.
For instances outside of the EMEA region that are slated to update to Looker 25.6 after May 23, 2025, Gemini in Looker will be enabled automatically, and Looker admins must disable Gemini in Looker manually.
Note: This item was updated on April 29, 2025.
Spanner now lets you use the INTERLEAVE IN clause to colocate child rows with parent rows without enforcing the parent-child relationship. When you use INTERLEAVE IN (without the PARENT option), you can insert child rows before inserting the parent row. You can also delete the parent row without affecting the child rows. For more information, see Create interleaved tables and Indexes and interleaving.
April 23, 2025
BigQueryYou can now set a maximum slot limit for a reservation. You can configure the maximum reservation size when creating or updating a reservation. This feature is in public preview.
You can now specify which reservation a query uses at runtime, and set IAM policies directly on reservations. This provides more flexibility and fine-grained control over resource management. This feature is in public preview.
You can now allocate idle slots fairly across reservations within a single admin project. This ensures each reservation receives an approximately equal share of available capacity. This feature is in public preview.
The following resource types are now publicly available through the ExportAssets, ListAssets, BatchGetAssetsHistory, QueryAssets, and Feed APIs.
- GKE Hub API
gkehub.googleapis.com/MembershipFeature
Cloud Billing supports Dark theme in the Google Cloud console (in preview)
Dark theme is now available in the Billing section of the Google Cloud console (preview). To enable the Dark theme, in the Google Cloud console, click Settings > Preferences > Appearance. Choose Dark theme and click Save.
Quality AI offers fine-grained access control in preview. Use IAM custom roles and authorized views to control who can view which portions of your dataset.
This feature is currently in Preview. Google SecOps now supports composite detections. Composite detections lets users link multiple YARA-L rules to detect complex, multistage threats. This capability enhances detection by correlating alerts that individual rules might not detect.
This feature is currently in Preview. Google SecOps now supports composite detections. Composite detections lets users link multiple YARA-L rules to detect complex, multistage threats. This capability enhances detection by correlating alerts that individual rules might not detect.
April 22, 2025
Apigee Integrated PortalOn April 22, 2025 we released a new version of the Apigee integrated portal.
Public Preview: Apigee Integrated Developer Portal Admin UI in the Google Cloud console.
This release adds the Apigee Integrated Developer Portal Admin UI from the Classic Apigee UI into the Google Cloud console.
Leveraging Google Cloud console components provides API providers and Portal Admins with a centralized platform to efficiently configure, publish, and manage your API consumer portals, eliminating the need to switch between different UIs.
No new APIs have been introduced in this release.
See Publishing overview to get started.
You can now specify build dependencies in your build configuration file. For more information, see Manage build dependencies.
Cloud KMS with Autokey is now in General Availability (GA) for Cloud Run.
Public Preview: General purpose C4D machine types have reached Public Preview. C4D is powered by the fifth generation AMD EPYC processor (Turin) and Google Titanium.
C4D is designed to run mission critical workloads including web app and game servers, AI inference, web serving, video streaming, and data centric applications like analytics, relational, and in-memory databases.
C4D is available in standard
, highmem
, and highcpu
machine types and only supports Google Cloud Hyperdisk storage.
To learn where to create C4D instances, see the Regions and zones page.
Release 6.3
- Cortex for Meridian.
- Cortex Framework for Meridian, Google's open-source Marketing Mix Modeling (MMM) tool (v1.0.5), delivers ready data models and automation of Meridian Model execution using Google Cloud tools like Enterprise Colab and Cloud Workflows.
- This integration empowers users to make data-driven marketing decisions by providing accurate campaign performance measurement and budget optimization.
- Cortex for Meridian simplifies the pre-modeling process by gathering and transforming data from core Cortex Framework data sources, including:
- Task Dependent DAGs:
- Provided out-of-the-box, recommended DAGs and task dependencies for SAP ECC/S4 reporting.
- Enabled the creation and deployment of customized task-dependent reporting settings for all data sources.
- CATGAP has been deprecated.
- SAP Machine Learning (ML) models have been deprecated.
- Resolved duplicate entries from
VendorsMD
- Fixed DATE_ADD overflow issue in
InventoryByPlant
. - Fixed mislabeled columns in
AccountingDocumentsReceivable
. - Addressed JSON parsing errors related to FLOAT numbers in Meta Raw to DAG Change Data Capture (CDC).
- Fixed a typo in the
LeadsCaptureConversions
Salesforce (SFDC) reporting table:LeadFirstResponeDatestamp
corrected toLeadFirstResponseDatestamp
.
Dataproc Metastore multi-regional services now support the use of customer-managed encryption keys (CMEKs) -- (in preview).
Committed use discounts are now generally available (GA) for Firestore in exchange for a commitment to continuously spend a certain amount on Firestore read/write/delete operations for one year or three years. For details, see Committed use discounts.
Committed use discounts are now generally available (GA) for Firestore in Datastore mode in exchange for a commitment to continuously spend a certain amount on read/write/delete operations for one year or three years. For details, see Committed use discounts.
The following parser documentation is now available:
Collect Barracuda Email Security Gateway logs
Collect CrowdStrike Falcon logs in CEF
Collect Juniper NetScreen Firewall logs
Collect Micro Focus NetIQ Access Manager logs
Collect Aruba Wireless Controller and Access Point logs
Collect BeyondTrust Secure Remote Access logs
Collect CyberArk Privileged Threat Analytics logs
Collect Fortinet FortiMail logs
Collect Sophos XG Firewall logs
Collect Cisco Stealthwatch logs
Collect Cisco Umbrella audit logs
Collect Cisco Umbrella DNS logs
Collect Cisco Umbrella Web Proxy logs
Collect CommVault Backup and Recovery logs
Collect Fortinet FortiAnalyzer logs
Collect Fortinet FortiAuthenticator logs
Collect Fortinet Firewall logs
Collect Palo Alto Networks Traps logs
Collect SecureAuth Identity Platform logs
Collect A10 Network Load Balancer logs
Collect AlgoSec Security Management logs
Collect Arbor Edge Defense logs
Collect Fortra Digital Guardian DLP logs
The following parser documentation is now available:
Collect Barracuda Email Security Gateway logs
Collect CrowdStrike Falcon logs in CEF
Collect Juniper NetScreen Firewall logs
Collect Micro Focus NetIQ Access Manager logs
Collect Aruba Wireless Controller and Access Point logs
Collect BeyondTrust Secure Remote Access logs
Collect CyberArk Privileged Threat Analytics logs
Collect Fortinet FortiMail logs
Collect Sophos XG Firewall logs
Collect Cisco Stealthwatch logs
Collect Cisco Umbrella audit logs
Collect Cisco Umbrella DNS logs
Collect Cisco Umbrella Web Proxy logs
Collect CommVault Backup and Recovery logs
Collect Fortinet FortiAnalyzer logs
Collect Fortinet FortiAuthenticator logs
Collect Fortinet Firewall logs
Collect Palo Alto Networks Traps logs
Collect SecureAuth Identity Platform logs
Collect A10 Network Load Balancer logs
Collect AlgoSec Security Management logs
Collect Arbor Edge Defense logs
Collect Fortra Digital Guardian DLP logs
The Looker Mobile (Legacy) application will be deprecated on March 1, 2026. Use the Looker application instead.
Looker (Google Cloud core) now supports Google group mirroring when using OAuth authentication.
Memorystore for Valkey supports storing and querying vector data. This feature is now Generally Available (GA). For more information, see About vector search.
Policy Controller version 1.20.2 is now available.
April 21, 2025
App Engine flexible environment PythonPython 3.13 is now available in Preview.
Python 3.13 is now available in Preview.
New Canvas View is enabled by default in the Integration Editor
The new Canvas View is now enabled by default in the integration editor. This change is a default setting and no manual enablement is required. You can switch to the old canvas view by disabling the New canvas view toggle.
For more information, see Use the new canvas view.
A weekly digest of client library updates from across the Cloud SDK.
Node.js
Changes for @google-cloud/bigquery
7.9.4 (2025-04-02)
Bug Fixes
BigQuery now provides spend-based committed use discounts (CUDs). Spend-based committed use discounts provide a discount in exchange for your commitment to spend a minimum amount per hour on PAYG compute resources listed here. You can purchase CUDs with a one or three year commitment period.
You can now enable fine-grained access control on BigQuery metastore Iceberg tables. This feature is generally available (GA).
You can get the required permissions to use BigQuery data preparation through the BigQuery Studio User (roles/bigquery.studioUser
) and Gemini for Google Cloud User (roles/cloudaicompanion.user
) roles, and permission to access the data you're preparing.
BigQuery data preparation no longer requires that you have the permissions granted by the following IAM roles:
- BigQuery Data Editor (
roles/bigquery.dataEditor
) - Service Usage Consumer (
roles/serviceusage.serviceUsageConsumer
)
For more information about the required roles, see Manage data preparations.
A weekly digest of client library updates from across the Cloud SDK.
Python
Changes for google-cloud-bigtable
2.30.1 (2025-04-17)
Bug Fixes
A new release is available. This release may include some or all of the following: general performance improvements, bug fixes, and updates to the API reference documentation.
DICOM files have a limit of 4 GB per tag. This limit does not apply for values with undefined length. For more information, see Resource limits.
A weekly digest of client library updates from across the Cloud SDK.
Python
Changes for google-cloud-logging
3.12.0 (2025-04-10)
Features
- Add REST Interceptors which support reading metadata (681bcc5)
- Add support for opt-in debug logging (681bcc5)
- Added flushes/close functionality to logging handlers (#917) (d179304)
Bug Fixes
- Allow protobuf 6.x (#977) (6757890)
- deps: Require google-cloud-audit-log >= 0.3.1 (#979) (1cc00ec)
- Fix typing issue with gRPC metadata when key ends in -bin (681bcc5)
Documentation
Cloud Logging adds support for the europe-north2 region. For a complete list of supported regions, see Supported regions.
Support for the Python 3.13 runtime is now in Preview.
Cloud Run functions now supports the Python 3.13 runtime at the Preview release level.
The notebook gallery is now available.
The notebook gallery is a curated collection of notebooks to help you get started using Colab Enterprise. This collection consists of ready-to-use templates and examples to make it easier to learn new techniques, understand best practices, and get projects started quickly. Browse the notebooks by category or use the search bar to find a notebook that helps you get started. See the notebook gallery.
Generally available: Compute flexible committed use discounts (CUDs) are available for the sole-tenancy premium that you pay for eligible sole-tenant node types. Flexible CUDs add flexibility to your Compute Engine spending capabilities by eliminating the need to restrict your commitments to a single project, region, or machine series.
For more information, see Compute flexible CUDs.
A weekly digest of client library updates from across the Cloud SDK.
Go
Changes for dataflow/apiv1beta3
0.10.6 (2025-04-15)
Bug Fixes
- dataflow: Update google.golang.org/api to 0.229.0 (3319672)
A weekly digest of client library updates from across the Cloud SDK.
Python
Changes for google-cloud-datastore
2.21.0 (2025-04-10)
Features
- Add REST Interceptors which support reading metadata (7be9c4c)
- Add support for opt-in debug logging (7be9c4c)
Bug Fixes
Google Cloud Marketplace has introduced:
- An improved revenue share program for new Google Cloud Marketplace deals.
- Four new Private Offer deal types that you can select when you create an offer:
- New
- Migration
- Native renewal
- Channel shift
For more information, see the Vendor Net Revenue Schedule. This revenue share program is only available to eligible Google Cloud Build partners and their respective Cloud Marketplace product istings. For eligibility criteria, see Vendor Net Revenue Schedule requirements.
Curated Detections has been enhanced with new detection content for Cloud Threats to include rule packs covering Office 365 and Okta. These rule packs are in public preview for customers with a Google Security Operations or Enterprise Plus license.
Curated Detections has been enhanced with new detection content for Cloud Threats to include rule packs covering Office 365 and Okta. These rule packs are in public preview for customers with a Google Security Operations or Enterprise Plus license.
Network Analyzer includes an insight that indicates if a GKE cluster's pod CIDR range isn't included in the ip-masq-agent
ConfigMap. For more information, see GKE IP masquerade configuration insights.
The Execution: Ingress Nightmare Vulnerability Execution
detector of Container Threat Detection is in Preview.
April 20, 2025
Google SecOps SOARRelease 6.3.43 is being rolled out to the first phase of regions as listed here.
This release contains internal and customer bug fixes.
April 19, 2025
Google SecOps SOARRelease 6.3.42 is now available for all regions.
April 18, 2025
Cloud SQL for MySQLCloud SQL for MySQL 8.0.40 is now the default minor version. To upgrade your existing instance to the new version, see Upgrade the database minor version.
New Dataproc Serverless for Spark runtime versions:
- 1.1.99
- 1.2.43
- 2.2.43
The ability to use Git proxy for Git calls to your SCM connections is now generally available.
Parallel file systems for HPC workloads: Added guidance about Google Cloud Managed Lustre.
(2025-R15) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.29.14-gke.1132000
- 1.29.15-gke.1017000
- 1.29.15-gke.1058000
- 1.29.15-gke.1108000
- 1.29.15-gke.1134000
- 1.30.10-gke.1145000
- 1.30.10-gke.1227000
- 1.30.10-gke.1227001
- 1.30.11-gke.1008001
- 1.30.11-gke.1072000
- 1.30.11-gke.1093000
- 1.31.5-gke.1169001
- 1.31.5-gke.1233001
- 1.31.6-gke.1020001
- 1.31.6-gke.1064000
- 1.31.6-gke.1099000
- 1.31.6-gke.1140000
- 1.31.6-gke.1221000
- 1.31.6-gke.1221001
- 1.31.7-gke.1013001
- 1.31.7-gke.1112000
- 1.31.7-gke.1149000
- 1.32.2-gke.1182001
- 1.32.2-gke.1182002
- 1.32.2-gke.1297001
- 1.32.2-gke.1400003
- 1.32.2-gke.1652000
- 1.32.2-gke.1652003
- 1.32.3-gke.1057001
- 1.32.3-gke.1170000
- 1.32.3-gke.1440000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.2-gke.1182003 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
Regular channel
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.10-gke.1022000
- 1.31.6-gke.1020000
- 1.31.6-gke.1064000
- 1.32.1-gke.1357001
- 1.32.2-gke.1182001
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
Stable channel
- Version 1.31.6-gke.1064001 is now the default version for cluster creation in the Stable channel.
- The following versions are now available in the Stable channel:
- The following versions are no longer available in the Stable channel:
- 1.29.13-gke.1109000
- 1.30.9-gke.1127000
- 1.30.9-gke.1201000
- 1.30.10-gke.1022000
- 1.31.5-gke.1169000
- 1.31.5-gke.1233000
- 1.31.6-gke.1020000
- 1.31.6-gke.1064000
- 1.32.2-gke.1182001
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.29 to version 1.30.10-gke.1070000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
Extended channel
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2451000
- 1.27.16-gke.2477000
- 1.27.16-gke.2528000
- 1.27.16-gke.2573000
- 1.27.16-gke.2650000
- 1.28.15-gke.1844000
- 1.28.15-gke.1881000
- 1.28.15-gke.1940000
- 1.28.15-gke.2003000
- 1.28.15-gke.2097000
- 1.30.10-gke.1022000
- 1.31.6-gke.1020000
- 1.31.6-gke.1064000
- 1.32.1-gke.1357001
- 1.32.2-gke.1182001
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2595000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2027000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
No channel
- Version 1.32.2-gke.1182003 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.29.13-gke.1109000
- 1.29.14-gke.1132000
- 1.29.15-gke.1017000
- 1.29.15-gke.1058000
- 1.29.15-gke.1108000
- 1.29.15-gke.1134000
- 1.30.9-gke.1046000
- 1.30.9-gke.1201000
- 1.30.10-gke.1022000
- 1.30.10-gke.1145000
- 1.30.10-gke.1227000
- 1.30.10-gke.1227001
- 1.30.11-gke.1008001
- 1.30.11-gke.1072000
- 1.30.11-gke.1093000
- 1.31.5-gke.1169000
- 1.31.5-gke.1169001
- 1.31.5-gke.1233000
- 1.31.5-gke.1233001
- 1.31.6-gke.1020001
- 1.31.6-gke.1064000
- 1.31.6-gke.1099000
- 1.31.6-gke.1140000
- 1.31.6-gke.1221000
- 1.31.6-gke.1221001
- 1.31.7-gke.1013001
- 1.31.7-gke.1112000
- 1.31.7-gke.1149000
- 1.32.1-gke.1729000
- 1.32.2-gke.1182002
- 1.32.2-gke.1297001
- 1.32.2-gke.1400003
- 1.32.2-gke.1652000
- 1.32.2-gke.1652003
- 1.32.3-gke.1057001
- 1.32.3-gke.1170000
- 1.32.3-gke.1440000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.10-gke.1070000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
(2025-R15) Version updates
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Rapid channel.
- The following versions are now available in the Rapid channel:
- The following versions are no longer available in the Rapid channel:
- 1.29.14-gke.1132000
- 1.29.15-gke.1017000
- 1.29.15-gke.1058000
- 1.29.15-gke.1108000
- 1.29.15-gke.1134000
- 1.30.10-gke.1145000
- 1.30.10-gke.1227000
- 1.30.10-gke.1227001
- 1.30.11-gke.1008001
- 1.30.11-gke.1072000
- 1.30.11-gke.1093000
- 1.31.5-gke.1169001
- 1.31.5-gke.1233001
- 1.31.6-gke.1020001
- 1.31.6-gke.1064000
- 1.31.6-gke.1099000
- 1.31.6-gke.1140000
- 1.31.6-gke.1221000
- 1.31.6-gke.1221001
- 1.31.7-gke.1013001
- 1.31.7-gke.1112000
- 1.31.7-gke.1149000
- 1.32.2-gke.1182001
- 1.32.2-gke.1182002
- 1.32.2-gke.1297001
- 1.32.2-gke.1400003
- 1.32.2-gke.1652000
- 1.32.2-gke.1652003
- 1.32.3-gke.1057001
- 1.32.3-gke.1170000
- 1.32.3-gke.1440000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.32.2-gke.1182003 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Rapid channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
(2025-R15) Version updates
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Regular channel.
- The following versions are now available in the Regular channel:
- The following versions are no longer available in the Regular channel:
- 1.30.10-gke.1022000
- 1.31.6-gke.1020000
- 1.31.6-gke.1064000
- 1.32.1-gke.1357001
- 1.32.2-gke.1182001
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.29 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.31.6-gke.1064001 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Regular channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
(2025-R15) Version updates
- Version 1.31.6-gke.1064001 is now the default version for cluster creation in the Stable channel.
- The following versions are now available in the Stable channel:
- The following versions are no longer available in the Stable channel:
- 1.29.13-gke.1109000
- 1.30.9-gke.1127000
- 1.30.9-gke.1201000
- 1.30.10-gke.1022000
- 1.31.5-gke.1169000
- 1.31.5-gke.1233000
- 1.31.6-gke.1020000
- 1.31.6-gke.1064000
- 1.32.2-gke.1182001
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.29 to version 1.30.10-gke.1070000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Stable channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
(2025-R15) Version updates
- Version 1.32.2-gke.1182003 is now the default version for cluster creation in the Extended channel.
- The following versions are now available in the Extended channel:
- The following versions are no longer available in the Extended channel:
- 1.27.16-gke.2451000
- 1.27.16-gke.2477000
- 1.27.16-gke.2528000
- 1.27.16-gke.2573000
- 1.27.16-gke.2650000
- 1.28.15-gke.1844000
- 1.28.15-gke.1881000
- 1.28.15-gke.1940000
- 1.28.15-gke.2003000
- 1.28.15-gke.2097000
- 1.30.10-gke.1022000
- 1.31.6-gke.1020000
- 1.31.6-gke.1064000
- 1.32.1-gke.1357001
- 1.32.2-gke.1182001
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.27 to version 1.27.16-gke.2595000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.28 to version 1.28.15-gke.2027000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled in the Extended channel will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
(2025-R15) Version updates
- Version 1.32.2-gke.1182003 is now the default version for cluster creation.
- The following versions are now available:
- The following node versions are now available:
- The following versions are no longer available:
- 1.29.13-gke.1109000
- 1.29.14-gke.1132000
- 1.29.15-gke.1017000
- 1.29.15-gke.1058000
- 1.29.15-gke.1108000
- 1.29.15-gke.1134000
- 1.30.9-gke.1046000
- 1.30.9-gke.1201000
- 1.30.10-gke.1022000
- 1.30.10-gke.1145000
- 1.30.10-gke.1227000
- 1.30.10-gke.1227001
- 1.30.11-gke.1008001
- 1.30.11-gke.1072000
- 1.30.11-gke.1093000
- 1.31.5-gke.1169000
- 1.31.5-gke.1169001
- 1.31.5-gke.1233000
- 1.31.5-gke.1233001
- 1.31.6-gke.1020001
- 1.31.6-gke.1064000
- 1.31.6-gke.1099000
- 1.31.6-gke.1140000
- 1.31.6-gke.1221000
- 1.31.6-gke.1221001
- 1.31.7-gke.1013001
- 1.31.7-gke.1112000
- 1.31.7-gke.1149000
- 1.32.1-gke.1729000
- 1.32.2-gke.1182002
- 1.32.2-gke.1297001
- 1.32.2-gke.1400003
- 1.32.2-gke.1652000
- 1.32.2-gke.1652003
- 1.32.3-gke.1057001
- 1.32.3-gke.1170000
- 1.32.3-gke.1440000
- Auto-upgrade targets are now available for the following minor versions:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.29 to version 1.30.10-gke.1070000 with this release.
- The following patch-only version auto-upgrade targets are now available for clusters with maintenance exclusions or other factors preventing minor version upgrades:
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.30 to version 1.30.10-gke.1070000 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.31 to version 1.31.6-gke.1064001 with this release.
- Control planes and nodes with auto-upgrade enabled will be upgraded from version 1.32 to version 1.32.2-gke.1182003 with this release.
Chrome Enterprise Threats Category
This feature is currently in Preview.
Google SecOps has introduced a new detection category, Chrome Enterprise Threats, as part of the Curated Detections feature. This category provides rule sets for extension and browser threats. For more information, see Overview of Chrome Enterprise Threats Category.
Chrome Enterprise Threats Category
This feature is currently in Preview.
Google SecOps has introduced a new detection category, Chrome Enterprise Threats, as part of the Curated Detections feature. This category provides rule sets for extension and browser threats. For more information, see Overview of Chrome Enterprise Threats Category.
The backups feature for Memorystore for Redis Cluster is now Generally Available (GA).
You can now manage backups for Memorystore for Valkey instances. This feature is Generally Available (GA).
Oracle Database@Google Cloud now lets you provision the Exadata Infrastructure instances with the new model X11M. This feature is generally available (GA). See Create Exadata Infrastructure instances.
The ability of Event Threat Detection to analyze foundational log sources is generally available (GA).
April 17, 2025
Anti Money Laundering AINew minor engine versions released for retail and commercial lines of business within the v004 tuning version. These extend support for the major version and include no significant changes versus the previous minor versions.
The CJIS control package now supports the following products:
- Access Transparency
- Cloud Tasks
- Cloud OS Login API
- Eventarc
- Firebase Security Rules
- Generative AI on Vertex AI
You can now use BigQuery DataFrames version 2.0, which makes security and performance improvements to the BigQuery DataFrames API, adds new features, and introduces breaking changes.
You can use partial ordering mode in BigQuery DataFrames to generate efficient queries. This feature is generally available (GA).
Airflow 2.10.5 is available in Cloud Composer.
Database retention policy is now enabled by default in Google Cloud console and remains disabled in Google Cloud CLI, API, and Terraform.
This feature helps to maintain the Airflow database size. You can enable or disable the database retention policy or adjust the retention period for new and existing environments.
The default environment's service account setting is gradually removed in Cloud Composer. After the change, you'll need to explicitly specify a service account when you create a new Cloud Composer environment. For more information about addressing the change, see the eariler announcement of this change.
In this release, the change is rolling out to the following regions: africa-south1, asia-northeast2, asia-south2, australia-southeast2, europe-north2, europe-southwest1, europe-west8, europe-west10, europe-west12, me-central1, me-central2, me-west1, northamerica-northeast2, northamerica-south1, southamerica-west1, us-east7, and us-south1. It will be rolled out to more regions in future releases.
Cloud Composer 2 environments now always use the environment's service account for performing PyPI packages installations:
- Existing Cloud Composer 2 environments that previously used the default Cloud Build service account now use the environment's service account instead.
- Cloud Composer 2 environments created in versions 2.10.2 and later already have this change.
- Cloud Composer 3 environments already use the environment's service account, and are not affected by this change.
- This change is gradually rolled out to all regions supported by Cloud Composer 2.
Cloud Composer now detects situations when asynchronous tasks are blocked in Airflow triggerers. If a trigger's execution is blocked for more than five minutes, Cloud Composer restarts the triggerer, which solves this transient issue.
(Cloud Composer 3) Key Access Justifications now correctly works for Customer Managed Encryption Keys (CMEK).
The bucket synchronization process doesn't fail if the /plugins
folder isn't available in the environment's bucket.
(Cloud Composer 3) It's now possible to override the default scopes of access tokens. Before the fix, the scope always defaulted to https://www.googleapis.com/auth/cloud-platform
and https://www.googleapis.com/auth/userinfo.email
. This resulted in authentication failures when accessing non-Google Cloud services.
The change is gradually rolled out to the following regions: africa-south1, asia-south2, australia-southeast2, europe-north2, europe-west3, europe-west10, europe-west12, northamerica-south1, southamerica-west1, us-east7, and us-south1. It will be rolled out to more regions in future releases.
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.5-build.0
- composer-3-airflow-2.10.2-build.13 (default)
- composer-3-airflow-2.9.3-build.20
New images are available in Cloud Composer 2:
- composer-2.12.1-airflow-2.10.5
- composer-2.12.1-airflow-2.10.2 (default)
- composer-2.12.1-airflow-2.9.3
Support dates for previous Cloud Composer 3 builds are available. All Cloud Composer 3 builds with Airflow 2.10.2 are supported until April 17, 2026.
In the Logs Explorer, you can now view the most frequently occurring fields and values in the JSON payload of your logs. For more information, see the Fields pane documentation.
Best practices for using Cloud Storage with media workloads are now available.
New Dataproc on Compute Engine subminor image versions:
- 2.0.137-debian10, 2.0.137-rocky8, 2.0.137-ubuntu18
- 2.1.85-debian11, 2.1.85-rocky8, 2.1.85-ubuntu20, 2.1.85-ubuntu20-arm
- 2.2.53-debian12, 2.2.53-rocky9, 2.2.53-ubuntu22
Dataproc on Compute Engine: The Spark BigQuery connector has been upgraded to version 0.34.1
in the latest 2.2
image version.
Fixed a bug in which Jupyter fails to restart upon cluster restart on Personal Authentication clusters.
You can now use custom constraints with Organization Policy to provide more granular control over specific fields for some Filestore resources. For more information, see Creating custom constraints for Filestore.
Gemini 2.5 Flash with thinking and other well-rounded capabilities is now available in Preview.
(New guide) Oracle E‑Business Suite with Oracle Database on Compute Engine VMs: Shows how to build the infrastructure to run Oracle E‑Business Suite applications with Oracle Database on Compute Engine VMs in Google Cloud.
GKE Inference Gateway is now available to significantly improve the performance, efficiency, and observability of generative AI workloads on GKE.
GKE Inference Gateway provides:
- Improved performance: AI serving tail latency is reduced, and AI serving throughput is increased through inference-optimized load balancing.
- Efficient resource utilization: Enables dense multi-workload serving of multiple LoRA fine-tuned models on a shared accelerator, leading to higher GPU/TPU utilization.
- Simplified operations: Features include model-aware routing, model-specific serving priority, and integrated AI Safety.
- Enhanced observability: Golden signals of observability are provided for inference requests.
Entity Context in Search
This feature enhances security investigations and incident response by letting users search for and view context events related to entities. It incorporates UDM entity context data to provide deeper insights into security incidents.
This feature is currently in Preview.
Entity Context in Search
This feature enhances security investigations and incident response by letting users search for and view context events related to entities. It incorporates UDM entity context data to provide deeper insights into security incidents.
This feature is currently in Preview.
Looker connector enhancements
You can now authorize the Looker connector to use the BigQuery OAuth credentials that you use with Looker, letting you view and interact with Looker Explores that use BigQuery data in Looker Studio. Learn more about how to authorize Looker data sources to use BigQuery OAuth credentials.
Custom organization policies are now generally available for Filestore. For more information, see Creating custom constraints for Filestore.
The discovery findings that Sensitive Data Protection generates in Security Command Center include recommended next steps. This improvement applies to the finding categories listed in Publish data profiles to Security Command Center.
The discovery findings that Sensitive Data Protection generates in Security Command Center include recommended next steps. This improvement applies to the finding categories listed in Publish data profiles to Security Command Center.
April 16, 2025
Cloud Service MeshNew troubleshooting tools for your service mesh are now available. You can get detailed error codes for your Istio resources and check the state of your mesh to identify and resolve configuration problems. Learn more about Resolving configuration issues and Understanding Feature State Conditions.
In-cluster Cloud Service Mesh 1.21 is no longer supported. For more information and to view the earliest end-of-life dates for other versions, see Supported versions.
M129 release
- Updated the Dataproc JupyterLab plugin to version 0.1.85.
You can now create Memorystore for Valkey instances with the Cluster Mode Disabled configuration. This configuration is in addition to the Cluster Mode Enabled configuration that we already support. The Cluster Mode Disabled feature is available in Preview. For more information, see Enable and disable cluster mode.
The polyglot voices feature is only supported in multi-regions.
Persistent resources for custom training is generally available (GA) and supports rebooting.
M129 release
The M129 release of Vertex AI Workbench instances includes the following:
- Updated the Dataproc JupyterLab plugin to version 0.1.85.
April 15, 2025
Apigee AnalyticsOn April 15, 2025 we released an updated version of Apigee Analytics and the Apigee UI.
Starting with this release, the Analytics dashboards available in the Apigee Classic UI redirect to the comparable dashboards in Apigee UI in Cloud console. These dashboards are available exclusively in the Apigee UI in Cloud console going forward.
For information and usage instructions for the Analytics dashboards, see Apigee API Analytics overview.
On April 15, 2025 we released an updated version of Apigee Analytics and the Apigee UI.
Starting with this release, the Analytics dashboards available in the Apigee Classic UI redirect to the comparable dashboards in Apigee UI in Cloud console. These dashboards are available exclusively in the Apigee UI in Cloud console going forward.
For information and usage instructions for the Analytics dashboards, see Apigee API Analytics overview.
Artifact Registry attachments are available in Preview for all repository formats. Attachments are artifacts that store metadata about a related artifact stored in Artifact Registry. To get started with attachments, see Store artifact metadata in attachments.
Fixed markdown rendering issues in chat for IntelliJ Gemini Code Assist.
We are releasing updated versions of the following premium parsers:
- Crowdstrike Detection Monitoring (CS_DETECTS)
- Crowdstrike Falcon (CS_EDR)
- Microsoft Defender for Endpoint
These updates include significant improvements to parser mappings. For a detailed list of all mapping changes, contact your Google SecOps representative.
The new versions will remain in an extended Release Candidate period through the end of May 2025. We recommend that you opt-in early and make any necessary adjustments before these updates become the default.
We are releasing updated versions of the following premium parsers:
- Crowdstrike Detection Monitoring (CS_DETECTS)
- Crowdstrike Falcon (CS_EDR)
- Microsoft Defender for Endpoint
These updates include significant improvements to parser mappings. For a detailed list of all mapping changes, contact your Google SecOps representative.
The new versions will remain in an extended Release Candidate period through the end of May 2025. We recommend that you opt-in early and make any necessary adjustments before these updates become the default.
Identity-Aware Proxy (IAP) now charges quota for programmatic and browser user requests independently. If you use IAP for programmatic workloads and have browser users within the same project, this change provides an improved representation of quota consumption.
For more information, see How can I address quota exceeded errors.
Regional endpoints are now available in Secure Source Manager. For more information, see Configure data locality by using regional endpoints.
April 14, 2025
Apigee XOn April 14, 2025 we released an updated version of Apigee.
Announcing data collectors data residency (DRZ) compliance for Apigee and Apigee hybrid.
Data collectors can be used with data residency for Subscription and Pay-as-you-go organizations and hybrid versions 1.14.0 and later.
See Data residency compatibility for information.
hybrid 1.11.2-hotfix.3
On April 14, 2025 we released an updated version of the Apigee hybrid software, 1.11.2-hotfix.3.
Apply this hotfix with the following steps:
In your overrides file, update the
image.url
andimage.tag
properties ofao
andruntime
:runtime: image: url: "gcr.io/apigee-release/hybrid/apigee-runtime" tag: "1.11.2-hotfix.3"
Install the hotfix release:
For Helm-managed releases, update the
apigee-env
chart with thehelm upgrade
command and your current overrides files:For each environment in your Apigee org:
helm upgrade ENV_RELEASE_NAME apigee-env/ \ --namespace APIGEE_NAMESPACE \ --set env=ENV_NAME \ --atomic \ -f OVERRIDES_FILE
- ENV_RELEASE_NAME is a name used to keep track of installation and upgrades of the
apigee-env chart
. This name must be unique from the other Helm release names in your installation. Usually this is the same as ENV_NAME. However, if your environment has the same name as your environment group, you must use different release names for the environment and environment group, for exampledev-env-release
anddev-envgroup-release
. For more information on releases in Helm, see Three big concepts in the Helm documentation. - APIGEE_NAMESPACE is your installation's namespace. The default is
apigee
. - ENV_NAME is the name of the environment you are upgrading.
- OVERRIDES_FILE is your edited overrides file.
- ENV_RELEASE_NAME is a name used to keep track of installation and upgrades of the
For
apigeectl
-managed releases:Install the hotfix release with
apigeectl init
using your updated overrides file:${APIGEECTL_HOME}/apigeectl init -f OVERRIDES_FILE --dry-run=client
Followed by:
${APIGEECTL_HOME}/apigeectl init -f OVERRIDES_FILE
Apply the hotfix release with
apigeectl apply
:${APIGEECTL_HOME}/apigeectl apply -f OVERRIDES_FILE --all-envs --dry-run=client
Followed by:
${APIGEECTL_HOME}/apigeectl apply -f OVERRIDES_FILE --all-envs
- For information on upgrading, see Upgrading Apigee hybrid to version 1.11.
- For information on new installations, see The big picture.
- For recommended actions after upgrading, see Validate policies after upgrade to 1.12-hotfix.3.
Stricter class instantiation checks included in this release.
JavaCallout policy now includes additional security during Java class instantiation. The enhanced security measure prevents the deployment of policies that directly or indirectly attempt actions that require permissions that are not allowed.
In most cases, existing policies will continue to function as expected without any issues. However, there is a possibility that policies relying on third-party libraries, or those with custom code that indirectly triggers operations requiring elevated permissions, could be affected.
To test your installation, follow the procedure in Validate policies after upgrade to 1.11.2-hotfix.3 to validate policy behavior.
Bug ID | Description |
---|---|
382967738 | Fixed a vulnerability in PythonScript policy. |
On April 14, 2025 we released an updated version of Apigee.
Announcing data collectors data residency (DRZ) compliance for Apigee and Apigee hybrid.
Data collectors can be used with data residency for Subscription and Pay-as-you-go organizations and hybrid versions 1.14.0 and later.
See Data residency compatibility for information.
The following resource types are now publicly available through the ExportAssets, ListAssets, BatchGetAssetsHistory, QueryAssets, and Feed APIs.
- Eventarc
eventarc.googleapis.com/Channel
eventarc.googleapis.com/ChannelConnection
cos-dev-125-18986-0-0
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.86 | v27.5.1 | v2.0.4 | See List |
Updated app-containers/containerd to v2.0.4.
Updated the Linux kernel to v6.6.86.
Modified toolbox to use unified cgroup hierarchy mode, when possible, instead of hybrid mode.
Upgraded app-admin/google-guest-agent to v20250331.00.
Upgraded app-admin/google-guest-configs to v20250328.00.
Upgraded app-containers/docker-credential-helpers to v0.9.3.
Fixed EINTR error in app-container/cni-plugins.
Upgraded chromeos-base/chromeos-common-script to v0.0.1-r662.
Upgraded chromeos-base/shill-client to v0.0.1-r4848.
Upgraded chromeos-base/power_manager-client to v0.0.1-r2966.
Upgraded sys-apps/dbus to v1.14.10-r196.
Upgraded chromeos-base/google-breakpad to v2025.04.01.213855-r235.
Upgraded chromeos-base/debugd-client to v0.0.1-r2731.
Upgraded chromeos-base/session_manager-client to v0.0.1-r2827.
Upgraded chromeos-base/update_engine-client to v0.0.1-r2478.
Upgraded chromeos-base/minijail to v18-r164.
Upgraded sys-apps/diffutils to v3.11-r2.
Upgraded net-nds/rpcbind to v1.2.7.
Upgraded net-misc/rsync to v3.4.1.
Upgraded dev-libs/nss to v3.110.
Upgraded sys-libs/libseccomp to v2.6.0-r2.
Upgraded dev-libs/expat to v2.7.1.
Upgraded app-arch/unzip to v6.0_p29.
Runtime sysctl changes:
- Changed: fs.file-max: 811816 -> 811798
cos-121-18867-0-94
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.74 | v27.5.1 | v2.0.4 | See List |
Updated app-containers/containerd to v2.0.4.
Modified toolbox to use unified cgroup hierarchy mode, when possible, instead of hybrid mode.
Fixed EINTR error in app-container/cni-plugins.
Upgraded sys-apps/diffutils to v3.11-r2.
Fixed CVE-2024-58083 in the Linux kernel.
Fixed CVE-2025-21999 in the Linux kernel.
Fixed CVE-2025-21887 in the Linux kernel.
Fixed CVE-2025-21867 in the Linux kernel.
Fixed CVE-2024-58070 in the Linux kernel.
Fixed CVE-2025-21853 in the Linux kernel.
Fixed CVE-2025-21853 in the Linux kernel.
Fixed CVE-2025-21763 in the Linux kernel.
Fixed CVE-2025-21762 in the Linux kernel.
Fixed CVE-2025-21764 in the Linux kernel.
Fixed CVE-2025-21759 in the Linux kernel.
Fixed CVE-2025-21760 in the Linux kernel.
Fixed CVE-2025-21726 in the Linux kernel.
Fixed CVE-2025-21796 in the Linux kernel.
Fixed CVE-2024-50138 in the Linux kernel.
Fixed KCTF-0c3057a in the Linux kernel.
Fixed CVE-2024-57979 in the Linux kernel.
Fixed CVE-2025-21727 in the Linux kernel.
Fixed CVE-2025-21812 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811827 -> 811714
cos-117-18613-164-109
Kernel | Docker | Containerd | GPU Drivers |
COS-6.6.72 | v24.0.9 | v1.7.24 | See List |
Modified toolbox to use unified cgroup hierarchy mode, when possible, instead of hybrid mode.
Upgraded sys-apps/diffutils to v3.11-r2.
Upgraded dev-libs/libusb to v1.0.28.
Fixed CVE-2025-21999 in the Linux kernel.
Fixed CVE-2025-21887 in the Linux kernel.
Fixed CVE-2025-21867 in the Linux kernel.
Fixed CVE-2024-58083 in the Linux kernel.
Fixed CVE-2024-58070 in the Linux kernel.
Fixed CVE-2025-21853 in the Linux kernel.
Fixed CVE-2025-21853 in the Linux kernel.
Fixed CVE-2025-21763 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 811785 -> 811760
cos-113-18244-291-102
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.123 | v24.0.9 | v1.7.24 | See List |
Modified toolbox to use unified cgroup hierarchy mode, when possible, instead of hybrid mode.
Upgraded sys-apps/diffutils to v3.11-r2.
Upgraded dev-libs/libusb to v1.0.28.
Fixed CVE-2025-22868 in dev-go/oauth2.
Updated dev-libs/expat to v2.7.0. This fixes CVE-2024-8176.
Fixed KCTF-0c3057a in the Linux kernel.
Fixed CVE-2024-35866 in the Linux kernel.
Fixed CVE-2025-21999 in the Linux kernel.
Fixed CVE-2024-58083 in the Linux kernel.
Fixed CVE-2025-21887 in the Linux kernel.
Fixed CVE-2025-21867 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812050 -> 812031
cos-109-17800-436-99
Kernel | Docker | Containerd | GPU Drivers |
COS-6.1.124 | v24.0.9 | v1.7.24 | See List |
Modified toolbox to use unified cgroup hierarchy mode, when possible, instead of hybrid mode.
Upgraded net-firewall/iptables to v1.8.11-r1.
Upgraded dev-libs/libusb to v1.0.28.
Upgraded sys-apps/diffutils to v3.11-r2.
Fixed CVE-2025-22868 in dev-go/oauth2.
Updated dev-libs/expat to v2.7.0. This fixes CVE-2024-8176.
Fixed CVE-2024-35866 in the Linux kernel.
Fixed KCTF-0c3057a in the Linux kernel.
Fixed CVE-2024-58083 in the Linux kernel.
Fixed CVE-2025-21887 in the Linux kernel.
Fixed CVE-2025-21867 in the Linux kernel.
Runtime sysctl changes:
- Changed: fs.file-max: 812258 -> 812288
Encrypting Dataplex data with customer-managed encryption keys (CMEK) is now available.
Headless web SDK 3.6.4 is released
Headless web SDK 3.6.4 fixes a problem where the virtual agent was sending multiple repeated messages to end-users in chat sessions.
Google Distributed Cloud (software only) for VMware 1.30.800-gke.66 is now available for download. To upgrade, see Upgrade a cluster or a node pool. Google Distributed Cloud 1.30.800-gke.66 runs on Kubernetes v1.30.11-gke.500.
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.
The following functional change was made in 1.30.800-gke.66:
- Removed support in the Konnectivity server (
konnectivity-server
) for the following weak cryptographic cipher suites: TLS_RSA_WITH_AES_256_GCM_SHA384 and TLS_RSA_WITH_AES_128_GCM_SHA256.
Fixed an issue that prevented user cluster upgrades when Dataplane V2 was explicitly configured with forward mode.
The 1.30.800-gke.66 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
Release 1.30.800-gke.66
Google Distributed Cloud for bare metal 1.30.800-gke.66 is now available for download. To upgrade, see Upgrade clusters. Google Distributed Cloud for bare metal 1.30.800-gke.66 runs on Kubernetes v1.30.11-gke.500.
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.
The following functional change was made in 1.30.800-gke.66:
- Updated the cluster upgrade operation to keep only the three latest
kubeadm
backups of etcd and configuration information for a node. Previously,kubeadm
kept node backups for every attempted upgrade.
The following issues are fixed in 1.30.800-gke.66:
Fixed an issue that resulted in an excessive creation of periodic
kube-proxy-cleanup
jobs on cluster nodes with high pod utilization.Fixed an issue that caused cluster creation to fail because kubelet restarted before required static pods are running.
Fixed an issue that allowed
bmctl reset
to run in situations where the reset resulted in the loss of quorum for control plane nodes. To run the command without enforcing the quorum, use the newly added--bypass-quorum-check
flag.
The 1.30.800-gke.66 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see Vulnerability fixes.
For information about the latest known issues, see Google Distributed Cloud for bare metal known issues in the Troubleshooting section.
A weekly digest of client library updates from across the Cloud SDK.
Go
Changes for pubsub/apiv1
1.49.0 (2025-04-07)
Features
ABAP SDK for Google Cloud version 1.10 (On-premises or any cloud edition)
Version 1.10 of the on-premises or any cloud edition of the ABAP SDK for Google Cloud is generally available (GA). In addition to offering expanded support for more than 294 Google Cloud APIs and few other enhancements, this version introduces the BigQuery AI and ML SDK for ABAP, Business Eventing Toolkit, and the ability to use Cloud Storage as content repository for SAP.
For more information, see What's new with the on-premises or any cloud edition of the ABAP SDK for Google Cloud.
End-to-end tracing is now generally available (GA). Spanner now supports end-to-end tracing, along with client-side tracing in the Node.js and Python client libraries, in addition to Java and Go. For more information, see Trace collection overview.
April 11, 2025
Access TransparencyAccess Transparency supports Backup for GKE in the GA stage.
Agent Assist offers a UI Connector with Salesforce to integrate with voice conversations.
For applicable events, if a context attribute value size limit is exceeded, you are notified through a publishing error (Eventarc Advanced), or attribute names for truncated values are listed in an extension attribute (Eventarc Standard). For more information, see Quotas and limits.
(New guide) Harness CI/CD pipeline for RAG applications: Shows how to implement a continuous integration (CI) and continuous deployment (CD) pipeline for a retrieval-augmented generation (RAG) application in Google Cloud. The architecture uses CI/CD products from Harness to deploy containers to Cloud Run services.
Use of Oracle Linux images provided by Compute Engine with Oracle Database
To run Oracle Database with SAP NetWeaver based applications on Google Cloud, SAP and Oracle have validated the use of the Oracle Linux images provided by Compute Engine.
For more information, see Supported operating systems.
If you set InfoType.version
to latest
when including the MAC_ADDRESS
infoType in your InspectConfig
, Sensitive Data Protection will now include MAC_ADDRESS_LOCAL
findings as type MAC_ADDRESS
in the scan results.
You can still use the old functionality by setting InfoType.version
to stable
, by leaving InfoType.version
unset when using the MAC_ADDRESS
infoType, or by using the MAC_ADDRESS_UNIVERSAL
infoType. In 30 days, the new functionality will be promoted to stable
.
April 10, 2025
Apigee XOn April 10, 2025, we released an updated version of Apigee.
The Apigee Extension Processor is now generally available (GA).
The Apigee Extension Processor lets Apigee customers add API management capabilities to Google Cloud and third-party products and services exposed using Cloud Load Balancing. Select from a range of Apigee policies that enable you to:
- Secure access to your workloads.
- Apply quota enforcement to network traffic.
- Manage Google access token and Google ID token injection to authenticate requests.
- Support native protocols like gRPC, SSE, and HTTP/3.
For more information, see the Apigee Extension Processor overview.
The Bigtable CQL client library for Java is available in Preview.
The Cassandra-Bigtable proxy adapter, which lets you connect your Apache Cassandra-based applications to Bigtable, is available in Preview.
The Bigtable Kafka sink, which lets you directly connect Apache Kafka and Google Cloud Managed Service for Apache Kafka, is now generally available (GA).
Managed APIs for Llama 4 Maverick and Scout are in Preview on Vertex AI. For more information, see the Llama 4 model card.
Design an optimal storage strategy for your cloud workload: Added guidance about Google Cloud Managed Lustre.
The following partner connectors have been added to the Looker Studio Connector Gallery:
- Netsuite by Windsor.ai
- Simplesat by Simplesat
- Pinterest Ads by Porter Metrics
- Recharge by Supermetrics
- Hurma by Hurma
- Shopware 6 Order Analytics by SHOPSY
- Instagram Public by Windsor.ai
When you create a Private Service Connect endpoint to connect to a regional endpoint of a supported service, you can use the public hostname in your configuration—for example, spanner.me-central2.rep.googleapis.com
.
April 09, 2025
AlloyDB OmniAlloyDB Omni is in General 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.
The alloydb_scann
extension is updated to include the following vector search improvements. These features are generally available (GA):
Inline filtering enables the execution of vector search and filter evaluation through the combined use of vector and secondary indexes. For more information, see "Inline filtering" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can let AlloyDB automatically create multiple parallel workers during index creation when the dataset grows, leading to faster build times. For more information, see "Build indexes in parallel" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
A distribution histogram is available in the
pg_stat_ann_indexes
view, which helps you understand the distribution of vectors between partitions of your ScaNN index. For more information, including recommendations about tuning thedistributionpercentile
metric, see "Tuning metrics" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.You can use a query recall evaluator to find the recall for a vector query for a given configuration, and to tune your parameters to achieve the desired vector query recall results for different vector indexes. For more information, see "Measure vector query recall" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.
The alloydb_scann
extension is updated to include the following vector search improvements in (Preview):
You can enable auto-maintenance for your ScaNN index and let incrementally manage the index such that when your dataset grows, AlloyDB splits large outlier partitions, and tries to provide better QPS and search results. For more information, see "Maintain indexes automatically" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
Adaptive filtering for ScaNN significantly improves the speed of filtered vector searches. Adaptive filtering automatically selects the most efficient filtering method at runtime. For more information, see "Filtered vector search" and "Adaptive filtering" in the documentation for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can enable index auto maintenance and adaptive inline filtering together using the
scann.enable_preview_features
Grand Unified Configuration (GUC) parameters. For more information, see "AlloyDB flags" for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
AlloyDB for PostgreSQL supports a 1 virtual central processing unit (vCPU) configuration with 8GB of memory, which is suitable for development and sandbox environments. For information about 1 vCPU supported regions and limitations, see Considerations when using 1 vCPU. This feature is in Preview.
AlloyDB Omni is in General 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.
AlloyDB supports AI-assisted troubleshooting that helps you resolve complex database performance issues like slow queries and high load. AI-assisted troubleshooting is available in Preview.
AlloyDB for PostgreSQL supports parameterized secure views, which provide a secure interface for application developers by improving data security and row access control while using SQL. This feature is in (Preview). For more information, see Parameterized secure views overview.
AlloyDB AI natural language (Preview) delivers secure and accurate responses for application end user natural language questions. For more information, see AlloyDB AI natural language overview.
AlloyDB AI query engine that builds on model endpoint management, and adds support for AI operators and Vertex AI multimodal and ranking models is available in (Preview). You can combine natural language phrases with SQL queries, like ai.if() for filters and joins, ai.rank() for ordering using ranking models, and ai.generate() for generating summaries of your data, and generate multimodal embeddings.
The alloydb_scann
extension is updated to include the following vector search improvements. These features are generally available (GA):
Inline filtering enables the execution of vector search and filter evaluation through the combined use of vector and secondary indexes. For more information, see "Inline filtering" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can let AlloyDB automatically create multiple parallel workers during index creation when the dataset grows, leading to faster build times. For more information, see "Build indexes in parallel" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
A distribution histogram is available in the
pg_stat_ann_indexes
view, which helps you understand the distribution of vectors between partitions of your ScaNN index. For more information, including recommendations about tuning thedistributionpercentile
metric, see "Tuning metrics" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.You can use a query recall evaluator to find the recall for a vector query for a given configuration, and to tune your parameters to achieve the desired vector query recall results for different vector indexes. For more information, see "Measure vector query recall" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.
The alloydb_scann
extension is updated to include the following vector search improvements in (Preview):
You can enable auto-maintenance for your ScaNN index and let incrementally manage the index such that when your dataset grows, AlloyDB splits large outlier partitions, and tries to provide better QPS and search results. For more information, see "Maintain indexes automatically" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
Adaptive filtering for ScaNN significantly improves the speed of filtered vector searches. Adaptive filtering automatically selects the most efficient filtering method at runtime. For more information, see "Filtered vector search" and "Adaptive filtering" in the documentation for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can enable index auto maintenance and adaptive inline filtering together using the
scann.enable_preview_features
Grand Unified Configuration (GUC) parameters. For more information, see "AlloyDB flags" for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
The alloydb_scann
extension is updated to include the following vector search improvements. These features are generally available (GA):
Inline filtering enables the execution of vector search and filter evaluation through the combined use of vector and secondary indexes. For more information, see "Inline filtering" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can let AlloyDB automatically create multiple parallel workers during index creation when the dataset grows, leading to faster build times. For more information, see "Build indexes in parallel" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
A distribution histogram is available in the
pg_stat_ann_indexes
view, which helps you understand the distribution of vectors between partitions of your ScaNN index. For more information, including recommendations about tuning thedistributionpercentile
metric, see "Tuning metrics" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.You can use a query recall evaluator to find the recall for a vector query for a given configuration, and to tune your parameters to achieve the desired vector query recall results for different vector indexes. For more information, see "Measure vector query recall" in the documentation for AlloyDB PostgreSQL, and AlloyDB Omni 15.7.1 and 16.3.0.
The alloydb_scann
extension is updated to include the following vector search improvements in (Preview):
You can enable auto-maintenance for your ScaNN index and let incrementally manage the index such that when your dataset grows, AlloyDB splits large outlier partitions, and tries to provide better QPS and search results. For more information, see "Maintain indexes automatically" in the documentation for AlloyDB PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
Adaptive filtering for ScaNN significantly improves the speed of filtered vector searches. Adaptive filtering automatically selects the most efficient filtering method at runtime. For more information, see "Filtered vector search" and "Adaptive filtering" in the documentation for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
You can enable index auto maintenance and adaptive inline filtering together using the
scann.enable_preview_features
Grand Unified Configuration (GUC) parameters. For more information, see "AlloyDB flags" for AlloyDB for PostgreSQL and AlloyDB Omni 15.7.1 and 16.3.0.
AlloyDB supports C4A Arm VMs on Google's custom-built Axiom processors. C4A VMs are available as predefined configurations from 1, 4, 8, 16, 32, 48, 64, and 72 vCPUs, up to 576 GB of DDR5 memory. C4A machines are available in limited regions. This feature is in Preview. For more information, see Considerations when using the 1 vCPU machine type.
AlloyDB now supports managed connection pooling in Preview. You can use managed connection pooling on your instances to improve the reliability, scalability, and performance of your workloads by optimizing resource utilization. For more information, see Configure managed connection pooling.
A bug was identified that can occasionally lead to parties appearing multiple times in prediction results. For engine versions v004.005 and later, this can also impact risk scores.
As of April 09, 2025 this bug has been fixed in-place for all existing engine versions in major version v004.004 and later.
Google recommends checking the risk scores output generated prior to this fix, or with engine versions that have not been fixed.
- For impacted engine versions within major versions v003.000, v004.002 or v004.004: Check whether the same party_id occurs multiple times in predictions output for a given risk_period_end_time. If so, remove these duplicate rows. The risk scores themselves are not affected.
- For impacted engine versions within major version v004.005 or later: Re-run prediction results. Risk scores might have been impacted for this run.
You can create and manage your App Hub applications using app-enabled folders, now available in Preview.
Gemini Cloud Assist in App Hub is supported in Preview. You can use the chat panel to retrieve information about your application in your app-enabled folder with Gemini assistance.
Gemini Cloud Assist for Artifact Registry is in Preview. You can learn about your container images with Gemini assistance.
To learn more, read the Gemini Cloud Assist overview.
Updated pricing, packaging, and setup guidance is now available for Gemini in BigQuery.
You can now combine raster and vector data with the ST_REGIONSTATS
geography function to perform geospatial analysis in BigQuery. For more information, see Work with raster data and try the tutorial that shows you how to use raster data to analyze global temperature by country. This feature is in preview.
You can now use the Apache Arrow format to stream data to BigQuery with the Storage Write API. This feature is available in preview.
Analytics Hub has been renamed BigQuery sharing. You'll see this new name in the documentation set and the marketing collateral. The product functionality and endpoints remain the same. For more information, see Introduction to data governance in BigQuery.
Dataplex Catalog has been renamed BigQuery universal catalog. You'll see this new name in the product page of the Google Cloud console, the documentation set, and the marketing collateral. Universal catalog brings together the data catalog capabilities of Dataplex Catalog and the runtime metastore capabilities of BigQuery metastore. For more information, see Introduction to data governance in BigQuery.
Continuous materialized views for Bigtable are available in Preview.
SQL support for Bigtable is generally available (GA), including an UNPACK
feature that lets you read time series data in a tabular format.
Logical views of Bigtable tables are available in Preview.
The Bigtable Studio query editor is generally available (GA).
The Airflow web server in Cloud Composer 3 requires at least 2 GB of memory when an environment is created or updated. This might lead to longer operation times or failures to perform these operations.
As a workaround, when you create a new Cloud Composer 3 environment or upgrade an existing environment, provide at least 2 GB of memory (default value) to the Airflow web server.
Gemini-powered auto-conversion is now available in Preview for all heterogeneous migration scenarios. You can use code and schema conversion enhancements automatically provided by Gemini to significantly reduce the time and complexity of your database migrations.
For more information about auto-conversion and other AI conversion features, such as conversion assistant or pattern matching, see Accelerate code and schema conversion with Gemini.
Database Migration Service support for heterogeneous SQL Server to PostgreSQL migrations is now available in Preview.
For more information, see:
Cross-Site Interconnect is available in Preview.
Cross-Site Interconnect is a new feature of Cloud Interconnect that helps you establish reliable, high-bandwidth Layer 2 connectivity between your on-premises network sites.
When you order Cross-Site Interconnect wires, Google provisions a transparent Layer 2 overlay over its global network between your two Cross-Site Interconnect locations.
For more information, see the Cross-Site Interconnect overview.
To help you get the right Cloud KMS keys on-demand, for consistent alignment with recommended encryption practices, Cloud KMS Autokey now has a free tier. The free tier covers the following usage:
- 100 free active key versions monthly
- 10,000 free cryptographic operations monthly
The free tier only applies to keys created using Cloud KMS Autokey. Key administration operations including key rotation are always free. For more details, see Cloud Key Management Service pricing
Application Monitoring lets you monitor the resources and infrastructure from the perspective of an App Hub application. The out-of-the-box (OOTB) dashboards generated for your application display log, metric, and incident data. These dashboards can help you understand how your application's resources are performing, and they can help you to diagnose issues. This feature is in Public Preview.
- Application Monitoring overview provides a brief overview of this feature.
- Set up application monitoring describes how to configure an observability scope so that you have an aggregated view of your log, metric, and trace data.
- View application telemetry describes the labels attached to your telemetry data, and it provides guidance about how to explore the OOTB dashboards.
Application Monitoring now supports app-enabled folders and App Hub host projects. For app-enabled folders, the metrics scope of the management project is automatically synchronized with the list of projects in the folder, provided quota is available. This feature is in Public Preview.
- Metrics scopes for app-enabled folders describes the synchronization algorithm and how to view your usage of the metrics scope quota.
Gemini Cloud Assist in Cloud Run is supported in Preview. You can use the chat panel to design, optimize, and troubleshoot your Cloud Run apps with Gemini assistance.
Cloud SQL Enterprise Plus edition now supports a new machine series called the C4A machine series, which provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. C4A uses a new type of storage called Hyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available in Preview.
For more information about the C4A machine series and its availability, see Machine series overview.
Query insights for Cloud SQL Enterprise Plus edition is now generally available (GA) for your Cloud SQL Enterprise Plus edition for MySQL instances. Query insights for Cloud SQL Enterprise Plus edition offers fine-grained metrics such as wait events and granular query plan samples for faster root-cause analysis and intelligent index recommendations.
For more information, see Use query insights to improve query performance.
Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.
Cloud SQL Enterprise Plus edition now supports a new machine series called the C4A machine series, which provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. C4A uses a new type of storage called Hyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available in Preview.
For more information about the C4A machine series and its availability, see Machine series overview.
Query insights for Cloud SQL Enterprise Plus edition is now generally available (GA) for your Cloud SQL Enterprise Plus edition for PostgreSQL instances. Query insights for Cloud SQL Enterprise Plus edition offers fine-grained metrics such as wait events and granular query plan samples for faster root-cause analysis and intelligent index recommendations.
For more information, see Use query insights to improve query performance.
Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.
Query insights for Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition is now generally available (GA) for Cloud SQL for SQL Server. You can also now view the query details, query plans, and statistical query execution charts for your top queries.
For more information, see Use query insights to improve query performance.
Dataplex Catalog has been renamed BigQuery universal catalog.
Database Center is generally available (GA). Database Center is an AI-assisted dashboard that gives you a centralized view across your database fleet. You can view database fleet health issues and recommendations, and you can ask questions about database fleet health issues, including availability configuration, data protection, security, and industry compliance. For more information, see Database Center overview.
Additional supported health issues are available in Database Center. Database Center detects health issues in multiple database products to help you maintain and troubleshoot your database fleet. For more information, see Supported health issues in the Database Center documentation.
You can view incidents and alerting policies in Database Center. Use incidents to be notified when a metric specific to a resource is more or less than a threshold value. Use an alerting policy to create incidents to help you monitor your database fleet resources. For more information, see Monitor your database fleet with alerting policies.
You can create a customized dashboard view that shows only the health issues in your database fleet that you want to see. A dashboard view can be for only you, or it can be shared with other users who have access to your Google Cloud project. For more information, see Create customized dashboard views.
Database Center is integrated with VPC Service Controls to secure data and resources. Use VPC Service Controls to create service perimeters that protect the resources in your database fleet and data of services that you explicitly specify. For more information, see Configure VPC Service Controls.
When you enable Gemini, the following performance recommendations and insights are available in Database Center:
- Inefficient query/index advisor for Cloud SQL
- Analyze option for high resource utilization health recommendation for Cloud SQL and AlloyDB.
For more information, see Supported health issues.
To use Gemini chat, you must open a Google Cloud project. Use Gemini chat to learn more about database fleet health issues in Database Center. For more information, see Use Gemini chat.
Dataplex Catalog has been renamed BigQuery universal catalog. You'll see this new name in the product page of the Google Cloud console, the documentation set, and the marketing collateral. Universal catalog brings together the data catalog capabilities of Dataplex Catalog and the runtime metastore capabilities of BigQuery metastore. For more information, see Introduction to data governance in BigQuery.
Dataproc Serverless for Spark: Gemini Cloud Assist Investigations is available in Preview for the following runtimes:
- 1.1
- 1.2
- 2.2
The Datastream API now supports streaming data to BigLake managed tables. For more information, see Stream data to BigLake managed tables (BLMT).
You can now use account connectors to connect your Google Cloud account with individual accounts on supported non-Google Developer Tools providers. This feature is in Preview.
You can now use Query insights to view query performance metrics for your database. This feature is in Preview.
Firestore is now available on Database Center. You can track your Firestore resources in the fleet inventory section and the resource table in the Database Center. You can also use Database Center to monitor the following health issues for your Firestore resources:
- No automated backup policy
- No point-in-time recovery
For more information about Database Center, see Database Center overview. For more information about health issues supported for Firestore, see Supported health issues.
You can now use Query insights to view query performance metrics for your database. This feature is in Preview.
Gemini Code Assist tools are in Preview. You can use tools to access external services from your IDE. To learn more about tools, see the Gemini Code Assist Tools overview.
Streamed chat responses are now generally available for IntelliJ and VS Code Gemini Code Assist. You can disable this feature in settings.
Agent Development Kit (ADK) is now available in Preview. For more information, see Agent Development Kit.
Vertex AI Agent Engine
The following features are now available for Vertex AI Agent Engine in Preview:
The following features are now generally available for Vertex AI Agent Engine:
Gemini Live API is now available as a public preview offering and has been updated with the following features:
- Support for responses in 8 voices and 31 languages using Chirp 3
- Updated UI support in Vertex AI Studio
- Expanded conversation session window
- Ability to extend conversation sessions
- Support to share your current screen with Gemini during conversations
- Transcription support for audio in and audio out
- Support to change or update the system instructions mid-session
For more information, see Gemini 2.0 Flash Live API.
Agent Garden is now available in Preview. For more information, see Vertex AI Agent Builder overview or go directly to Agent Garden in the Cloud Console.
Gemini 2.5 Pro is now available as a public preview offering.
For more information, see Gemini 2.5 Pro.
Vertex AI Agent Builder now refers to a suite of features for building and deploying AI agents in Vertex AI. For more information see, Vertex AI Agent Builder overview.
The original Vertex AI Agent Builder product has been renamed AI Applications. The product functionality and endpoints remain the same. For more information, see What is AI Applications?.
Grounding: Grounding with Google Maps is now available as a Public Experimental feature. For more information, see Grounding with Google Maps.
Grounding: Web Grounding for Enterprise is now Generally available. For more information, see Web Grounding for Enterprise.
Design storage for AI and ML workloads in Google Cloud: Updated to include Cloud Storage FUSE, Anywhere Cache, Hyperdisk ML, and Google Cloud Managed Lustre.
(New guide) Optimize AI and ML workloads with Cloud Storage FUSE: Learn how to optimize performance for AI and ML workloads on Google Kubernetes Engine (GKE) by using Cloud Storage FUSE.
Web SDK 2.24.4 patch is released
This patch fixes a cross-site scripting vulnerability.
Looker 25.6 is expected to include the following changes, features, and fixes:
Expected Looker (original) deployment start: Monday, April 14, 2025
Expected Looker (original) final deployment and download available: Thursday, April 24, 2025
Expected Looker (Google Cloud core) deployment start: Monday, April 14, 2025
Expected Looker (Google Cloud core) final deployment: Monday, April 28, 2025
In the Chart Config Editor, you can save a configuration as a template so that you can reuse it in other visualizations or share it as a starting point for other users.
The classification for the version
, versions
, and page_events
API endpoints have been changed from "Admin" to "N/A" in System Activity queries. These endpoints no longer count toward Admin API endpoint quotas.
The Druid JDBC driver has been updated from 1.22.0 to 1.25.0.
The Athena JDBC driver has been updated from 2.0.35.1000 to 2.1.5.1000.
The Dremio JDBC driver has been updated from 4.5.0 to 25.2.0.
The Spark Databricks JDBC driver has been updated from 2.6.34 to 2.7.1.
The Exasol JDBC driver has been updated from 6.2.3 to 24.2.1.
The Denodo JDBC driver has been updated from 8.8.0 to 9.1.3.
The Trino JDBC driver has been updated from 402 to 468.
Looker now supports key-pair authentication for Snowflake connections. Note: This feature is available only in Looker 25.6.17 and later.
An issue has been fixed where an Action Hub query could finish with a complete
status even if the query failed. This feature now performs as expected.
An issue has been fixed where sorting on a table visualization could fail to retrieve cached results, even if cached results were available for the query. This feature now performs as expected.
An issue has been fixed where a dashboard tile could appear to load indefinitely if a user didn't have permission to the model. This feature now performs as expected.
The file browser in the Looker IDE can now display files nested in 21 or fewer folders. The previous limit was 6.
An issue has been fixed where certain LookML validation errors could prevent Looker from successfully retrieving a list of models on the instance. This feature now performs as expected.
If a user doesn't have an email address associated with their Looker account, the schedule dialog will not display the Send Test button.
An issue has been fixed where an empty manifest file could cause the LookML Validator to display an error. This feature now performs as expected.
An issue has been fixed where changing the subtotal column sort on dashboard tiles wouldn't properly update the sort order. This feature now performs as expected.
An issue has been fixed where schedules to SFTP destinations could time out because of long SSH key generation times. This feature now performs as expected.
An issue has been fixed where an embedded folder could still be loading content but not display a loading indicator. This feature now performs as expected.
When uploading a JSON database authentication file to a connection, Looker now requires the file to be configured with the service_account
type.
An issue has been fixed where Looker would return a 500 error when it displayed a visualization with no results when the Grid Layout was set to By Row. This feature now performs as expected.
A new Labs feature, Fast Dev Mode Transition, improves the performance of Development Mode on your instance by loading LookML projects in read-only mode until a developer clicks the Create Developer Copy button for the project.
The New Database Connection Setup feature is now out of Labs and generally available. This feature updates the Add/Edit Connection page with a modernized UI, enhanced validation, connection testing capabilities, and a comprehensive configuration summary. If you want to revert to the legacy connections workflow, you can enable the Use Legacy Connections Page legacy toggle.
The Content Validator scoping feature is now generally available for customer-hosted Looker deployments (the feature is already available for Looker-hosted deployments). This feature lets developers scope the validation to specific LookML projects and a specific content folder (including its subfolders, if any). This can improve the performance of the Content Validator.
An issue has been fixed where embed users could save Looks to shared folders that they didn't have access to if the New Explore & Look Saving Labs feature was enabled. This feature now performs as expected.
The New Database Connection Setup feature is now generally available. This feature updates the Add/Edit Connection page with a modernized UI, enhanced validation, connection testing capabilities, and a comprehensive configuration summary. If you want to revert to the legacy connections workflow, you can enable the Use Legacy Connections Page legacy toggle.
Recommendations for Memorystore for Redis are now available at Database Center. With this release, Database Center displays health issues about the manageability and performance of Memorystore for Redis. This feature is in Preview. For more information, see Database Center overview and Database health issues.
Recommendations for Memorystore for Redis Cluster are now available at Database Center. With this release, Database Center displays health issues about the manageability and performance of Memorystore for Redis. This feature is in Preview. For more information, see Database Center overview and Database health issues.
Gemini Cloud Assist for Flow Analyzer is in Preview. You can generate SQL queries for VPC Flow Logs with Gemini assistance.
Model Armor and GKE integration
Model Armor now enforces security policies uniformly on generative AI inference traffic using a traffic extension. This applies to all application load balancers, including Google Kubernetes Engine Inference Gateway. This feature is in Preview. For more information, see Integration with Google Kubernetes Engine.
IAM recommender findings are now available with project-level activations of Security Command Center.
The Google Kubernetes Engine (GKE) Gateway supports using extensions to add custom logic into the load balancing processing path. For more information, see GKE extensions. This feature is in Preview.
You can configure Model Armor with Service Extensions to protect AI workloads on supported Application Load Balancers. For more information, see Callouts to Google services. This feature is in Preview.
You can use Gemini assistance to help you use system insights to optimize and troubleshoot Spanner resources. For more information, see Optimize and troubleshoot with Gemini assistance.
Spanner offers Cassandra compatibility with API support and new migration tools allowing seamless lift-and-shift migrations of Cassandra applications. For more information, see Migrate from Cassandra to Spanner.
General availability support for the following integration:
April 08, 2025
AlloyDB OmniIf you use mutating admission webhooks in your Kubernetes cluster, you might experience issues when you create database clusters and the webhooks conflict with the AlloyDB Omni Kubernetes Operator. Examples of mutating admission webhooks include LimitRanger and DefaultTolerationSecond. When the conflict occurs, the database pod repeatedly switches between running and terminating. To work around this issue, disable these webhooks where you run your AlloyDB Omni database cluster.
Action required: You can access Kubernetes operator 1.4.0 high availability (HA) improvements for automatic setup, failover, and healing capabilities starting with AlloyDB Omni 15.7.1 and later. To access these features, see "Migrate to the latest version of AlloyDB Omni on Kubernetes" for AlloyDB Omni 15.7.1 and 16.3.0.
AlloyDB Omni version 16.3.0 is generally available (GA). Version 16.3.0 includes the following features and changes:
- AlloyDB Omni supports PostgreSQL version 16.3.
- Asynchronous I/O improves performance on systems with atomic writes for high concurrency Online Transaction Processing (OLTP) workloads. This feature is available in Preview.
- You can upgrade your AlloyDB Omni PostgreSQL 15-based containers to AlloyDB Omni PostgreSQL 16 using
pg_upgrade
. For more information, see Upgrade to AlloyDB Omni version 16.3.0 on a VM. - AlloyDB Omni provides additional low-level logs (called "internal logs"), which are useful for debugging database issues. Production users are encouraged to enable this feature for greater observability. We recommend that you enable this feature to improve production observability.
- Active Directory integration lets you use your Active Directory Server to authenticate users for accessing your AlloyDB Omni 16.3.0 databases. This feature is available in Preview. For more information, see Integrate Active Directory with AlloyDB Omni.
- Multiple extensions are updated.
- Multiple GUCs have been updated or added.
- Security fixes for CVE-2024-7348 are implemented.
- Various bug fixes.
AlloyDB Omni version 15.7.1 is generally available (GA). Version 15.7.1 includes the following features and changes:
- AlloyDB Omni supports PostgreSQL version 15.7.
- AlloyDB Omni provides additional low-level logs (called internal logs), which are useful for debugging database issues. Production users are encouraged to enable this feature for greater observability. We recommend that you enable this feature to improve production observability.
- Multiple extensions are updated.
- Multiple GUCs have been updated or added.
- Security fixes for CVE-2024-7348 are implemented.
- Bug fixes.
The PostgreSQL Audit Extension (pgaudit) logging fix In AlloyDB Omni 15.7.0, which enables the pgAudit
extension together with the PostgreSQL logging_collector
parameter, might have resulted in audit logs loss. This issue is fixed in AlloyDB Omni versions 15.7.1 and 16.3.0.
The AlloyDB Omni Kubernetes operator version 1.4.0 is generally available (GA). Version 1.4.0 includes the following new features and changes:
- You can enable Active Directory integration on your Kubernetes-based AlloyDB Omni database cluster so that you can allow your existing Active Directory-based users to access your AlloyDB Omni database. This feature is available in Preview. For more information, see Integrate Active Directory with AlloyDB Omni on Kubernetes.
- You can create backups in any cloud or on-premises object storage systems that are compatible with the Amazon S3 API. For more information, see Create backups to S3-compatible storage (AlloyDB Omni 15.7.1 and 16.3.0).
- You can now access log files from sidecar containers.
- You can manually upgrade your AlloyDB Omni 15 database clusters to AlloyDB Omni 16.3.0 using
pg_upgrade
. For more information, see Migrate to the latest version of AlloyDB Omni on Kubernetes. - Beginning with Kubernetes operator version 1.4.0, the
alloydb_omni_instance_postgresql_wait_time_second_total
metric is renamed toalloydb_omni_instance_postgresql_wait_time_us_total
to reflect the correct unit of the metric value. If you are not already using microseconds (us
) for your metric unit, your queries and dashboard calculations need to change to reflect the correct unit of this metric:seconds
->us
. For more information, see Upgrade your AlloyDB Omni Kubernetes operator to version 1.4.0. - The PgBouncer connection pooler is generally available (GA). This release includes g-pgBouncer 1.4.0, which incorporates features and bug fixes from PgBouncer 1.24.0.
- You can configure the monitoring dashboard on your Grafana operator to visualize metrics using the monitoring endpoint of the Kubernetes operator.
- When the AlloyDB Omni Kubernetes Operator detects low disk space, the Kubernetes Operator reports a low disk space Critical Incident (CI) on the database cluster.
- AlloyDB Omni provides internal logs for debugging database issues. We recommend that you enable this feature to improve production observability. See "Enable internal logging" for AlloyDB Omni 15.7.1 and 16.3.0 for details.
- Disk cache metrics
alloydb_omni_database_postgresql_chill_cache_get_entry_calls_total
andalloydb_omni_database_postgresql_chill_cache_num_hits_total
are exposed when you enable disk cache on AlloyDB Omni versions 15.7.1 and 16.3.0. These metrics are database container-level metrics. For more information, see AlloyDB Omni metrics (15.7.1 and 16.3.0). - Use
alloydb_omni_instance_postgresql_version
to get the current PostgreSQL major version. For more information, see "Database container-level metrics" for AlloyDB Omni 15.7.1 and 16.3.0. - Various bug fixes and performance improvements.
The Kubernetes 1.4.0 DBCluster might have a status of DBClusterReady
even though its endpoint, which allows clients to connect, is not yet ready.
If you use mutating admission webhooks in your Kubernetes cluster, you might experience issues when you create database clusters and the webhooks conflict with the AlloyDB Omni Kubernetes Operator. Examples of mutating admission webhooks include LimitRanger and DefaultTolerationSecond. When the conflict occurs, the database pod repeatedly switches between running and terminating. To work around this issue, disable these webhooks where you run your AlloyDB Omni database cluster.
Action required: You can access Kubernetes operator 1.4.0 high availability (HA) improvements for automatic setup, failover, and healing capabilities starting with AlloyDB Omni 15.7.1 and later. To access these features, see "Migrate to the latest version of AlloyDB Omni on Kubernetes" for AlloyDB Omni 15.7.1 and 16.3.0.
AlloyDB Omni version 16.3.0 is generally available (GA). Version 16.3.0 includes the following features and changes:
- AlloyDB Omni supports PostgreSQL version 16.3.
- Asynchronous I/O improves performance on systems with atomic writes for high concurrency Online Transaction Processing (OLTP) workloads. This feature is available in Preview.
- You can upgrade your AlloyDB Omni PostgreSQL 15-based containers to AlloyDB Omni PostgreSQL 16 using
pg_upgrade
. For more information, see Upgrade to AlloyDB Omni version 16.3.0 on a VM. - AlloyDB Omni provides additional low-level logs (called "internal logs"), which are useful for debugging database issues. Production users are encouraged to enable this feature for greater observability. We recommend that you enable this feature to improve production observability.
- Active Directory integration lets you use your Active Directory Server to authenticate users for accessing your AlloyDB Omni 16.3.0 databases. This feature is available in Preview. For more information, see Integrate Active Directory with AlloyDB Omni.
- Multiple extensions are updated.
- Multiple GUCs have been updated or added.
- Security fixes for CVE-2024-7348 are implemented.
- Various bug fixes.
AlloyDB Omni version 15.7.1 is generally available (GA). Version 15.7.1 includes the following features and changes:
- AlloyDB Omni supports PostgreSQL version 15.7.
- AlloyDB Omni provides additional low-level logs (called internal logs), which are useful for debugging database issues. Production users are encouraged to enable this feature for greater observability. We recommend that you enable this feature to improve production observability.
- Multiple extensions are updated.
- Multiple GUCs have been updated or added.
- Security fixes for CVE-2024-7348 are implemented.
- Bug fixes.
The PostgreSQL Audit Extension (pgaudit) logging fix In AlloyDB Omni 15.7.0, which enables the pgAudit
extension together with the PostgreSQL logging_collector
parameter, might have resulted in audit logs loss. This issue is fixed in AlloyDB Omni versions 15.7.1 and 16.3.0.
The AlloyDB Omni Kubernetes operator version 1.4.0 is generally available (GA). Version 1.4.0 includes the following new features and changes:
- You can enable Active Directory integration on your Kubernetes-based AlloyDB Omni database cluster so that you can allow your existing Active Directory-based users to access your AlloyDB Omni database. This feature is available in Preview. For more information, see Integrate Active Directory with AlloyDB Omni on Kubernetes.
- You can create backups in any cloud or on-premises object storage systems that are compatible with the Amazon S3 API. For more information, see Create backups to S3-compatible storage (AlloyDB Omni 15.7.1 and 16.3.0).
- You can now access log files from sidecar containers.
- You can manually upgrade your AlloyDB Omni 15 database clusters to AlloyDB Omni 16.3.0 using
pg_upgrade
. For more information, see Migrate to the latest version of AlloyDB Omni on Kubernetes. - Beginning with Kubernetes operator version 1.4.0, the
alloydb_omni_instance_postgresql_wait_time_second_total
metric is renamed toalloydb_omni_instance_postgresql_wait_time_us_total
to reflect the correct unit of the metric value. If you are not already using microseconds (us
) for your metric unit, your queries and dashboard calculations need to change to reflect the correct unit of this metric:seconds
->us
. For more information, see Upgrade your AlloyDB Omni Kubernetes operator to version 1.4.0. - The PgBouncer connection pooler is generally available (GA). This release includes g-pgBouncer 1.4.0, which incorporates features and bug fixes from PgBouncer 1.24.0.
- You can configure the monitoring dashboard on your Grafana operator to visualize metrics using the monitoring endpoint of the Kubernetes operator.
- When the AlloyDB Omni Kubernetes Operator detects low disk space, the Kubernetes Operator reports a low disk space Critical Incident (CI) on the database cluster.
- AlloyDB Omni provides internal logs for debugging database issues. We recommend that you enable this feature to improve production observability. See "Enable internal logging" for AlloyDB Omni 15.7.1 and 16.3.0 for details.
- Disk cache metrics
alloydb_omni_database_postgresql_chill_cache_get_entry_calls_total
andalloydb_omni_database_postgresql_chill_cache_num_hits_total
are exposed when you enable disk cache on AlloyDB Omni versions 15.7.1 and 16.3.0. These metrics are database container-level metrics. For more information, see AlloyDB Omni metrics (15.7.1 and 16.3.0). - Use
alloydb_omni_instance_postgresql_version
to get the current PostgreSQL major version. For more information, see "Database container-level metrics" for AlloyDB Omni 15.7.1 and 16.3.0. - Various bug fixes and performance improvements.
The Kubernetes 1.4.0 DBCluster might have a status of DBClusterReady
even though its endpoint, which allows clients to connect, is not yet ready.
The command to connect to the interactive serial console of a server is changing on May 1, 2025.
Old command:
ssh -i SSH_KEY_ID -p 9600 PROJECT_ID.REGION.SERVER_NAME.USERNAME.bms=true@ssh-serialport.googleapis.com
New command:
ssh -i SSH_KEY_ID -p 9600 PROJECT_ID.REGION.SERVER_NAME.USERNAME.bms=true@\REGION\-ssh-serialport.googleapis.com
We recommend that you update your configurations by April 30, 2025 to avoid any disruptions. For instructions, see Configure serial console.
BigQuery ML now offers a built-in TimesFM univariate time series forecasting model that implements Google Research's open source TimesFM model. You can use BigQuery ML's built-in TimesFM model with the AI.FORECAST
function to perform forecasting without having to create and train your own model. This lets you avoid the need for model management.
To try using a TimesFM model with the AI.FORECAST
function, see Forecast a time series with a TimesFM univariate model.
This feature is in preview.
You can now create, view, modify, and delete Apache Iceberg resources in BigQuery metastore. This feature is generally available (GA).
You can now connect BigQuery metastore to Apache Flink. This feature is generally available (GA).
New Dataproc on Compute Engine subminor image versions:
- 2.2.52-debian12, 2.2.52-rocky9, 2.2.52-ubuntu22
Dataproc on Compute Engine: Fixed an issue with the retrieval of an Access token when using the ranger-gcs-plugin
with 2.2 images.
Previous Custom Extractor versions pretrained-foundation-model-v1.0-2023-08-22
and pretrained-foundation-model-v1.1-2024-03-12
will be deprecated on April 9, 2025. To ensure uninterrupted service, prediction traffic to these versions, including any fine-tuned variants, will be automatically redirected to the latest version, pretrained-foundation-model-v1.4-2025-02-05
.
For guidance on how to fine-tune a new version, refer to the fine tuning documentation.
(New guide) Oracle E-Business Suite with Oracle Exadata in Google Cloud: Shows how to build the infrastructure to run Oracle E-Business Suite applications with Oracle Cloud Infrastructure Exadata in Google Cloud.
Headless web SDK 3.6.3 is released
Headless web SDK 3.6.3 fixes a cross-site scripting vulnerability.
(2025-R14) Version updates
GKE cluster versions have been updated.
New versions available for upgrades and new clusters.
The following Kubernetes versions are now available for new clusters and for opt-in control plane upgrades and node upgrades for existing clusters. For more information on versioning and upgrades, see GKE versioning and support and Upgrades.
Rapid channel
- The following versions are now available in the Rapid channel:
Regular channel
There are no new releases in the Regular channel.
Stable channel
There are no new releases in the Stable channel.
Extended channel
- The following versions are now available in the Extended channel:
No channel
- The following versions are now available:
- The following node versions are now available:
(2025-R14) Version updates
- The following versions are now available in the Rapid channel:
(2025-R14) Version updates
There are no new releases in the Regular channel.
(2025-R14) Version updates
There are no new releases in the Stable channel.
(2025-R14) Version updates
- The following versions are now available in the Extended channel:
(2025-R14) Version updates
- The following versions are now available:
- The following node versions are now available:
Google Cloud Managed Lustre is now Generally Available (GA) with access by invitation.
Managed Lustre provides a fully managed parallel file system optimized for AI and HPC applications, with storage capacity up to 1 PB.
To request access to Managed Lustre in your Google Cloud project, contact your sales representative.
Custom organization policies are now generally available for Identity-Aware Proxy. For more information, see Use custom organization policies.
April 07, 2025
AI ApplicationsVertex AI Search: Stream Google Cloud Storage buckets to data stores
In addition to one time and periodic imports from Cloud Storage, you can stream unstructured data from Cloud Storage into a data store. This lets you serve results from the bucket to your users in near real time.
Streaming must be set up at the bucket-level (not at the folder- or file-level), and the bucket may only contain unstructured data.
For general information about creating data stores, see Create a search data store.
Vertex AI Search: Grounded generation with the generateGroundedContent
API
The generateGroundedContent
API to that grounds your answers with your inline text, Vertex AI Search data store, and Google Search is no longer available.
Instead, to generate grounded answers, Google recommends that you use the Generally available groundContent
API. You can either ground your answers with Google Search or with your own data. For more information, see Overview.
BigQuery data preparation is generally available (GA). It offers AI-powered suggestions from Gemini for data cleansing, transformation, and enrichment. BigQuery supports visual data preparation pipelines and pipeline scheduling with Dataform.
You can now create remote models in BigQuery ML based on Llama and Mistral AI models in Vertex AI.
Use the ML.GENERATE_TEXT
function with these remote models to perform generative natural language tasks for text stored in BigQuery tables. Try this feature with the Generate text by using the ML.GENERATE_TEXT
function tutorial.
This feature is generally available (GA).
An updated version of JDBC driver for BigQuery is now available.
Smart-tuning is now supported for materialized views when they are in the same project as one of their base tables, or when they are in the project running the query. This feature is generally available (GA).
BigQuery ML now uses dynamic token-based batching for embedding generation requests. Dynamic token-based batching puts as many rows as possible into one request. This change boosts per-request utilization and improves scalability for any queries per minute (QPM) quota. Actual performance varies based on the embedding content length, with an average 10x improvement.
A weekly digest of client library updates from across the Cloud SDK.
All Cloud Composer environment's GKE clusters are set up with maintenance exclusions from March 27, 2025 to April 12, 2025. For more information, see Maintenance exclusions.
Direct VPC egress support for Cloud Run jobs is now generally available (GA).
You can now configure Identity-Aware Proxy (IAP) for Cloud Run to secure your services with a single click from all ingress paths (in Preview).
Configuring GPU in your Cloud Run service is now generally available (GA).
Cloud Run Threat Detection is available in Preview.
Cloud SQL now supports the Enterprise Plus recommender. Based on your application workloads and resource utilization, the recommender helps you optimize performance by identifying SQL Server instances that might see performance improvements when upgraded to Cloud SQL Enterprise Plus edition.
A weekly digest of client library updates from across the Cloud SDK.
Node.js
Changes for @google-cloud/storage
7.16.0 (2025-03-31)
Features
Config Connector version 1.130.2 is now available.
New Beta resources (direct reconciler)
New Fields
-
- Added
spec.configmanagement.configSync.stopSyncing
in version1.129.
- Added
-
- Added
spec.defaultBackupScheduleType
field. - Added
spec.labels
field
- Added
New Alpha resources (direct reconciler)
ApphubApplication
BackupDRManagementServer
BackupDRBackupVault
BackupDRBackupPlan
BackupDRBackupPlanAssociation
BatchJob
BigLakeTable
BigQueryReservation
CodeDeployDeliveryPipeline
DataplexLake
DatastreamPrivateConnection
DatastreamConnectionProfile
DocumentAIProcessor
GKEBackupBackupPlan
GKEBackupRestorePlan
NetAppBackupPolicy
NotebooksEnvironment
SpannerInstanceConfig
VertexAIFeaturestore
VMwareEnginePrivateCloud
VMwareEngineNetwork
VMwareEngineNetworkPeering
VMwareEngineNetworkPolicy
WorkflowExecution
Reconciliation Improvements
Added support for direct reconciliation to more resources, with opt-in behaviour. The API is backward compatible. To use the direct reconciler, add the alpha.cnrm.cloud.google.com/reconciler: direct
annotation to the corresponding Config Connector object. The following resources now have direct reconciliation support (and we list some of the issues that this fixes):
- SpannerInstance
- You can use
spec.edition
field to optimize your enterprise edition type - You can use
spec.autoscalingConfig
to automate the scaling instead of manually configurespec.processingUnit
orspec. numNodes
. - You can use the
defaultBackupScheduleType
now. - Behavior Change If you use the SpannerInstance Kubernetes
metadata.labels
to configure your GCP labels, please change them to use thespec.labels
field instead.
- You can use
The basic HDD extended range tier is now generally available to all GKE customers through the Filestore CSI driver.
Premium parsers
Specific high-volume parsers are now categorized as premium. Google aims to address customer issues related to premium parsers as quickly as possible, typically within a few days.
For a complete list of different types of parsers and the level of support that Google provides for each, see Manage prebuilt and custom parsers.
For a complete list of premium parsers, see Default parser configuration and ingestion.
Premium parsers
Specific high-volume parsers are now categorized as premium. Google aims to address customer issues related to premium parsers as quickly as possible, typically within a few days.
For a complete list of different types of parsers and the level of support that Google provides for each, see Manage prebuilt and custom parsers.
For a complete list of premium parsers, see Default parser configuration and ingestion.
Preview: You can now enable IAP directly on your Cloud Run services without configuring load balancers.
For more information, see Configure Identity-Aware Proxy for Cloud Run.
Looker has released version 1.4.2 of the Looker–Power BI Connector. See the Looker–Power BI Connector change log for details about version 1.4.2.
IPv6 subnet exchange is generally available.
You can use export filters to configure a VPC spoke to exchange IPv6 subnet ranges or both IPv4 and IPv6 subnet ranges. For more information, see VPC connectivity with export filters.
For Autonomous Databases, you now have the options to set up public network access and private network access in Google Cloud. This feature is generally available (GA).
A weekly digest of client library updates from across the Cloud SDK.
Go
Changes for pubsub/apiv1
1.48.1 (2025-04-01)
Bug Fixes
- pubsub/pstest: Message ordering issue (#11603) (1d6ffc0)
- pubsub: Update golang.org/x/net to 0.37.0 (1144978)
Documentation
- pubsub: Update documentation for JavaScriptUDF to indicate that the
message_id
metadata field is optional instead of required (f437f08)
Cloud Run Threat Detection is available in Preview.
April 06, 2025
Google SecOpsCreate a quick action (Preview)
Administrators can now predefine quick actions for analysts to execute directly within cases and alerts.
The Quick Actions widget can be added to default case and alert views, and customized alert views within playbooks.
For more information, see Create a quick action.
What's New in Google SecOps
At the top of your Google SecOps screen, click the question mark and select What's New to display the top five new features in the Google SecOps platform.
Release 6.3.41 is now available for all regions.
April 05, 2025
Google SecOps SOARRelease 6.3.42 is being rolled out to the first phase of regions as listed here.
Create a quick action (Preview)
Administrators can now predefine quick actions for analysts to execute directly within cases and alerts.
The Quick Actions widget can be added to default case and alert views, and customized alert views within playbooks.
For more information, see Create a quick action.
April 04, 2025
Access ApprovalAccess Approval supports Document AI in the GA stage.
Access Approval supports Storage Intelligence in the GA stage.
BigQuery ML now supports the following generative AI functions, which let you analyze text using a Vertex AI Gemini model. The function output includes a response that matches the type in the function name:
This feature is in preview.
The following resource types are now publicly available through the analyze policy (AnalyzeIamPolicy and AnalyzeIamPolicyLongrunning) APIs.
- Compute Engine
compute.googleapis.com/StoragePool
- Discovery Engine
discoveryengine.googleapis.com/Engine
A new release is available. This release may include some or all of the following: general performance improvements, bug fixes, and updates to the API reference documentation.
You can include pipe syntax in the SQL queries you run on the Log Analytics page. Pipe syntax supports a linear query structure designed to make your queries easier to read, write, and maintain. The pipe syntax feature is generally available (GA).
If you have enabled logging for failures of an uptime check, you can view the logs from the Uptime details page. For more information, see View details of an uptime check.
The rollout of the following extension versions and plugin versions is complete:
Extensions and plugins
- PostGIS is upgraded from 3.4.4 to 3.5.2.
To use these versions of the extensions, update your instance to [PostgreSQL version]. R20250302.00_04
.
If you use a maintenance window, then the updates to the minor, extension, and plugin versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks.
For more information on checking your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.
1.25.0-asm.8 is now available for in-cluster Cloud Service Mesh.
You can now download 1.25.0-asm.8 for in-cluster Cloud Service Mesh. It includes the features of Istio 1.25.0 subject to the list of supported features.
The following environment variables are not supported:
- PILOT_MX_ADDITIONAL_LABELS
- PILOT_DNS_CARES_UDP_MAX_QUERIES
- PILOT_DNS_JITTER_DURATION
- PILOT_SEND_UNHEALTHY_ENDPOINTS
The following annotations are not supported:
- networking.istio.io/traffic-distribution
- istio.io/reroute-virtual-interfaces
For details on upgrading Cloud Service Mesh, see Upgrade Cloud Service Mesh. Cloud Service Mesh version 1.25.0-asm.8 uses Envoy v1.33.1-dev.
There is a known issue where all gateway CRs will see a downtime for status updates when upgrading from 1.24.3 to 1.25.x .
On June, 30, 2024, Red Hat Enterprise Linux (RHEL) 7 will reach end of support and the images marked deprecated on Google Cloud. If you use RHEL 7 images in your project, review RHEL end of support.
On June 30th, 2024, CentOS 7 will reach end of support and the images marked deprecated on Google Cloud. If you use CentOS 7 images in your project, review CentOS end of support guidance .
Optimize log management using extractors
This feature is currently in Preview.
You can now optimize log management by creating extractors to pull specific fields from high-volume log sources. For more information, see Work with extractors.
Optimize log management using extractors
This feature is currently in Preview.
You can now optimize log management by creating extractors to pull specific fields from high-volume log sources. For more information, see Work with extractors.
Google Cloud NetApp Volumes now supports SnapMirror-based volume migration for allow-listed users. This feature lets you migrate from ONTAP-based Flex volumes to NetApp Volumes. For more information, see Volume migration.
Risk Manager is now called Cyber Insurance Hub. Additional insurance partners have been added with expanded customer eligibility.
For detailed information about this product, see the Cyber Insurance Hub documentation.
The Secret Manager add-on for Google Kubernetes Engine (GKE) now supports the automatic rotation of secrets. You can configure the Secret Manager add-on to automatically rotate secrets so that secrets updated in Secret Manager after initial pod deployment are automatically and periodically pushed to the pod. This feature is available in Preview.
For more information, see Configure automatic rotation of secrets.
Spanner has added the PARAMETER_DEFAULT
column to the INFORMATION_SCHEMA.PARAMETERS
table. This column returns the default value of change stream read functions parameters.
April 03, 2025
BigQueryBigQuery migration assessment now includes support for Amazon Redshift Serverless. This feature is in preview.
You can now generate structured data by using BigQuery ML's AI.GENERATE_TABLE
function with Gemini 1.5 Pro, Gemini 1.5 Flash, and Gemini 2.0 Flash models. You can use the AI.GENERATE_TABLE
function's output_schema
argument to more easily format the model's response. The output_schema
argument lets you specify a SQL schema for formatting, similar to the schema used in the CREATE TABLE
statement. By creating structured output, you can more easily convert the function output into a BigQuery table.
Try this feature with the Generate structured data by using the AI.GENERATE_TABLE
function tutorial.
This feature is in preview.
The unification of Cloud Composer 3 billing with BigQuery is paused until further notice. The change was previously scheduled for April 13, 2025.
In recently released Airflow builds of Cloud Composer 3, the Airflow web server requires more CPU to finish its initialization when an environment is created or updated. This might lead to longer operation times or failures to perform these operations.
As a workaround, when you create a new Cloud Composer 3 environment or upgrade an existing environment, provide at least 1 CPU to the Airflow web server.
This issue currently affects composer-3-airflow-2.10.2-build.12 and composer-3-airflow-2.9.3-build.19 Airflow builds.
You can now integrate Cloud SQL for MySQL and Vertex AI (in Preview). This allows you to invoke predictions and generate vector embeddings using models hosted in Vertex AI. To use this integration, update your instance to [MySQL version].R20250304.00_01
.
For more information, see Integrate Cloud SQL with Vertex AI.
New Dataproc Serverless for Spark runtime versions:
- 1.1.98
- 1.2.42
- 2.2.42
Dataproc Serverless for Spark: Installed CUDA, cuDNN and NCCL NVIDIA libraries in 1.2 and 2.2 runtimes.
Google Cloud VMware Engine now supports 24 ve2 node types, enabling precise and efficient environment sizing. See VMware Engine node types for full details.
GKE now provides insights and recommendations that help you identify workloads without resource requests or limits so that you can specify the resource needs for these workloads. Configuring CPU and memory requests and limits for containers is the best practice for improving reliability and performance, and is a necessary prerequisite for understanding and optimizing resource utilization by your workloads and their cost.
Migrate to Virtual Machines supports importing Arm disk images to Google Cloud. For information on operating systems supporting this feature, see Supported operating systems.
In Spanner Graph you can view a visualization of graph elements returned by a Spanner Graph query and of a Spanner Graph schema. A graph query visualization helps you understand the query results by revealing patterns, dependencies, and anomalies in the returned graph elements. A graph schema visualization helps you understand how the nodes and edges in a schema are related. For more information, see Work with Spanner Graph visualizations.