Krkn (pronounced “kraken”) is a chaos engineering tool for Kubernetes and OpenShift. It was originally built by Red Hat’s performance and scale team to find resilience bugs in OpenShift itself, and is the chaos framework they use in their own release pipeline.
It ships a library of chaos scenarios driven by YAML — pod disruption, node shutdown, network chaos via tc/iptables, CPU/memory/IO hogs, time skew, application outages, etcd/API-server outages, zone failures, and PVC/ceph disruption. Each scenario runs for a configured duration while Krkn snapshots Prometheus metrics and measures cluster/application health against user-defined Cerberus signals. If the cluster or a monitored app breaches its SLOs during the run, the scenario fails, which makes the tool useful inside CI rather than just for manual game days. Krkn-hub packages the scenarios as container images so you can run them from a pipeline with only environment variables.
In the chaos tooling landscape it sits alongside Chaos Mesh, LitmusChaos, and Gremlin. Its niche is Kubernetes control-plane and infrastructure-level fault injection with tight Prometheus/SLO integration, rather than application-level HTTP/gRPC fault injection.