More Info:
Limit the rate at which the API server accepts requests.Risk Level
LowAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
Create an EventRateLimit configuration file (on every control plane node)
-
Back up the existing API server manifest (on every control plane node)
-
Edit the API server manifest to enable EventRateLimit and reference the config file (on every control plane node)
Open the file:Then edit it with a text editor (for example):In thespec.containers[0].command(the list of- --flag=valuelines), ensure:- The
--enable-admission-pluginsflag includesEventRateLimitin the comma‑separated list, for example: - Add or update the admission config file flag to point to the file you created:
- The
-
Allow the API server static pod to restart automatically
Saving the manifest under/etc/kubernetes/manifests/will cause the kubelet on the control plane node to restart thekube-apiserverpod. No additional command is required, but expect a brief control‑plane disruption during restart. -
Verify the API server process flags include EventRateLimit and the config file (on every control plane node)
Confirm the output contains:
--enable-admission-plugins=...EventRateLimit...--admission-control-config-file=/etc/kubernetes/admission/event-rate-limit.yaml
Using kubectl
Using kubectl
kubectl cannot modify kube-apiserver process flags or the static pod manifest at
/etc/kubernetes/manifests/kube-apiserver.yaml, so this finding cannot be remediated through Kubernetes API objects. To address it, you must edit the manifest and related configuration directly on every control plane node; see the Manual Steps section for the required host-level changes.Automation
Automation

