Case Study: Bringing Chaos Engineering to the Cloud Native Develo...
summary
A concrete case shows cloud-native chaos run from the dev loop: a Litmus YAML chaos workflow (a pod-delete experiment that kills the Postgres pod for 45s every 5s with a GET probe) exposes a real failure in a simple to-do app; developers use Okteto to sync code to a remote Kubernetes dev namespace, add a retry loop, and re-run the same manifest. The retry change turns probe failures into passing results, proving manifest-driven chaos tests validate resilience before merge.
AI-written summary · about
chapters (8)
- 0:00Introduction to speakers
- 1:00Chaos engineering concepts
- 4:27Integrating chaos testing
- 6:23Overview of Litmus Chaos
- 11:24Octeto and development
- 13:38Chaos engineering demo
- 23:26Conclusion and takeaways
- 26:24Q&A session
related talks
23mChaos Engineering for Cloud Native
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
40mJourney into the World of Chaos Engineering
27mPutting Chaos Into Continuous Delivery to Increase App...
22mAll Clouds Need a Sprinkle of Chaos
35mKeynote: Reliability in Cloud Native DevOps
28mCloud Native Chaos Engineering
01h 01mEmbrace chaos to achieve stability