请在任意节点执行以下步骤验证NodeD的安装状态。

通过如下命令查看K8s集群中NodeD的Pod，需要满足Pod的STATUS为Running，READY为1/1。如果集群中有多个节点安装了NodeD，每个节点都需要确认。

kubectl get pods -n mindx-dl -o wide | grep noded

回显示例：

noded-bnmwt                        1/1     Running   10         40d    192.168.41.28     ubuntu       <none>           <none>

通过如下命令查看NodeD组件日志。

kubectl logs -n mindx-dl {NodeD组件的Pod名字}

回显示例如下，表示组件正常运行。

[root@***** clusterD]# kubectl logs -f -n mindx-dl         noded-6dp22 
[INFO]     2024/12/20 17:37:01.839137 1       hwlog/api.go:108    noded.log's logger init success
[INFO]     2024/12/20 17:37:01.839313 1       noded/main.go:88    noded starting and the version is v6.0.T600_linux-aarch64
W1220 17:37:01.839337       1 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
[INFO]     2024/12/20 17:37:01.845520 1       config/configurator.go:219    get config cm failed when init, may be not create, load from local json file
[INFO]     2024/12/20 17:37:01.845566 1       config/configurator.go:109    init fault config from config map failed, start load local json file
[INFO]     2024/12/20 17:37:01.879025 1       config/configurator.go:97    update fault config success
[INFO]     2024/12/20 17:37:01.879138 1       config/configurator.go:114    init config from local json file success
[INFO]     2024/12/20 17:37:01.956277 286     monitoring/monitor_manager.go:80    report interval: 5
[INFO]     2024/12/20 17:37:01.958292 251     cmreporter/configmap_reporter.go:83    report node fault device info to k8s by configmap success, time is 2024-12-20T17:37:01Z
[INFO]     2024/12/20 17:37:06.959146 286     monitoring/monitor_manager.go:80    report interval: 5
[INFO]     2024/12/20 17:37:11.960225 286     monitoring/monitor_manager.go:80    report interval: 5
[INFO]     2024/12/20 17:37:16.964435 286     monitoring/monitor_manager.go:80    report interval: 5
[INFO]     2024/12/20 17:37:21.968612 286     monitoring/monitor_manager.go:80    report interval: 5
...