linki/chaoskube
chaoskube periodically kills random pods in your Kubernetes cluster. observed · 2026-08-28
Health v2 · maintenance only
91/100
- Activity 95
- Release rhythm 81
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 44.5
- age_days: 3590
- days_rel: 49
- days_push: 32
- n_releases_24m: 11
Adoption not part of the score
1934 stars · 126 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
chaoskube is a Go CLI tool that periodically terminates random pods in a Kubernetes cluster to test resilience. It supports filtering targets by namespace, labels, annotations, and age, plus quiet periods, and ships with a Helm chart.
Use cases
- kill random pods in kubernetes to test resilience
- chaos engineering for kubernetes clusters
- simulate pod failures to verify self-healing
- test how services recover from pod termination
- run a chaos monkey on my k8s cluster
- validate cluster behavior under arbitrary pod failures
When to choose
- you run workloads on Kubernetes and want simple scheduled pod terminations
- you want a lightweight chaos tool with label/namespace filtering and dry-run mode
- you prefer Helm-based deployment of a chaos monkey
When to avoid
- you need network fault injection, CPU/memory stress, or node-level chaos
- you need a full chaos engineering platform with experiments and metrics
- your workloads are not on Kubernetes
Facets
cli-tool · maturity active
cli deployment testing cloud-computing go cli chaos-engineering chaos-monkey kubernetes pod-failure-testing resilience-testing helm-chart devops containers docker linux
1 source
- readme: https://github.com/linki/chaoskube · fetched 2026-08-28 · 3d6f3e168956
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| linki/chaoskube | main | 91 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem