Hi All, I am unable to deploy custom scheduler. I updated the following options . . .

Kubernetes
#1

Shalini:
Hi All, I am unable to deploy custom scheduler. I updated the following options along with the port in the custom-scheduler but I keep getting error saying address already in use

 containers:
  - command:
    - kube-scheduler
    - --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
    - --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
    - --bind-address=127.0.0.1
    - --scheduler-name=my-scheduler
    - --lock-object-name=my-scheduler
    - --kubeconfig=/etc/kubernetes/scheduler.conf
    - --leader-elect=false
    image: <http://k8s.gcr.io/kube-scheduler:v1.19.0|k8s.gcr.io/kube-scheduler:v1.19.0>
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10260
        scheme: HTTPS
#2

unnivkn:
please refer the solution /var/answers

#3

Mani:
you should define --port otherwise it will take 10259 by default

#4

Saravanakumar Raju:
use --secure-port

#5

Saravanakumar Raju:

image.png
image.png726×178 44.4 KB

#6

Rocky:
hi @Shalini - Pls refer to the https://app.slack.com/client/TDSBA9B9V/CHMV3P9NV/thread/CHMV3P9NV-1613871659.027900|thread for custom scheduler explanation by @Craig Shea; this should clear all your question.

#7

Shalini:
Thanks everyone