The latest articles on DEV Community by Benedikt Hollerauer (@benedikt_hollerauer). https://dev.to/benedikt_hollerauer https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3991039%2F2ad3f266-77e7-4373-bf28-948e43e0adf6.jpg https://dev.to/benedikt_hollerauer en Benedikt Hollerauer Thu, 18 Jun 2026 14:17:08 +0000 https://dev.to/benedikt_hollerauer/reproducing-crashloopbackoff-oomkills-and-phantom-services-on-a-kind-cluster-3a95 https://dev.to/benedikt_hollerauer/reproducing-crashloopbackoff-oomkills-and-phantom-services-on-a-kind-cluster-3a95 <p>Most engineers learn what a CrashLoopBackOff or an OOMKill actually looks like during an incident. That is the worst possible time. So we built a tool to create those conditions on purpose.</p> <p>Rotelle is an open source Kubernetes failure simulator written in Rust. You deploy it into a cluster and trigger named failure modes on demand: crash loops, OOM kills, missing env vars, unreachable services and more. Each one is reproducible so you can drill on it, write the runbook before you need it or use it as a fixture to test tooling against.</p> <p>Reproducible failures are also why we are building this. The Infraware Terminal at <a href="https://infraware.dev/" rel="noopener noreferrer">infraware.dev</a> investigates real incidents with a human approving every step, and you cannot train or evaluate something like that without realistic failures to point it at.</p> <p>If you run Kubernetes, try it on a test cluster and open an issue with anything that breaks or any failure mode you want added. Adding a scenario is one Rust file plus one registration line.</p> <p>Apache 2.0: github.com/infraware-dev/infraware-rotelle</p> kubernetes devops rust opensource