Why does Kubernetes kube-proxy cause traffic skew with gRPC workloads?
gRPC operates on HTTP/2, multiplexing hundreds of RPC calls over long-lived, persistent TCP connections. Kubernetes kube-proxy load balances at Layer 4 (the initial TCP handshake). Once a TCP stream connects to a backend pod, all subsequent RPCs pin to that pod indefinitely, causing massive load imbalance.
Answered in
Client-Side Load Balancing on Kubernetes: Why gRPC Traffic Skews and How Databricks Routes Per RequestHow Databricks eliminated gRPC traffic skew in Kubernetes: custom xDS control plane, client-side P2C routing, zone-affinity, and slow-start ramp-up.
Read the full analysisOther questions this article answers
More cloud infrastructure questions
- How does client-side load balancing solve the gRPC connection pinning problem?
- What is the role of Envoy Discovery Service (EDS) and xDS in Databricks' architecture?
- What is the Power of Two Choices (P2C) algorithm and why is it preferred over round robin?
- Does multi-zone deployment guarantee high availability?
- What is static stability in a multi-zone design?
- Does quorum prevent every database split brain?
- What is the core architectural difference between a hypervisor and a container runtime?
- Why do containers introduce higher security risks in multi-tenant environments?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Cloud Infrastructure beat.