NodeD
- Run the following command to check the pod of the NodeD in the Kubernetes cluster. Ensure that STATUS of the pod is Running and READY is 1/1. If the NodeD is installed on multiple nodes in the cluster, confirm the pod status one by one.
kubectl get pods -n mindx-dl -o wide
Information similar to the following is displayed.
root@ubuntu:~# kubectl get pods -n mindx-dl -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES ... noded-bnmwt 1/1 Running 10 40d 192.168.41.28 ubuntu <none> <none> ...
- Run the following command to view the logs of the NodeD component:
kubectl logs -n mindx-dl {name_of_the_NodeD's pod}If the following information is displayed continuously, the component is running properly.
... [INFO] 2022/10/25 17:58:03.358409 1 pkg/heartbeat.go:104 set node heartbeat time 1666691883 # 1666691883 indicates the timestamp, which may be different. [INFO] 2022/10/25 17:58:03.364407 1 pkg/heartbeat.go:132 patch node annotations success ...
Information similar to the following is displayed.
root@ubuntu-173:~# kubectl logs -n mindx-dl noded-bnmwt [INFO] 2022/10/24 18:07:52.740417 1 hwlog@v0.0.0/api.go:91 noded.log's logger init success [INFO] 2022/10/24 18:07:52.740996 1 main.go:46 noded starting and the version is v3.0.0_linux-x86_64 [WARN] 2022/10/24 18:07:52.741129 1 K8stool@v0.0.0/self_K8s_client.go:153 Neither --kubeconfig nor --master was specified.Using the inClusterConfig. This might not work. [INFO] 2022/10/24 18:07:52.763703 1 pkg/heartbeat.go:104 set node heartbeat time 1666606072 [INFO] 2022/10/24 18:07:52.763821 1 pkg/heartbeat.go:114 set node heartbeat interval 5 [INFO] 2022/10/24 18:07:52.783396 1 pkg/heartbeat.go:132 patch node annotations success [INFO] 2022/10/24 18:07:57.784028 1 pkg/heartbeat.go:104 set node heartbeat time 1666606077 [INFO] 2022/10/24 18:07:57.789906 1 pkg/heartbeat.go:132 patch node annotations success ...
Parent topic: Confirming Component Status