Ensure that the –tls-cert-file and –tls-private-key-file arguments are set as appropriate
| Property | |
|---|---|
| Language | |
| Severity |
Description#
The Kubernetes API server is not configured with the –tls-cert-file and –tls-private-key-file flags, meaning it may accept unencrypted connections. This leaves API traffic vulnerable to interception and tampering.
Impact#
Without TLS, sensitive data—including authentication tokens and cluster configuration—can be exposed to network attackers. This could allow unauthorized access, credential theft, or manipulation of cluster operations, undermining the entire security of the Kubernetes environment.
Resolution#
Follow the Kubernetes documentation and set up the TLS connection on the apiserver. Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the TLS certificate and private key file parameters.