Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Krkn

krkn-chaos.dev

  • Free plan
  • Linux
  • Web
  • API
  • Self-hosted
7.6 Club score Visit krkn-chaos.dev

What Krkn is

Krkn injects deliberate failures into Kubernetes clusters so teams can see how applications and infrastructure respond to disruption. It offers more than 20 scenarios involving pods, containers, nodes, networks, applications, resources, storage, and time. The recommended runner, krknctl, can discover and coordinate scenarios; other deployment options include pre-built containers, a browser dashboard, and a standalone Python program. Krkn can evaluate Prometheus metrics against SLO pass/fail criteria and review results during and after a run. The dashboard supports Elasticsearch and Grafana, and telemetry can be sent to S3 or Elasticsearch. Cerberus monitors Kubernetes and OpenShift health and provides a go/no-go signal, reports, and a metrics API. Krkn-AI uses evolutionary algorithms and objectives supplied by users to identify impactful experiments. Krkn describes saving recovery state and automatic restoration, though some disruptions may leave a system unrecoverable. It is a CNCF Sandbox project for resilience measurement, not security provision. Requirements include Kubernetes or OpenShift 1.21+, cluster-admin kubeconfig access, and Docker 20.10+ or Podman 4.0+.

Who it suits

Krkn suits first-time chaos engineers and teams building resilience-testing workflows. It is aimed at Kubernetes or OpenShift users with cluster-admin access who want to assess application or cluster resilience.

Good to know, and what to watch

  • More than 20 scenarios span several cluster components.
  • Prometheus metrics can be checked against SLO criteria.
  • Offers CLI, containers, dashboard, and standalone Python options.
  • Cerberus provides cluster-health signals and a metrics API.
  • Free plan; no usage limits are stated on opened pages.
  • Some disruptions may leave the target unrecoverable.
  • krkn-hub runs only one scenario type per execution.
  • Standalone installation requires Python 3.9 and manual dependencies.
  • Requires cluster-admin kubeconfig access and a supported container runtime.

Krkn

Free

Free plan

Getting started

  1. Prepare a Kubernetes or OpenShift 1.21+ cluster
  2. Obtain cluster-admin kubeconfig access
  3. Install Docker 20.10+ or Podman 4.0+
  4. Choose krknctl, a pre-built container, the browser dashboard, or standalone Python
  5. Run Krkn outside the cluster against the Kubernetes or OpenShift API
  6. Connect Prometheus, Elasticsearch, Grafana, S3, or Slack as needed

Limits to check

The free Krkn plan lists no pricing or usage limits on the referenced pages. krkn-hub supports one scenario type per execution; multiple types require the standalone installation. Some disruptive scenarios may not be recoverable.

The Club's review

Overview

Krkn is a free, self-hosted tool for deliberately disrupting Kubernetes clusters and assessing how they respond. It suits platform teams and chaos engineers who want to test resilience against defined failure scenarios and service objectives. Its range of execution methods and SLO checks is useful, but some experiments can leave a system unrecoverable.

Key features

Krkn covers more than 20 chaos scenarios across pods, containers, nodes, networks, applications, resources, storage, and time. This gives teams room to probe failures at several layers, rather than limiting testing to a single component. The recommended krknctl CLI discovers, runs, and orchestrates scenarios; pre-built containers, a browser-based dashboard, and a standalone Python program offer other ways to run it.

One important workflow constraint is that krkn-hub runs one scenario type per execution. Teams that need to combine scenario types in a single execution must use the standalone installation, which requires Python 3.9 and manual dependency management. That is a meaningful trade-off: krknctl is the straightforward recommended route, while the standalone route brings more flexibility at the cost of installation work.

Krkn can evaluate Prometheus PromQL queries against SLO pass/fail criteria and review metrics during and after an experiment. The dashboard supports Elasticsearch and Grafana integration, and telemetry can be sent to S3 or Elasticsearch. Cerberus complements the experiments by monitoring Kubernetes and OpenShift health, exposing a go/no-go signal, reports, and a metrics API; it can also report failures in Slack.

Krkn-AI uses evolutionary algorithms with user-defined goals such as SLOs and application health checks to identify impactful experiments. That approach may help teams explore failure scenarios against their own objectives, rather than relying only on manually selected tests. Krkn also saves recovery state before changes and can automatically restore a cluster if an experiment goes wrong, but this is not a guarantee: some disruptive scenarios may leave the target system in a non-recoverable condition.

Krkn identifies as a CNCF Sandbox project. Its security self-assessment says it is not a security provider and does not currently adhere to compliance standards. The project lists software bills of materials for Krkn, krkn-lib, and krknctl, says a security-insights.yml should be added to its roadmap, and accepts vulnerability reports through GitHub's vulnerability reporting tool. Treat it as a resilience-testing tool, not a security or compliance product.

Pricing

Krkn: free. The free plan is the only plan described, with no pricing or usage limits stated. There is no paid tier to compare against; teams should instead weigh the operational cost of running the tool themselves and the effort of managing standalone dependencies when they need combined scenario types.

Krkn is self-hosted and requires Kubernetes or OpenShift 1.21+, cluster-admin kubeconfig access, and Docker 20.10+ or Podman 4.0+. The installation guide recommends running it outside the cluster against the Kubernetes or OpenShift API. Those requirements suit teams already equipped to administer clusters, but make it a less natural fit for organizations seeking a managed, low-privilege service.

Platforms

Krkn is available through API, Linux, web, and self-hosted deployments. Its options include a CLI, containers, a browser dashboard, and the standalone Python program. Kubernetes support, cloud fault injection, network fault injection, and blast-radius controls are supported.

Who it's for

Krkn is a strong fit for Kubernetes and OpenShift operators, platform teams, and chaos engineers who want to run controlled disruptions and judge results against metrics or SLOs. Its documented workflow is approachable for first-time chaos engineers as well as teams building resilience-testing processes, provided they have cluster-admin access and can manage the environment. It is not the right choice for security assurance, compliance evidence, or teams that cannot accept the possibility of a disruption that does not automatically recover.

Pros and cons

Pros

  • Broad scenario coverage: More than 20 scenario types span infrastructure, applications, storage, and time, giving teams several failure dimensions to evaluate.
  • Objective-based evaluation: Prometheus queries can pass or fail runs against SLOs, with metrics available during and after experiments.
  • Multiple deployment paths: CLI, containers, dashboard, and standalone Python accommodate different operating preferences.
  • Health monitoring alongside disruption: Cerberus provides a go/no-go signal, reports, a metrics API, and Slack failure reporting for Kubernetes and OpenShift.

Cons

  • Recovery is not assured: Some scenarios can leave the target system unrecoverable, so careful targeting and operational safeguards matter.
  • Scenario composition has a cost: krkn-hub handles one scenario type per execution; combining types requires the standalone installation and its manual Python dependency management.
  • It is not a security product: Krkn says it does not adhere to compliance standards, so it cannot replace security testing or compliance tooling.
  • Cluster access is substantial: The documented requirements include cluster-admin kubeconfig access, which may be unsuitable where broad credentials are restricted.

Alternatives

Explore the Chaos Engineering Platforms directory to compare options across the category.

  • FaultMesh is worth considering when a team wants a freemium option with a free trial, core fault types, resilience scoring, and a published paid Growth plan.
  • Reliably may suit teams prioritizing an open-source approach that avoids lock-in and broad desktop and web platform support.
  • Chaos Toolkit is another free, open-source CLI option, released under Apache License 2.0.
  • ChaosBlade is a free open-source alternative with a stated range of system platforms, programming-language applications, and 200+ experiment scenarios.
  • Chaos Mesh is a free, cloud-native chaos engineering platform that runs on Kubernetes.
  • Krkn-AI is a free, Linux and self-hosted option under Apache License 2.0.
  • LitmusChaos offers both a free hosted SaaS plan and an open-source version that can be installed on a cluster.
  • Toxiproxy is a free, open-source TCP proxy under the MIT license.

Verdict

Choose Krkn if you run Kubernetes or OpenShift and need a free, self-hosted way to introduce controlled failures and evaluate their effects against Prometheus SLOs. Its broad scenarios, multiple run modes, and health-monitoring support make it a capable resilience-testing toolkit. Look elsewhere if you need security or compliance assurance, a managed service, or confidence that every disruptive run can be rolled back safely.

The verdict

Krkn provides several ways to run controlled Kubernetes disruptions and evaluate their effects against metrics and SLOs. Treat it as resilience-testing software, not a security provider, and account for scenarios that may not be recoverable.

Questions people ask

How much does Krkn cost?

Krkn is listed as free, with a free per-free plan and no usage limits stated on the referenced pages.

What does Krkn require?

The getting-started requirements are Kubernetes or OpenShift 1.21+, cluster-admin kubeconfig access, and Docker 20.10+ or Podman 4.0+.

How can I run it?

Options include krknctl, pre-built container images, a browser-based dashboard, and a standalone Python program.

Can Krkn validate service objectives?

Yes. It can evaluate Prometheus PromQL queries and automatically pass or fail a chaos run against SLO criteria.

Is Krkn a security product?

No. Krkn describes itself as a resilience-measurement project rather than a security provider, and it does not currently adhere to compliance standards.

What the maker publishes

CLI
krknctl discovers, runs, and orchestrates chaos scenarios, and is the recommended way to run Krkn. source
Deployment options
Krkn offers a CLI, pre-built container images, a browser-based dashboard, and a standalone Python program. source
Install options
Installation options include a CLI, pre-built containers, a browser-based dashboard, and a standalone Python program. source
Integrations
The dashboard supports Elasticsearch and Grafana integration, and Krkn can send telemetry to S3 or Elasticsearch. source
Integrations
The documentation describes integrations with Prometheus, Elasticsearch, Grafana, Slack, S3, and CI/CD systems such as Jenkins and GitHub Actions. source
Krkn AI
Krkn-AI uses evolutionary algorithms and user-defined objectives such as SLOs and application health checks to identify impactful chaos experiments. source
Metrics and SLOs
Krkn can validate SLO pass/fail criteria with Prometheus PromQL queries and review metrics during and after chaos scenarios. source
Monitoring
Cerberus monitors Kubernetes and OpenShift cluster health and exposes a go/no-go signal, reports, and a metrics API. source
Monitoring
Cerberus monitors Kubernetes and OpenShift health and exposes a go/no-go signal, reports, and a metrics API. source
Notable limits
krkn-hub runs one scenario type per execution; running multiple scenario types in one execution requires the standalone Krkn installation. source
Operating guidance
The installation guide recommends running Krkn outside the cluster against the Kubernetes or OpenShift API. source
Project status
Krkn identifies itself as a Cloud Native Computing Foundation Sandbox project. source
Project status
The site identifies Krkn as a Cloud Native Computing Foundation Sandbox project. source
Purpose
Krkn injects deliberate failures into Kubernetes clusters to test their resilience. source
Purpose
Krkn injects deliberate failures into Kubernetes clusters to test their resilience. source
Requirements
The getting-started guide lists Kubernetes or OpenShift 1.21+, cluster-admin kubeconfig access, and Docker 20.10+ or Podman 4.0+ as requirements. source
Rollback
The site says Krkn saves recovery state before changes and can automatically restore the cluster if chaos goes wrong. source
Rollback
Krkn’s rollback system persists changes to the filesystem before a scenario so it can restore targeted Kubernetes objects or subsystems. source
Rollback limitation
The security self-assessment says some disruptive scenarios may leave the target system in a non-recoverable condition. source
Runtime requirement
The standalone Python installation requires a Python 3.9 environment and manual dependency management. source
Scenario coverage
The site lists 20+ chaos scenarios spanning pods, nodes, networks, applications, storage, and time. source
Scenarios
The site lists more than 20 chaos scenarios covering pods, containers, nodes, networks, applications, resources, storage, and time. source
Security documentation
The security self-assessment lists a software bill of materials for Krkn, krkn-lib, and krknctl, and says a security-insights.yml should be added to the roadmap. source
Security posture
Krkn says it is not a security provider and does not currently adhere to compliance standards. source

Checked against the maker's pages on 7 Oct 2026.