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
MediumAddress
SecurityCompliance Standards
- CIS EKS
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
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: -
If your kubelet is also configured via systemd flags, ensure there is no conflicting
--event-record-qpsflag. Check the drop-in file:If you see--event-record-qps=...in anyKUBELET_*_ARGSvariable, edit the file to either remove that flag or set it to the same value (e.g., 0): -
Reload systemd unit files on the worker node:
-
Restart the kubelet on the worker node (this will briefly disrupt pod scheduling on that node):
-
Verify the kubelet process is running with the desired configuration on the worker node:
Confirm there is no conflicting
--event-record-qpsflag, or if present it matches the value you set in/var/lib/kubelet/config.yaml.
Using kubectl
Using kubectl
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.Automation
Automation

