Cloud Native Chaos Engineering
summary
A concrete cloud-native chaos stack called Litmus exists and goes GA 1.0, implemented as Kubernetes CRDs: ChaosExperiment, ChaosEngine, ChaosResult, with an operator and Helm chart that integrates into CI/GitOps. It runs chaos by invoking pluggable binaries (examples: Pumbaa, powerfulseal packaged as containers), stores results for Prometheus, and publishes experiments to ChaosHub. An OpenEBS case shows targeted failures (kill target, replica, container) automated and observable, and the project is community-driven and usable in production.
AI-written summary · about
chapters (10)
- 0:00Preamble
- 1:20Chaos Eng is...
- 3:14Agenda
- 4:28Cloud Native Chaos Engineering
- 5:48Cloun Native environment(s)
- 11:45Cloud Native Chaos Engineering
- 13:31Principles
- 21:44Cloud Native Chaos Engineering - Example
- 22:36ChaosHub
- 26:55How can you contribute
related talks
29mCloud Native Chaos Engineering with Lit...
31mCloud Native Chaos Engineering at scale
34mChaos Engineering For Hybrid Targets With LitmusChaos
30mThe Narrative of Reliability: A Chaos Engineering Case Study with LitmusChaos
28mChaos Engineering alongside Litmus and Jenkins
26mAchieving Cloud-Native Resiliency: The Evolution of Chaos Engineering
39mMake Cloud Native Chaos Engineering Easier - Deep Dive into Chaos Mesh
27mPutting Chaos Into Continuous Delivery to Increase App...
