Skip to content

Commit

Permalink
Explain when to use the taint
Browse files Browse the repository at this point in the history
Signed-off-by: Dean Roehrich <[email protected]>
  • Loading branch information
roehrich-hpe committed Aug 1, 2024
1 parent a781677 commit a2d224e
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/guides/node-management/drain.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,10 @@ Given the limitations of DaemonSets, the NNF software will be drained by using t
as described in
[Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/).

This would be used only after the WLM jobs have been removed from that Rabbit (preferably) and there is some reason to also remove the NNF software from it. This might be used before a Rabbit is powered off and pulled out of the cabinet, for example, to avoid leaving pods in "Terminating" state (harmless, but it's noise).

If an admin used this taint before power-off it would mean there wouldn't be "Terminating" pods laying around for that Rabbit. After a new/same Rabbit is put back in its place, the NNF software won't jump back on it while the taint is present. The taint can be removed at any time, from immediately after the node is powered off up to some time after the new/same Rabbit is powered back on.

### Drain NNF pods from a rabbit node

Drain the NNF software from a node by applying the `cray.nnf.node.drain` taint.
Expand Down

0 comments on commit a2d224e

Please sign in to comment.