Building a gRPC Proxyless World: How Reddit Scaled Resilience...
summary
Reddit implements a proxyless gRPC stack using an XDS control plane that reconcilies Gateway API, EndpointSlices and Services into per-resource XDS snapshots, enabling client-local load balancing across multi-cluster, multi-region k8s. Key pieces are config map injector that writes bootstrap.json per namespace so XDS endpoints change without code edits and a validating webhook that rejects routes that would crash the control plane. Rollout uses a sampling client with per-RPC vs per-connection sampling, state-of-the-world XDS with 5–10s batching, and CSDS + gRPC-go metrics for observability.
AI-written summary · about
chapters (10)
- 0:00Reddit infrastructure intro
- 1:03Kubernetes service discovery
- 2:07Multi-cluster discovery challenges
- 3:33Proxy vs proxyless matrix
- 5:41Proxyless gRPC control plane
- 7:28Config map injector
- 8:30Validating webhook protection
- 9:33Proxyless gRPC observability
- 10:57Client sampling migration
- 13:07Q&A
related talks
20mProxyless Service Mesh with gRPC
23mA Simplified Service Mesh With gRPC
25mAdapting Our XDS Control Plane for Proxyless gRPC
23mHow Proxyless gRPC Works in a Service Mesh
35mBack To the Basics - Service Mesh Fundamentals
33mgRPC For Microservices: Service-mesh and Observability
22mHow We Control Routing between gRPC Services for Testing with Our Custom xDS...
21mDial Once, Scale Infinitely: Production-Ready gRPC Without the Mess