Scenarios
Tip
Many pod scenarios now support theexclude_label parameter to protect critical pods while testing others. See individual scenario pages (Pod Failures, Pod Network Chaos) for details.Supported Chaos Scenarios
Pod & Container Disruptions
Pod Failures
pod_disruption_scenariosInjects pod failures to test application resilience and recovery mechanisms
Container Failures
container_scenariosInjects container failures based on the provided kill signal
KubeVirt VM Outage
kubevirt_vm_outageSimulates VM-level disruptions by deleting Virtual Machine Instances to test resilience and recovery
Node & Cluster Failures
Node Failures
node_scenariosInjects node failures through OpenShift/Kubernetes and cloud APIs
Power Outages
cluster_shut_down_scenariosShuts down the cluster for a specified duration and verifies cluster health upon restart
Zone Outages
zone_outages_scenariosCreates zone outages to observe impact on cluster availability and application resilience
Node CPU Hog
hog_scenariosHogs CPU resources on targeted nodes to test resource contention
Node Memory Hog
hog_scenariosHogs memory resources on targeted nodes to test memory pressure handling
Node IO Hog
hog_scenariosHogs IO resources on targeted nodes to test disk performance degradation
Network Disruptions
Network Chaos
network_chaos_scenariosIntroduces network latency, packet loss, and bandwidth restriction using tc and Netem
Pod Network Chaos
pod_network_scenariosIntroduces network chaos at pod level including latency, packet loss, and bandwidth restriction
Network Chaos NG
network_chaos_ng_scenariosNext-generation network filtering scenarios with improved infrastructure
DNS Outages
network_chaos_ng_scenariosBlocks all outgoing DNS traffic from pods, preventing hostname resolution
ETCD Split Brain
network_chaos_ng_scenariosIsolates etcd nodes to force leader re-election and test cluster resilience
Aurora Disruption
network_chaos_ng_scenariosBlocks MySQL and PostgreSQL traffic to AWS Aurora database engines
EFS Disruption
network_chaos_ng_scenariosBlocks connections to AWS EFS, causing temporary failure of mounted volumes
Application & Service Disruptions
Application Outages
application_outages_scenariosIsolates application Ingress/Egress traffic to test dependency handling and recovery timing
Service Disruption
service_disruption_scenariosDeletes all objects within a namespace to test service recovery and data resilience
Service Hijacking
service_hijacking_scenariosHijacks service HTTP traffic to simulate custom responses and test client error handling
Syn Flood
syn_flood_scenariosGenerates substantial TCP traffic directed at Kubernetes services to test DDoS resilience
Storage & Data Disruptions
PVC Disk Fill
pvc_scenariosFills up PersistentVolumeClaims to test disk space exhaustion handling
System & Time Disruptions
Time Skew
time_scenariosSkews system time and date to test time-sensitive applications and certificate handling