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!)
The nomad volume deregister command currently returns an error if the volume has any claims. A -force flag would do the following:
warn the operator
delete the volume from the state store, implicitly dropping all claims
Note that this would not also unmount/detach the volume, which we'll make the responsibility of a nomad volume detach command if the volumewatcher can't do the job.
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!)
The
nomad volume deregister
command currently returns an error if the volume has any claims. A-force
flag would do the following:Note that this would not also unmount/detach the volume, which we'll make the responsibility of a
nomad volume detach
command if the volumewatcher can't do the job.The text was updated successfully, but these errors were encountered: