Skip to content

Commit

Permalink
Relationship betw cray.nnf.node.drain taint and Storage resource.
Browse files Browse the repository at this point in the history
Signed-off-by: Dean Roehrich <[email protected]>
  • Loading branch information
roehrich-hpe committed Jul 31, 2024
1 parent daed78b commit ac9bb89
Showing 1 changed file with 18 additions and 0 deletions.
18 changes: 18 additions & 0 deletions docs/guides/node-management/drain.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,30 @@ as it cleans up the NNF pods.
kubectl taint node $NODE cray.nnf.node.drain=true:NoSchedule cray.nnf.node.drain=true:NoExecute
```

This will cause the node's `Storage` resource to be disabled:

```console
$ kubectl get storages
NAME STATE STATUS MODE AGE
rabbit1 Enabled Disabled Live 3m18s
rabbit2 Enabled Ready Live 3m18s
```

The `Storage` resource will contain the following message indicating the reason it has been disabled:

```console
$ kubectl get storages rabbit1 -o json | jq -rM .status.message
Kubernetes node is tainted with cray.nnf.node.drain
```

To restore the node to service, remove the `cray.nnf.node.drain` taint.

```shell
kubectl taint node $NODE cray.nnf.node.drain-
```

The `Storage` resource will revert to a `Ready` status.

## The CSI Driver

While the CSI driver pods may be drained from a Rabbit node, it is advisable not to do so.
Expand Down

0 comments on commit ac9bb89

Please sign in to comment.