Istio and why do we need it
summary
Explains how Istio sits on Kubernetes to add a declarative networking API and per-workload sidecar proxies that enforce routing, TLS and policy. Shows concrete configs: Gateways, VirtualServices, DestinationRules used to create header-based canary splits, subset-based load balancing, and gateway-bound ingress; virtual services merge across namespaces and sidecars push updated policies. Demonstrates a request path through gateway → virtual service → subset → service, and notes observability, fail-injection and recovery actually work in this setup.
AI-written summary · about
chapters (5)
related talks
28mIstio in Action: Taking Kubernetes Traffic Control to the Next Level
45mIstio to the Rescue
25mIstio for Node Developers
43mService Mesh for developers
28mA Not-so-Scary Way to Add Istio to Your Platform, Step by Step
47mIstio, le meilleur ami de votre cluster K8S
01h 01mMeshing Around with Istio
01h 06mIstio on Kubernetes: Smart Canaries, Dark Launches and Chaos
