Google Cloud Release Notes

In GKE version 1.32.2-gke.1652000 and later, new external LoadBalancer Services use zonal Network Endpoint Group (NEG) backends by default. This applies only to new backend service-based external LoadBalancer Services. Existing LoadBalancer Services are not affected. To learn more, see Create a backend service-based external load balancer.

The Places SDK for iOS version 9.4.1 is now available. See the Release Notes for information about this release and for all previous releases or subscribe to the Release Notes XML feed.

If you are a new user, see Set Up in the Google Cloud Console to start the installation process.

If you are an existing customer, see the upgrade instructions at Versions.

Place Details UI Kit. The Place Details UI Kit allows you to add an individual UI component that displays place details to your app. See the full documentation.

Cloud Deploy now uses Skaffold 2.14 as the default Skaffold version, as of March 21, 2025, for all target types.

All GKE clusters now export four new rollup metrics by default at no additional charge. These new metrics are for monitoring GKE TPU NodePools and JobSets:

• kubernetes.io/node_pool/accelerator/times_to_recover: Distribution of recovery period durations. Each sample indicates a single recovery operation for the NodePool to recover from a downtime period. The data is sampled within 60s after the completion of NodePool recovery, and emitted within 24h. This metric does not include a sample for downtime period longer than 7 days. This metric is only applicable for GKE multi-host TPU node pools.

• kubernetes.io/jobset/times_between_interruptions: Distribution of times between the end of last interruption and beginning of current interruption for a JobSet. Each sample indicates a single duration between last and current interruption. The data is sampled within 60s after the current interruption starts, and emitted within 24h. The metric does not include a sample for duration between interruptions longer than 7 days. This metric is only applicable for JobSets running on nodes with GPU/TPU and having a single replicated job.

• kubernetes.io/jobset/times_to_recover: Distribution of recovery period durations. Each sample indicates a single recovery operation for the JobSet to recover from a downtime period. The data is sampled within 60s after the completion of JobSet recovery, and emitted within 24h. This metric does not include samples for downtime periods longer than 7 days. This metric is only applicable for JobSets running on nodes with GPU/TPU and having a single replicated job.

• kubernetes.io/jobset/uptime: Total time the JobSet has been available. The data is sampled every 60s and emitted within 24h after sampling. This metric is only applicable for JobSets running on nodes with GPU/TPU and having a single replicated job.

The Risk section of the SecOps console has been updated for Security Command Center Enterprise, introducing the following features in Preview:

• Issues are the most important security risks Security Command Center Enterprise has found in your cloud environments. Sourced from Security Command Center's virtual red teaming and security graph, issues give you all the details you need to understand, triage, and remediate a risk. Explore attack path diagrams, attack exposure scores, exposed resources, related findings, and whether multiple issues exist on a primary resource, all from the one place.
• Security graph is a graph database that has cloud resources like assets, identities, apps, and data assigned to its nodes, while the edges of the graph determine the risk relationship between those resources following detection rules. When a relationship risk is discovered, the security graph generates an issue.
• Chokepoints are critical severity issues that focus on common resources or resource groups where multiple attack paths converge. Because of this focus on a common point, resolving a chokepoint can resolve other issues too, like toxic combinations.

Quotas for scheduled emails

Looker Studio now limits the number of recipients to whom a user can send scheduled emails per day and per month. See the Quotas for scheduled email delivery section for more information. If you have Looker Studio Pro, no such quotas apply. However, any reports in the Owned by me folder are considered to be personal reports and will be subject to quotas. To resolve this, you can upgrade a report to Looker Studio Pro.

Partner connection launch update

The following partner connectors have been added to the Looker Studio Connector Gallery:

• Reddit Ads by Dataslayer
• Odoo Accounting AppiWorks by Jivrus Technologies
• Spotify Advertising by Power My Analytics
• Instagram Insights by Data Bloo
• Niteco Performance Insights by Niteco Group
• Yahoo! Japan Display by Catchr
• Line Ads by Catchr Sources
• Yahoo! Japan Search Ads by Catchr
• Oracle AppiWorks by Jivrus Technologies
• Trackingplan by Trackingplan
• Facebook Ads by Master Metrics
• YouTube Analytics by everythingData
• YouTube Analytics by Two Minute Reports
• X Ads by Two Minute Reports
• Google Ads by everythingData
• Hubspot by everythingData
• IOT Dashzoom by Dashzoom
• ad:personam Analytics by ad:personam GmbH
• 快客-Thread 社群洞察 by 黑客數位
• Datastore AppiWorks by Jivrus Technologies
• Google PageSpeed by Catchr
• Yelp Review by Catchr
• Xero by Windsor.ai
• Google Trends by Catchr
• Appstore Review by Catchr
• Branch by Catchr
• Airbnb Review by Catchr
• Booking Review by Catchr
• Facebook Review by Catchr
• Glassdoor Review by Catchr
• Capterra Review by Catchr
• g2 Review by Catchr
• Indeed Review by Catchr
• Tripadvisor Review by Catchr
• Google Play Review by Catchr
• Trustpilot Review by Catchr
• DynamoDB AppiWorks by Jivrus Technologies
• 快客-Instagram 社群洞察 by 黑客數位
• Capterra PPC by everythingData
• ProfitWell by Catchr
• Zoho CRM by Catchr
• ChartMogul by Catchr
• HubSpot by Dataslayer

You can now use custom constraints with Organization Policy to provide more granular control over specific fields for some networksecurity and networkservices resources.

Encrypt your data-in-use by using Confidential Computing. This feature is now available in Preview. You can enable the Confidential VM service when you create a Vertex AI Workbench instance. To get started, see Create an instance with Confidential Computing.