-
Notifications
You must be signed in to change notification settings - Fork 39.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
promote DisableNodeKubeProxyVersion feature gate to beta #123845
promote DisableNodeKubeProxyVersion feature gate to beta #123845
Conversation
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. |
656815c
to
00e5075
Compare
/cc @danwinship |
Changelog suggestion -Set the DisableNodeKubeProxyVersion feature gate to be enabled by default.. it will stop setting the KubeProxyVersion field.
+Graduated the `DisableNodeKubeProxyVersion` feature gate to beta.
+By default, the kubelet no longer attempts to set the `.status.kubeProxyVersion` field for its associated
+Node. |
/remove-sig api-machinery |
/triage accepted |
/sig network |
|
||
if len(kpv) != 0 { | ||
return fmt.Errorf("node %s had kube-proxy version %s which should be empty", | ||
n.ObjectMeta.Name, kpv) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test shouldn't just assume that the feature gate is set to its default value; you can run the tests with various combinations of feature gates.
You can either check the feature gate here and then check the appropriate result depending on that, or else ignore the feature gate and make the test accept either value ("empty" or "matches kubelet version").
(Yeah, this should have been changed in alpha.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can either check the feature gate here and then check the appropriate result depending on that, or else ignore the feature gate and make the test accept either value ("empty" or "matches kubelet version").
We can't seem to detect whether the feature gate is enable in the e2e test, so I choose accept either value.
/milestone v1.31 |
00e5075
to
98c29f0
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
/lgtm
/approve
LGTM label has been added. Git tree hash: 1f88789001d332db35d8ebf5e6ff90d356846c6b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HirazawaUi, thockin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
this is clearing a GA field, we should have given a year from deprecation announcement before defaulting on (announced in 1.29, default on in 1.33) reverting in #126720 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
In KEP, we plan to promote the DisableNodeKubeProxyVersion feature gate to the beta version in version 1.31
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: