Skip to content

Commit

Permalink
add migration docs for scheduler component config api from v1beta2 to…
Browse files Browse the repository at this point in the history
… v1beta3

Signed-off-by: kerthcet <[email protected]>
  • Loading branch information
kerthcet committed Nov 9, 2021
1 parent c059c31 commit 490b875
Showing 1 changed file with 14 additions and 27 deletions.
41 changes: 14 additions & 27 deletions content/en/docs/reference/scheduling/config.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,7 @@ by implementing one or more of these extension points.

You can specify scheduling profiles by running `kube-scheduler --config <filename>`,
using the
KubeSchedulerConfiguration ([v1beta1](/docs/reference/config-api/kube-scheduler-config.v1beta1/)
or [v1beta2](/docs/reference/config-api/kube-scheduler-config.v1beta2/))
KubeSchedulerConfiguration ([v1beta2](/docs/reference/config-api/kube-scheduler-config.v1beta2/))
struct.

A minimal configuration looks as follows:
Expand Down Expand Up @@ -179,30 +178,6 @@ that are not enabled by default:
volume limits can be satisfied for the node.
Extension points: `filter`.

The following plugins are deprecated and can only be enabled in a `v1beta1`
configuration:

- `NodeResourcesLeastAllocated`: Favors nodes that have a low allocation of
resources.
Extension points: `score`.
- `NodeResourcesMostAllocated`: Favors nodes that have a high allocation of
resources.
Extension points: `score`.
- `RequestedToCapacityRatio`: Favor nodes according to a configured function of
the allocated resources.
Extension points: `score`.
- `NodeLabel`: Filters and / or scores a node according to configured
{{< glossary_tooltip text="label(s)" term_id="label" >}}.
Extension points: `filter`, `score`.
- `ServiceAffinity`: Checks that Pods that belong to a
{{< glossary_tooltip term_id="service" >}} fit in a set of nodes defined by
configured labels. This plugin also favors spreading the Pods belonging to a
Service across nodes.
Extension points: `preFilter`, `filter`, `score`.
- `NodePreferAvoidPods`: Prioritizes nodes according to the node annotation
`scheduler.alpha.kubernetes.io/preferAvoidPods`.
Extension points: `score`.

### Multiple profiles

You can configure `kube-scheduler` to run more than one profile.
Expand Down Expand Up @@ -285,10 +260,22 @@ only has one pending pods queue.
* A plugin enabled in a v1beta2 configuration file takes precedence over the default configuration for that plugin.

* Invalid `host` or `port` configured for scheduler healthz and metrics bind address will cause validation failure.
{{% /tab %}}

{{% tab name="v1beta2 → v1beta3" %}}
* Increase the default weight of three plugins:
* `InterPodAffinity` from 1 to 2
* `NodeAffinity` from 1 to 2
* `TaintToleration` from 1 to 3

* The legacy scheduler policy config is removed, the associated flags `policy-config-file`, `policy-configmap`, `policy-configmap-namespace` and `use-legacy-policy-config` are also removed.

* The scheduler v1beta1 configuration version is unsupported.

* The scheduler plugins `ServiceAffinity`, `NodeLabel`, `NodePreferAvoidPods`, `NodeResourcesLeastAllocated`, `NodeResourcesMostAllocated` and `RequestedToCapacityRatio` are removed.
{{% /tab %}}
{{< /tabs >}}

{{< /tabs >}}
## {{% heading "whatsnext" %}}

* Read the [kube-scheduler reference](/docs/reference/command-line-tools-reference/kube-scheduler/)
Expand Down

0 comments on commit 490b875

Please sign in to comment.