-
Notifications
You must be signed in to change notification settings - Fork 2k
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
docs: updates for CSI plugin improvements for 1.3.0 #12466
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.
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! just the one thought
tasks last. | ||
|
||
Typically, you should run node plugins as Nomad `system` jobs so they | ||
can mount volumes on any client in a datacenter. Controller plugins |
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.
can mount volumes on any client in a datacenter. Controller plugins | |
can mount volumes on any client in a cluster. Controller plugins |
Unless datacenter
is intentional (?)
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.
It was intentional, because a system job runs across the specific datacenter they're deployed in and not the whole cluster. But on second thought there can be more than 1 DC for a given system job and that makes it read awkwardly. Maybe "can mount volumes on any client where they are running"?
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Preview links: