-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Graduate Kubelet plugin registration/watcher to GA #70559
Graduate Kubelet plugin registration/watcher to GA #70559
Conversation
/sig node |
/retest |
1 similar comment
/retest |
@tallclair PTAL |
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.
/lgtm
Though I'm not sure why the Kubelet struct needed to be reformated?
@RenaudWasTaken thanks for review, not sure why my editor reformatted code after I updated kubelet to point to v1 package. Will take a look. Thanks. |
@vishh PTAL. Looking for approval for 1.13. |
Hmm.. Was the switch from alpha->GA discussed early on? What makes us believe that the existing API & behavior is what we'd like to maintain for at-least a year from now? |
@vishh Hi. This is to go from Beta -> GA. This feature has been in used for a while now. The reference to beta packages were not updated in last previous release. To answer your other questions: this API has been in used by may CSI drivers (https://kubernetes-csi.github.io/docs/Drivers.html). As CSI moves to GA this quarter, we feel this is one of the other API that could go GA as well. |
This feature defines how CSI drivers are discovered. GA of this feature is a blocker CSI GA (which we are planning for this 1.13 release). It also means that once CSI goes GA the requirements from CSI for this feature are unlikely to change since CSI it self needs to remain backwards compatible and backwards incompatible changes would break CSI). The existing API has been sufficient for CSI and we haven't changed it since alpha. The only known use cases that we are currently aware of that may require changing the API is adding windows support -- but that so far seems like it won't require any change or only additive change. |
I was misguided by the comment which changed from |
/priority important-soon |
@vishh Please re-approve. I had to rebase. |
@tallclair PTAL, looking for approval for this feature. |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saad-ali, vishh, vladimirvivien 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 |
/lgtm |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR contains code changes necessary to graduate the Kubelet Plugin Watcher registration mechanism from
Beta
toGA
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #70484
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE