github/krkn
1
0
Fork 0
mirror of https://github.com/krkn-chaos/krkn.git synced 2026-02-14 18:10:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Add pointer to the litmus based scenarios

Browse Source
This commit is contained in:
Naga Ravi Chaitanya Elluri
2021-04-30 11:03:24 -04:00
parent a14f4c2561
commit 70b14956c7
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -16,7 +16,7 @@ Instructions on how to setup the config and the options supported can be found a
### Kubernetes/OpenShift chaos scenarios supported ### Kubernetes/OpenShift chaos scenarios supported
Kraken supports pod, node and time/date based scenarios. Kraken supports pod, node, time/date and [litmus](https://github.com/litmuschaos/litmus) based scenarios.
- [Pod Scenarios](docs/pod_scenarios.md) - [Pod Scenarios](docs/pod_scenarios.md)
@@ -24,6 +24,8 @@ Kraken supports pod, node and time/date based scenarios.
- [Time Scenarios](docs/time_scenarios.md) - [Time Scenarios](docs/time_scenarios.md)
- [Litmus Scenarios](docs/litmus_scenarios.md)
### Kraken scenario pass/fail criteria and report ### Kraken scenario pass/fail criteria and report
It's important to make sure to check if the targeted component recovered from the chaos injection and also if the Kubernetes/OpenShift cluster is healthy as failures in one component can have an adverse impact on other components. Kraken does this by: It's important to make sure to check if the targeted component recovered from the chaos injection and also if the Kubernetes/OpenShift cluster is healthy as failures in one component can have an adverse impact on other components. Kraken does this by: