Menu

1 / 6

A GKE API Timeout Traced to Three Bugs in Three Layers

DEV Community: kubernetes·Taha Echakiri·13 days ago
#HJNGBlkW
#devtokubernetes#devto#dev#google#three
Reading 0:00
15s threshold

TL;DR

The Kubernetes API server is the component of a cluster that answers every request from kubectl, controllers, operators and the pods themselves.

An API timeout means a client opened a TCP connection toward that server and never completed the handshake, so the failure sits on the path before any Kubernetes logic runs.

Google Cloud published the case study on 30 October 2026: from January 2026, pods in five GKE clusters in europe-west intermittently failed to reach the kube-apiserver, and at its peak the incident blocked around 800 developers from deploying to production.

The escalation timeline ran from intermittent timeouts on day 1 to simultaneous packet captures on day 22, after the custom kopf operator, External Secrets, security agents, conntrack exhaustion and control plane sizing had all been cleared as suspects.

The captures showed a fresh SYN answered by an ACK that belonged to an earlier connection, and Private Service Connect was reusing source ports through NAT.

A challenge ACK is the…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.