Practicing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
summary
LitmusChaos is shown running automated chaos experiments against Kubernetes and cloud infra using the Litmus Chaos Operator and new Litmus 3.0 UI, with a built control plane + execution plane that schedules YAML experiments, probes, and rollbacks. Claims: >500 companies use it for POCs, 30 million Docker pulls, Delivery Hero targets ~4,000 services. Demo deletes pods (pod-delete), measures a resiliency score, and automatically restores the cart service after the chaos run.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:56Downtime costs beyond money
- 6:45Chaos engineering as integration
- 10:13Why chaos engineering matters
- 13:47Industries using chaos
- 16:14Running a chaos game day
- 19:23Introducing Litmus Chaos
- 22:32Getting started with Litmus UI
- 24:58Live chaos experiment demo
- 32:56Real-world chaos use cases
- 35:47Future of chaos engineering
related talks
30mThe Narrative of Reliability: A Chaos Engineering Case Study with LitmusChaos
34mChaos Engineering For Hybrid Targets With LitmusChaos
23mChaos Engineering for Cloud Native
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
25mDestroy Your System To Make It More Reliable: An Easy Way To Start Chaos Engineering With LitmusChao
35mKeynote: Reliability in Cloud Native DevOps
33mCase Study : Improving Resilience of Applications in Telco Environme...
29mCase Study: Bringing Chaos Engineering to the Cloud Native Develo...