Bringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
summary
Shows a hands‑on use of litmus chaos with two live demos: a pod delete against an online boutique product‑catalog and the same against a sockshop catalog while observing metrics in Grafana. Installs a cluster‑scoped Litmus portal, selects faults from a Hub or private Git, tunes chaos engines and probes, and schedules experiments. Observed a 512 error during the injection, ReplicaSet immediately recreates pods, and reverse‑schedule cleanup restores the original state.
AI-written summary · about
chapters (18)
- 0:00Introduction to talk
- 1:05What causes downtimes
- 3:31Cloud native reliability challenges
- 3:51What is chaos engineering
- 7:23Solutions chaos engineering provides
- 8:47CNCF chaos engineering landscape
- 9:52Introducing LitmusChaos
- 10:37LitmusChaos architecture overview
- 12:25Types of chaos experiments
- 13:06Demo setup overview
- 14:08Installing LitmusChaos portal
- 16:38Selecting chaos experiments
- 18:02Configuring pod delete experiment
- 21:10Running chaos experiment
- 22:13Observing system failure
- 23:18Second demo with monitoring
- 26:28Key takeaways and conclusion
- 26:50Q&A session
related talks
25mDestroy Your System To Make It More Reliable: An Easy Way To Start Chaos Engineering With LitmusChao
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
33mMonkey Business For Serious Systems: Why chaos engineering isnt crazy
28mChaos Engineering alongside Litmus and Jenkins
34mChaos Engineering For Hybrid Targets With LitmusChaos
26mCanonical chaos through Litmus
29mEngineering Chaos for Resilient Applications: A Gameday Guide
32mChaos Engineering with Litmus and Jenkins