Unraveling the Chaos: Raising Workload Resilience on K8s with Chaos Mesh
summary
Chaos engineering using Chaos Mesh to find hidden vulnerabilities in Kubernetes workloads by simulating critical failures. Practical techniques for testing workload resilience on Kubernetes and using those tests to improve system robustness and reliability.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:04What is chaos engineering
- 3:34When not to use chaos
- 5:16Distributed systems challenges
- 7:24Tests versus experiments
- 9:26Chaos improvement cycle
- 10:30Chaos engineering goal
- 11:14What is Chaos Mesh
- 14:30Chaos Mesh architecture
- 15:57Pod fail practical example
- 17:21Network delay experiment
- 19:28HTTP replace experiment
- 20:33AWS KS experiment
- 22:24Availability zone failure
- 24:30Anti-affinity and pod topology
- 26:39High load and registry issues
- 28:47Chaos Mesh improvements
- 29:50Insights and optimizations
- 30:53Resilience culture
related talks
26mAchieving Cloud-Native Resiliency: The Evolution of Chaos Engineering
32mImplementing Chaos Engineering in Kubernetes
23mChaos Engineering for Cloud Native
01h 22mKeynotes Día 2
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
40mJourney into the World of Chaos Engineering
17mResilient Applications on Kubernetes
23mBuilding Ultra-Large-Scale Cloud Native Edge Systems Using Chaos Engineering