Kube32 gives tiny ESP32 boards pods, kubectl and CrashLoopBackOff
WebAssembly workloads let microcontrollers mimic a cluster, with a desktop simulator to try first.
An ESP32-S3 can now participate in the familiar ritual of watching a pod fail and restart. Kube32 brings kubectl and k9s to a cluster of microcontrollers, including CrashLoopBackOff.
The project README describes one firmware image for all boards. A board with PSRAM runs the control plane and a local kubelet; workers can run without PSRAM. The listed control-plane requirement includes 8 MB flash and at least 2 MB PSRAM.
Pods execute through the wasm3 interpreter. That swaps Linux containers for WebAssembly modules while keeping a recognizable management interface. Hardware access gets a per-pod capability boundary covering things such as GPIO, I2C and UART.
There is a desktop route before reaching for the soldering gear. The same sources build kube32-sim on macOS and Linux, and the quick start launches a two-node simulated cluster with an echo workload.
The project’s own benchmark says equivalent compute runs “32 to 95 times slower” in the interpreter than as native C. The recommended workload is control logic, I/O and glue. Heavy compute belongs in native host functions. Those are maker measurements, not results reproduced for this article.
The next interesting demonstration is a useful device whose control logic survives a node loss. That would make the miniature cluster worth keeping after the first CrashLoopBackOff joke.