From 327f7b199fbb3485482e5f5d4b746d23402ce166 Mon Sep 17 00:00:00 2001 From: jtydlack <139967002+jtydlack@users.noreply.github.com> Date: Wed, 27 Nov 2024 09:26:35 +0100 Subject: [PATCH] Add disk_deatch_attach_scenario in docs Signed-off-by: jtydlack <139967002+jtydlack@users.noreply.github.com> --- docs/node_scenarios.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/node_scenarios.md b/docs/node_scenarios.md index 6d81b1dd..dd435d98 100644 --- a/docs/node_scenarios.md +++ b/docs/node_scenarios.md @@ -4,7 +4,7 @@ The following node chaos scenarios are supported: 1. **node_start_scenario**: Scenario to stop the node instance. 2. **node_stop_scenario**: Scenario to stop the node instance. -3. **node_stop_start_scenario**: Scenario to stop and then start the node instance. Not supported on VMware. +3. **node_stop_start_scenario**: Scenario to stop the node instance for specified duration and then start the node instance. Not supported on VMware. 4. **node_termination_scenario**: Scenario to terminate the node instance. 5. **node_reboot_scenario**: Scenario to reboot the node instance. 6. **stop_kubelet_scenario**: Scenario to stop the kubelet of the node instance. @@ -12,6 +12,7 @@ The following node chaos scenarios are supported: 8. **restart_kubelet_scenario**: Scenario to restart the kubelet of the node instance. 9. **node_crash_scenario**: Scenario to crash the node instance. 10. **stop_start_helper_node_scenario**: Scenario to stop and start the helper node and check service status. +11. **node_disk_detach_attach_scenario**: Scenario to detach node disk for specified duration. **NOTE**: If the node does not recover from the node_crash_scenario injection, reboot the node to get it back to Ready state. @@ -20,6 +21,8 @@ The following node chaos scenarios are supported: , node_reboot_scenario and stop_start_kubelet_scenario are supported on AWS, Azure, OpenStack, BareMetal, GCP , VMware and Alibaba. +**NOTE**: node_disk_detach_attach_scenario is supported only on AWS. + #### AWS