Help Center> Cloud Container Engine> User Guide (Kuala Lumpur Region)> Clusters> Upgrading a Cluster> Troubleshooting for Pre-upgrade Check Exceptions> Kubernetes Node Taints

Updated on 2024-01-24 GMT+08:00

View PDF

Kubernetes Node Taints

Check Item

Check whether the taint needed for cluster upgrade exists on the node.

**Table 1** Taint checklist
Taint Name	Impact
node.kubernetes.io/upgrade	NoSchedule

Solution

Scenario 1: The node is skipped during the cluster upgrade.

For details about how to configure kubectl, see Connecting to a Cluster Using kubectl.
Check the kubelet version of the corresponding node. The following information is expected:

Figure 1 kubelet version

If the version of the node is different from that of other nodes, the node is skipped during the upgrade. Reset the node and upgrade the cluster again. For details about how to reset a node, see Resetting a Node.

Resetting a node will reset all node labels, which may affect workload scheduling. Before resetting a node, check and retain the labels that you have manually added to the node.

Parent topic: Troubleshooting for Pre-upgrade Check Exceptions

Previous topic: Node Mount Points

Next topic: everest Restrictions

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.