Cloud Native Chaos Engineering at scale
summary
Three years of work becomes a deployable platform: a Helm-installable Litmus portal with a public/private chaos hub, a Prometheus exporter, and declarative chaos workflow units implemented on top of Argo Workflows so experiments run in sequence or parallel and return consolidated results. It integrates with GitLab, GitHub Actions, Spinnaker and GitOps (Flux/ArgoCD style), supports non‑Kubernetes targets via their APIs, and promises Litmus 2.0 with open observability and a growing library of IO, DNS and VM/cloud experiments.
AI-written summary · about
chapters (10)
- 0:00Cloud native chaos intro
- 3:06Traditional chaos limits
- 7:03Why cloud native differs
- 11:20Principles of cloud native
- 15:34Litmus chaos platform
- 21:56Chaos workflows multi-cloud
- 24:30Non-K8s chaos engineering
- 26:17CNCF integrations roadmap
- 27:45Chaos Native future
- 30:12Conclusion
related talks
29mCloud Native Chaos Engineering with Lit...
28mCloud Native Chaos Engineering
26mConstructing Chaos Workflows with Argo and LitmusChaos
30mThe Narrative of Reliability: A Chaos Engineering Case Study with LitmusChaos
34mCreate Chaos Experiments Using Litmus-SDK
12mLightning Talk: Using Argo Workflows to Curate Chaos Engineering wi...
34mHands-On Chaos Engineering Workshop with LitmusChaos and the Road to CNCF Graduation
23mEchoes in the Core: Designing Resilient Platforms
