> ## Documentation Index
> Fetch the complete documentation index at: https://docs.siderolabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

> KubeSchedulerConfig configures kube-scheduler controlplane static pod.

# KubeSchedulerConfig

```yaml theme={null}
apiVersion: v1alpha1
kind: KubeSchedulerConfig
image: registry.k8s.io/kube-scheduler:v1.37.0-beta.0 # The container image used to run the kube-scheduler component.
# Provide configuration for the kube-scheduler static pod.
config:
    profiles:
        - plugins:
            score:
                disabled:
                    - name: PodTopologySpread
# Extra command line arguments to supply to the kube-scheduler.
extraArgs:
    feature-gates: AllBeta=true
```

<table>
  <thead>
    <tr>
      <th>Field</th>
      <th>Type</th>
      <th>Description</th>
      <th>Value(s)</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`enabled`</td>
      <td>bool</td>
      <td>By default, kube-scheduler static pod is enabled.<br />Set to false to disable the kube-scheduler (assuming it runs on other controlplane node).</td>

      <td />
    </tr>

    <tr>
      <td>`image`</td>
      <td>string</td>
      <td>The container image used to run the kube-scheduler component.<br /><br />The image reference should contain the tag, even if it is pinned by digest.</td>

      <td />
    </tr>

    <tr>
      <td>`config`</td>
      <td>Unstructured</td>
      <td>Provide configuration for the kube-scheduler static pod.<br /><br />There is no need to specify kind and apiVersion fields (they will be set automatically),<br />but the rest of the configuration should be provided as is.<br /><br />See [https://kubernetes.io/docs/reference/scheduling/config/](https://kubernetes.io/docs/reference/scheduling/config/) for the details of the configuration schema.</td>

      <td />
    </tr>

    <tr>
      <td>`extraArgs`</td>
      <td>Args</td>
      <td>Extra command line arguments to supply to the kube-scheduler.<br /><br />It is preferable to use `config` field to provide configuration overrides.</td>

      <td />
    </tr>

    <tr>
      <td>`env`</td>
      <td>map\[string]string</td>
      <td>The `env` field allows for the addition of environment variables for the kube-scheduler.</td>

      <td />
    </tr>

    <tr>
      <td>`resources`</td>
      <td><a href="#resources">ResourcesConfig</a></td>
      <td>Configure the kube-scheduler resources.</td>

      <td />
    </tr>
  </tbody>
</table>

## resources

ResourcesConfig represents the pod resources.

<table>
  <thead>
    <tr>
      <th>Field</th>
      <th>Type</th>
      <th>Description</th>
      <th>Value(s)</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`requests`</td>
      <td>Unstructured</td>
      <td>Requests configures the reserved cpu/memory resources.</td>

      <td />
    </tr>

    <tr>
      <td>`limits`</td>
      <td>Unstructured</td>
      <td>Limits configures the maximum cpu/memory limits a pod can use.</td>

      <td />
    </tr>
  </tbody>
</table>