repowiserepowise

Library

krkn-chaos / krkn

Chaos and resiliency testing tool for Kubernetes with a focus on improving performance under failure conditions. A CNCF sandbox project.

★ 522stars on GitHubPythonApache-2.0

Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.

Setup instructions on GitHub

Releases on GitHub (latest v5.2.15, Nov 11, 2026)

Repowise maps public repos from their source. Not affiliated with krkn-chaos. What is Repowise?

github.com/krkn-chaos/krknIndexed at 2fbf4b5

What is krkn?

krkn is a chaos and resiliency testing tool for Kubernetes. It injects deliberate failures into Kubernetes clusters to check whether they stay resilient under turbulent conditions. The project is written mainly in Python. Its code health is 6.8 out of 10 (Fair), ranked #159 of 4,000+ indexed repos. The last commit to krkn was on Sep 17, 2026, and 76 people have contributed.

As of commit 2fbf4b5, indexed Sep 20, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentskrkn.md

Repo facts: type, license, health, rank, contributors
krkn facts
TypeLibrary
LicenseApache-2.0
Code health6.8 / 10 (Fair)
Health rank#159 of 4,000+ indexed repos
Last commitSep 17, 2026
Contributors76
Bus factor2
Size426 files, 48,601 lines

Explore krkn

Ask about this code in your agent

This connects Repowise to krkn's code. It does not install krkn.

Useful if you want to change or fork krkn: your agent can ask how it is put together and get answers that cite its files.

Ask about krkn

Answers come from krkn's README and source, with the files they cite. Two free answers a day without an account.

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of krkn-chaos/krkn from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

krkn-chaos/krkn FAQ

What is krkn?

krkn is a chaos and resiliency testing tool for Kubernetes clusters. It injects deliberate failures into a cluster to check whether the cluster stays resilient under turbulent conditions.

How does krkn work?

krkn works by injecting deliberate failures into Kubernetes clusters. The core logic lives in the krkn directory, and resiliency checks are handled in krkn/resiliency/resiliency.py.

What language is krkn written in?

krkn is written mainly in Python, with 231 Python files and 30 shell files in the project index. Its primary language is Python.

How is the krkn code organized?

krkn is organized into 7 modules. The largest are krkn with 134 files, tests with 72 files and CI with 48 files.

Who is krkn for?

krkn is for testing Kubernetes clusters for resiliency. It is meant for checking how a cluster behaves when failures are injected into it.

What license does krkn use?

krkn uses the Apache-2.0 license. The project is distributed under the Apache-2.0 license identifier.

Code health

6.8out of 10Fair

Hotspots average 3.5, the place fixes pay off most.

On the leaderboards:#44 of 71 Python repos

Key features of krkn

  • Injects deliberate failures into Kubernetes clusters to check whether they remain resilient under turbulent conditions.
  • Offers an interactive Killercoda tutorial that deploys a target app on a 2-node Kubernetes cluster and injects pod and node chaos with krknctl.
  • Links to blog posts, podcasts and community interviews about the project on its website.
  • Holds monthly office hours for community questions, with agenda items added in advance.

How krkn-chaos/krkn works

The entry point is server.py, the only entry point listed for the project. Most of the code sits in the krkn directory, which has 134 files and holds the core logic. krkn/resiliency/resiliency.py is one of the files flagged as a hotspot, and it belongs to the resiliency part of the code. krkn/summarized_reports/transform.py sits under the summarized reports package and is also flagged as a hotspot. The tests directory, with 72 files, includes tests such as tests/test_summarized_reports.py, and the CI directory, with 48 files, holds the CI test tooling under CI/tests_v2.

The codebase has 426 files and 3,315 symbols in 7 modules, led by Python, Shell and Makefile. Code health is 6.8 out of 10, rated fair.