Ensure that the --streaming-connection-idle-timeout argument is not set to 0

MediumLevel 1Automatedopenshift

Description

Do not disable timeouts on streaming connections. Reads every node's effective kubelet configuration with oc get --raw /api/v1/nodes/<node>/proxy/configz; requires a cluster-admin oc login. A missing value means the 4h default.

How it is checked

Audit method: Shell command

shell

nodes=$(oc get nodes -o jsonpath='{range .items[*]}{.metadata.name}{"\n"}{end}') || exit 1
[ -n "$nodes" ] || exit 1
ok=1
for n in $nodes; do
  c=$(oc get --raw "/api/v1/nodes/$n/proxy/configz") || exit 1
  if ! { ! printf '%s' "$c" | grep -Eq '"streamingConnectionIdleTimeout":"0s"'; }; then echo "noncompliant: $n"; ok=0; fi
done
if [ "$ok" -eq 1 ]; then echo compliant; fi

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Follow the instructions in the documentation to create a kubeletconfig CRD and set the streamingConnectionIdleTimeout to the desired value. Do not set the value to 0.

Properties

Operating systems: Any
Tags: openshiftworker-nodekubelet
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 4.2.6 Ensure that the --streaming-connection-idle-timeout argument is not set to 0

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target openshift