yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
a41a4e0331fbc0beff63bb28fa59228cc9a751df
doc-exports/docs/cce/umn/cce_10_0460.html
qiujiandong1 ab1e53a279 CCE UMN 20251031 version 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2026-01-15 10:25:22 +00:00

2.9 KiB
Raw Blame History

Kubernetes Node Taint

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

Solutions

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

  1. Configure the kubectl command. For details, see Accessing 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.