Hi I am trying to create a second scheduler in my env but it failed..Appreciate . . .

Kubernetes
#1

Edmund Kueh:
Hi I am trying to create a second scheduler in my env but it failed…Appreciate some advise here: Below is the kube-scheduler.yml file for the 2nd scheduler. Do I need to change the port to some other port number ? Do I need to set leader-elect to be false for the first and second scheduler ? The original scheduler is failing…

image.png
image.png790×52 4.41 KB

image.png

#2

Edmund Kueh:
Do I need to set --lock-object-name for the 2nd scheduler ?

#3

Mohamed Sabe:
you should change the labels under metadata to be > component: my-scheduler & also check the ports

#4

Edmund Kueh:
After changing the metadata, my custom scheduler is fine…but the original scheduler has crashed…

image.png
image.png744×94 4.98 KB

#5

Tej_Singh_Rana:
Hello, @Edmund Kueh
Can you please share the output of?

$ kubectl describe po <scheduler-name> -n <namespace>
#6

Edmund Kueh:
This is the YML file for my custom scheduler. I have specified a different port no
image.png

#7

Edmund Kueh:
@Tej_Singh_Rana This is the output from k describe pod for the original scheduler

image.png
image.png1462×379 24.7 KB

#8

Tej_Singh_Rana:
what about logs?

#9

Tej_Singh_Rana:

$ kubectl logs <pod-name> -n kube-system
#10

Md Ishaq R:
@Tej_Singh_Rana just a quick question , as i see @Edmund Kueh is trying to create the second scheduler as a static , where as it has to be created as a normal scheduler if i am not wrong

#11

Md Ishaq R:
and if @Edmund Kueh is trying to create a static scheduler , he has to change the --port to --secure-port: 2060 and also change livernes port as per the --secure-port

#12

Tej_Singh_Rana:
But he is trying in his local env.

#13

Tej_Singh_Rana:
If it’s possible can you please share your yaml file?

#14

Md Ishaq R:

Inkedissue 2_LI.jpg
Inkedissue 2_LI.jpg804×632 106 KB

#15

Md Ishaq R:
the port under liveness port and the --secure-port should be same

#16

Md Ishaq R:
and the port should be different from the orginal scheduler file

#17

Edmund Kueh:
What does --secure-port flag used for ? Can it be any port no ?

#18

Md Ishaq R:
as mentioned in the file the orginal port is 10258 example you can give it 10259

#19

Md Ishaq R:
–secure-port int Default: 10259 The port on which to serve HTTPS with authentication and authorization.If 0, don’t serve HTTPS at all. use it to not conflict with the default one. you can check more about kube-schedular options from official documentation, please check here
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/