Hey! In the Multiple Schedule custom scheduler I am having a few doubts, would b . . .

Kubernetes
#1

Sayan Mondal:
Hey! In the Multiple Schedule custom scheduler I am having a few doubts, would be great if someone could clarify the same

When creating a custom scheduler my scheduler keeps crashing and restating if I don’t provide the

command:
- --secure-port=0

What does it exactly do?

My scheduler is in a continuous CrashLoopBackOff can someone please help me identify the issue, besides the secure-port I’ve pasted the yaml in the thread

• Does the --port and probes port have to be same?
• When I change the metadata.labels.component to my-scheduler from kube-scheduler I’m getting a new pod my-scheduler-controlplane Why is this happening?
• Why are we not changing spec.containers.name where exactly is it being used?

#2

Hello @Sayan Mondal
The default scheduler uses secure-port on port 10259 to serve HTTPS with authentication and authorization. This is not needed for our custom scheduler, so we can disable HTTPS by setting the value of secure-port to 0.

And when you create a static pod, its name is shown as “pod name + node name”.
Also, the container name can be the same in both because they are two different pods. so no need to change the container name.

Thanks,
KodeKloud Support