github/krkn
1
0
Fork 0
mirror of https://github.com/krkn-chaos/krkn.git synced 2026-04-15 06:57:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

container checking in pod

Browse Source
This commit is contained in:
Paige Rubendall
2021-08-19 15:47:16 -04:00
committed by Naga Ravi Chaitanya Elluri
parent 07ccfbf0aa
commit 22fcab57f5
4 changed files with 98 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/container_scenarios.md
View File

@@ -14,4 +14,25 @@ scenarios:
container_name: "<specific container name>" # This is optional, can take out and will kill all containers in all pods found under namespace and label
pod_names: # This is optional, can take out and will select all pods with given namespace and label
- <pod_name>
retry_wait: <number of seconds to wait for container to be running again> (defaults to 120seconds)
```
#### Post Action
In all scenarios we do a post chaos check to wait and verify the specific component
Here there are two options:
1. Pass a custom script in the main config scenario list, that will run before the chaos and verify the output matches post chaos scenario
See [scenarios/post_action_etcd_container.py](https://github.com/cloud-bulldozer/kraken/tree/master/scenarios/post_action_etcd_container.py) for an example
```
- container_scenarios: # List of chaos pod scenarios to load
- - scenarios/container_etcd.yml
- scenarios/post_action_etcd_container.py
```
2. Allow kraken to wait and check the killed containers become ready again. Kraken keeps a list of the specific
containers that were killed as well as the namespaces and pods to verify all containers that were affected recover properly
```
retry_wait: <seconds to wait for container to recover>
```