forked from docs/doc-exports
qiujiandong1
ab1e53a279
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>
93 lines
8.9 KiB
HTML
93 lines
8.9 KiB
HTML
<a name="cce_bestpractice_0014"></a><a name="cce_bestpractice_0014"></a>
|
|
|
|
<h1 class="topictitle1">Resource Planning for the Target Cluster</h1>
|
|
<div id="body0000001217302181"><p id="cce_bestpractice_0014__p131025384">CCE allows you to customize cluster resources to meet various service requirements. <a href="#cce_bestpractice_0014__table1841815113913">Table 1</a> lists the key performance parameters of a cluster and provides the planned values. You can set the parameters based on your service requirements. It is recommended that the performance configuration be the same as that of the source cluster.</p>
|
|
<div class="notice" id="cce_bestpractice_0014__note1065614489"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_bestpractice_0014__p86561441285">After a cluster is created, the resource parameters marked with asterisks (*) in <a href="#cce_bestpractice_0014__table1841815113913">Table 1</a> cannot be modified.</p>
|
|
</div></div>
|
|
|
|
<div class="tablenoborder"><a name="cce_bestpractice_0014__table1841815113913"></a><a name="table1841815113913"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_bestpractice_0014__table1841815113913" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Example of CCE cluster planning</caption><thead align="left"><tr id="cce_bestpractice_0014__row9842101513919"><th align="left" class="cellrowborder" valign="top" width="13.86138613861386%" id="mcps1.3.3.2.5.1.1"><p id="cce_bestpractice_0014__p10842515173920">Resource</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="18.81188118811881%" id="mcps1.3.3.2.5.1.2"><p id="cce_bestpractice_0014__p8515114620215">Key Performance Parameter</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="53.465346534653456%" id="mcps1.3.3.2.5.1.3"><p id="cce_bestpractice_0014__p1284271512391">Description</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="13.86138613861386%" id="mcps1.3.3.2.5.1.4"><p id="cce_bestpractice_0014__p1584219153393">Example Value</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="cce_bestpractice_0014__row184217155391"><td class="cellrowborder" rowspan="3" valign="top" width="13.86138613861386%" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p19842215163915">Cluster</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="18.81188118811881%" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p35159461125"><strong id="cce_bestpractice_0014__b5390232995">*</strong>Cluster Type</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="53.465346534653456%" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p154776184504">CCE supports multiple cluster types to meet diverse needs, including highly reliable, highly secure, commercial containers.</p>
|
|
<p id="cce_bestpractice_0014__p818113235013">You can select <strong id="cce_bestpractice_0014__b97525772515">CCE Standard Cluster</strong> or <strong id="cce_bestpractice_0014__b591175942513">CCE Turbo Cluster</strong> as required.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="13.86138613861386%" headers="mcps1.3.3.2.5.1.4 "><p id="cce_bestpractice_0014__p1784219151395">CCE standard cluster</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row88425158392"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p195157467210"><strong id="cce_bestpractice_0014__b1457213342916">*</strong>Network Model</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p18179172711514">Select <span class="uicontrol" id="cce_bestpractice_0014__uicontrol1078624512614"><b>VPC network</b></span> or <span class="uicontrol" id="cce_bestpractice_0014__uicontrol978654515261"><b>Tunnel network</b></span> for your CCE standard cluster.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p2842515153910">VPC network</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row16842191511395"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p125150461214"><strong id="cce_bestpractice_0014__b151391747191711">*</strong>Number of master nodes</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p9538145716222">Select the number of master nodes, also known as control plane nodes. These nodes are hosted on CCE and run Kubernetes components like kube-apiserver, kube-controller-manager, and kube-scheduler.</p>
|
|
<ul id="cce_bestpractice_0014__ul153172167234"><li id="cce_bestpractice_0014__en-us_topic_0000001199341190_li9706202816307"><strong id="cce_bestpractice_0014__b73301744302">3 (HA)</strong>: Three master nodes will be created to ensure high availability.</li><li id="cce_bestpractice_0014__en-us_topic_0000001199341190_li29225205107"><strong id="cce_bestpractice_0014__b78121705112">Single</strong>: Only one master node will be created in your cluster.<div class="note" id="cce_bestpractice_0014__en-us_topic_0000001199341190_note4588942194910"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_bestpractice_0014__en-us_topic_0000001199341190_ul134995309413"><li id="cce_bestpractice_0014__en-us_topic_0000001199341190_li9499143034113">If more than half of the master nodes in a CCE cluster are faulty, the cluster cannot function properly. </li></ul>
|
|
</div></div>
|
|
</li></ul>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p795482545218">3 Masters</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row384241515399"><td class="cellrowborder" rowspan="5" valign="top" width="13.86138613861386%" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p17842151514393">Node</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="18.81188118811881%" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p363135913252">Node Type</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="53.465346534653456%" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p399565917561">Select a node type based on service requirements. The available node flavors will then be displayed in the <strong id="cce_bestpractice_0014__b91018590394">Specifications</strong> area for you to choose from.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="13.86138613861386%" headers="mcps1.3.3.2.5.1.4 "><p id="cce_bestpractice_0014__p192550504556">Elastic Cloud Server (VM)</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row16841543171117"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p06841743181116">Node Specifications (vary depending on the actual region)</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p563185902519">Select a node flavor that best fits your service needs. </p>
|
|
<p id="cce_bestpractice_0014__p1518981785712">For optimal cluster component performance, you are advised to choose a node with at least 4 vCPUs and 8 GiB of memory.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p1468494381117">4 vCPUs | 8 GiB</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row1930813101560"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p14631459122518">OS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p13631959162512">Select an OS for the nodes.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p1730815109568">EulerOS</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row7336123731"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p1433612311315">System Disk</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__p590942616323">System disk used by the node OS. The value ranges from 40 GiB to 1024 GiB. The default value is 50 GiB.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p17336113634">50 GiB</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_bestpractice_0014__row1484218154391"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.1 "><p id="cce_bestpractice_0014__p0669147185817">Data Disk</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.2 "><p id="cce_bestpractice_0014__li1124252010378p0">Add a data disk for container runtime and kubelet. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.5.1.3 "><p id="cce_bestpractice_0014__p103541922185813">100 GiB</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_bestpractice_0013.html">Migrating Kubernetes Clusters to CCE Using Velero</a></div>
|
|
</div>
|
|
</div>
|
|
|