Service Mesh for developers
summary
Istio runs as a control plane (istiod) that programs Envoy sidecars per pod to do routing, observability (Kiali) and auth; the demo shows declarative traffic control—via virtual services—doing a 95/5 traffic split and later a 50/50 shift to perform canary rollouts without redeploys. Istio issues and auto-rotates certs (mTLS automatic rotation), supports header routing and chaos-style fault injection (example: 5s delay injected at 0.1% and 400 responses), and works on Kubernetes via namespace sidecar injection; trade-offs shown: extra CPU/memory and two extra proxy hops.
AI-written summary · about
chapters (10)
- 0:00Introduction to service mesh
- 1:43Evolution of architectures
- 3:50Kubernetes architecture
- 7:41The problem with microservices
- 12:58Understanding service meshes
- 16:41Istio components and proxies
- 19:32Demonstrating traffic control
- 26:48Advanced mesh features
- 30:41Observability and security
- 34:47Trade-offs and Q&A
related talks
28mService Mesh: Demystifying Istio
25mIstio for Node Developers
01h 01mMeshing Around with Istio
50mService Mesh and Sidecars with Istio and Envoy
58mService Mesh and Sidecars with Istio and Envoy
34mService Mesh for Developers
01h 01mIstio Service Mesh & pragmatic microservices architecture
01h 06mIstio on Kubernetes: Smart Canaries, Dark Launches and Chaos
