Skip to main content

More Info:

The eventRecordQPS setting caps the rate at which the kubelet records events. Setting it to 0 or a suitable level ensures appropriate event capture for auditing and troubleshooting.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS EKS

Triage and Remediation

Remediation

Manual Steps

  1. On every worker node, open the kubelet config file and set eventRecordQPS (example sets it to 0 for unlimited; adjust as needed):
    Add or modify the key under the top-level config (or appropriate section) so it reads:
  2. If your kubelet is also configured via systemd flags, ensure there is no conflicting --event-record-qps flag. Check the drop-in file:
    If you see --event-record-qps=... in any KUBELET_*_ARGS variable, edit the file to either remove that flag or set it to the same value (e.g., 0):
  3. Reload systemd unit files on the worker node:
  4. Restart the kubelet on the worker node (this will briefly disrupt pod scheduling on that node):
  5. Verify the kubelet process is running with the desired configuration on the worker node:
    Confirm there is no conflicting --event-record-qps flag, or if present it matches the value you set in /var/lib/kubelet/config.yaml.
kubectl cannot modify kubelet process flags or the /var/lib/kubelet/config.yaml file on worker nodes; this setting must be changed directly on each node’s host configuration (e.g., kubelet config file or systemd unit). Refer to the Manual Steps section for the exact on-node remediation and verification commands.