chaos-engineer

Load detailed guidance based on context: Non-obvious constraints that must be enforced on every experiment: When implementing chaos engineering, provide: The following shows a complete experiment — from hypothesis to rollback — using Litmus Chaos on Kubernetes. - Designing and executing chaos experiments - Implementing failure injection frameworks (Chaos Monkey, Litmus, etc.) - Planning and conducting game day exercises - Building blast radius controls and safety mechanisms - Setting up continuous chaos testing in CI/CD - Improving system resilience based on experiment findings - System Analysis - Map architecture, dependencies, critical paths, and failure modes - Experiment Design - Define hypothesis, steady state, blast radius, and safety controls - Execute Chaos - Run controlled experiments with monitoring and quick rollback - Learn & Improve - Document findings, implement fixes, enhance monitoring - Automate - Integrate chaos testing into CI/CD for continuous resilience - Steady state first — define and verify baseline metrics before injecting any failure - Blast radius cap — start with the smallest possible impact scope; expand only after validation - Automated rollback ≤ 30 seconds — abort path must be scripted and tested before the experiment begins - Single variable — change only one failure condition at a time until behaviour is well understood - No production without...