Google Kubernetes Engine

Backup for GKE is now available in the following region: asia-southeast3 (Bangkok, Thailand).

For more information, see Backup for GKE locations.

(2026-R43) Security updates

h4

(2026-R43) Version updates

h4

(2026-R43) Version updates

h4

(2026-R43) Version updates

h4

(2026-R43) Version updates

h4

(2026-R43) Version updates

h4

(2026-R43) Version updates

h4

The microVM sandbox type is now Generally Available (GA) with GKE Sandbox in clusters that run version 1.37.0-gke.4713000 and later.

MicroVM sandboxes provide hardware virtualization and isolation for untrusted workloads, AI agent runtimes, and multi-tenant environments.

Starting with GKE version 1.36, the default engine for kube-dns is CoreDNS.

For Pod IP DNS queries in the <a-b-c-d>.<namespace>.pod.cluster.local format, CoreDNS returns NXDOMAIN if the specified <namespace> does not exist.

GKE support for using the c4-standard-* machine types (up to 192 vCPUs) as Confidential GKE Nodes with Intel TDX is generally available.

For more information, see the following pages:

Starting on July 1, 2026, Identity Service for GKE is deprecated in GKE version 1.36 and earlier.

This feature is also unavailable in organizations that were created on or after July 1, 2025. GKE version 1.37 and later don't support Identity Service for GKE. Before you upgrade clusters to 1.37 and later, disable this feature and migrate to Workforce Identity Federation.

In GKE control plane versions 1.36.3-gke.1244000 and later, Cloud Storage FUSE CSI driver (gcsfusecsi-node) DaemonSet Pods fail to start on specific node pools.

In GKE control plane versions 1.36.3-gke.1244000 and later, Cloud Storage FUSE CSI driver ( gcsfusecsi-node ) DaemonSet Pods fail to start on specific node pools. The Pods crash and log the following error:

(2026-R42) Version updates

h4

(2026-R42) Version updates

h4

(2026-R42) Version updates

h4

(2026-R42) Version updates

h4

You can use Vertical Pod Autoscaler (VPA) with Horizontal Pod Autoscaler (HPA) to automatically optimize container CPU requests for workloads that scale…

You can use Vertical Pod Autoscaler (VPA) with Horizontal Pod Autoscaler (HPA) to automatically optimize container CPU requests for workloads that scale replicas based on CPU utilization.

(2026-R42) Version updates

h4

(2026-R42) Version updates

h4