Skip to main content

More Info:

The kubelet —event-qps argument should be set to a level that ensures appropriate event capture. Proper event capture supports auditing and troubleshooting of node activity.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS OKE

Triage and Remediation

Remediation

Manual Steps

  1. On every worker node, open the kubelet systemd drop-in configuration for editing:
  2. In the ExecStart= line, add or adjust the --event-qps flag so it is explicitly set to 0 (or your chosen value that ensures appropriate capture). For example:
    Ensure there is only one --event-qps flag present.
  3. If your kubelet also uses a config file at /etc/kubernetes/kubelet-config.json, ensure it does not conflict. Either remove any eventQPS entry or set it consistently:
    Example JSON snippet:
  4. Reload systemd configuration on the worker node:
  5. Restart kubelet on the worker node (note: this briefly disrupts the node’s workloads):
  6. Verify on the worker node that kubelet is running with the desired --event-qps setting:
    Confirm the output includes --event-qps=0 (or your chosen value).
kubectl cannot modify kubelet process flags or the /etc/kubernetes/kubelet-config.json and systemd unit files on worker nodes. To remediate this finding, you must change the kubelet configuration on each worker node’s host OS (for example, /etc/systemd/system/kubelet.service.d/00-default.conf and the kubelet config file) as described in the Manual Steps section.