Back to feed
GCP·Google Kubernetes Engine·
AI Insights

Issue: In GKE version 1.35 and later, workloads that use Workload Identity to authenticate to Google Cloud APIs might...

In GKE version 1.35 and later, workloads that use Workload Identity to authenticate to Google Cloud APIs might experience transient connectivity timeouts or refused connections to the GKE metadata server immediately following node startup. For recommendations and workarounds, see Timeout errors at Pod startup.

Read original announcement

More from Google Kubernetes Engine

GKE is introducing the following changes to expand the capabilities of maintenance exclusions:Jun 2, 2026GKE Gateway now supports backend authenticated TLS for Gateway-originated connections to Pods or InferencePools for the...May 29, 2026In GKE versions 1.36.0-gke.2459000 and later, you can directly configure Cloud Logging for L4 load balancer backend...May 28, 2026Confidential GKE Nodes now support cluster level enablement of AMD SEV-SNP and Intel TDX on GKE Autopilot.May 28, 2026