...
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
So let's connect to the control-plane and move to the /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 (administrator permissions are likely required)
...
Connection refused for KubeProxy
The If you get the following error it's because the metrics bind address of kube-proxy is default to 127.0.0.1:10249 that , that prometheus instances cannot access to. You should expose metrics by changing metricsBindAddress field value to 0.0.0.0:10249 if , if you want to collect them. To
To perform the modification, we access, in editing mode, the kube-proxy ConfigMap
...