chaos-mesh/chaos-mesh
A Chaos Engineering Platform for Kubernetes. observed · 2026-08-28
Health v2 · maintenance only
95/100
- Activity 99
- Release rhythm 86
- 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: 72
- age_days: 2556
- days_rel: 15
- days_push: 7
- n_releases_24m: 12
Adoption not part of the score
7858 stars · 1029 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Chaos Mesh is an open-source, cloud-native chaos engineering platform for Kubernetes that injects controlled faults (pod, network, DNS, HTTP, I/O, time, stress, kernel, JVM, and cloud provider faults) via Kubernetes custom resources. It includes a web dashboard, a workflow engine for serial/parallel experiment orchestration, and multi-cluster experiment dispatch.
Use cases
- inject pod failures and network latency into kubernetes workloads to test resilience
- run chaos experiments in production to find reliability weaknesses
- orchestrate serial and parallel fault injection workflows with health checks
- simulate disk io, dns, and http faults in a kubernetes cluster
- validate microservices fault tolerance before major releases
- manage chaos experiments across multiple kubernetes clusters from one dashboard
When to choose
- you run workloads on Kubernetes and want Kubernetes-native chaos experiments via CRDs and RBAC
- you need broad fault coverage including network, io, kernel, JVM, and cloud provider faults
- you want a web dashboard and workflow engine for scheduling and orchestrating experiments
- you need a mature CNCF incubating project with production usage at large companies
When to avoid
- your systems run outside Kubernetes or on bare physical machines only
- you need simple load or performance testing rather than fault injection
- you cannot grant cluster-level permissions or run privileged daemons in your cluster
Facets
application · maturity active
testing monitoring workflow-automation container-orchestration deployment cloud-computing testing microservices cloud self-hosted go chaos-engineering fault-injection kubernetes-operator cncf site-reliability-engineering resilience-testing web-dashboard devops containers kubernetes docker
10 sources
- readme: https://github.com/chaos-mesh/chaos-mesh · fetched 2026-08-28 · 737cba423cee
- homepage: https://chaos-mesh.org · fetched 2026-08-29 · ff28bca0574f
- site_page: https://chaos-mesh.org/docs · fetched 2026-08-29 · 902bbf43813c
- site_page: https://chaos-mesh.org/docs/next · fetched 2026-08-29 · e2e77832baec
- site_page: https://chaos-mesh.org/docs/2.7.3 · fetched 2026-08-29 · 316b916daeba
- site_page: https://chaos-mesh.org/docs/2.6.7 · fetched 2026-08-29 · 80c125fdf5dc
- site_page: https://chaos-mesh.org/docs/production-installation-using-helm · fetched 2026-08-29 · bad2fa75d90d
- site_page: https://chaos-mesh.org/docs/simulate-pod-chaos-on-kubernetes · fetched 2026-08-29 · 51b2fcfe1368
- site_page: https://chaos-mesh.org/docs/create-chaos-mesh-workflow · fetched 2026-08-29 · 6dbe8c861cd6
- site_page: https://chaos-mesh.org/supported-releases · fetched 2026-08-29 · 208d2f139033
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| chaos-mesh/chaos-mesh | main | 95 |
For agents
markdown · JSON · MCP: product_card(name="chaos-mesh/chaos-mesh")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem