[KEP-4330] add min-compatibility-version to control plane.#133980
[KEP-4330] add min-compatibility-version to control plane.#133980k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
/ok-to-test |
feb91e9 to
a8ba894
Compare
64143b9 to
ff3b786
Compare
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
|
/triage accepted |
|
/remove-sig etcd |
|
/remove-kind api-change |
538aa74 to
bebc3ce
Compare
liggitt
left a comment
There was a problem hiding this comment.
/approve
one doc suggestion, lgtm otherwise
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, siyuanfoundation The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Siyuan Zhang <[email protected]>
|
/cc @sttts |
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 7a00c3a119eee72d1a787749c0a14912401e9c5b |
|
Changelog tweak (suggested) -new `--min-compatibility-version` flag for apiserver, kcm and kube schedule
+Added a new `--min-compatibility-version` command line setting for kube-apiserver, kube-controller-manager and kube-scheduler. |
Updated PR description. Thanks for the suggestion! |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Adding the --min-compatibility-version part of KEP-4330
The biggest change is adding
MinCompatibilityVersionfield in feature spec, which allows setting the feature at different stages based on the server --min-compatibility-version. The usage of MinCompatibilityVersion for CEL and storage version is already in place.This PR also exposes the
--min-compatibility-versionflag in apiserver, kcm and scheduler.The
MinCompatibilityVersionfeature unlocks the option to accelerate the adoption of some features that can be accelerated if there is no backward compatibility concerns.Which issue(s) this PR is related to:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: