Lightning Talk

on YouTube ↗11m

" summary

Chaos engineering is framed as a repeatable loop: define steady state, hypothesize failure, run experiments, fix weaknesses, and repeat. Implementation uses Kubernetes-native operators and CRDs plus an agent-driven control plane and a UI called Chaos Center. Project metrics claim 2,000 installs per day and 10 million Docker pulls with a 50+ experiments catalog and a 2.0 stable release. Cited impact: 51% of outages are avoidable and outages cost $1–5M per hour on average.

AI-written summary · about

" chapters (7)

1. 0:00Chaos engineering intro
2. 1:04Roots of chaos engineering
3. 3:54Service outages impact
4. 5:21Four chaos engineering steps
5. 6:24Building chaos culture
6. 7:49Litmus Chaos for Kubernetes
7. 9:16Call to action

" related talks

• 30mThe Narrative of Reliability: A Chaos Engineering Case Study with LitmusChaosPrithvi Raj Venkat Raj · KubeDay Japan 2022
• 26mAchieving Cloud-Native Resiliency: The Evolution of Chaos EngineeringPrithvi Raj Venkat Raj · DevOpsDays Poznań 2021
• 28mCloud Native Chaos EngineeringUma Mukkara · Conf42 Chaos Engineering 2020
• 29mCloud Native Chaos Engineering with Lit...Uma Mukkara, Saiyam Pathak, Karthik S, Udit Gaurav · KubeCon + CloudNativeCon Europe 2022
• 39mChaos: Breaking your Systems to Make them UnbreakableJason Yee · TestCon Europe 2019
• 32mImplementing Chaos Engineering in KubernetesAntonio Liccardi · containerday 2023
• 12mLightning Talk: Using Argo Workflows to Curate Chaos Engineering wi...Saranya Jena, Amit Kumar Das · ArgoCon 2022
• 31mCloud Native Chaos Engineering at scaleUma Mukkara · Conf42 Chaos Engineering 2021