Please refer to the following commands to perform a health check or investigation into the Rok CSI Node.
1.Check the status of the Rok CSI Node DaemonSet:
$ kubectl get daemonset -n rok rok-csi-node -o wide
2. Check the status of the Rok CSI Node Pods:
$ kubectl get pods -n rok -l app=rok-csi-node
3. Inspect events on the Rok CSI Node DaemonSet:
$ kubectl describe daemonset -n rok rok-csi-node
4. Inspect the events on a specific Rok CSI Node Pod, for example:
$ kubectl describe pod -n rok rok-csi-node-fpdgj
5. Inspect the logs of a specific Rok CSI Node Pod, for example:
$ kubectl logs -n rok rok-csi-node-fpdgj -c csi-node -f
After successful deployment, and under normal operation, the Rok CSI Controller Pod should emit the following log message:
2022-04-11T13:05:57.255684+0000 pid=70/tid=157/no-func libtrpt:36c7689ae1b3:274 [INFO]
Initiator port `csi-node-70.csi.0.rok-csi-node-fpdgj:i:1'
has successfully connected with target port `composerd.0.composerd. 0.rok-ddtd4:t:5':
Nexus `csi-node-70.csi.0.rok-csi-node-fpdgj:i:1,composerd.0.composerd.0.rok-ddtd4:t:5,tcp://10.124.1.15:45077' was created
2022-04-11T13:05:57.258653+0000 pid=70/tid=157/no-func libpu:745038e8e27a:937
[INFO] Created nexus `csi-node-70.csi.0.rok-csi-node-fpdgj:i:1,
composerd.0.composerd.0.rok-ddtd4:t:5,tcp://10.124.1.15:45077',
`csi-node-70.csi.0.rok-csi-node-fpdgj:i:1' -> (composerd.0.composerd.0.rok-ddtd4:t:5, tcp://10.124.1.15:45077)
Comments
0 comments
Article is closed for comments.