Outage · High impact
How Google Traced GKE API Timeouts to a Linux Kernel TCP Bug
InfoQ · By Renato Losio ·
The Brief
- Three interacting bugs across GKE, Private Service Connect and the Linux kernel caused intermittent Kubernetes API connectivity failures.
- The failures blocked around 800 developers from deploying to production.
- Google has detailed how the bugs were traced, according to InfoQ.
Why it matters
Intermittent loss of Kubernetes API connectivity can stall deployments and CI/CD pipelines, and this case shows how a kernel-level TCP bug can surface as a managed-service problem.
Who’s affected
- GKE users
- Teams using Private Service Connect with GKE
Google recently detailed how three interacting bugs across Google Kubernetes Engine (GKE), Private Service Connect, and the Linux kernel caused intermittent Kubernetes API connectivity failures, blocking around 800 developers from deploying to production. By Renato Losio