Krkn-Chaos

Krkn Documentation

Everything you need to get started with chaos engineering on Kubernetes.

Why Krkn?

Purpose-built for real-world chaos engineering

Why Chaos? Distributed systems often assume the network is reliable, latency is zero, and resources are always available — yet these assumptions lead to outages. Chaos testing helps uncover weaknesses before they impact production.

Why Krkn? We built Krkn to be lightweight (runs outside the cluster), support both cloud and Kubernetes scenarios, perform metric checks during and after chaos, and validate resilience with post-scenario alerts. Learn more about Krkn.