Chaos Mesh

Chaos Mesh is an open-source chaos-engineering platform for teams running Kubernetes. It is best suited to platform and reliability engineers who want to define and coordinate fault experiments through cluster resources. Its broad simulation coverage and free self-hosted model make it a strong Kubernetes option, provided teams are prepared to manage privileged access and deployment details.

Overview

Chaos Mesh manages experiments through Kubernetes CustomResourceDefinitions and the Kubernetes API, making it a natural fit for organizations that already operate workloads through Kubernetes. It can simulate faults in development, testing, and production, with selectors and namespace controls to focus experiments on chosen targets and contain their blast radius. That control is important: for Pod Kill experiments, the project recommends a ReplicaSet or similar controller so the Pod can restart automatically.

Coverage reaches beyond Pods and networks to DNS, HTTP, I/O, time, stress, kernels, block devices, JVMs, physical machines, and AWS, Azure, and GCP faults. This breadth supports testing failure responses across application and infrastructure layers, though teams should plan carefully before introducing faults into production. Chaos Mesh originated in TiDB's core testing platform and inherited testing experience from that environment.

Key features

Scheduling, workflows, and health checks

Schedule resources support recurring experiments, while Workflow resources can run experiments serially or in parallel and check their status and results. StatusCheck resources add application health checks. Together, these tools let teams coordinate repeatable exercises rather than launch isolated disruptions, although they still require sound experiment design and target selection.

Dashboard and integrations

Chaos Dashboard provides a web interface and HTTP API for creating, managing, and observing experiments. Role-based access control is enabled by default, and Kubernetes RBAC governs permissions; namespace annotations can further restrict where experiments are enabled. On Google Cloud Platform, the Dashboard can use Google OAuth authentication.

The Dashboard stores data in SQLite by default. Without persistent volumes, that data is lost after a reboot, so teams should configure persistent storage or use MySQL or PostgreSQL when that suits their operations better. The Grafana data-source plugin requires Chaos Mesh 2.1 or later and Grafana 10.0 or later; it was tested on Grafana 10.0.3. A GitHub Action integrates Chaos Mesh into GitHub Actions CI workflows.

Cluster operations and security

The official Helm repository supports Helm 3 and provides a command to install Chaos Mesh into a Kubernetes namespace. Chaos Daemon runs as a Kubernetes DaemonSet with privileged permission by default, though that permission can be disabled. This is a meaningful security consideration for teams reviewing cluster privileges, not a minor setup preference.

RemoteCluster can install Chaos Mesh components in remote Kubernetes clusters and synchronize experiment status, but the feature is in an early stage. Kubernetes compatibility is version-specific: Chaos Mesh 2.8 supports Kubernetes 1.30 through 1.35, while 2.7 supports versions 1.26 through 1.28. Teams should match their chosen release to their cluster version.

Pricing

Chaos Mesh is free and open source under the Apache License 2.0. The Chaos Mesh plan costs nothing and runs on Kubernetes. There are no paid tiers to weigh against a feature-restricted free plan, but operators take responsibility for self-hosting, storage, permissions, and upgrades.

Community technical support is available through CNCF Slack in #project-chaos-mesh and GitHub Discussions. Security issues are fixed as soon as possible and back-ported to the last two releases, so teams should keep deployment and upgrade practices aligned with their risk requirements.

Platforms

Chaos Mesh supports API, self-hosted, and web access. Kubernetes is a requirement for its deployment model, and the Dashboard supplies the web interface. It is not a general-purpose desktop fault-testing tool; its strongest fit is within Kubernetes operations.

Who it's for

Choose Chaos Mesh if your team runs Kubernetes and wants a free way to schedule, scope, and observe fault experiments across workloads and cloud infrastructure. Its Kubernetes-native model and workflow controls are especially relevant to platform and reliability teams building recurring resilience checks or CI exercises.

Look elsewhere if you need a tool that does not require Kubernetes, or if your organization cannot accept a privileged DaemonSet component and the operational responsibility of self-hosting. The default permission can be disabled, but that does not remove the need to assess the deployment's security and storage configuration.

Pros and cons

• Pros: Broad fault coverage includes application, system, network, and major cloud scenarios, giving Kubernetes teams one platform for varied resilience exercises.
• Pros: Scheduling, serial or parallel workflows, health checks, and target controls support repeatable experiments with a more deliberate blast radius.
• Pros: Free Apache-licensed software avoids subscription costs and can be installed through Helm 3.
• Cons: Chaos Daemon is privileged by default, which requires security review in clusters with strict permission policies.
• Cons: Dashboard data can disappear after a reboot unless persistent volumes or an alternative database are configured.
• Cons: Kubernetes version support differs by Chaos Mesh release, and remote-cluster support remains early-stage.

Alternatives

For a broader set of choices, see Chaos Engineering Platforms.

• Chaos Toolkit is a free open-source CLI for teams seeking a different open-source chaos-engineering option across API, desktop, and self-hosted platforms.
• Reliably is a freemium option that describes itself as open source and says its approach avoids lock-in; its Free plan is free for one team member.
• ChaosBlade is a free open-source chaos-engineering tool with more than 200 experiment scenarios, suited to readers comparing scenario breadth.
• Gremlin is a paid option with a 30-day free trial that requires no credit card and does not auto-convert, for teams evaluating a trial-based alternative.
• Steadybit is a paid alternative with an Enterprise plan that includes on-prem installation, SAML, audit log, and enterprise support.
• AWS Fault Injection Service charges $0.10 per action-minute, plus $0.10 per action-minute for each additional account, and may suit teams considering an action-minute-priced alternative.
• PowerfulSeal is an Apache-2.0 open-source option for self-hosted Kubernetes chaos testing, installed with pip or Docker.
• LitmusChaos offers both a free hosted SaaS plan and a free open-source platform for installation on your own cluster.

Verdict

Chaos Mesh is a strong choice for Kubernetes platform and reliability teams that want broad, schedulable fault injection without subscription fees. Its Kubernetes-native orchestration and scope controls are the main reasons to choose it; the privileged daemon and the need to manage storage and version compatibility are the reasons to look elsewhere.