-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Update pluginwatcher doc #68562
Update pluginwatcher doc #68562
Conversation
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.
Added couple of suggestions.
- Implements the Registration service specified in | ||
pkg/kubelet/apis/pluginregistration/v*/api.proto. | ||
Here are the general rules that Kubelet plugin developers should follow: | ||
- Run as 'root' user. Currently creating socket under PluginsDir, a root owned |
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.
Is that Run plugin as root
?
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.
Well your plugin should have the correct permissions to create and read any files in the plugin directory.
|
||
# Kubelet Internal API | ||
|
||
For internal kubelet clients using the pluginwatcher module, you will need to |
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.
is "internal kubelet client" been defined somewhere? i feel it is more clear to say: For any kubelet components
@@ -32,3 +42,25 @@ Here are the general rules that Kubelet plugin developers should follow: | |||
|
|||
- For an example plugin implementation, take a look at example_plugin.go | |||
included in this directory. | |||
|
|||
|
|||
# Kubelet Internal API |
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 same question, is "Kubelet internal API" been defined somewhere? thanks
5b32c05
to
a6659eb
Compare
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.
Rename file README.md so mark down will render properly.
/LGTM |
a6659eb
to
bf91fd8
Compare
@vladimirvivien done! |
bf91fd8
to
d37d24d
Compare
pluginwatcher module in kubelet.go by calling AddHandler(pluginType, handler). | ||
|
||
|
||
The lifecycle follows a simple Validate -> Register -> DeRegister state machine. |
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 ascii graph is off when render the file, add a extra blank line will work (find out by rendering a readme file in my local IDE).
d37d24d
to
339a89a
Compare
339a89a
to
7905629
Compare
/retest |
Fixed @figo |
/lgtm |
/assign @yujuhong |
ping @vishh for approval |
Maybe @saad-ali can help with approval on this docs PR :) ? |
Appreciate taking time to write this readme @RenaudWasTaken. Can you also add this text to the k8s device plugin docs page, or at-least link to this doc? /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RenaudWasTaken, vishh 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 |
Thanks @vishh ! Yep, I'll take care of the PR tomorrow! |
What this PR does / why we need it: Adds more documentation about the pluginwatcher process and development
Which issue(s) this PR fixes See issue kubernetes/enhancements#595 and issue #65773
Special notes for your reviewer:
/sig node
/kind documentation
/cc @vikaschoudhary16 @figo @sbezverk @saad-ali @vladimirvivien @jiayingz
Release note: