I couldn't understand how to run scheduler.

Question

I couldn't understand how to run scheduler.

zewenli98 opened this issue 4 years ago · comments

Hi there, I'm new to this field and I couldn't fully understand the README file. Could you give me some suggestions about some questions?

The first question is how to run scheduler with --policy-config-file=XXX --use-legacy-policy-config=true?

The second is what's XXX in --policy-config-file=XXX?

Any help would be appreciated!

Shengbo Song · Answer 1 · Tue Jul 21 2020 09:36:53 GMT+0800 (China Standard Time)

Hi there, I'm new to this field and I couldn't fully understand the README file. Could you give me some suggestions about some questions?

The first question is how to run scheduler with --policy-config-file=XXX --use-legacy-policy-config=true?

The second is what's XXX in --policy-config-file=XXX?

Any help would be appreciated!

Read this article to help you understand scheduler policy

Zewen (Evan) Li · Answer 2 · Wed Jul 22 2020 16:51:31 GMT+0800 (China Standard Time)

Thanks for the material. I got to know the scheduler policy. What I want to do now is to carry out the scheduler extender.

But when I run bin/gpu-admission --address=127.0.0.1:3456 --v=4 --config=build/gpu-admission.config --kubeconfig=/etc/kubernetes/admin.conf --policy-config-file=scheduler-policy-config.json --use-legacy-policy-config=true, I got the error unknown flag: --policy-config-file.

How can I fix it? Thanks in advance!

Shengbo Song · Answer 3 · Wed Jul 22 2020 18:56:02 GMT+0800 (China Standard Time)

Thanks for the material. I got to know the scheduler policy. What I want to do now is to carry out the scheduler extender.

But when I run bin/gpu-admission --address=127.0.0.1:3456 --v=4 --config=build/gpu-admission.config --kubeconfig=/etc/kubernetes/admin.conf --policy-config-file=scheduler-policy-config.json --use-legacy-policy-config=true, I got the error unknown flag: --policy-config-file.

How can I fix it? Thanks in advance!

--policy-config-file=XXX --use-legacy-policy-config=true is for kube-scheduler not gpu-admission.

Zewen (Evan) Li · Answer 4 · Wed Jul 22 2020 20:42:34 GMT+0800 (China Standard Time)

--policy-config-file=XXX --use-legacy-policy-config=true is for kube-scheduler not gpu-admission.

I also tried kube-scheduler --policy-config-file=scheduler-policy-config.json --use-legacy-policy-config=true, but got the error:

I0722 12:37:41.094767  428293 registry.go:150] Registering EvenPodsSpread predicate and priority function
I0722 12:37:41.094833  428293 registry.go:150] Registering EvenPodsSpread predicate and priority function
I0722 12:37:41.534391  428293 serving.go:313] Generated self-signed cert in-memory
failed to create listener: failed to listen on 0.0.0.0:10251: listen tcp 0.0.0.0:10251: bind: address already in use

Zewen (Evan) Li · Answer 5 · Fri Jul 24 2020 17:16:48 GMT+0800 (China Standard Time)

--policy-config-file=XXX --use-legacy-policy-config=true is for kube-scheduler not gpu-admission.

I also tried kube-scheduler --policy-config-file=scheduler-policy-config.json --use-legacy-policy-config=true, but got the error:
I0722 12:37:41.094767  428293 registry.go:150] Registering EvenPodsSpread predicate and priority function
I0722 12:37:41.094833  428293 registry.go:150] Registering EvenPodsSpread predicate and priority function
I0722 12:37:41.534391  428293 serving.go:313] Generated self-signed cert in-memory
failed to create listener: failed to listen on 0.0.0.0:10251: listen tcp 0.0.0.0:10251: bind: address already in use

By the way, the 10251 port is listened by default kube-scheduler:

@mYmNeo Could you help me figure it out? Thanks in advance!

Zewen (Evan) Li · Answer 6 · Sat Jul 25 2020 22:34:38 GMT+0800 (China Standard Time)

@mYmNeo Could you please offer more details?

Hong Yuchen · Answer 7 · Mon May 08 2023 17:45:38 GMT+0800 (China Standard Time)

Have you solved the problem?
I also encountered this problem, my k8s version is 1.24.10, what should I do?