Skip to content
Infraware.dev
Book a live demo
Book a demo

Open source · Apache-2.0

A small, sharp Kubernetes failure simulator: six reproducible failure scenarios you can trigger on cue, in your own cluster. rotelle is the public part of Infraware: no engagement needed, no account, no us. Run it with us, without us, against us.

rotelle on GitHub ↗ Watch it break a cluster live

The scenarios

Six ways to have a bad night, on demand.

Each one is a real failure mode, triggered on cue: the pod actually crashes, the memory actually runs out.

  • crash-loop A pod that exits on every fifth request, so Kubernetes keeps restarting it: the classic page.
  • oom-kill A background memory leak, until the kernel ends the pod.
  • missing-env-var A pod that exits at startup when a required variable is missing: the classic first run.
  • service-unreachable Every request hangs, as if the Service had no matching pods.
  • ingress-conflict Every third request returns 502, as a routing conflict would.
  • slow-response Every request is delayed past the readiness probe, as a degraded pod would be.

Why it exists

One tool, three jobs.

The demo ritual

Every live demo starts with rotelle breaking a real cluster in front of you, not a recording. You pick the failure.

The acceptance test

Pilots are accepted on three rotelle scenarios agreed on the first call, run end to end in your cluster with your security lead watching: alert, investigation, brief, signature, record.

The evaluation harness

Reproducible failures are how we test Virgil against known ground truth, and how you can, before believing a word of this site.

The install, the scenario controls, and the docs live in the repository README, the project stands on its own, with or without Infraware attached.

How to start

You've read the mechanism. Now watch it run.

Book a live demo Security and architecture