Project: Litmus (Observability and Analysis / Chaos Engineering)
File: node-cpu-hog.md

This experiment causes CPU resource exhaustion on the Kubernetes node. The experiment aims to verify resiliency of applications whose replicas may be evicted on account on nodes turning unschedulable (Not Ready) due to lack of CPU resources. The CPU chaos is injected using a helper pod running the linux stress tool (a workload generator). The chaos is effected for a period equalling the TOTALCHAOSDURATION Application implies services. Can be reframed as: Tests application resiliency upon replica evictions caused due to lack of CPU resources !!! tip "Scenario: Stress the CPU of node" ??? info "View the uses of the experiment" coming soon ??? info "Verify the prerequisites" Ensure that Kubernetes Version > 1.16 Ensure that the Litmus Chaos Operator is running by executing <code>kubectl get pods</code> in operator namespace (typically, <code>litmus</code>).If not, install from <a href="https://v1-docs.litmuschaos.io/docs/getstarted/#install-litmus">here</a> Ensure that the <code>node-cpu-hog</code> experiment resource is available in the cluster by executing <code>kubectl get chaosexperiments</code> in the desired namespace. If not, install from <a href="https://hub.litmuschaos.io/api/chaos/master?file=faults/kubernetes/node-cpu-hog/fault.yaml">here</a> ??? info "View the default validations" The target nodes should be in ready state before and after chaos injection. !!! tip "NOTE" If you are using this experiment as part of a litmus workflow scheduled constructed & executed from chaos-center, then you may be making use of the RBAC, which is pre installed in the cluster as part of the agent setup. ??? note "View the Minimal RBAC permissions" ```yaml apiVersion: v1 kind: ServiceAccount metadata: name: node-cpu-hog-sa namespace: default labels: name: node-cpu-hog-sa app.kubernetes.io/part-of: litmus apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: node-cpu-hog-sa labels: name: node-cpu-hog-sa app.kubernetes.io/part-of: litmus rules: apiGroups: [""] resources: ["pods"] verbs: ["create","delete","get","list","patch","update", "deletecollection"] apiGroups: [""] resources: ["events"] verbs: ["create","get","list","patch","update"] apiGroups: [""] resources: ["configmaps"] verbs: ["get","list",] apiGroups: [""] resources: ["pods/log"] verbs: ["get","list","watch"] apiGroups: [""] resources: ["pods/exec"] verbs: ["get","list","create"] apiGroups: ["batch"] resources: ["jobs"] verbs: ["create","list","get","delete","deletecollection"] apiGroups: ["litmuschaos.io"] resources: ["chaosengines","chaosexperiments","chaosresults"] verbs: ["create","list","get","patch","update","delete"] apiGroups: [""] resources: ["nodes"] verbs: ["get","list"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: node-cpu-hog-sa labels: name: node-cpu-hog-sa app.kubernetes.io/part-of: litmus roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: node-cpu-hog-sa subjects: kind: ServiceAccount name: node-cpu-hog-sa namespace: default ``` Use this sample RBAC manifest to create a chaosServiceAccount in the desired (app) namespace. This example consists of the minimum necessary role permissions to execute the

??? info "check the experiment tunables" <h2>Mandatory Fields</h2> <table> <tr> <th> Variables </th> <th> Description </th> <th> Notes </th> </tr> <tr> <td> TARGET_NODES </td> <td> Comma separated list of nodes, subjected to node cpu hog chaos</td> <td> </td> </tr> <tr> <td> NODE_LABEL </td> <td> It contains node label, which will be used to filter the target nodes if TARGET_NODES ENV is not set </td> <td>It is mutually exclusive with the TARGETNODES ENV. If both are provided then it will use the TARGETNODES</td> </tr> </table> <h2>Optional Fields</h2> <table> <tr> <th> Variables </th> <th> Description </th> <th> Notes </th> </tr> <tr> <td> TOTALCHAOSDURATION </td> <td> The time duration for chaos insertion (seconds) </td> <td> Defaults to 60 </td> </tr> <tr> <td> LIB </td> <td> The chaos lib used to inject the chaos </td> <td> Defaults to <code>litmus</code> </td> </tr> <tr> <td> LIB_IMAGE </td> <td> Image used to run the stress command </td> <td> Defaults to <code>litmuschaos/go-runner:latest</code> </td> </tr> <tr> <td> RAMP_TIME </td> <td> Period to wait before & after injection of chaos in sec </td> <td> Optional </td> <td> </td> </tr> <tr> <td> NODECPUCORE </td> <td> Number of cores of node CPU to be consumed </td> <td> Defaults to <code>2</code> </td> <td> </td> </tr> <tr> <td> NODESAFFECTEDPERC </td> <td> The Percentage of total nodes to target </td> <td> Defaults to 0 (corresponds to 1 node), provide numeric value only </td> </tr> <tr> <td> SEQUENCE </td> <td> It defines sequence of chaos execution for multiple target pods </td> <td> Default value: parallel. Supported: serial, parallel </td> </tr> </table> Refer the and to tune the common tunables for all experiments and node specific tunables. It contains number of cores of node CPU to be consumed. It can be tuned via `NODECPUCORE` ENV. Use the following example to tune this: ```yaml apiVersion: litmuschaos.io/v1alpha1 kind: ChaosEngine metadata: name: engine-nginx spec: engineState: "active" annotationCheck: "false" chaosServiceAccount: node-cpu-hog-sa experiments: name: node-cpu-hog spec: components: env: name: NODECPUCORE value: '2' name: TOTALCHAOSDURATION value: '60' ``` It contains percentage of node CPU to be consumed. It can be tuned via `CPU_LOAD` ENV. Use the following example to tune this: ```yaml apiVersion: litmuschaos.io/v1alpha1 kind: ChaosEngine metadata: name: engine-nginx spec: engineState: "active" annotationCheck: "false" chaosServiceAccount: node-cpu-hog-sa experiments: name: node-cpu-hog spec: components: env: name: CPU_LOAD value: "100" name: NODECPUCORE value: '0' name: TOTALCHAOSDURATION value: '60' ```