Skip to content

Latest commit

 

History

History
48 lines (33 loc) · 3.36 KB

README.md

File metadata and controls

48 lines (33 loc) · 3.36 KB

krkn-hub aka kraken-hub

Hosts container images and wrapper for running scenarios supported by Kraken, a chaos testing tool for OpenShift/Kubernetes clusters to ensure it is resilient to failures. All we need to do is run the containers with the respective environment variables defined as supported by the scenarios without having to maintain and tweak files!

Supported chaos scenarios

Scenario Description Working
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 ✔️
Namespace failures Fails the components in a namespace by deleting it ✔️
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 Introducs network chaos at pod level ✔️

Set Up

You can use docker or podman to run kraken-hub

Install Podman your certain operating system based on these instructions

or

Install Docker

Docker is also supported but all variables you want to set (separate from the defaults) need to be set at the command line In the form -e <VARIABLE>=<value>

You can take advantage of the get_docker_params.sh script to create your parameters string This will take all environment variables and put them in the form "-e =" to make a long string that can get passed to the command

For example: docker run $(./get_docker_params.sh) --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:power-outages

Adding New Scenarios/Testing Changes

Refer to the 2 docs below to be able to test your own images with any changes and be able to contribute them to the repository