Kubernetes on Edge: Bringing Your Code to Constraine...
summary
Demonstrations show two concrete paths: a Docker image built with buildx runs on a Raspberry Pi, a privileged container exposing /dev/gpio0 privileged container reads a DHT sensor and posts JSON to a cloud endpoint; and a Rust-compiled WebAssembly module packaged as an OCI image runs on Kubernetes via crustlet + Wasmtime, producing periodic CloudEvents. The WASM image is tiny — about 3 MB wasm image — and the demos successfully schedule and execute both container and WASM workloads on edge nodes.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:38The Agenda
- 1:06What Is Web Assembly
- 2:07How Does Webassembly Compare to Docker
- 22:42Kilton Hopkins
- 25:37Types of Edge Deployments
- 26:43Processing Data from Edge Devices
- 28:17What Does wazi Look like Today
- 29:21Edge Specific Challenges
- 29:31Architecture of Microservices
- 30:18Dynamic Access
- 31:12What Is It Going To Be like To Integrate Webassembly with Existing Edge Technologies
- 32:41Resources
- 36:17What Changes with Webassembly
related talks
31mWith WasmEdge to New Shores
33mKubernetes on the edge: running low-latency workloads with WebAssembly
31mJamming with CRI-O & crun: Facilitating the Convergence of AI, WASM, and Kubernetes
28mGo Containerless on Kubernetes with WebAssembly and Rust
10mKubernetes: Enabling Edge Workloads
34mManaging WebAssembly Applications Using Docker and k8s Tooling
25mManaging WebAssembly apps with Kubernetes
39mRunning WebAssembly on Kubernetes