How is chaos engineering integrated into CD pipelines?

Chaos engineering, pioneered by Netflix's Chaos Monkey, validates system resilience by deliberately injecting failures in a controlled way. Integrating it into CD pipelines means resilience is validated continuously, not just during periodic gamedays. In a CD pipeline for a staging or canary environment, chaos experiments can be automated: inject random pod termination (Chaos Monkey, Chaos Mesh), introduce network latency or packet loss between services (Istio fault injection), simulate disk failures, or exhaust CPU/memory on specific nodes. The pipeline monitors SLOs during the chaos injection period — if the service degrades beyond acceptable thresholds, the deployment is aborted before reaching more users. Tools include Chaos Mesh and LitmusChaos (Kubernetes-native), Gremlin (enterprise), and AWS Fault Injection Simulator. The key discipline is defining a "steady state hypothesis" — what normal looks like — before running experiments, so you can quantifiably confirm resilience was maintained.