Skip to main content

Kubelet service kill

Kubelet service kill makes the application unreachable on the account of the node turning unschedulable (in NotReady state).

  • Kubelet service is stopped (or killed) on a node to make it unschedulable for a specific duration.
  • The application node goes back to normal state and services are resumed after the chaos duration.

Kubelet Service Kill

Use cases

Kubelet service kill fault determines the resilience of an application when a node becomes unschedulable, that is, NotReady state.


  • Kubernetes > 1.16 is required to execute this fault.
  • Node specified in the TARGET_NODE environment variable (the node for which Docker service would be killed) should be cordoned before executing the chaos fault. This ensures that the fault resources are not scheduled on it or subject to eviction. This is achieved using the following steps:
    • Get node names against the applications pods using command kubectl get pods -o wide.
    • Cordon the node using command kubectl cordon <nodename>.
  • The target nodes should be in the ready state before and after injecting chaos.

Mandatory tunables

Tunable Description Notes
TARGET_NODE Name of the target node. For example, node-1. For more information, go to target node.
NODE_LABEL Node label used to filter the target node if TARGET_NODE environment variable is not set. It is mutually exclusive with the TARGET_NODE environment variable. If both are provided, the fault uses TARGET_NODE. For more information, go to node label.

Optional tunables

Tunable Description Notes
TOTAL_CHAOS_DURATION Duration that you specify, through which chaos is injected into the target resource (in seconds). Default: 60 s. For more information, go to duration of the chaos.
LIB_IMAGE Image used to inject chaos. Default: chaosnative/chaos-go-runner:main-latest. For more information, go to image used by the helper pod.
RAMP_TIME Period to wait before and after injecting chaos (in seconds). For example, 30 s. For more information, go to ramp time.

Kill kubelet service

Name of the target node. Tune it by using the TARGET_NODE environment variable.

The following YAML snippet illustrates the use of this environment variable:

# kill the kubelet service of the target node
kind: ChaosEngine
name: engine-nginx
engineState: "active"
annotationCheck: "false"
chaosServiceAccount: litmus-admin
- name: kubelet-service-kill
# name of the target node
value: 'node01'
VALUE: '60'