Running K8s in the Browser. Yes, Really. Well, Not Really. Kind of.
summary
Claims a working proof of concept that reimplements Kubernetes-like orchestration inside the browser by running WebAssembly modules with WASI and BEAM/Elixir semantics, using Gleam-compiled code, a backend proxy plus websockets, and tabs as nodes to simulate clustering. It pushes WASM modules into browser runtimes, routes HTTP between modules and external services, and leverages shipping closures over the wire to move live processes. A demo is omitted, but the prototype reportedly runs and can simulate deploys and rollbacks.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 1:24Historical context of computing
- 6:04Problem with complexity in systems
- 7:26WebAssembly and WASI benefits
- 9:35Elixir and BEAM advantages
- 10:42Running in the browser rationale
- 12:28Conclusion and call to action
related talks
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
23mWhat If... Kubernetes Core Pieces Could Be Extended with Pluggable WebAssembly Modules?
28mWasm + Kubernetes: Beyond Containers
33mKubernetes on the edge: running low-latency workloads with WebAssembly
24mWeb Assembly, Docker, Containerd, and Kubernetes
31mBuilding Event-Driven WebAssembly on Kubernetes: Runtime, Observability, and…
28mGo Containerless on Kubernetes with WebAssembly and Rust
15mWriting Kubectl plugins using WebAssembly
