Istio in Action: Global Request Routing for Seamless Data...
summary
Pigment uses Kubernetes and Istio to route a single hostname to region-specific clusters, generating hundreds of VirtualServices from a central config and adding an Envoy Lua middleware that inspects requests, calls a global backend to resolve a X-pigment-location value, buffers bodies (capped via Content-Length) and sets that header for routing. Authentication currently shares a DB in Europe, the system runs in production nine months with no major outage, and global blackbox agents continuously verify correct EU/US routing.
AI-written summary · about
chapters (12)
- 0:00Istio in production at Pigment
- 1:04Global request routing need
- 4:41Seamless data locality
- 8:38Global auth edge cases
- 9:23Third-party routing without headers
- 11:30Envoy Lua middleware
- 14:25Testing routing middleware
- 15:52Seamless user experience
- 17:35Deployment and developer velocity
- 19:19Lessons learned
- 21:24Future routing plans
- 24:32Q&A
related talks
28mIstio in Action: Taking Kubernetes Traffic Control to the Next Level
37mReinventing Networking: A Deep Dive into Istio's Multicluster Gateways
39mStitching a Service Mesh Across Hundreds of Discrete Networks
33mCheap Routes, Fast Paths & Keeping Track
37mUsing Istio to Manage the Cross-Regional & Cross-Cluster...
23mDemystifying Load Balancing in Istio
28mMulti-Cluster Service Mesh With Istio
19mMulti-region Service Mesh: How Koyeb Built and Operates One Using Kuma and Envoy