A Tale of Two Plugins: Safely Extending the Kubernetes Scheduler with WebAssembly
summary
Kube-scheduler gains a third extension path: WebAssembly modules that avoid rebuilding the scheduler and the network roundtrips of webhooks by compiling plugin logic to language-agnostic plugins that run in-process with a narrow host API. Implementation covers module loading, memory isolation, and sandbox limitations (no direct syscalls, explicit host calls), programming ergonomics for passing pod/node state, and benchmarks showing competitive latency with lower deployment friction than previous approaches.
AI-written summary · about
chapters (6)
- 0:00Kubernetes scheduler extensions
- 4:55Scheduler plugin limitations
- 13:00Multi-language scheduler challenges
- 22:10Performance overhead in extensions
- 29:04Benchmark results and future
- 31:23Conclusion
related talks
31mA Tale of Two Plugins Safely Extending the Kubernetes Scheduler with WebAssembly
23mWhat If... Kubernetes Core Pieces Could Be Extended with Pluggable WebAssembly Modules?
15mWriting Kubectl plugins using WebAssembly
27mGet WITty: Evolving Kubernetes Scheduling With the WebAssembly Component Model
26mWhat If... Kube-Apiserver Could be Extended Via WebAssembly?
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
30mEnhancing the Kubernetes Scheduler for Diverse Workloads in Large Clusters
41mLeveraging WebAssembly to Write Kubernetes Admission Policies