More Info:
Do not disable timeouts on streaming connections.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every worker node, check whether kubelet uses a config file and/or flags:
Review the command line for
--config=and--streaming-connection-idle-timeout=. -
If
/var/lib/kubelet/config.yamlis in use, edit it to ensure the timeout is non‑zero:If the key does not exist or is set differently, open the file and add or adjust it under the top-level config:and set: -
If kubelet uses command-line flags via systemd, edit the drop-in file on each worker node:
In the
Environment=line that defines kubelet args, either:- Replace any existing
--streaming-connection-idle-timeout=0with: - Or, if it is missing, append:
- Replace any existing
-
Reload systemd and restart kubelet on each worker node so changes take effect:
-
Verify kubelet is running with a non‑zero streaming idle timeout on each worker node:
Confirm in the output that:
--streaming-connection-idle-timeout=5mis present (if using flags), and- There is no
--streaming-connection-idle-timeout=0.
Using kubectl
Using kubectl
kubectl cannot modify kubelet process flags or its config file on worker nodes, so this finding cannot be fixed via the Kubernetes API. To remediate, edit
/var/lib/kubelet/config.yaml or the kubelet systemd drop-in on each worker node as described in the Manual Steps section.Automation
Automation

