When the Kubernetes API Went Silent: A Three-Layer Networking Mystery
Google, Friday, October 30th, 2026
Google details a GKE support case in which three separate bugs, ending in a Linux kernel patch, blocked pods from reaching the Kubernetes API.
A January 2026 ticket reported pods intermittently timing out reaching the API server in a large multi-cluster GKE environment in europe-west using Private Service Connect.
The problem turned out to be three distinct bugs in different layers of the stack producing the same symptom.
Around 800 developers were blocked from deploying to production for weeks and clusters in the region stalled.
Engineers from GKE, Private Service Connect, networking, hostnet, kernel and upstream Linux traced the causes, and the final fix was a Linux kernel patch.