Introduction to Istio Configuration - Joy Zhang, Google
summary
Istio claims operators can turn any workload into a managed service with intent-driven configs (no redeploys) by using Envoy sidecars for traffic interception and control-plane components Pilot, Mixer and Citadel. Configuration lives in Kubernetes CRDs, Pilot converts intents to xDS, Mixer uses adapter-backed policy (Stackdriver available). A new layer introduces mesh / service / service-consumer APIs and a Galley as configuration pipeline that validates, transforms and will distribute optimized, scoped configs per-cluster; Galley currently acts as a sink-through prototype while composable config packages and multi-cluster automation are in progress.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 4:08Istio Components
- 5:31Mixer
- 6:07Configuration Flow
- 9:15Power Audit
- 10:06Website
- 10:25Problems
- 12:02What we can do
- 12:59Whats next
- 13:54Architecture
- 15:27API Layers
- 19:27Composable Model
- 21:44Configuration Processing Engine
- 23:11Galle
- 23:59Multi Cluster Environment
- 24:54Implementation
- 26:36Working Group
related talks
01h 01mMeshing Around with Istio
43mService Mesh for developers
47mIstio on Kubernetes: Chaos, Canaries, Dark Launches
45mIstio to the Rescue
25mIstio and why do we need it
21mIstio as a monolith
47mIstio, le meilleur ami de votre cluster K8S
01h 06mIstio on Kubernetes: Smart Canaries, Dark Launches and Chaos