IstioD - from microservices to monolithic
summary
Claim: the Istio control plane consolidates seven microservices into one istiod monolith, removing Mixer, Citadel, injector, node agent and others and distributing work into Envoy sidecars. Concrete results: CRDs drop 23→12 CRDs, single control-plane binary, faster startup and better performance, simpler install and day‑2 ops. Tools and proof: envoy sidecars, istioctl analyze, a Bookinfo demo and measured improvements. Roadmap items include canary control‑plane upgrades and external control plane hosting; the consolidation is implemented and shows the reported benefits.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:05How a service mesh works
- 4:30What is Istio
- 6:21microservices
- 8:54advantages of microservices
- 11:38monolithic approach
- 18:50complexity reduction
- 21:17community updates
- 27:04InPlace Canary
- 31:20Live Demo
- 43:09Questions
related talks
20mHow to Optimise your Mesh with Istio Sidecar
19mPlanning the Zero-Downtime Lifecycle of Your Service Mesh
24mNavigating the Maze of Multi-Cluster Istio: Lessons Learned at Scale
10mLightning Talk: Sail-Operator: Making Seamless Istio Upgrad...
44mA Guided Tour of ISTIO Ambient Mesh
28mChallenges and Best Practices While Upgrading Istio in a Production...
27mIstio Ambient Mesh in Production: Our Journey from Sidecar to Sidecar-less
24mRunning Istio in Production as a Small Team of Newbies