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-10-14 GMT+08:00
View PDF
Share

Kubernetes Node Taints

Check Items

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.

  1. Configure the kubectl command. For details, see Connecting to a Cluster Using kubectl.
  2. 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.