Installation
Choose Your Installation Method
Krkn provides multiple ways to run chaos scenarios. Choose the method that best fits your needs:
| Tool | What is it? | Best For |
|---|---|---|
| krknctl | CLI tool with auto-completion | Complex workflow orchestration, querying and running scenarios, ease of use |
| krkn-hub | Pre-built container images | CI/CD pipelines, automation |
| krkn Dashboard | Web UI for running scenarios | Visual runs, demos, teams that prefer a GUI |
| krkn | Standalone Python program | Full control, development, and customization |
Recommendation
krknctl is the recommended way to run Krkn. It provides the simplest path to chaos testing with powerful capabilities including complex workflow orchestration, built-in scenario discovery, and interactive query support — all without managing configuration files.Recommendation
Look for features marked with [BETA] (e.g., [BETA] Krkn Resilience Score). Beta features provide early access to new capabilities for experimentation and feedback and may not yet meet the stability, performance, or compatibility guarantees of GA features. Please refer to the Beta feature policy for more details.
Recommendation
Look for features marked with [BETA] (e.g., [BETA] Krkn Resilience Score). Beta features provide early access to new capabilities for experimentation and feedback and may not yet meet the stability, performance, or compatibility guarantees of GA features. Please refer to the Beta feature policy for more details.Installation Methods
krknctl (Recommended)
What is it? A dedicated command-line interface (CLI) tool that simplifies running Krkn chaos scenarios while providing powerful orchestration capabilities.
Why use it?
- Complex workflow orchestration — chain and orchestrate multiple chaos scenarios in sophisticated workflows
- Query capabilities — discover, understand, and explore all supported scenarios directly from the CLI
- Ease of use — command auto-completion, built-in input validation, and interactive prompts remove the guesswork
- No configuration files — no need to manage YAML configs or Python environments manually
- Container-native — runs scenarios via container runtime (Podman/Docker) with zero setup overhead
Best for: All users — from first-time chaos engineers to teams building complex resilience testing workflows.
krkn-hub
What is it? A collection of pre-built container images that wrap Krkn scenarios, configured via environment variables.
Why use it?
- No Python environment setup required
- Easy integration with CI/CD systems (Jenkins, GitHub Actions, etc.)
- Consistent, reproducible chaos runs
- Scenarios are isolated in containers
Best for: CI/CD pipelines, automated testing, and users who prefer containers over local Python setups.
Note
krkn-hub runs one scenario type per execution. For running multiple scenarios in a single run, use the standalone krkn installation.Krkn Dashboard
What is it? A web application that lets you run Krkn chaos scenarios from your browser, with real-time logs and Elasticsearch/Grafana integration.
Why use it?
- Scenario selection and parameter forms
- Real-time visibility into running chaos containers
- Visualized run history and metrics
Best for: Demos, shared machines, and teams that prefer a GUI.
krkn (Standalone Python)
What is it? The core Krkn chaos engineering tool, run as a standalone Python program cloned from Git.
Why use it?
- Full control over configuration and execution
- Run multiple different scenario types in a single execution
- Direct access to all features and customization options
- Ideal for development and advanced customization
Best for: Advanced users, developers contributing to Krkn, and scenarios requiring fine-grained control.