Distributed Flexibility: Nomad and Vault in a Post-Kubernetes World
summary
Cosmonic runs a production PaaS built on WebAssembly modules scheduled by Nomad and uses a custom firecracker task driver to provide multi-tenant isolation. The driver supports the Jailer, boots VMs from ZFS snapshots for fast startup, mounts templates via the mmds metadata service, and implements memory ballooning to avoid OOM kills. Nomad integration is four lines of config; a Vault-backed key value provider replaces Redis without code changes. Most work is open source and in active improvement.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 1:32WebAssembly fundamentals
- 5:01WasmCloud and architecture
- 10:24Why we chose Nomad
- 15:59Firecracker task driver
- 22:46Lessons learned
- 28:38Vault integration
- 32:26Future and conclusion
related talks
40mNomad: Scheduling Applications at Scale
36mWho Knew Dogfood Could Taste This Good? A WebAssembly In Production Story
29mOrchestrating Wasm: Reconciliation Loops Aren't Owned by Kubernetes
39mMind the Gap Between the Future and the Present
32mFuzzing Nomad with Nomad
33mDistributed Scheduler Hell
26mDon't be Afraid of CSI: How Critical TechWorks Orchestrates Stateful Apps with Nomad & a CSI Process
34mDistributed applications and Kubernetes