443fdaa86b
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. This changeset provides a new command to bridge this gap by providing the operator the ability to intervene. The command doesn't take an allocation ID so that the operator doesn't have to keep track of alloc IDs that may have been GC'd. Handle this case in the unpublish RPC by sending the client RPC for all the terminal/nil allocs on the selected node.
29 lines
669 B
Plaintext
29 lines
669 B
Plaintext
---
|
|
layout: docs
|
|
page_title: 'Commands: volume detach'
|
|
sidebar_title: detach
|
|
description: |
|
|
Detach volumes with CSI plugins.
|
|
---
|
|
|
|
# Command: volume detach
|
|
|
|
The `volume detach` command detaches external storage volumes with Nomad's
|
|
[Container Storage Interface (CSI)][csi] support.
|
|
|
|
## Usage
|
|
|
|
```plaintext
|
|
nomad volume detach [options] [volume] [node]
|
|
```
|
|
|
|
The `volume detach` command requires two arguments, specifying the ID of the
|
|
volume to be detached and the node to detach it from. Detaching will fail if
|
|
the volume is still in use by an allocation.
|
|
|
|
## General Options
|
|
|
|
@include 'general_options.mdx'
|
|
|
|
[csi]: https://github.com/container-storage-interface/spec
|