Skip to main content
Hong Kong
AIMenta
C

Chaos Mesh

by CNCF / PingCAP

CNCF open-source Kubernetes-native chaos engineering platform enabling APAC SRE and platform engineering teams to inject pod, node, network, storage, and application-layer faults into Kubernetes workloads through a declarative ChaosExperiment API and web dashboard — supporting scheduled, workflow-driven, and CI/CD-triggered chaos experiments for APAC production system resilience validation.

Visit Chaos Mesh (opens in new tab) Get a recommendation
AIMenta verdict
Recommended
5/5

"Chaos Mesh is the CNCF Kubernetes chaos engineering platform for APAC — fault injection for pods, nodes, network, and storage with dashboard-driven experiment orchestration. Best for APAC SRE teams validating production resilience on Kubernetes without manual failure scripting."

Features
7
Use cases
4
Watch outs
4
What it does

Key features

  • Multi-layer fault injection — pod, network, DNS, I/O, kernel, and HTTP chaos for APAC Kubernetes workloads
  • Chaos Dashboard — form-based APAC experiment creation and real-time fault visualisation without YAML
  • Workflow CRD — multi-step APAC game-day scenario orchestration with parallel and sequential fault sequences
  • Namespace annotation guard — explicit opt-in for APAC namespace chaos injection prevents accidental production faults
  • NetworkChaos — packet loss, delay, partition, and bandwidth throttling between APAC Kubernetes services
  • HTTPChaos — APAC API-level request/response manipulation for service-layer resilience testing
  • Scheduled experiments — cron-based APAC chaos injection for continuous resilience validation
When to reach for it

Best for

  • APAC SRE and platform engineering teams running Kubernetes who need a structured chaos engineering platform for validating production resilience without manual fault injection scripts or ad-hoc node reboots
  • APAC engineering organisations practicing game-day exercises — Chaos Mesh's Workflow CRD enables multi-step failure cascade simulations that test APAC system behaviour under realistic compound failures
  • APAC teams with distributed microservices requiring NetworkChaos testing to validate that services degrade gracefully under APAC inter-service network failures, packet loss, and latency spikes
  • APAC platform engineering teams integrating chaos engineering into CI/CD pipelines — Chaos Mesh's Kubernetes API enables programmatic chaos experiment creation and completion monitoring from APAC CI/CD pipeline steps
Don't get burned

Limitations to know

  • ! Kubernetes-only — Chaos Mesh only injects faults into Kubernetes workloads; APAC organisations with significant on-premise non-Kubernetes infrastructure (legacy VMs, bare-metal) need complementary chaos tools for non-APAC-Kubernetes systems
  • ! Privilege requirements — some Chaos Mesh fault types (kernel chaos, I/O chaos) require elevated pod privileges; APAC platform teams with strict pod security admission policies must evaluate compatibility with their APAC pod security baseline
  • ! Observability integration — Chaos Mesh Dashboard does not natively integrate with APAC observability platforms (Prometheus, Grafana, Datadog); APAC SRE teams must configure separate metric correlation between chaos events and APAC system metrics manually
  • ! Learning curve for complex scenarios — Chaos Mesh's Workflow CRD for multi-step APAC chaos scenarios requires understanding Chaos Mesh's task graph model; APAC teams new to chaos engineering should start with single ChaosExperiment resources before composing multi-step Workflows
Context

About Chaos Mesh

Chaos Mesh is a CNCF open-source Kubernetes-native chaos engineering platform originated by PingCAP (the team behind TiDB) that enables APAC SRE and platform engineering teams to inject controlled faults into Kubernetes workloads across all system layers — pod lifecycle, network topology, file system, kernel, and application HTTP/gRPC interfaces — through a declarative ChaosExperiment Custom Resource API and a Chaos Dashboard web UI, without requiring direct shell access to APAC production nodes or manual failure injection scripts.

Chaos Mesh's fault injection model covers the complete APAC infrastructure fault taxonomy: PodChaos (pod kill, container kill, pod failure simulation), NetworkChaos (network partition, bandwidth throttling, packet loss, packet delay, packet duplication between APAC Kubernetes services), StressChaos (CPU stress and memory stress on APAC pods to simulate resource contention), DNSChaos (DNS resolution failure and DNS spoofing for APAC service discovery resilience), IOChaos (filesystem I/O latency, permission errors, and data corruption for APAC storage-dependent services), and HTTPChaos (HTTP request/response manipulation at the application level for APAC API resilience testing).

Chaos Mesh's Workflow CRD — where APAC SRE teams define multi-step chaos scenarios as Chaos Mesh Workflows (orchestrating parallel fault injection, sequential chaos experiments, and conditional chaos termination based on APAC system metrics) — enables APAC game-day simulations that test complex failure cascades (network partition causing message queue backpressure causing APAC database connection pool exhaustion) rather than isolated single-fault injections that don't reflect realistic APAC production failure modes.

Chaos Mesh's Chaos Dashboard — the Chaos Mesh web UI for APAC SRE teams — provides experiment definition through a form-based interface (selecting fault type, target pods via label selector, fault duration, and scheduling), real-time experiment visualisation showing active fault injection on APAC Kubernetes topology, experiment history with event timeline, and archive of completed APAC chaos experiments for post-mortem analysis — enabling APAC SRE teams to run and monitor chaos experiments without writing YAML or running kubectl commands.

Chaos Mesh's Kubernetes-native security model — where Chaos Mesh uses Kubernetes RBAC to control which APAC teams can create ChaosExperiment resources in which namespaces, and requires explicit namespace annotation (`chaos-mesh.org/inject: enabled`) to make APAC namespace pods eligible for chaos injection — provides guardrails that prevent accidental APAC production chaos injection from APAC development or staging namespace experiments, satisfying APAC enterprise security policies requiring explicit chaos injection authorisation.

Beyond this tool

Where this category meets practice depth.

A tool only matters in context. Browse the service pillars that operationalise it, the industries where it ships, and the Asian markets where AIMenta runs adoption programs.

Or browse All tools · Encyclopedia · Case studies · Rankings