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 followingSo 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

apiVersion: v1
kind: Pod
metadata:
  labels:
    component: kube-scheduler
    tier: control-plane
  name: kube-scheduler
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-scheduler
    - --port=0	# <--- Enter the value 10251 for the scheduler, 10252 for the controllerManager
.
.
.