Istio, we have a problem! Understanding and fixing bugs with a service-mesh
summary
Istio injects Envoy sidecars to capture all HTTP traffic and adds Service Graph visibility, Prometheus metrics and Grafana dashboards, and Zipkin traces without code changes; a real bug shows repeated /0 calls and 22 retries; fixes are deployed as a labeled v2, tested with header-based canary and traffic mirroring (real user requests copied to v2), then shifted via weighted blue‑green routing; the demo builds, monitors, and validates the fix end-to-end on a local Kubernetes cluster.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:34What Is My Web Application
- 13:28Distributed Traces
- 19:11Canary Deployment
- 24:14Traffic Mirroring
- 29:38A Bluegreen Deployment
related talks
47mIstio, We Have a Problem! Understanding and Fixing Service Mesh Bugs
19mIstio, we have a problem! Understanding and fixing bugs with a service-mesh
35mIstio, We Have a Problem! Understanding and Fixing Bugs with a Service Mesh
45mIstio to the Rescue
25mIstio for Node Developers
33mObserving and Troubleshooting your Microservices with Istio
28mService Mesh: Demystifying Istio
01h 06mIstio on Kubernetes: Smart Canaries, Dark Launches and Chaos
