vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/cce/umn/cce_10_0460.html
Dong, Qiu Jian f7b9a88535 CCE UMN update -20240625 version 
Reviewed-by: Kovács, Zoltán <zkovacs@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-09-04 11:43:54 +00:00

2.9 KiB
Raw Permalink Blame History

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.