Releasesby GlyphStarting on June 30, 2026, the Filestore API ( file.googleapis.com ) is enabled by default when you enable...
Starting on June 30, 2026, the Filestore API ( file.googleapis.com ) is enabled by default when you enable the Kubernetes Engine API ( container.googleapis.com ) in a project. The Filestore API is required for PersistentVolumes that use the ReadWriteMany access mode in GKE . New Features
Also shipped Jul 16, 2026Google Cloud in July 2026 →
DCM Projects: New capabilities (Preview)
DCM Projects now supports the following capabilities in preview: For more information, see Supported object types in DCM Projects and Deploy and manage DCM Projects .
VOLATILE scalar UDFs are supported with dynamic table incremental refresh (General availability)
VOLATILE scalar user-defined functions (UDFs) are now supported with dynamic table incremental refresh in INCREMENTAL, AUTO, and ADAPTIVE refresh modes. This applies to scalar UDFs written in Python, Java, Scala, JavaScript, and SQL. For incremental refresh, VOLATILE UDFs are supported only in the SELECT clause.
Scala and Java UDFs in Unity Catalog are now generally available
Register Scala and Java user-defined functions (UDFs) in Unity Catalog and reuse them across notebooks, jobs, and SQL warehouses with Unity Catalog governance. Reuse existing JVM logic and get better performance than Python UDFs on all compute, including serverless. See Scala and Java user-defined functions (UDFs) in Unity Catalog .
MLflow trace storage in Unity Catalog is now generally available
MLflow trace storage in Unity Catalog tables is now generally available. Databricks recommends storing traces in Unity Catalog for new and production workloads: storage is unlimited, traces are stored in OpenTelemetry (OTel) format, access is governed through Unity Catalog schema and table permissions, and you can query traces with SQL, Genie, AI/BI...
Agentic code converter is in Beta
The agentic code converter is in Beta . Use it to convert legacy SQL dialects, such as T-SQL, Snowflake, Redshift, Oracle, BigQuery, and Teradata, to ANSI SQL in migration projects in your workspace.
Google Gemini 3 Pro is retired
Google Gemini 3 Pro is retired. Gemini 3.1 Pro is the recommended replacement. See Deprecated and retired models for migration guidance.
More from Google Kubernetes EngineEvery Google Kubernetes Engine release →
(2026-R30) Version updates
GKE cluster versions have been updated. New versions available for upgrades and new clusters. The following versions are now available for new GKE clusters, and for manual control plane upgrades and node upgrades for existing clusters. For more information about versioning and upgrades, see GKE versioning and support and About GKE cluster upgrades .
Note : Your clusters might not have these versions available
Note : Your clusters might not have these versions available. Rollouts are already in progress when we publish the release notes, and can take multiple days to complete across all Google Cloud zones. Version 1.36.0-gke.4681000 is now the default version for cluster creation in the Rapid channel.
In GKE version 1.36.0-gke.3204000 and later, when you manually or automatically create a GKE node pool that...
In GKE version 1.36.0-gke.3204000 and later, when you manually or automatically create a GKE node pool that consumes capacity reservations, you can stop GKE from falling back to on-demand capacity if reserved capacity isn't available.
GKE version 1.33 now supports the N4D machine series for node pool auto-creation and Autopilot clusters in...
GKE version 1.33 now supports the N4D machine series for node pool auto-creation and Autopilot clusters in the following patch versions and later: Node pool auto-creation : 1.33.12-gke.1208000 and later Autopilot : 1.33.13-gke.1079000 and later
In GKE version 1.36.0-gke.4447000 and later, the VerticalPodAutoscaler supports CPU startup boost , which...
In GKE version 1.36.0-gke.4447000 and later, the VerticalPodAutoscaler supports CPU startup boost , which temporarily increases CPU requests during application startup to improve startup latency and cost efficiency. This feature is available in Preview. Stable Channel
GKE Dataplane V2 clusters running version 1.35.1-gke.1516000 or later now use CNI version 1.1.0 in the CNI...
GKE Dataplane V2 clusters running version 1.35.1-gke.1516000 or later now use CNI version 1.1.0 in the CNI configuration files. This change requires downstream CNI plugins to be compatible with CNI version 1.1.0.
Rollout sequencing with custom stages is now generally available
Rollout sequencing with custom stages is now generally available. This version of rollout sequencing, which is recommended if you're configuring an environment for the first time, offers a robust set of features including the following: Define custom stages : Sequence the rollout of a new GKE version across environments.
To improve security, Ubuntu node images in GKE version 1.37 and later don't pre-install the vulkan-tools...
To improve security, Ubuntu node images in GKE version 1.37 and later don't pre-install the vulkan-tools package. If you run Vulkan diagnostic tools (such as vulkaninfo ) directly on GKE Ubuntu hosts, then you must manually install the vulkan-tools package. This change doesn't affect containerized GPU/Vulkan workloads.