csi: remove rbd wording from node loss doc
since ceph-csi driver now handles both rbd and cephfs
volume node loss case, let's remove rbd specific
wording from the node loss doc in rook.
Signed-off-by: subhamkrai <srai@redhat.com>
(cherry picked from commit ae33d23053)
This commit is contained in:
1 parent
617a347d97
commit
617abc0202
2 files changed
+2
-345
No files matched your search
@@ -196,7 +196,7 @@ The erasure coded pool must be set as the `dataPool` parameter in
|
||||
|
||||
## Node Loss
|
||||
|
||||
If a node goes down where a pod is running where a RBD RWO volume is mounted, the volume cannot automatically be mounted on another node. The node must be guaranteed to be offline before the volume can be mounted on another node.
|
||||
If a node goes down where a pod is running where a volume is mounted, the volume cannot automatically be mounted on another node. The node must be guaranteed to be offline before the volume can be mounted on another node.
|
||||
|
||||
|
||||
### Handling Node Loss
|
||||
@@ -209,7 +209,7 @@ kubectl taint nodes <node-name> node.kubernetes.io/out-of-service=nodeshutdown:N
|
||||
kubectl taint nodes <node-name> node.kubernetes.io/out-of-service=nodeshutdown:NoSchedule
|
||||
```
|
||||
|
||||
After the taint is added to the node, the CephCSI driver will automatically handle the network fencing to prevent connections to Ceph from the RBD volume on that node.
|
||||
After the taint is added to the node, the CephCSI driver will automatically handle the network fencing to prevent connections to Ceph from the volume on that node.
|
||||
|
||||
### Node Recovery
|
||||
|
||||
|
||||
Reference in new issue
Block a user