How We Control Routing between gRPC Services for Testing with Our Custom xDS...
summary
Claims a small custom xDS control plane makes per-PR routing simple: it discovers Cloud Run services every 30 seconds, generates header-based route rules so one request can hit serviceA-PR2 then serviceB-PR1, and pushes them via ADS over a single gRPC stream. Implementation uses go-control-plane for the ADS server and snapshot cache, talks to Google Cloud Run admin API, and requires no sidecars because gRPC clients apply routing client-side; a header-debugger UI proves combinations work end-to-end.
AI-written summary · about
chapters (6)
- 0:00Introduction and agenda
- 1:55What is XDS
- 7:57XDS support in gRPC
- 10:32Custom XDS for testing
- 17:05Building your own XDS control plane
- 21:04Summary and conclusion
related talks
20mProxyless Service Mesh with gRPC
16mxDS in gRPC for Service Mesh
23mA Simplified Service Mesh With gRPC
23mHow Proxyless gRPC Works in a Service Mesh
25mAdapting Our XDS Control Plane for Proxyless gRPC
17mBuilding a gRPC Proxyless World: How Reddit Scaled Resilience...
23mxDS Support in gRPC
34mgRPC Proxyless Service Mesh with Security