Help Center/ Cloud Container Engine/ User Guide (Paris Regions)/ FAQs/ Workload/ Others/ Why Cannot a Pod Be Scheduled to a Node?

Updated on 2023-07-06 GMT+08:00

View PDF

Why Cannot a Pod Be Scheduled to a Node?

Check whether the node and Docker are normal. For details, see Check Item 7: Whether Internal Components Are Normal.
If the node and Docker are normal, check whether an affinity policy is configured for the pod. For details, see Check Item 3: Affinity and Anti-Affinity Configuration of the Workload.
Check whether the resources on the node are sufficient. If the resources are insufficient, expand the capacity or add nodes.

Parent topic: Others

Previous topic: What Should I Do If Error Message "Auth is empty" Is Displayed When a Private Image Is Pulled?

Next topic: What Is the Image Pull Policy for Containers in a CCE Cluster?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.