Stitching a Service Mesh Across Hundreds of Discrete Networks
Talkat KubeCon + CloudNativeCon North America 2019 · on Wednesday, 2019-11-20· at 10:55· Room 6F - San Diego Convention Center, Upper Level·
summary
Intuit runs about 160 clusters and ~5,400 globally unique namespaces and moves from a shared Istio control plane to per-cluster control planes plus a controller-of-control-planes called Admiral. Admiral watches clusters, creates ServiceEntry and DestinationRule objects, implements a CRD called global traffic policy, and syncs locality-aware routing (demoed 80/20 → 20/80 shift) so services keep a single identity across namespaces, preserve mTLS and end-to-end encryption, avoid a single point of failure, and require no runtime state in the controller.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:11Why Service Mesh?
- 3:37Deployment Complexities
- 5:05Some Intuit Statistics
- 5:34Realistic Topology
- 6:25What Do We Need from Our Mesh?
- 8:43Shared Mesh Control Plane
- 14:38Multiple Control Planes - with Admiral
- 15:53Demo (video)
- 25:41It's open source!
- 26:58Meet Intuit at Booth 547
- 37:19Meet Intuit at Booth S47
related talks
37mReinventing Networking: A Deep Dive into Istio's Multicluster Gateways
28mMulti-Cluster Service Mesh With Istio
34mContainer Networking Untangling Services Meshes and SDNs
43mService Mesh and the future of networking
21mAnother Choice for Istio Multi-Cluster & Multi-Network Deployment Model
37mUsing Istio to Manage the Cross-Regional & Cross-Cluster...
37mStretching the Mesh
47mService mesh options with Istio, Linkerd, and/or Consul