feat(charts): Adding chaos charts for node-memory-hog experiment (#163)
* feat(charts): Adding chaos charts for node-memory-hog experiment Signed-off-by: Udit Gaurav <uditgaurav@gmail.com>
This commit is contained in:
@@ -19,7 +19,6 @@ spec:
|
||||
- "daemonsets"
|
||||
- "jobs"
|
||||
- "pods"
|
||||
- "pods/exec"
|
||||
- "events"
|
||||
- "chaosengines"
|
||||
- "chaosexperiments"
|
||||
|
@@ -11,14 +11,15 @@ metadata:
|
||||
spec:
|
||||
displayName: node-cpu-hog
|
||||
categoryDescription: |
|
||||
Node CPU hog contains chaos to disrupt state of kubernetes resources. Experiments can inject a cpu skipe on a node where the application pod is scheduled.
|
||||
- Causes (forced/graceful) cpu hog on a perticular node where the application deployment is available.
|
||||
- After test the recovery should be manual of the application pod and node in case they are not in appropriate state.
|
||||
|
||||
Node CPU hog contains chaos to disrupt the state of Kubernetes resources. Experiments can inject a CPU spike on a node where the application pod is scheduled.
|
||||
- CPU hog on a particular node where the application deployment is available.
|
||||
- After test, the recovery should be manual for the application pod and node in case they are not in an appropriate state.
|
||||
|
||||
keywords:
|
||||
- Kubernetes
|
||||
- CPU
|
||||
- State
|
||||
- State
|
||||
- Node
|
||||
platforms:
|
||||
- GKE
|
||||
maturity: alpha
|
||||
|
@@ -15,7 +15,7 @@ metadata:
|
||||
name: node-cpu-hog-sa
|
||||
rules:
|
||||
- apiGroups: ["","litmuschaos.io","batch","apps"]
|
||||
resources: ["pods","daemonsets","jobs","pods/exec","events","chaosengines","chaosexperiments","chaosresults"]
|
||||
resources: ["pods","jobs","events","chaosengines","chaosexperiments","chaosresults"]
|
||||
verbs: ["create","list","get","patch","update","delete"]
|
||||
- apiGroups: [""]
|
||||
resources: ["nodes"]
|
||||
|
Reference in New Issue
Block a user