Releases: litmuschaos/chaos-runner
Releases · litmuschaos/chaos-runner
1.4.0-RC1
1.3.0
1.3.0-RC1
1.2.2
[Cherry pick for 1.2.2] (#59)
* (fix) Added name of the runner Pod in ChaosEngine Events (#56)
Signed-off-by: Rahul M Chheda <rahul.chheda@mayadata.io>
* (feat) Added support for AdminMode (#45)
* (feat) Added support for AdminMode
- Replaced EngineDetails.AppNamespace to EngineDetails.EngineNamespace
- Added logic to check for resources in chaosEngine namespace
- Only job will be created in AppNamespace (experiment.Namespace)
- Synced the experiment.Namespace = engineDetails.EngineNamespace, when AdminMode is true
- Added OS ENV as ENGINE_NAMESPACE passed from operator, into engineDetails struct
* Sycned experiment.Namespace and engineDetails.EngineNamespace
Signed-off-by: Rahul M Chheda <rahul.chheda@mayadata.io>
* refcator(chaos_ns): Rename Engine_NAMESPACE to CHAOS_NAMESPACE (#57)
Signed-off-by: shubhamchaudhary <shubham.chaudhary@mayadata.io>
Co-authored-by: Shubham Chaudhary <shubham.chaudhary@mayadata.io>
1.2.0
1.2.0-RC1
1.1.0
1.1.0-RC1
1.0.0
1.0.0-RC2
Getting Started
Prerequisites to install
- Make sure you have a healthy Kubernetes Cluster.
- Kubernetes 1.11+ is installed
Installation
kubectl apply -f https://litmuschaos.github.io/pages/litmus-operator-latest.yaml
Verify your installation
-
Verify if the chaos operator is running
kubectl get pods -n litmus -
Verify if chaos CRDs are installed
kubectl get crds | grep chaos -
Verify if the chaos experiments are installed.
kubectl get chaosexperiments
For more details refer to the documentation at Docs