Mind the Gap Between the Future and the Present
summary
Two concrete Kubernetes integration patterns emerge: Wrapped uses runtimeClass/containerd shims (Spin, runi) so a Wasm module appears as a pod and logs show it running like a normal container; that approach works but forces node runtime changes and inherits Kubernetes limits. Alongside uses a wasmCloud operator, wash CLI, CRDs and a wasm manifest to deploy hosts and components across GCP, AKS and a laptop, bridging clusters to a Redis backend; the live demo shows cross-cluster requests succeeding and components (single-digit MB Wasm binaries) as the unit of distribution.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:43Speaker context
- 2:46WebAssembly basics
- 4:32Bare metal to WASM
- 6:15WebAssembly vs containers: key differences
- 8:40Component model explained
- 15:42Extending Kubernetes for WebAssembly
- 19:59Wrapped vs alongside
- 22:23Live demo: wrapped WebAssembly in Kubernetes
- 24:30Demo: alongside WASM with wasmCloud
- 31:56Wrapped integration pros/cons
- 33:42Alongside integration pros/cons
- 36:08Present versus future
- 36:50Q&A
related talks
28mWasm + Kubernetes: Beyond Containers
24mWeb Assembly, Docker, Containerd, and Kubernetes
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
33mLeveling Up Wasm Support in Kubernetes
33mKubernetes on the edge: running low-latency workloads with WebAssembly
23mWhat If... Kubernetes Core Pieces Could Be Extended with Pluggable WebAssembly Modules?
28mGo Containerless on Kubernetes with WebAssembly and Rust