-
Notifications
You must be signed in to change notification settings - Fork 1.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
CSI Volume Attachment/Detachment #6904
Comments
Partially for my own understanding and to help sync up understanding in a discussion with @langmartin, I've broken this down in a little more detail into something that might make a good section of the RFC at some point: Publishing VolumesWhen the client receives an allocation which includes a CSI volume, the alloc runner will block its main
Tasks:
Unpublishing VolumesWhen an alloc is marked terminal, the client will issue a The Tasks:
Node FailureThe unpublishing workflow above assumes the cooperation of a healthy client that can report that allocs are terminal. There will be two ways we'll reconcile this:
Tasks:
|
@tgross This sgtm |
Going to close this in lieu of the broken-out issues. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
This is a placeholder issue for designing how nomad servers should manage the attachment of CSI Volumes, and how they should eventually be detached from a node.
Considerations
The text was updated successfully, but these errors were encountered: