Check Item
Check whether the taint, as shown in Table 1, exists on the node.
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. If the following information is expected:
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.