doc-exports/docs/cce/umn/cce_10_0654.html

<a name="cce_10_0654"></a><a name="cce_10_0654"></a>

<h1 class="topictitle1">Synchronizing Node Pools</h1>
<div id="body0000001564597921"><p id="cce_10_0654__p12532332101219">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.</p>
<div class="notice" id="cce_10_0654__note417219165143"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0654__ul43215297206"><li id="cce_10_0654__li7321192972015">Do not delete or reset nodes during batch synchronization. Otherwise, the synchronization of node pool configuration may fail.</li><li id="cce_10_0654__li166402302204">This operation involves resetting nodes. <strong id="cce_10_0654__b93441952155516">Workloads running on a node may be interrupted due to standalone deployment or insufficient schedulable resources.</strong> Evaluate the upgrade risks and perform the upgrade during off-peak hours. Alternatively, <a href="https://kubernetes.io/docs/tasks/run-application/configure-pdb/" target="_blank" rel="noopener noreferrer">specify a disruption budget for your key applications</a> to ensure the availability of these applications during the upgrade.</li><li id="cce_10_0654__li121201213155914">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.</li><li id="cce_10_0654__li1906164412547">Only some node pool parameters can be synchronized by resetting nodes. The constraints are as follows:<ul id="cce_10_0654__ul1983773019558"><li id="cce_10_0654__en-us_topic_0000001564478021_li1743542655118">Changes to the container engine, OS, security hardening, or pre-/post-installation script in a node pool take effect only on new nodes. To synchronize the modification onto existing nodes, manually reset these nodes.</li><li id="cce_10_0654__en-us_topic_0000001564478021_li756951114281">Changes to resource tags and Kubernetes labels/taints in a node pool will be automatically synchronized to existing nodes. You do not need to reset these nodes.</li></ul>
<ul id="cce_10_0654__ul6608677519"><li id="cce_10_0654__li18677195412463">If a new OS patch exists in the environment, you can synchronize the node pool to update the OS.</li></ul>
</li></ul>
</div></div>
<div class="section" id="cce_10_0654__section7681224173015"><h4 class="sectiontitle">Synchronizing a Single Node</h4><ol id="cce_10_0654__ol3210234114416"><li id="cce_10_0654__li19210034174416"><span>Log in to the <span id="cce_10_0654__ph1343399462112627">CCE console</span>.</span></li><li id="cce_10_0654__li2210103415443"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0654__uicontrol81723683495515"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <span class="uicontrol" id="cce_10_0654__uicontrol30734145395515"><b>Nodes</b></span> tab.</span></li><li id="cce_10_0654__li18131106184816"><span>Find the node marked with <strong id="cce_10_0654__b112264518538">Node pool updated</strong> in the node pool.</span></li><li id="cce_10_0654__li1021017348444"><span>Move the cursor to <span class="uicontrol" id="cce_10_0654__uicontrol67151577915"><b>Node pool updated</b></span>. The <strong id="cce_10_0654__b1715857795">Reset</strong> button is displayed. You can then determine whether to reset the node immediately.</span></li></ol>
</div>
<div class="section" id="cce_10_0654__section185910414306"><h4 class="sectiontitle">Batch Synchronization</h4><ol id="cce_10_0654__ol2073011220179"><li id="cce_10_0654__li18281961715"><span>Log in to the <span id="cce_10_0654__ph358310043112627">CCE console</span>.</span></li><li id="cce_10_0654__li18289971715"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0654__uicontrol20700584744235"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0654__b15184805584235">Node Pools</strong> tab.</span></li><li id="cce_10_0654__li11298919177"><span>Choose <span class="uicontrol" id="cce_10_0654__uicontrol22014550995515"><b>More &gt; Synchronize</b></span> in the <strong id="cce_10_0654__b10711937165513">Operation</strong> column of the target node pool.</span></li><li id="cce_10_0654__li1429169191711"><span>In the <span class="uicontrol" id="cce_10_0654__uicontrol14298971715"><b>Batch synchronization</b></span> window, configure parameters.</span><p><ul id="cce_10_0654__ul02959141715"><li id="cce_10_0654__li1687092692015"><strong id="cce_10_0654__b1694015192402">OS</strong>: shows the image of the target version. You do not need to configure this parameter.</li><li id="cce_10_0654__li7746112161318"><strong id="cce_10_0654__b0114105810218">Synchronization Type</strong>: <strong id="cce_10_0654__b1278941602216">Reset node</strong> is supported.</li><li id="cce_10_0654__li3295911174"><strong id="cce_10_0654__b107061415104912">Max. Nodes for Batch Synchronization</strong>: 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.</li><li id="cce_10_0654__li653712501158">In the node list, select the nodes requiring the synchronization of node pool configurations.</li></ul>
</p></li><li id="cce_10_0654__li7291091174"><span>Click <span class="uicontrol" id="cce_10_0654__uicontrol1895916334119"><b>OK</b></span>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0222.html">Managing Node Pools</a></div>
</div>
</div>