Kube scheduler config not recognized

[didlawowo]

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:

# scheduler-config.yaml
apiVersion: kubescheduler.config.k8s.io/v1
kind: KubeSchedulerConfiguration
metadata:
  name: custom-scheduler-config
profiles:
- schedulerName: default-scheduler
  plugins:
    score:
      disabled:
      - name: NodeResourcesBalancedAllocation
      - name: NodeResourcesFit
      enabled:
      - name: NodePreferAvoid
        weight: 100
  pluginConfig:
  - name: NodePreferAvoid
    args:
      scoreStrategy:
        type: MostAllocated
        resources:
        - name: cpu
          weight: 1
        - name: memory
          weight: 1
      preferredNodes:
      - nodeSelectorTerms:
        - matchExpressions:
          - key: kubernetes.io/hostname
            operator: In
            values:
            - ryzen
      avoidNodes:
      - nodeSelectorTerms:
        - matchExpressions:
          - key: kubernetes.io/hostname
            operator: In
            values:
            - rtx

---
# Apply this to your kube-scheduler configuration in /etc/kubernetes/manifests/kube-scheduler.yaml
apiVersion: v1
kind: Pod
metadata:
  name: kube-scheduler
  namespace: kube-system
spec:
  containers:
  - name: kube-scheduler
    image: k8s.gcr.io/kube-scheduler:v1.30.0 # Use your cluster's version
    command:
    - kube-scheduler
    - --config=/etc/kubernetes/scheduler-config.yaml # Point to your config
    volumeMounts:
    - mountPath: /etc/kubernetes/scheduler-config.yaml
      name: scheduler-config
      readOnly: true
  volumes:
  - name: scheduler-config
    hostPath:
      path: /etc/kubernetes/scheduler-config.yaml
      type: File

Steps To Reproduce:
apply this config

Expected behavior:
existing crd

Actual behavior:
not exist

Additional context / logs:

The Kubernetes API could not find kubescheduler.config.k8s.io/KubeSchedulerConfiguration for requested resource kube-infra/custom-scheduler-config. Make sure the "KubeSchedulerConfiguration" CRD is installed on the destination cluster.

[brandond]

1. This is a config file. You point the scheduler at it via the --config=/etc/kubernetes/scheduler-config.yaml arg. You do NOT apply it to the cluster.
2. K3s does not run the scheduler in a pod, and does not store anything in /etc/kubernetes/manifests, so following instructions to modify pod manifests there is not correct. Are you following instructions written for a different Kubernetes distro? Also it looks like you ignored the instructions in the comments of the manifest you found.

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

[didlawowo]

1. This is a config file. You point the scheduler at it via the --config=/etc/kubernetes/scheduler-config.yaml arg. You do NOT apply it to the cluster.
2. K3s does not run the scheduler in a pod, and does not store anything in /etc/kubernetes/manifests, so following instructions to modify pod manifests there is not correct. Are you following instructions written for a different Kubernetes distro? Also it looks like you ignored the instructions in the comments of the manifest you found.

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

there is no document in the link you provide custom args say nothing...

could you give a better document how to use that?

[brandond]

In your example pod spec - from wherever you got that - it says:

    - 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. So you in the k3s config, you would want to set:

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.