Chaos Validation Made Easy
summary
Shows a practical Harness + Litmus workflow that runs a pod-delete on a GKE boutique microservice, wires in Prometheus/Grafana metrics and three reusable resilience probes (HTTP, CMD, Prometheus) with modes like start-of-test, continuous and edge. The HTTP and CMD probes pass, the Prometheus probe reports 88.33% vs the required >=90%, and the experiment produces a resilience score of 75. Demonstrates declarative experiment YAML, CI/CD scheduling, and that automated validation can catch a sub-90% SL0 objective.
AI-written summary · about
chapters (15)
- 0:00intro
- 0:22preamble
- 0:57what causes downtime
- 2:23the problem with existing solutions
- 3:38the cloud-native problem
- 4:40what is chaos engineering
- 5:15chaos engineering best practices
- 6:30harness chaos engineering
- 9:26getting started
- 11:10what are resilience probes
- 12:27how to use these probes?
- 12:49types of probes
- 13:05use cases
- 14:29demo
- 28:08ask any questions!
related talks
01h 01mMastering Resilience Probes: Simplify chaos hypot...
29mEngineering Chaos for Resilient Applications: A Gameday Guide
26mUnified Chaos Injection And SLO Validation Experiments In Kubernetes
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
30mFrom Monitoring to Observability: Left Shift your SLOs with Chaos
29mCase Study: Bringing Chaos Engineering to the Cloud Native Develo...
25mDestroy Your System To Make It More Reliable: An Easy Way To Start Chaos Engineering With LitmusChao