Istio in Action: Taking Kubernetes Traffic Control to the Next Level
summary
Istio is used to manage Kubernetes traffic with concrete resources: VirtualService and DestinationRule for routing (by path or user agent) and an IngressGateway at the front. Demonstrations include configuring a 50/50 traffic split and a 21-line YAML example that mirrors 100% of traffic to a new service to reveal bugs before cutover. Observability is provided with Kiali, and progressive canary automation options discussed are Flagger and Argo Rollouts.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:24What is Istio
- 1:05Traffic control with mesh
- 3:14Why Kubernetes needs mesh
- 4:36Istio benefits for devs
- 5:42Deployment vs release
- 7:05Advanced Istio use cases
- 9:39Traffic routing demo
- 13:01Canary deployments setup
- 15:11Traffic mirroring for testing
- 17:31Real-time mirroring simulation
- 19:16Observability and security
- 20:01Istio best practices
- 21:49Scaling Istio
- 23:14Mirroring outside cluster
- 24:01Canary releases explained
- 25:05When to use Istio
- 26:28Automating Canary with observability
- 27:10Canary tools
- 27:53Summary & Q&A
related talks
45mIstio to the Rescue
25mIstio for Node Developers
25mIstio and why do we need it
43mService Mesh for developers
01h 06mIstio on Kubernetes: Smart Canaries, Dark Launches and Chaos
47mIstio on Kubernetes: Chaos, Canaries, Dark Launches
47mIstio, le meilleur ami de votre cluster K8S
24mIstio in Production: Expected Value, Results, and Effort