Service Mesh - Beyond the Hype
summary
Consul Connect is presented as a production service mesh with a long history (launched 2014, known deployments with 30k+ agents) that provides automatic mTLS and identity-based intentions via a control plane + sidecar proxies data plane. The demo builds a Kubernetes three‑tier app, uses Consul service resolver and splitter to perform a 50/50 traffic split between hello V1 and V2 then shifts 100% to V2, and enforces a deny intention (403). Cross‑datacenter mesh gateway failover demo struggles on stage but a successful run is linked on Twitter.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:08Where I live
- 3:27Origin of the term
- 4:16The Street
- 5:56Challenges
- 11:04Implicit dependency
- 11:41How the mesh works
- 13:00Protocol awareness
- 14:14Console
- 15:19Kubernetes
- 15:57Rules
- 16:35Connect Features
- 17:48Service Web
- 19:03Raw Output
- 19:31Service Hello
- 21:01Debug
- 21:31Testing
- 22:05Service Splitter
- 22:51Service Resolver
- 24:25Moving Traffic
- 25:28Error 403
- 26:10Mesh Demo
- 29:04Groupctl
- 31:19Twitter
related talks
40mIntroducing A New Architecture for Simplified Service Mesh Deployments
27mConsul Mesh Federation Deep Dive
46mProgressive Deployments with Consul Service Mesh
41mService Mesh beyond single clusters
45mService Mesh Big Survey
31mClean-up Your Service Mess with Service Mesh
50mDistributed systems patterns with Spring Cloud, Service Meshes and eBPF
37mThe Service Mesh Wars: A New Hope for Kubernetes