You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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

Modify kube-scheduler.yaml 
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
.
.
.

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.

--port

Moving to the official documentation we get some info regarding the --port parameter

--port int     Default: 10251

The port on which to serve HTTP insecurely without authentication and authorization. If 0, don't serve plain HTTP at all.

Since the default is port 10251, deleting or commenting the parameter would have the same result.

  • No labels