Data and AI releases

548 this month · 176 companies

The bare metal machine types from the C3 machine series are now generally available with GKE clusters

Generally availableNot yet verified

The bare metal machine types from the C3 machine series are now generally available with GKE clusters. You can now provision machine types such as c3-standard-192-metal in Standard mode with any available GKE version.

Read on docs.cloud.google.com

Also shipped Sep 1, 2026Google Cloud in September 2026 →

More from Google Kubernetes EngineEvery Google Kubernetes Engine release →

(2026-R37) 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 .

Update
Source ↗

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.3-gke.1767000 is now the default version for cluster creation in the Rapid channel.

Preview
Source ↗

Kubernetes 1.37 is available

Kubernetes 1.37 is now available in the Rapid channel. For more information about the content of Kubernetes 1.37, read the Kubernetes 1.37 Release Notes and Kubernetes 1.37 Release Blog .

Update
Source ↗

Removed in 1.37

- Identity Service for GKE is no longer supported starting in GKE 1.37: Creating new clusters or upgrading existing clusters to GKE version 1.37 or later with Identity Service for GKE enabled is blocked. For external OIDC authentication, please migrate to Workforce Identity Federation .

Deprecation
Source ↗

Other changes in 1.37

- Starting with GKE version 1.37.0-gke.2100000, newly created clusters default to using control plane node creation, which improves cluster security by having the control plane manage node registration instead of kubelet self-registration. Existing clusters are not affected.

Update
Source ↗