chore(new_chart): Add chart for pod IO stress charts (#320)
* chore(new_chart): Add chart for pod io stress charts Signed-off-by: Udit Gaurav <udit.gaurav@mayadata.io>
This commit is contained in:
@@ -28,7 +28,7 @@ spec:
|
||||
value: '120'
|
||||
|
||||
## specify the size as percentage of free space on the file system
|
||||
- name: FILESSYSTEM_UTILIZATION_PERCENTAGE
|
||||
- name: FILESYSTEM_UTILIZATION_PERCENTAGE
|
||||
value: '10'
|
||||
|
||||
## enter the name of the desired node
|
||||
|
@@ -1,7 +1,7 @@
|
||||
apiVersion: litmuschaos.io/v1alpha1
|
||||
description:
|
||||
message: |
|
||||
Give a memory hog on a node belonging to a deployment
|
||||
Give IO disk stress on a node belonging to a deployment
|
||||
kind: ChaosExperiment
|
||||
metadata:
|
||||
name: node-io-stress
|
||||
@@ -50,12 +50,12 @@ spec:
|
||||
|
||||
## specify the size as percentage of free space on the file system
|
||||
## default value 90 (in percentage)
|
||||
- name: FILESSYSTEM_UTILIZATION_PERCENTAGE
|
||||
- name: FILESYSTEM_UTILIZATION_PERCENTAGE
|
||||
value: '10'
|
||||
|
||||
## we can specify the size in Gigabyte (Gb) also in place of percentage of free space
|
||||
## NOTE: for selecting this option FILESSYSTEM_UTILIZATION_PERCENTAGE should be empty
|
||||
- name: FILESSYSTEM_UTILIZATION_BYTES
|
||||
## NOTE: for selecting this option FILESYSTEM_UTILIZATION_PERCENTAGE should be empty
|
||||
- name: FILESYSTEM_UTILIZATION_BYTES
|
||||
value: ''
|
||||
|
||||
## Total number of workers default value is 4
|
||||
|
@@ -13,8 +13,7 @@ spec:
|
||||
categoryDescription: |
|
||||
This experiment causes disk stress on the Kubernetes node. The experiment aims to verify the resiliency of applications that share this disk resource for ephemeral or persistent storage purposes..
|
||||
- Disk stress on a particular node filesystem where the application deployment is available.
|
||||
- The amount of disk stress can be either specifed as the size in percentage of the total free space on the file system or simply in Gigabytes(Gb)
|
||||
- After the test, the recovery should be manual for the application pod and node in case they are not in an appropriate state.
|
||||
- The amount of disk stress can be either specifed as the size in percentage of the total free space on the file system or simply in Gigabytes(GB)
|
||||
keywords:
|
||||
- Kubernetes
|
||||
- Disk
|
||||
|
Reference in New Issue
Block a user