Naga Ravi Chaitanya Elluri 1057917731 Add duration parameter for node scenarios ...

This option is enabled only for node_stop_start scenario where
user will want to stop the node for certain duration to understand
the impact before starting the node back on. This commit also bumps
the timeout for the scenario to 360 seconds from 120 seconds to make
sure there's enough time for the node to get to Ready state from the
Kubernetes side after the node is started on the infra side.

Signed-off-by: Naga Ravi Chaitanya Elluri <nelluri@redhat.com>

2024-08-12 13:40:18 -04:00

..

arcaflow

Arcaflow upgrade to engine v0.17.1 (#639)

2024-06-04 14:13:33 -04:00

kind

Integration of the new pod recovery monitoring strategy implemented in krkn-lib (#609)

2024-04-23 10:49:01 +02:00

kube

SYN flood scenario (#668)

2024-07-29 15:31:37 -04:00

openshift

Add duration parameter for node scenarios

2024-08-12 13:40:18 -04:00

plugin.schema.json

Integration of the new pod recovery monitoring strategy implemented in krkn-lib (#609)

2024-04-23 10:49:01 +02:00

plugin.schema.README.md

Fixes #265: Replace Powerfulseal and introduce Wolkenwalze SDK for plugin system

2022-08-02 16:25:03 +01:00