yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

CCE UMN for 24.2.0 version -20240428

Browse Source 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
This commit is contained in:
Dong, Qiu Jian
2024-06-10 08:19:07 +00:00
committed by zuul
parent 99a2d77599
commit 86fb05065f
569 changed files with 9251 additions and 7871 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/cce/umn/cce_10_0129.html
View File

@ -294,12 +294,12 @@ $configBlock
</thead>
<tbody><tr id="cce_10_0129__row162102049564"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.3.3.4.2.2.2.3.1.1 "><p id="cce_10_0129__p421019416569">Multi AZ</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.3.3.4.2.2.2.3.1.2 "><ul id="cce_10_0129__ul122101425619"><li id="cce_10_0129__li142101342560"><strong id="cce_10_0129__b6395193820145">Preferred</strong>: Deployment pods of the add-on will be preferentially scheduled to nodes in different AZs. If all the nodes in the cluster are deployed in the same AZ, the pods will be scheduled to that AZ.</li><li id="cce_10_0129__li52682031184214"><strong id="cce_10_0129__b1516164563318">Equivalent mode</strong>: Deployment pods of the add-on are evenly scheduled to the nodes in the cluster in each AZ. If a new AZ is added, you are advised to increase add-on pods for cross-AZ HA deployment. With the Equivalent multi-AZ deployment, the difference between the number of add-on pods in different AZs will be less than or equal to 1. If resources in one of the AZs are insufficient, pods cannot be scheduled to that AZ.</li><li id="cce_10_0129__li3210440562"><strong id="cce_10_0129__b4304164818353">Required</strong>: Deployment pods of the add-on will be forcibly scheduled to nodes in different AZs. If there are fewer AZs than pods, the extra pods will fail to run.</li></ul>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.3.3.4.2.2.2.3.1.2 "><ul id="cce_10_0129__ul122101425619"><li id="cce_10_0129__li142101342560"><strong id="cce_10_0129__b6395193820145">Preferred</strong>: Deployment pods of the add-on will be preferentially scheduled to nodes in different AZs. If all the nodes in the cluster are deployed in the same AZ, the pods will be scheduled to that AZ.</li><li id="cce_10_0129__li52682031184214"><strong id="cce_10_0129__b8203192017422">Equivalent mode</strong>: Deployment pods of the add-on are evenly scheduled to the nodes in the cluster in each AZ. If a new AZ is added, you are advised to increase add-on pods for cross-AZ HA deployment. With the Equivalent multi-AZ deployment, the difference between the number of add-on pods in different AZs will be less than or equal to 1. If resources in one of the AZs are insufficient, pods cannot be scheduled to that AZ.</li><li id="cce_10_0129__li3210440562"><strong id="cce_10_0129__b105801282497">Required</strong>: Deployment pods of the add-on will be forcibly scheduled to nodes in different AZs. If there are fewer AZs than pods, the extra pods will fail to run.</li></ul>
</td>
</tr>
<tr id="cce_10_0129__row1121010416566"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.3.3.4.2.2.2.3.1.1 "><p id="cce_10_0129__p12210114165612">Node Affinity</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.3.3.4.2.2.2.3.1.2 "><ul id="cce_10_0129__ul1621054145617"><li id="cce_10_0129__li1721017413562"><strong id="cce_10_0129__b2074619819545">Incompatibility</strong>: Node affinity is disabled for the add-on.</li><li id="cce_10_0129__li52109417563"><strong id="cce_10_0129__b7658101316551">Node Affinity</strong>: Specify the nodes where the add-on is deployed. If you do not specify the nodes, the add-on will be randomly scheduled based on the default cluster scheduling policy.</li><li id="cce_10_0129__li1421015415561"><strong id="cce_10_0129__b98581358205610">Specified Node Pool Scheduling</strong>: Specify the node pool where the add-on is deployed. If you do not specify the node pool, the add-on will be randomly scheduled based on the default cluster scheduling policy.</li><li id="cce_10_0129__li92101542568"><strong id="cce_10_0129__b634615619572">Custom Policies</strong>: Enter the labels of the nodes where the add-on is to be deployed for more flexible scheduling policies. If you do not specify node labels, the add-on will be randomly scheduled based on the default cluster scheduling policy.<p id="cce_10_0129__p19210104145617">If multiple custom affinity policies are configured, ensure that there are nodes that meet all the affinity policies in the cluster. Otherwise, the add-on cannot run.</p>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.3.3.4.2.2.2.3.1.2 "><ul id="cce_10_0129__ul1621054145617"><li id="cce_10_0129__li1721017413562"><strong id="cce_10_0129__b2074619819545">Not configured</strong>: Node affinity is disabled for the add-on.</li><li id="cce_10_0129__li52109417563"><strong id="cce_10_0129__b7658101316551">Node Affinity</strong>: Specify the nodes where the add-on is deployed. If you do not specify the nodes, the add-on will be randomly scheduled based on the default cluster scheduling policy.</li><li id="cce_10_0129__li1421015415561"><strong id="cce_10_0129__b98581358205610">Specified Node Pool Scheduling</strong>: Specify the node pool where the add-on is deployed. If you do not specify the node pool, the add-on will be randomly scheduled based on the default cluster scheduling policy.</li><li id="cce_10_0129__li92101542568"><strong id="cce_10_0129__b634615619572">Custom Policies</strong>: Enter the labels of the nodes where the add-on is to be deployed for more flexible scheduling policies. If you do not specify node labels, the add-on will be randomly scheduled based on the default cluster scheduling policy.<p id="cce_10_0129__p19210104145617">If multiple custom affinity policies are configured, ensure that there are nodes that meet all the affinity policies in the cluster. Otherwise, the add-on cannot run.</p>
</li></ul>
</td>
</tr>
@ -316,7 +316,7 @@ $configBlock
</p></li><li id="cce_10_0129__li9455819152615"><span>Click <strong id="cce_10_0129__b165814819135">Install</strong>.</span></li></ol>
</div>
<div class="section" id="cce_10_0129__section0377457163618"><h4 class="sectiontitle">Components</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0129__table1965341035819" frame="border" border="1" rules="all"><caption><b>Table 6 </b>CoreDNS components</caption><thead align="left"><tr id="cce_10_0129__row1565319102582"><th align="left" class="cellrowborder" valign="top" width="28.000000000000004%" id="mcps1.3.4.2.2.4.1.1"><p id="cce_10_0129__p14653141018584">Component</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0129__table1965341035819" frame="border" border="1" rules="all"><caption><b>Table 6 </b>Add-on components</caption><thead align="left"><tr id="cce_10_0129__row1565319102582"><th align="left" class="cellrowborder" valign="top" width="28.000000000000004%" id="mcps1.3.4.2.2.4.1.1"><p id="cce_10_0129__p14653141018584">Component</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="45%" id="mcps1.3.4.2.2.4.1.2"><p id="cce_10_0129__p065391025820">Description</p>
</th>
@ -345,7 +345,7 @@ $configBlock
<ol id="cce_10_0129__ol1895815493314"><li id="cce_10_0129__li29576413330">The query is first sent to the DNS caching layer in CoreDNS.</li><li id="cce_10_0129__li79589463318">From the caching layer, the suffix of the request is examined and then the request is forwarded to the corresponding DNS:<ul id="cce_10_0129__ul29582417338"><li id="cce_10_0129__li495814453313">Names with the cluster suffix, for example, <strong id="cce_10_0129__b11610940133413">.cluster.local</strong>: The request is sent to CoreDNS.</li></ul>
<ul id="cce_10_0129__ul189581349330"><li id="cce_10_0129__li169582413313">Names with the stub domain suffix, for example, <strong id="cce_10_0129__b208218633511">.acme.local</strong>: The request is sent to the configured custom DNS resolver that listens, for example, on 1.2.3.4.</li><li id="cce_10_0129__li195815453320">Names that do not match the suffix (for example, <strong id="cce_10_0129__b13519452133513">widget.com</strong>): The request is forwarded to the upstream DNS.</li></ul>
</li></ol>
<div class="fignone" id="cce_10_0129__fig7582181514118"><span class="figcap"><b>Figure 1 </b>Routing</span><br><span><img id="cce_10_0129__image23305161015" src="en-us_image_0000001750791424.png"></span></div>
<div class="fignone" id="cce_10_0129__fig7582181514118"><span class="figcap"><b>Figure 1 </b>Routing</span><br><span><img id="cce_10_0129__image23305161015" src="en-us_image_0000001897906037.png"></span></div>
</div>
</div>
<div>