Skip to content

Commit

Permalink
Merge pull request #3315 from kerthcet/feature/ga-conponent-config
Browse files Browse the repository at this point in the history
graduate kube-scheduler ComponentConfig to GA
  • Loading branch information
k8s-ci-robot authored Jun 6, 2022
2 parents ed335b3 + 5c920af commit 5320deb
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion keps/sig-scheduling/785-scheduler-component-config-api/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,9 @@

The kube-scheduler configuration API `kubescheduler.config.k8s.io` was in alpha
for several releases. We graduated it to beta in 1.19 as `v1beta1`. We introduced
`v1beta2` and `v1beta3` in 1.22 and 1.23 respectively.
`v1beta2` and `v1beta3` in 1.22 and 1.23 respectively. We'd like to graduate it
to GA in 1.25 and mark `v1beta2` as deprecated to avoid breaking existing users,
we'll remove the support of `v1beta2` in 1.26.

## Motivation

Expand Down Expand Up @@ -108,6 +110,10 @@ The third iteration, `kubescheduler.config.k8s.io/v1beta3`, includes the followi
The main reason is that some plugins have "default" behavior without needing user inputs, whereas the above plugins are
about user preferences, so should have more influence while making scheduling decisions.
More information on the discussion can be found [here](https://github.com/kubernetes/kubernetes/issues/88174).

The fourth iteration, `kubescheduler.config.k8s.io/v1`, includes the following changes:
- Mark `v1beta2` as deprecated

### Risks and Mitigations

The major risk is around the removal of the `unreserve` extension point.
Expand Down Expand Up @@ -219,6 +225,9 @@ N/A
- No changes to plugins enabled by default. Only their weights would change.
- Remove `v1beta1`.

When `v1` gets introduced:
- Mark `v1beta2` as deprecated.

### Monitoring requirements

* **How can an operator determine if the feature is in use by workloads?**
Expand Down Expand Up @@ -302,3 +311,4 @@ N/A
- 2021-07-08: Introducing `v1beta2`.
- 2021-08-06: Introducing `v1beta3`.
- 2021-09-01: Remove `v1beta1` and the legacy policy config API.
- 2022-05-18: Introducing `v1` and mark `v1beta2` as deprecated.

0 comments on commit 5320deb

Please sign in to comment.