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.