Service Mesh Extensibility Explained
summary
Shows concrete extensions for Istio: replacing the iptables init container with a CNI plugin to avoid NET_ADMIN, swapping the Envoy image or patching its config, and injecting bytecode via Envoy WASM pushed to a registry. Demo builds a WASM module, pushes it to WebAssembly Hub, applies it to reviews v1 and adds a “hello world” response header. Also builds a virtual-destination CRD plus traffic-policy to fail over across two clusters; traffic shifts to review v3 when cluster1 instances are killed.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:09The Data Plane Extensibility
- 5:24Unique Container
- 7:08Change the Proxy Config
- 10:20Ingress Gateway
- 11:47Control Plane Extension Ports
- 13:32Demo
- 16:23Onboard Filter
- 18:46Using Web Assembly
- 22:45The Virtual Destination Crd
- 23:05Traffic Policy
- 24:25Configuration
- 24:57Debug Configuration
related talks
31mExtending Sidecarless Applications with Wasm in Istio Ambient Mesh
30mMultiplayer Istio: Collaborative WASM Plugins with Intel and Layer5
30mTaking Service Mesh a Step Further with WebAssembly
23mWhat If... Kubernetes Core Pieces Could Be Extended with Pluggable WebAssembly Modules?
36mSi Vis Pacem, Adde Rete -- If You Want Peace, Add a Mesh!
11m⚡ Lightning Talk: Meshin’ With WebAssembly: Taking Linkerd Beyond Containers
32mExtending Envoy Using WebAssembly (Wasm)
33mDeveloping & Debugging WebAssembly Filters for Envoy