Kubernetes on the edge: running low-latency workloads with WebAssembly
summary
Demo builds a Go web server compiled with TinyGo and fetched/pushed with WKG to a local OCI registry, then runs it on a kind cluster wired by SpinCube (spin operator + runtime-class-manager) to execute the component with Wasmtime via containerd shim. A regular container image is ~2.2 MB vs the Wasm artifact at 338 KB; scaling to 20 replicas across 10 iterations gives mean startup ~2.5s for containers and ~2.1s for Wasm (~400 ms faster). Uses WASI 0.3.1; both endpoints respond correctly.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:08Kubernetes on the edge explained
- 3:35What is WebAssembly
- 7:31Running Wasm on Kubernetes
- 9:17Demo setup overview
- 12:28Wasm app implementation
- 16:47Deploying Wasm workloads
- 19:13Verifying running services
- 19:34Artifact size comparison
- 21:22Startup time measurement
- 25:56Wasm vs containers future
- 28:22Summary and resources
- 29:04Q&A session
related talks
31mBuilding Event-Driven WebAssembly on Kubernetes: Runtime, Observability, and…
39mRunning WebAssembly on Kubernetes
28mGo Containerless on Kubernetes with WebAssembly and Rust
33mLeveling Up Wasm Support in Kubernetes
44mA Greener, Cost-Effective Cloud with Serverless WebAssembly
29mSupercharge Your Kubernetes AI Deployments with Wasm
25mManaging WebAssembly apps with Kubernetes
28mWasm + Kubernetes: Beyond Containers