What’s New In Chaos Mesh And Deep Dive Into Multi Clusters Support
summary
Chaos Mesh adds a multi-cluster coordinator/agent model that lets one central controller submit and observe experiments on remote clusters, and extends cloud chaos with Azure actions (VM stop, restart, disk detach). Version 2.4 ships block chaos via kernel IO scheduler (ioem) to inject I/O delay and soon IOPS limits without ptrace side effects, plus physical-machine chaos using chaosd, workflow status checks (HTTP now, Prometheus planned), and a drag‑and‑drop workflow UI.
AI-written summary · about
chapters (6)
- 0:00Start
- 9:26AzureChaos
- 15:44PhysicalMachineChaos
- 17:32Status Check in Workflow
- 20:28Why Multi Clusters Support?
- 23:48Future Plans
related talks
32mImplementing Chaos Engineering in Kubernetes
32mUnraveling the Chaos: Raising Workload Resilience on K8s with Chaos Mesh
29mCloud Native Chaos Engineering with Lit...
28mCloud Native Chaos Engineering
28mContaining Chaos with Kubernetes
23mEchoes in the Core: Designing Resilient Platforms
39mChaos: Breaking your Systems to Make them Unbreakable
21mCluster API Deep Dive
