Detections
Analytics

1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Verify kubelet's certificate before establishing connection.

Rationale:

The connections from the apiserver to the kubelet are used for fetching logs for pods, attaching (through kubectl) to running pods, and using the kubelet's port-forwarding functionality. These connections terminate at the kubelet's HTTPS endpoint. By default, the apiserver does not verify the kubelet's serving certificate, which makes the connection subject to man-in-the-middle attacks, and unsafe to run over untrusted and/or public networks.

Impact:

You require TLS to be configured on apiserver as well as kubelets.

Solution

Follow the Kubernetes documentation and setup the TLS connection between the apiserver and kubelets. Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.

--kubelet-certificate-authority=<ca-string>

Default Value:

By default, --kubelet-certificate-authority argument is not set.

See Also

https://workbench.cisecurity.org/files/2968

Item Details

References: CSCv6|3.4, CSCv7|4.5

Plugin: Unix

Control ID: fbd0595bc0cb715b6cb5a708ca40ab99e566e5cf35156d7e5979286736f65dff