How to foster a Culture of Resilience
summary
Chaos engineering moves from ad hoc failure drills to automated checks: run a delete‑pod CPU/memory attack with Pumba on Kubernetes, verify a gateway keeps 95% successful requests or survives a three‑minute payment downtime, and store those objectives as policies-as-code that run in CI/CD (GitHub Actions or pipeline) against staging or production‑like environments. Add static checks (linters, readiness probe audits), schedule experiments with a central scheduler to avoid parallel interference, and fail builds when long‑running experiments uncover regressions.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:14Understanding resilience
- 2:48Chaos engineering basics
- 5:56Identifying challenges
- 10:54Shifting the approach
- 13:22Defining system capabilities
- 17:54Making resilience a culture
- 20:13Policies as code
- 23:21Implementing policy checks
- 26:54Integration into pipelines
- 29:11Q&A and recap
related talks
43mBuilding a culture from Chaos
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
47mImproving Business Resiliency with Chaos Engineering
27mImplementing Chaos Engr. in a Risk Averse Culture
29mThe Curious SRE: Cultivating a Mindset for System Resilience
48mHarnessing Chaos; the hidden ingredient behind building better systems
43mBetter Software Development Systems through Stress
21mEmbracing Resilience in CD Pipelines