YAML File for Starting a Component Is Successfully Executed, But the pod Corresponding to the Component Is Not Displayed

Symptom

For example, if the Ascend Device Plugin is used, the YAML file for starting the component is successfully executed, and multiple created items are displayed. The Kubernetes DaemonSet (ds) resource corresponding to the Ascend Device Plugin has been created, but the pod cannot be found.

Cause Analysis

The node may lack the label corresponding to the Ascend Device Plugin. The node where the Ascend Device Plugin is installed must have the accelerator=huawei-Ascendxxx label, for example, accelerator=huawei-Ascend910.

Solution

Run the kubectl command to add the corresponding label to the node. For details, see Table 1.

Parent topic: Faults During Installation