Creating chaos in containers

on YouTube ↗37m

" summary

Explains concrete chaos practices for containers: define four health checks — liveness checks, local, dependency and anomaly — and test CPU, memory and especially network (inject latency, packet loss, black‑hole) because orchestrators don’t guarantee per‑pod bandwidth. Names tools that work: Chaos Monkey, Gremlin and AWS Fault Injection Simulator (CPU/memory/io/network faults on ECS/EKS). Recommends a prepare→detect→respond→learn flywheel, run experiments with runbooks and rollback guards, and capture CoE retrospectives with action items and owners.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 6:27Liveness checks
3. 7:06Local health checks
4. 8:01Dependency health checks
5. 9:18Anomaly detection
6. 17:18The uptime flywheel

" related talks

• 38mCreating chaos in containersMaish Saidel-Keesing · Voxxed Days Brussels 2023
• 57mChaos Engineering PrimerSergiu Bodiu · Voxxed Days Singapore 2017
• 01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failureAdrian Hornsby · NDC Oslo 2019
• 45mDeveloping a Chaos Architecture MindsetAdrian Cockcroft · GOTO Chicago 2018
• 18mChaos Engineering: Break It On PurposeMorgan Carter · BSides London 2021
• 22mAll Clouds Need a Sprinkle of ChaosAna Medina · Postman Galaxy 2021
• 46mDesigning a System for ChaosPaul Stack · DevConf 2019
• 33mBeyond the Monkeys Chaos Engineering on the CloudBella Wiseman, Sindhuja Durai · CloudOpen @ Open Source Summit North America 2022