Releasesby GlyphIn GKE version 1.37.0-gke.3570000 and later, you can split each Local SSD on a node between ephemeral storage...
In GKE version 1.37.0-gke.3570000 and later, you can split each Local SSD on a node between ephemeral storage and raw block storage. When you create a cluster or node pool, use the capacity property of the --ephemeral-storage-local-ssd flag to set how much Local SSD capacity GKE formats for ephemeral storage.
Also shipped Nov 3, 2026Google Cloud in November 2026 →
[In preview] Public Preview: Extend immutability for PITR backups for Azure SQL Database and Azure SQL Managed Instance
With this enhancement, you have the ability to lock your retention to the configured PITR retention, beyond the default 7 days of immutable backups that are already available. This is especially useful for financial customers who typically have 35 days of
UI improvements now generally available for PD Reliability Platform customers
Customers on PD Reliability Platform now have an improved UI experience, including: Consolidated settings: Brings all your configuration and admin settings together in one place. New nav: Provides streamlined access to your most important capabilities. Your Subscription: Shows where the opportunities are to shift work off humans and onto AI and automation.
Claude auto-connect (beta) for PagerDuty MCP Server now in Early Access
With Claude auto-connect, members with a matching PagerDuty account are connected to PagerDuty in Claude automatically, with no sign-in screen and no identity provider (IdP) configuration. Members act as themselves in PagerDuty, with the permissions they already have there.
Dependabot version updates support Agent Package Manager
You can now keep your AI agent skills, prompts, and instructions up to date with Dependabot version updates for Agent Package Manager (APM) . Dependabot opens pull requests to update supported git dependencies declared in apm.yml and regenerates apm.lock.yaml when it’s present. This support covers version updates, not security updates.
Okta connector is available in Beta
The managed Okta connector is now available in Beta in Databricks Lakeflow Connect. Workspace admins can enable Lakeflow Connect for Okta on the Previews page . Use the connector to ingest identity and access data from Okta into Databricks, including users, groups, group memberships, app integrations, devices, policies, and administrator roles.
Trigger Lakeflow Jobs when upstream jobs complete (Beta)
You can now run a Lakeflow Job when one or more upstream jobs complete, including across workspaces attached to the same Unity Catalog metastore. Configure dependencies on the downstream job. See Trigger jobs when upstream jobs complete .
More from Google Kubernetes EngineEvery Google Kubernetes Engine release →
Managed OpenTelemetry for GKE is generally available
Managed OpenTelemetry for GKE is now generally available, allowing users to collect traces, metrics, and logs using a Google-managed collector. It supports OTLP ingestion and improved integration with Cloud Telemetry API.
(2026-R46) Version updates
Google Kubernetes Engine released update 2026-R46, providing new cluster versions for manual control plane and node upgrades as well as new cluster creation.
New GKE versions released to Rapid channel
Google Kubernetes Engine updated its Rapid channel with new versions, including 1.34.12-gke.1539000, 1.35.9-gke.1505000, 1.36.5-gke.1982000, and 1.37.1-gke.3020000, alongside new 1.38.0 alpha releases.
C4D bare metal machine types are generally available on GKE
C4D bare metal machine types are now generally available on Google Kubernetes Engine for clusters running version 1.36 or later.
(2026-R45) Version updates
Google Kubernetes Engine released update 2026-R45 with updated cluster versions for new clusters and manual upgrades.
GKE update sets 1.37.1-gke.1697000 as Rapid channel default
Google Kubernetes Engine set 1.37.1-gke.1697000 as the default version in the Rapid channel and introduced new patch and alpha versions alongside auto-upgrade targets.
You can now provision GKE nodes from storage-optimized Z4M machine series : - Manually: starting from GKE...
You can now provision GKE nodes from storage-optimized Z4M machine series : Manually: starting from GKE version 1.36.3-gke.1767000 and later. Using compute classes, cluster autoscaler, node pool auto-creation and in Autopilot clusters: starting from GKE version 1.37.0-gke.4713000 and later.
For GKE Standard CPU node pools, GKE can now upgrade nodes by updating the existing Compute Engine VM in...
For GKE Standard CPU node pools, GKE can now upgrade nodes by updating the existing Compute Engine VM in place, instead of deleting the VM and creating a new one. Because the node keeps its underlying VM, it also keeps its compute capacity during the upgrade. This lowers the risk that a node upgrade fails or stalls because resources aren't available.