Set up the kubernetes integration.
Do not bind the Controller Manager service to non-loopback insecure addresses.
The Controller Manager API service which runs on port 10252/TCP by default is used for health and metrics information and is available without authentication or encryption. As such it should only be bound to a localhost interface, to minimize the cluster’s attack surface
Run the following command on the master node:
ps -ef | grep kube-controller-manager
Verify that the
--bind-address argument is set to
Edit the Controller Manager pod specification file
/etc/kubernetes/manifests/kube-controller-manager.yaml on the master node and ensure the correct value for the
By default, the
--bind-address parameter is set to
Notes: Although the current Kubernetes documentation site says that
--address is deprecated in favour of
--bind-address. Kubeadm 1.11 still makes use of
Version 6.9.1 Limit Open Ports, Protocols, and Services - Ensure that only ports, protocols, and services with validated business needs are running on each system.
Version 7.9.2 Ensure Only Approved Ports, Protocols and Services Are Running - Ensure that only network ports, protocols, and services listening on a system with validated business needs, are running on each system.