Help Center>
Cloud Container Engine>
FAQs>
Workload>
Scheduling Policies>
Why Cannot a Pod Be Scheduled to a Node?
Updated on 2024-07-04 GMT+08:00
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.
Scheduling Policies FAQs
- How Do I Evenly Distribute Multiple Pods to Each Node?
- How Do I Prevent a Container on a Node from Being Evicted?
- Why Are Pods Not Evenly Distributed to Nodes?
- How Do I Evict All Pods on a Node?
- How Do I Check Whether a Pod Is Bound with CPU Cores?
- What Should I Do If Pods cannot Be Rescheduled After the Node Is Stopped?
- How Do I Prevent a Non-GPU or NPU Workload from Being Scheduled to a GPU or NPU Node?
- Why Cannot a Pod Be Scheduled to a Node?
Feedback
Was this page helpful?
Provide feedbackThank 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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore