Synchronizing Node Pools¶
After the configuration of a node pool is updated, some configurations cannot be automatically synchronized for existing nodes. You can manually synchronize configurations for these nodes.
Important
Do not delete or reset nodes during batch synchronization. Otherwise, the synchronization of node pool configuration may fail.
This operation involves resetting nodes. Workloads running on a node may be interrupted due to standalone deployment or insufficient schedulable resources. Evaluate the upgrade risks and perform the upgrade during off-peak hours. Alternatively, specify a disruption budget for your key applications to ensure the availability of these applications during the upgrade.
During configuration synchronization for existing nodes, the nodes will be reset, and the system disks and data disks will be cleared. Back up important data before the synchronization.
Only some node pool parameters can be synchronized by resetting nodes. The constraints are as follows:
When editing the resource tags of the node pool. The modified configuration takes effect only for new nodes. To synchronize the configuration to the existing nodes, manually reset the existing nodes.
Updates of kubernetes labels and taints are automatically synchronized to existing nodes. You do not need to reset nodes.
Synchronizing a Single Node¶
Log in to the CCE console.
Click the cluster name to access the cluster console. Choose Nodes in the navigation pane and click the Nodes tab on the right.
Find upgrade in the Node Pool column of the existing nodes in the node pool.
Click update. In the dialog box that is displayed, confirm whether to reset the node immediately.
Batch Synchronization¶
Log in to the CCE console.
Click the cluster name to access the cluster console. Choose Nodes in the navigation pane and click the Node Pools tab on the right.
Choose More > Synchronize in the Operation column of the target node pool.
In the Batch synchronization window, configure parameters.
OS: shows the image of the target version. You do not need to configure this parameter.
Synchronization Policy: Node Reset is supported.
Max. Nodes for Batch Synchronize: maximum number of nodes that will be unavailable during node synchronization. Nodes will be unavailable during synchronization by resetting the nodes. Properly configure this parameter to prevent pod scheduling failures caused by too many unavailable nodes in the cluster.
Node List: Select the nodes requiring the synchronization of node pool configurations.
Click OK.