Help Center/ Ubiquitous Cloud Native Service/ FAQs/ On-Premises Clusters/ What Can I Do If a Node Is Not Ready After the Node Specifications Are Expanded?

Updated on 2025-12-22 GMT+08:00

View PDF

What Can I Do If a Node Is Not Ready After the Node Specifications Are Expanded?

Symptom

After the specifications of a node in an on-premises cluster are expanded, Kubernetes of the node may fail to be started. This means the node is not ready.

Procedure

The /mnt/paas/kubernetes/kubelet/cpu_manager_state file stores original cpu_manager_policy, which is the core binding setting of the original CPU cores and needs to be deleted. Restart kubelet to enable cpu_manager to bind cores based on the existing CPU topology and generate cpu_manager_state again.

Run the following commands:

rm /mnt/paas/kubernetes/kubelet/cpu_manager_state

systemctl restart kubelet

Wait for a period of time until the node recovers.

Parent topic: On-Premises Clusters

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.

Chatbot