The solution given is also not working while creating multi scheduler called my- . . .

Kubernetes-Slack Discussions
#1

Dhivagar K:
the solution given is also not working while creating multi scheduler called my-scheduler

#2

Mohamed Ayman:
you should change the port and use --secure-port=0 option. Please check the following:

apiVersion: v1
kind: Pod
metadata:
 annotations:
 <http://scheduler.alpha.kubernetes.io/critical-pod|scheduler.alpha.kubernetes.io/critical-pod>: ""
 creationTimestamp: null
 labels:
 component: my-scheduler
 tier: control-plane
 name: my-scheduler
namespace: kube-system
spec:
 containers:
- command:
- kube-scheduler
- --address=127.0.0.1
- --kubeconfig=/etc/kubernetes/scheduler.conf
- --leader-elect=false
- --port=10282
- --scheduler-name=my-scheduler
- --secure-port=0
 image: <http://k8s.gcr.io/kube-scheduler-amd64:v1.16.0|k8s.gcr.io/kube-scheduler-amd64:v1.16.0>
 imagePullPolicy: IfNotPresent
 livenessProbe:
 failureThreshold: 8
 httpGet:
 host: 127.0.0.1
 path: /healthz
 port: 10282
 scheme: HTTP
 initialDelaySeconds: 15
 timeoutSeconds: 15
 name: kube-scheduler
 resources:
 requests:
 cpu: 100m
 volumeMounts:
- mountPath: /etc/kubernetes/scheduler.conf
 name: kubeconfig
 readOnly: true
 hostNetwork: true
 priorityClassName: system-cluster-critical
 volumes:
- hostPath:
 path: /etc/kubernetes/scheduler.conf
 type: FileOrCreate
 name: kubeconfig
#3

Mohamed Ayman:
you need to deploy the custom scheduler using kubectl apply not as static POD.