Skip to content
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: add -force flag to volume deregister #8251

Closed
tgross opened this issue Jun 23, 2020 · 1 comment · Fixed by #8295
Closed

CSI: add -force flag to volume deregister #8251

tgross opened this issue Jun 23, 2020 · 1 comment · Fixed by #8295

Comments

@tgross
Copy link
Member

tgross commented Jun 23, 2020

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.

@github-actions
Copy link

github-actions bot commented Nov 5, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant