+
+ | Experiment Name |
+ Description |
+ Link |
+
+
+ | Container Kill |
+ Kill one container in the application pod |
+ container-kill |
+
+
+ | Disk Fill |
+ Fill the Ephemeral Storage of the Pod |
+ disk-fill |
+
+
+ | Docker Service Kill |
+ Kill docker service of the target node |
+ docker-service-kill |
+
+
+ | Kubelet Service Kill |
+ Kill kubelet service of the target node |
+ kubelet-service-kill |
+
+
+ | Node CPU Hog |
+ Stress the cpu of the target node |
+ node-cpu-hog |
+
+
+ | Node Drain |
+ Drain the target node |
+ node-drain |
+
+
+ | Node IO Stress |
+ Stress the IO of the target node |
+ node-io-stress |
+
+
+ | Node Memory Hog |
+ Stress the memory of the target node |
+ node-memory-hog |
+
+
+ | Node Restart |
+ Restart the target node |
+ node-restart |
+
+
+ | Node Taint |
+ Taint the target node |
+ node-taint |
+
+
+ | Pod Autoscaler |
+ Scale the replicas of the target application |
+ pod-autoscaler |
+
+
+ | Pod CPU Hog |
+ Stress the CPU of the target pod |
+ pod-cpu-hog |
+
+
+ | Pod Delete |
+ Delete the target pods |
+ pod-delete |
+
+
+ | Pod DNS Spoof |
+ Spoof dns requests to desired target hostnames |
+ pod-dns-spoof |
+
+
+ | Pod DNS Error |
+ Error the dns requests of the target pod |
+ pod-dns-error |
+
+
+ | Pod IO Stress |
+ Stress the IO of the target pod |
+ pod-io-stress |
+
+
+ | Pod Memory Hog |
+ Stress the memory of the target pod |
+ pod-memory-hog |
+
+
+ | Pod Network Latency |
+ Induce the network latency in target pod |
+ pod-network-latency |
+
+
+ | Pod Network Corruption |
+ Induce the network packet corruption in target pod |
+ pod-network-corruption |
+
+
+ | Pod Network Duplication |
+ Induce the network packet duplication in target pod |
+ pod-network-duplication |
+
+
+ | Pod Network Loss |
+ Induce the network loss in target pod |
+ pod-network-loss |
+
+
+ | Pod Network Partition |
+ Disrupt network connectivity to kubernetes pods |
+ pod-network-partition |
+
+
+
+### Application Chaos
+
+While Chaos Experiments under the Generic category offer the ability to induce chaos into Kubernetes resources, it is difficult to analyze and conclude if the chaos induced found a weakness in a given application. The application specific chaos experiments are built with some checks on *pre-conditions* and some expected outcomes after the chaos injection. The result of the chaos experiment is determined by matching the outcome with the expected outcome.
+
+
+