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

Symptom

Take the Ascend Device Plugin as an example. 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 is not displayed.

Causes

The node may lack the label for 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 label the node. For details, see Mapping between nodes and labels.

Parent topic: Troubleshooting