Scenarios
Supported chaos scenarios
| Scenario | Description |
|---|
| Pod failures | Injects pod failures |
| Container failures | Injects container failures based on the provided kill signal |
| Node failures | Injects node failure through OpenShift/Kubernetes, cloud API’s |
| zone outages | Creates zone outage to observe the impact on the cluster, applications |
| time skew | Skews the time and date |
| Node cpu hog | Hogs CPU on the targeted nodes |
| Node memory hog | Hogs memory on the targeted nodes |
| Node IO hog | Hogs io on the targeted nodes |
| Service Disruption | Deleting all objects within a namespace |
| Application outages | Isolates application Ingress/Egress traffic to observe the impact on dependent applications and recovery/initialization timing |
| Power Outages | Shuts down the cluster for the specified duration and turns it back on to check the cluster health |
| PVC disk fill | Fills up a given PersistenVolumeClaim by creating a temp file on the PVC from a pod associated with it |
| Network Chaos | Introduces network latency, packet loss, bandwidth restriction in the egress traffic of a Node’s interface using tc and Netem |
| Pod Network Chaos | Introduces network chaos at pod level |
| Service Hijacking | Hijacks a service http traffic to simulate custom HTTP responses |