Creating chaos in containers
summary
Covers concrete chaos experiments for containers: run in-container CPU and memory stress, inject CPU/memory/disk/IO limits, latency, packet loss and blackholes at both host and container levels, and detect outliers via anomaly checks; use Chaos Monkey, Gremlin or AWS Fault Injection Simulator (managed FIS support for containers coming soon); adopt a one‑box production‑like segment for safe tests, run frequent game days, and document failures with five‑why CoE postmortems to turn each outage into actionable fixes.
AI-written summary · about
chapters (8)
- 0:00Intro
- 6:00Health checks
- 11:25Container dependencies
- 18:35The flywheel
- 22:48The learn phase
- 27:35The corrections
- 31:21Additional resources
- 33:00Feedback
related talks
37mCreating chaos in containers
57mChaos Engineering Primer
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
46mDesigning a System for Chaos
39mChaos: Breaking your Systems to Make them Unbreakable
52mGetting started with Chaos Engineering
45mDeveloping a Chaos Architecture Mindset
22mAll Clouds Need a Sprinkle of Chaos
