Replies: 3 comments
-
Check the k3s docs for information on how to pass args to the scheduler: https://docs.k3s.io/cli/server#customized-flags-for-kubernetes-processes |
Beta Was this translation helpful? Give feedback.
-
there is no document in the link you provide custom args say nothing... could you give a better document how to use that? |
Beta Was this translation helpful? Give feedback.
-
In your example pod spec - from wherever you got that - it says: command:
- kube-scheduler
- --config=/etc/kubernetes/scheduler-config.yaml # Point to your config For k3s, as the page I referenced says, you pass args to kube-scheduler via kube-scheduler-arg:
- --config=/etc/kubernetes/scheduler-config.yaml # Point to your config As the comment suggests you can put that scheduler config file wherever you want on the node, you just need to provide the correct path in the arg. |
Beta Was this translation helpful? Give feedback.
-
i'm trying to setup kubescheduler inside my k3S cluster
Environmental Info:
K3s Version: 1.30
Node(s) CPU architecture, OS, and Version:
three arm64 node, and 2 amd64 node
Cluster Configuration:
"3 servers, 2 agents"
Describe the bug:
i want to apply a kube scheduler config but crd not exist:
Steps To Reproduce:
apply this config
Expected behavior:
existing crd
Actual behavior:
not exist
Additional context / logs:
Beta Was this translation helpful? Give feedback.
All reactions