Connection refused for KubeScheduler and KubeControllerManager
The origin of this problem is similar for both components. We present the solution for the scheduler, which will be easily applicable for the controllerManager as well. Going to the Status/Targets section of the Prometheus UI you should see a situation similar to the following/etc/kubernetes/manifests
folder. Inside we will find the kube-controller-manager.yaml
and kube-scheduler.yaml
files. Using a text editor, we edit the two files as follows
As for the controllerManager, you must enter the value 10252. Note that the number of ports mentioned here corresponds to the values of the ports present in the Endpoint
column in the screenshot of the Prometheus UI. After this change the state should change from DOWN
to UP.