---
answer: direct
beat: cloud-infrastructure
source: 1 article · updated: November 15, 2026
---

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 Request

How Databricks eliminated gRPC traffic skew in Kubernetes: custom xDS control plane, client-side P2C routing, zone-affinity, and slow-start ramp-up.

Crashtech Editorial November 15, 2026 Cloud Infrastructure

Read the full analysis

Other questions this article answers

More cloud infrastructure questions

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.