Get WITty: Evolving Kubernetes Scheduling With the WebAssembly Component Model
Talkat KubeCon + CloudNativeCon Europe 2025 · on Thursday, 2025-04-03· at 16:00· Level 1 | Hall Entrance S10 | Room D·
summary
Claims that adopting the WebAssembly Component Model makes Kubernetes scheduler plugins language‑agnostic; attempted a component refactor that auto‑generates bindings but hit blockers: no reliable Wazero component runtime for Go, no stable wit generator from protobuf/OpenAPI, and missing Go host/guest support. Evaluated alternatives like Xism PDK (JSON and proto plumbing) and early transpiler Gravity. Benchmarks show proto beats JSON and the component path can be faster for simple string paths, but tooling gaps leave the solution only partially working today.
AI-written summary · about
chapters (11)
- 0:00WebAssembly in Kubernetes
- 1:04Kubernetes scheduler extensions
- 3:10What is WebAssembly
- 5:59WebAssembly SDK limits
- 9:15Component Model solution
- 13:09Component Model challenges
- 15:42Alternative runtimes like XTism
- 18:56JSON vs Protobuf performance
- 21:47Early tools and benchmarks
- 24:59Call to action for contributors
- 26:52Q&A
related talks
31mA Tale of Two Plugins Safely Extending the Kubernetes Scheduler with WebAssembly
32mA Tale of Two Plugins: Safely Extending the Kubernetes Scheduler with WebAssembly
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
33mKubernetes on the edge: running low-latency workloads with WebAssembly
36mBootstrapping Ecosystems: Unveiling the Power of the Component Model
13mKeynote: Are We Componentized Yet?
38mIn the beginning was about metal, now is about Web: exploring WebAssembly in cloud envir.
15mWriting Kubectl plugins using WebAssembly