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 | Complexity |
|---|---|---|---|
| krknctl | CLI tool with auto-completion | Quick testing, ease of use | ⭐ Easy |
| krkn-hub | Pre-built container images | CI/CD pipelines, automation | ⭐⭐ Moderate |
| krkn | Standalone Python program | Full control, multiple scenarios | ⭐⭐⭐ Advanced |
Recommendation
New to Krkn? Start with krknctl - it’s the easiest way to get started with chaos testing!Installation Methods
krknctl (Recommended)
What is it? A dedicated command-line interface (CLI) tool that simplifies running Krkn chaos scenarios.
Why use it?
- Command auto-completion for faster workflows
- Built-in input validation to catch errors early
- No need to manage configuration files manually
- Runs scenarios via container runtime (Podman/Docker)
Best for: Users who want a streamlined, user-friendly experience without managing configs.
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 (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.
