Mastering Resilience Probes: Simplify chaos hypot...
summary
Hands‑on workshop builds a LitmusChaos control plane plus an execution agent and runs three live experiments against the Online Boutique (≈19 microservices) in Kubernetes, each 60s long: a Prometheus probe checks latency, an HTTP probe validates endpoints, and a CMD probe reads kubectl top; one experiment injects 100% network loss to cart, another spikes CPU and a node stress test pushes node CPU >50%, causing probes to fail and an observed resiliency score to drop from 50% to 0% as shown in Grafana.
AI-written summary · about
chapters (17)
- 0:00LitmusChaos introduction
- 1:25Agenda and chaos basics
- 2:10Downtime impact
- 4:17Why downtimes persist
- 6:50Chaos engineering risks
- 9:21Simplify chaos with LitmusChaos
- 12:55LitmusChaos features
- 15:06LitmusChaos UI dashboard
- 23:20Resilience probes deep dive
- 26:53Online boutique demo
- 32:33Shift left resiliency
- 35:00First chaos: network failure
- 37:10Second chaos: CPU spike
- 41:49Probe execution modes
- 49:27Third chaos: node CPU hog
- 55:31Q&A part one
- 58:14Q&A part two
related talks
28mChaos Validation Made Easy
29mEngineering Chaos for Resilient Applications: A Gameday Guide
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
34mChaos Engineering For Hybrid Targets With LitmusChaos
33mCase Study : Improving Resilience of Applications in Telco Environme...
39mResilience & Chaos Engineering in the Cloud
25mDestroy Your System To Make It More Reliable: An Easy Way To Start Chaos Engineering With LitmusChao