Abstract

Before your first container hits production on Kubernetes you install a distro, a CNI, an ingress, cert-manager, Prometheus, Loki and ArgoCD. None of them is your app. After ten years of running platform teams on Kubernetes, I built Reliaburger to put the lot into one Rust binary: scheduler, gossip, Raft, eBPF service discovery, ingress, mTLS, registry, metrics, logs, GitOps and chaos testing, driven by TOML. An app with health checks, ingress and autoscaling is twelve lines. This is a hands-on session, so bring a laptop (macOS on Apple silicon or Linux; Windows is not supported yet). In 60 minutes you will:

1. Install Reliaburger with one command and start a node on your laptop. No container runtime, no root, no VMs: the built-in process runtime runs plain binaries.
2. Deploy an app from a twelve-line TOML file and watch it in the terminal dashboard and the web UI.
3. Ship a deliberately sick version and watch the health checker restart it, then roll back with one command.
4. Break it on purpose with the built-in fault injector: kill an instance, freeze another, and let relish wtf explain what just happened.
5. Read the manual and the source code from inside the binary. I will be next to you for the questions the manual does not answer.
6. Provide feedback! It is 0.1.0. It will break. That is the point, and I want to hear about it.

Bio

Miko Pawlikowski has been running platform teams on top of Kubernetes since version 1.0, and has the scars to show for it. He is the author of Chaos Engineering (Manning) and of Reliaburger, a batteries-included container orchestrator written in Rust, along with the book Building Reliaburger that documents how every subsystem was designed and built.