Exotic Runtime Targets: Ruby and Wasm on Kubernetes and GitOps Delivery Pipelines
summary
Deploys WebAssembly modules with Ruby on Kubernetes using GitOps: builds a multi‑arch EKS cluster bootstrapped with Flux, packages Spin runtime in a container and deploys via Helm, and runs Wasm modules with Wasmer/Wasmtime plus WASI/WAGI. Embedding a full Ruby interpreter in Wasm is ~30MB and breaks C extensions, so a Rust Wasm parser is used; a Ruby Kubernetes operator (cubeclient) calls the Wasm function to scrape ghcr pages, returns the download count string, stores it in CRD status, and the working operator is implemented in ~3 hours with plans for Prometheus export.
AI-written summary · about
chapters (7)
- 0:00Start
- 8:31Runtime Format
- 10:55Features: Format
- 12:21Ruby and pointers
- 13:37What is Spin?
- 22:58Based on (dependency)
- 24:26How is the code?
related talks
15mExotic Runtime Targets: Ruby and Wasm on Kubernetes and GitOps Delivery Pipelines
30mWASM in the Wild West: A Practical Application Tale
33mKubernetes on the edge: running low-latency workloads with WebAssembly
31mWith WasmEdge to New Shores
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
25mManaging WebAssembly apps with Kubernetes
39mWebAssembly on Kubernetes
39mRunning WebAssembly on Kubernetes