You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The soundness guarantees of the CSI specification leave a little to be desired in our ability to provide a 100% reliable automated solution for managing volumes. We can bridge this gap by providing the operator the ability to intervene. (And make development easier!)
A new nomad volume detach command would accept the following arguments:
-node: Nomad node ID for the volume's attachment
:id: Nomad volume ID for the volume
It would do the following:
check any remaining claims to verify the allocations are terminal or nil.
trigger a NodeUnpublish and NodeUnstage.
trigger a ControllerUnpublish.
The text was updated successfully, but these errors were encountered:
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
The soundness guarantees of the CSI specification leave a little to be desired in our ability to provide a 100% reliable automated solution for managing volumes. We can bridge this gap by providing the operator the ability to intervene. (And make development easier!)
A new
nomad volume detach
command would accept the following arguments:-node
: Nomad node ID for the volume's attachment:id
: Nomad volume ID for the volumeIt would do the following:
NodeUnpublish
andNodeUnstage
.ControllerUnpublish
.The text was updated successfully, but these errors were encountered: