1.2.3 Ensure that the --kubelet-https argument is set to true

Warning! Audit Deprecated

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

View Next Audit Version

Information

Use https for kubelet connections.

Rationale:

Connections from apiserver to kubelets could potentially carry sensitive data such as secrets and keys. It is thus important to use in-transit encryption for any communication between the apiserver and kubelets.

Impact:

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

Solution

Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and remove the --kubelet-https parameter.

Default Value:

By default, kubelet connections are over https.

See Also

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

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-8(1), CSCv6|14.2, CSCv7|14.4

Plugin: Unix

Control ID: 41c4cf02dd14b364021f14f29483744cba67299b9c71e8b8fbdf10cfd5878c20