Istio, We Have a Problem! Understanding and Fixing Bugs with a Service-Mesh
summary
Deploys a multi‑service quiz app on a local Docker for Mac Kubernetes cluster, injects Envoy sidecars, and uses Service Graph, Prometheus + Grafana dashboards and Jaeger traces to find a bug (traces show 10 vs 48 spans and reveal repeated identical /random calls). Fix compiles, then rollout uses Istio VirtualService for header‑based canary, traffic mirroring (doubles downstream load, beware side effects) and weighted blue/green traffic shifts to validate before cutover.
AI-written summary · about
chapters (13)
- 0:00Intro
- 12:29Deploying the fix in a controlled manner
- 13:44Configuring Istio
- 15:55Traffic Mirroring
- 17:08Reconfiguring Digital Service
- 18:54Bluegreen Deployment
- 21:53Visibility
- 24:12Memory
- 24:34Thank you
- 24:54Performance overhead
- 26:00How to fix overhead
- 32:05Should we try it
- 32:35Questions
related talks
35mIstio, We Have a Problem! Understanding and Fixing Bugs with a Service Mesh
56mHow to get a grip on your microservices system using a service-mesh
52mEmpower Your Microservices with Istio Service Mesh
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
55mEmpower Your Microservices with Istio Service Mesh
01h 01mIstio Service Mesh & pragmatic microservices architecture
34mIstio 101: Open Source Service Mesh for Microservices
46mService Mush: Debugging Istio Deployments