Continuous Delivery & Resource Health for SpinKube/WASM Applications With A...
summary
ArgoCD manages SpinKube (Spin) WebAssembly apps by bootstrapping the cluster (operator, runtimeClass using containerd) then syncing a spin-cube CRD generated by spin scaffold; images are pushed to OCI-compatible registries (GHCR, Harbor) after spin build. Argo requires Lua health checks added to its configmap or core so CRD status maps to healthy/progressing/degraded; a community PR exists to upstream this. The presenters demo a live PR merge but the live demo fails to load in time; the approach otherwise works end-to-end.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:03Continuous delivery principles
- 2:07What is WebAssembly
- 5:17Introducing Spin and WASM apps
- 8:06SpinKube platform
- 10:56Deploying WASM apps with Argo CD
- 13:50Resource health checks
- 15:59Custom health checks for SpinKube CRDs
- 19:10Benefits of Argo CD health checks
- 20:35Best practices and wrap-up
related talks
39mRunning WebAssembly on Kubernetes
31mBuilding Event-Driven WebAssembly on Kubernetes: Runtime, Observability, and…
33mKubernetes on the edge: running low-latency workloads with WebAssembly
23mGitOps for the Edge: Delivering WebAssembly with Argo CD
52mCross-cloud App Splitting With WebAssembly Components
01h 03mTruly Portable Code: Serverless WebAssembly in a Distributed World
24mFrom Sensors to Servers: Efficient Edge Computing with Akri and WebAssembly
30mCloud-Native vNext with WebAssembly and Spin