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

CCE UMN for 23.9.0 version -20240123

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-03-27 05:38:53 +00:00 committed by zuul
parent a5523910b0
commit 03485beee6
183 changed files with 4229 additions and 2316 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1277
docs/cce/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

1804
docs/cce/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

7
docs/cce/umn/cce_01_0300.html
View File

@ -8,7 +8,12 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_01_0300__row115169185311"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1015129185318">2023-11-06</p>
<tbody><tr id="cce_01_0300__row15301133891"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p16301431995">2024-01-29</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul15421838121115"><li id="cce_01_0300__li142114389110">Supported the creation of clusters of v1.27.</li><li id="cce_01_0300__li9321143631220">Updated <a href="cce_10_0550.html">Troubleshooting for Pre-upgrade Check Exceptions</a>.</li><li id="cce_01_0300__li2036942911281">Replaced "CCE Cluster Version Release Notes" in section "Product Bulletin" with <a href="cce_10_0405.html">Release Notes for CCE Cluster Versions</a>.</li><li id="cce_01_0300__li68581132114010">Updated the kernel version of EulerOS 2.9.</li></ul>
</td>
</tr>
<tr id="cce_01_0300__row115169185311"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1015129185318">2023-11-06</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul09563134221"><li id="cce_01_0300__li6956131302215">Deleted section "Storage Management: Flexvolume (Deprecated)".</li><li id="cce_01_0300__li974117510255">Updated <a href="cce_10_0020.html">Networking</a>.</li><li id="cce_01_0300__li127038227309">Updated <a href="cce_10_0374.html">Storage</a>.</li><li id="cce_01_0300__li1685474216317">Deleted the description of CentOS 7.7.</li></ul>
</td>

2
docs/cce/umn/cce_10_0003.html
View File

@ -85,7 +85,7 @@
<tr id="cce_10_0003__cce_10_0198_row25394514014"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.4.3.4.2.4.2.2.3.1.1 "><p id="cce_10_0003__cce_10_0198_p25391859406">Resource Tag</p>
</td>
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.4.3.4.2.4.2.2.3.1.2 "><p id="cce_10_0003__cce_10_0198_p275333410342">You can add resource tags to classify resources.</p>
<p id="cce_10_0003__cce_10_0198_p117537347346">You can create <strong id="cce_10_0003__cce_10_0198_cce_10_0363_b6239155511710">predefined tags</strong> in Tag Management Service (TMS). Predefined tags are available to all service resources that support tags. You can use these tags to improve tagging and resource migration efficiency. </p>
<p id="cce_10_0003__cce_10_0198_p117537347346">You can create <strong id="cce_10_0003__cce_10_0198_cce_10_0363_b6239155511710">predefined tags</strong> in TMS. Predefined tags are available to all service resources that support tags. You can use these tags to improve tagging and resource migration efficiency. </p>
<p id="cce_10_0003__cce_10_0198_p16753133419348">CCE will automatically create the "CCE-Dynamic-Provisioning-Node=<em id="cce_10_0003__cce_10_0198_i111451122126">node id</em>" tag.</p>
</td>
</tr>

4
docs/cce/umn/cce_10_0004.html
View File

@ -6,7 +6,7 @@
</li></ul>
</div>
<div class="section" id="cce_10_0004__section74111324152813"><h4 class="sectiontitle"><span class="keyword" id="cce_10_0004__keyword544709935144944">Inherent Label of a Node</span></h4><p id="cce_10_0004__p096179164111">After a node is created, some fixed labels exist and cannot be deleted. For details about these labels, see <a href="#cce_10_0004__table83962234533">Table 1</a>.</p>
<div class="note" id="cce_10_0004__note1531361014395"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0004__p16314181043913">Do not manually change the inherent labels that are automatically added to a node. If the manually changed value conflicts with the system value, the system value prevails.</p>
<div class="note" id="cce_10_0004__note1531361014395"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0004__p16314181043913">Do not manually change the inherent labels that are automatically added to a node. If the manually changed value conflicts with the system value, the system value is used.</p>
</div></div>
<div class="tablenoborder"><a name="cce_10_0004__table83962234533"></a><a name="table83962234533"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0004__table83962234533" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inherent labels of a node</caption><thead align="left"><tr id="cce_10_0004__row941112314533"><th align="left" class="cellrowborder" valign="top" width="45%" id="mcps1.4.2.4.2.3.1.1"><p id="cce_10_0004__p1541113238536">Key</p>
@ -94,7 +94,7 @@
</table>
</div>
</div>
<div class="section" id="cce_10_0004__section33951611481"><h4 class="sectiontitle">Adding or Deleting a Node Label</h4><ol id="cce_10_0004__ol4618636938"><li id="cce_10_0004__li12107195613316"><span>Log in to the CCE console.</span></li><li id="cce_10_0004__li36690501449"><span>Click the cluster name, access the cluster details page, and choose <strong id="cce_10_0004__b1130441713441">Nodes</strong> in the navigation pane. On the page displayed, select a node and click <strong id="cce_10_0004__b1530481719449">Manage Labels and Taints</strong>.</span></li><li id="cce_10_0004__li2568164932420"><span>In the displayed dialog box, click <span class="uicontrol" id="cce_10_0004__uicontrol197381013144411"><b>Add batch operations</b></span> under <span class="uicontrol" id="cce_10_0004__uicontrol147382132448"><b>Batch Operation</b></span>, and then choose <span class="uicontrol" id="cce_10_0004__uicontrol1973861354418"><b>Add/Update</b></span> or <span class="uicontrol" id="cce_10_0004__uicontrol2073819135443"><b>Delete</b></span>.</span><p><p id="cce_10_0004__p59891449182418">Enter the key and value of the label to be added or deleted, and click <strong id="cce_10_0004__b10531103420434">OK</strong>.</p>
<div class="section" id="cce_10_0004__section33951611481"><h4 class="sectiontitle">Adding or Deleting a Node Label</h4><ol id="cce_10_0004__ol4618636938"><li id="cce_10_0004__li12107195613316"><span>Log in to the CCE console.</span></li><li id="cce_10_0004__li36690501449"><span>Click the cluster name, access the cluster details page, and choose <strong id="cce_10_0004__b1130441713441">Nodes</strong> in the navigation pane. On the page displayed, select a node and click <strong id="cce_10_0004__b1530481719449">Labels and Taints</strong> above the list.</span></li><li id="cce_10_0004__li2568164932420"><span>In the displayed dialog box, click <span class="uicontrol" id="cce_10_0004__uicontrol197381013144411"><b>Add Operation</b></span> under <span class="uicontrol" id="cce_10_0004__uicontrol147382132448"><b>Batch Operation</b></span>, and then choose <span class="uicontrol" id="cce_10_0004__uicontrol1973861354418"><b>Add/Update</b></span> or <span class="uicontrol" id="cce_10_0004__uicontrol2073819135443"><b>Delete</b></span>.</span><p><p id="cce_10_0004__p59891449182418">Enter the key and value of the label to be added or deleted, and click <strong id="cce_10_0004__b10531103420434">OK</strong>.</p>
<p id="cce_10_0004__p12647141114247">For example, the key is <strong id="cce_10_0004__b842352706145648">deploy_qa</strong> and the value is <strong id="cce_10_0004__b842352706145652">true</strong>, indicating that the node is used to deploy the QA (test) environment.</p>
</p></li><li id="cce_10_0004__li68199221571"><span>After the label is added, check the added label in node data.</span></li></ol>
</div>

4
docs/cce/umn/cce_10_0009.html
View File

@ -7,13 +7,13 @@
<div class="section" id="cce_10_0009__section14876601632"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0009__p545510319312">The node where the workload is running is accessible from public networks.</p>
</div>
<div class="section" id="cce_10_0009__section0402183334411"><h4 class="sectiontitle">Using the Console</h4><ol id="cce_10_0009__ol1748117409446"><li id="cce_10_0009__li16481144064414"><a name="cce_10_0009__li16481144064414"></a><a name="li16481144064414"></a><span>Create a secret for accessing a third-party image repository.</span><p><p id="cce_10_0009__p75695254516">Click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0009__b361110141418">ConfigMaps and Secrets</strong>. On the <strong id="cce_10_0009__b146111414154116">Secrets</strong> tab, click <strong id="cce_10_0009__b9611714144114">Create Secret</strong> in the upper right corner. Set <strong id="cce_10_0009__b1161113140413">Secret Type</strong> to <strong id="cce_10_0009__b461115144411">kubernetes.io/dockerconfigjson</strong>. For details, see <a href="cce_10_0153.html">Creating a Secret</a>.</p>
<p id="cce_10_0009__p819111064514">Enter the user name and password used to access the third-party image repository.</p>
<p id="cce_10_0009__p819111064514">Enter the username and password used to access the third-party image repository.</p>
</p></li><li id="cce_10_0009__li13221161713456"><span>When creating a workload, you can enter a private image path in the format of <em id="cce_10_0009__i138551445252">domainname/namespace/imagename:tag</em> for <span class="uicontrol" id="cce_10_0009__uicontrol252303262917"><b>Image Name</b></span> and select the key created in <a href="#cce_10_0009__li16481144064414">1</a> for <span class="uicontrol" id="cce_10_0009__uicontrol1912713512391"><b>Image Access Credential</b></span>.</span><p><p id="cce_10_0009__p79771915112918"></p>
</p></li><li id="cce_10_0009__li1682113518595"><span>Set other parameters and click <span class="uicontrol" id="cce_10_0009__uicontrol14664142510020"><b>Create Workload</b></span>.</span></li></ol>
</div>
<div class="section" id="cce_10_0009__section18217101117197"><h4 class="sectiontitle">Using kubectl</h4><ol id="cce_10_0009__ol84677271516"><li id="cce_10_0009__li2338171784610"><span>Use kubectl to connect to the cluster. For details, see <a href="cce_10_0107.html">Connecting to a Cluster Using kubectl</a>.</span></li><li id="cce_10_0009__li54671627213"><span>Use kubectl to create a secret of the kubernetes.io/dockerconfigjson.</span><p><pre class="screen" id="cce_10_0009__screen1466527017">kubectl create secret docker-registry <strong id="cce_10_0009__b184651127812"><i><span class="varname" id="cce_10_0009__varname20740165882418">myregistrykey</span></i> </strong> -n <strong id="cce_10_0009__b1984843918253"><i><span class="varname" id="cce_10_0009__varname846884372519">default</span></i></strong> --docker-server=<strong id="cce_10_0009__b124669278112"><i><span class="varname" id="cce_10_0009__varname153949106259">DOCKER_REGISTRY_SERVER</span></i></strong> --docker-username=<strong id="cce_10_0009__b9466927114"><i><span class="varname" id="cce_10_0009__varname6836161311251">DOCKER_USER</span></i></strong> --docker-password=<strong id="cce_10_0009__b1046662715116"><i><span class="varname" id="cce_10_0009__varname321011555243">DOCKER_PASSWORD</span></i></strong> --docker-email=<strong id="cce_10_0009__b54661627119"><i><span class="varname" id="cce_10_0009__varname17516111722514">DOCKER_EMAIL</span></i></strong></pre>
<p id="cce_10_0009__p164665271714">In the preceding command, <em id="cce_10_0009__i18443812102618">myregistrykey</em> indicates the key name, <em id="cce_10_0009__i8904529112612">default</em> indicates the namespace where the key is located, and other parameters are as follows:</p>
<ul id="cce_10_0009__ul84670278112"><li id="cce_10_0009__li4467142711112"><strong id="cce_10_0009__b640184594119">DOCKER_REGISTRY_SERVER</strong>: address of a third-party image repository, for example, <strong id="cce_10_0009__b240104584114">www.3rdregistry.com</strong> or <strong id="cce_10_0009__b1440215458415">10.10.10.10:443</strong></li><li id="cce_10_0009__li13467127716"><strong id="cce_10_0009__b164021745114117">DOCKER_USER</strong>: account used for logging in to a third-party image repository</li><li id="cce_10_0009__li746782712110"><strong id="cce_10_0009__b1539245574117">DOCKER</strong><strong id="cce_10_0009__b4392185511418">_PASSWORD</strong>: password used for logging in to a third-party image repository</li><li id="cce_10_0009__li1546712278117"><strong id="cce_10_0009__b10402845154110">DOCKER_EMAIL</strong>: email of a third-party image repository</li></ul>
<ul id="cce_10_0009__ul84670278112"><li id="cce_10_0009__li4467142711112"><strong id="cce_10_0009__b640184594119">DOCKER_REGISTRY_SERVER</strong>: address of a third-party image repository, for example, <strong id="cce_10_0009__b240104584114">www.3rdregistry.com</strong> or <strong id="cce_10_0009__b1440215458415">10.10.10.10:443</strong></li><li id="cce_10_0009__li13467127716"><strong id="cce_10_0009__b625118469208">DOCKER_USER</strong>: account used for logging in to a third-party image repository</li><li id="cce_10_0009__li746782712110"><strong id="cce_10_0009__b1539245574117">DOCKER</strong><strong id="cce_10_0009__b4392185511418">_PASSWORD</strong>: password used for logging in to a third-party image repository</li><li id="cce_10_0009__li1546712278117"><strong id="cce_10_0009__b10402845154110">DOCKER_EMAIL</strong>: email of a third-party image repository</li></ul>
</p></li><li id="cce_10_0009__li161523518110"><span>Use a third-party image to create a workload.</span><p><div class="p" id="cce_10_0009__p13583471429">A kubernetes.io/dockerconfigjson secret is used for authentication when you obtain a private image. The following is an example of using the myregistrykey for authentication.<pre class="screen" id="cce_10_0009__screen0583771125">apiVersion: v1
kind: Pod
metadata:

2
docs/cce/umn/cce_10_0011.html
View File

@ -6,7 +6,7 @@
<p id="cce_10_0011__p1778412445517"><a href="#cce_10_0011__fig192245420557">Figure 1</a> shows the mapping relationships between access channels, container ports, and access ports.</p>
<div class="fignone" id="cce_10_0011__fig192245420557"><a name="cce_10_0011__fig192245420557"></a><a name="fig192245420557"></a><span class="figcap"><b>Figure 1 </b>Intra-cluster access (ClusterIP)</span><br><span><img id="cce_10_0011__image1942163010278" src="en-us_image_0000001647417816.png"></span></div>
</div>
<div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Creating a ClusterIP Service</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0011__li836916478329"><span>Choose <strong id="cce_10_0011__b85507206148">Networking</strong> in the navigation pane and click <strong id="cce_10_0011__b1938115214148">Create Service</strong> in the upper right corner.</span></li><li id="cce_10_0011__li3476651017144"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0011__ul4446314017144"><li id="cce_10_0011__li6462394317144"><strong id="cce_10_0011__b181470402505">Service Name</strong>: Service name, which can be the same as the workload name.</li><li id="cce_10_0011__li89543531070"><strong id="cce_10_0011__b2091115317145">Service Type</strong>: Select <strong id="cce_10_0011__b291265312145">ClusterIP</strong>.</li><li id="cce_10_0011__li4800017144"><strong id="cce_10_0011__b3997151161512">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0011__li43200017144"><strong id="cce_10_0011__b16251723161514">Selector</strong>: Add a label and click <strong id="cce_10_0011__b157041550131611">Add</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0011__b796831114161">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0011__b1117311264160">OK</strong>.</li><li id="cce_10_0011__li388800117144"><strong id="cce_10_0011__b102328496354">Port</strong><ul id="cce_10_0011__ul13757123384316"><li id="cce_10_0011__li475711338435"><strong id="cce_10_0011__b712192113108">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0011__li353122153610"><strong id="cce_10_0011__b2766425101013">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0011__li177581033194316"><strong id="cce_10_0011__b2045852761014">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li></ul>
<div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Creating a ClusterIP Service</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0011__li836916478329"><span>Choose <strong id="cce_10_0011__b85507206148">Networking</strong> in the navigation pane and click <strong id="cce_10_0011__b1938115214148">Create Service</strong> in the upper right corner.</span></li><li id="cce_10_0011__li3476651017144"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0011__ul4446314017144"><li id="cce_10_0011__li6462394317144"><strong id="cce_10_0011__b181470402505">Service Name</strong>: Service name, which can be the same as the workload name.</li><li id="cce_10_0011__li89543531070"><strong id="cce_10_0011__b2091115317145">Service Type</strong>: Select <strong id="cce_10_0011__b291265312145">ClusterIP</strong>.</li><li id="cce_10_0011__li4800017144"><strong id="cce_10_0011__b3997151161512">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0011__li43200017144"><strong id="cce_10_0011__b1758945315469">Selector</strong>: Add a label and click <strong id="cce_10_0011__b195891153164610">Confirm</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0011__b796831114161">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0011__b1117311264160">OK</strong>.</li><li id="cce_10_0011__li388800117144"><strong id="cce_10_0011__b102328496354">Port</strong><ul id="cce_10_0011__ul13757123384316"><li id="cce_10_0011__li475711338435"><strong id="cce_10_0011__b712192113108">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0011__li353122153610"><strong id="cce_10_0011__b2766425101013">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0011__li177581033194316"><strong id="cce_10_0011__b2045852761014">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li></ul>
</li></ul>
</p></li><li id="cce_10_0011__li5563226917144"><span>Click <strong id="cce_10_0011__b15590122052614">OK</strong>.</span></li></ol>
</div>

13
docs/cce/umn/cce_10_0012.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Creating a Node Pool</h1>
<div id="body1564122277019"><div class="section" id="cce_10_0012__section14878105383915"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0012__p8060118">This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see <a href="cce_10_0081.html">Node Pool Overview</a>.</p>
</div>
<div class="section" id="cce_10_0012__section4988121734011"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0012__ul194117397405"><li id="cce_10_0012__li9346218204215">The autoscaler add-on needs to be installed for node auto scaling. For details about the add-on installation and parameter configuration, see <a href="cce_10_0154.html">autoscaler</a>.</li></ul>
<div class="section" id="cce_10_0012__section4988121734011"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0012__ul194117397405"><li id="cce_10_0012__li9346218204215">The autoscaler add-on needs to be installed for node auto scaling. For details about the add-on installation and parameter configuration, see <a href="cce_10_0154.html">CCE Cluster Autoscaler</a>.</li></ul>
</div>
<div class="section" id="cce_10_0012__section953835110714"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0012__ol20304182312323"><li id="cce_10_0012__li9293104917265"><span>Log in to the CCE console.</span></li><li id="cce_10_0012__li2075471341"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0012__uicontrol1687204583717"><b>Nodes</b></span> in the navigation pane and click the <strong id="cce_10_0012__b1624616332153">Node Pools</strong> tab on the right.</span></li><li id="cce_10_0012__li3387652384"><span>In the upper right corner of the page, click <strong id="cce_10_0012__b11543594158">Create Node Pool</strong>.</span><p><p id="cce_10_0012__p118166389258"><strong id="cce_10_0012__b861915213014">Basic Settings</strong></p>
@ -54,7 +54,14 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0012__row1979195915497"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.3.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0012__p18005944914">Node Type</p>
<tbody><tr id="cce_10_0012__row1666817718587"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.3.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0012__p13216122213017">AZ</p>
</td>
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.3.2.3.2.4.1.2.3.1.2 "><p id="cce_10_0012__p4383635121713">AZ where the node is located. Nodes in a cluster can be created in different AZs for higher reliability. The value cannot be changed after the node is created.</p>
<p id="cce_10_0012__p13307144019185">You are advised to select <strong id="cce_10_0012__b99097411068">Random</strong> to deploy your node in a random AZ based on the selected node flavor.</p>
<p id="cce_10_0012__p4786153575318">An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. To enhance workload availability, create nodes in different AZs.</p>
</td>
</tr>
<tr id="cce_10_0012__row1979195915497"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.3.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0012__p18005944914">Node Type</p>
</td>
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.3.2.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0012__p17807592491">CCE cluster:<ul id="cce_10_0012__cce_10_0363_ul203199555124"><li id="cce_10_0012__cce_10_0363_li931925518124">ECS (VM): Containers run on ECSs.</li></ul>
</div>
@ -176,7 +183,7 @@
<tr id="cce_10_0012__cce_10_0363_row25394514014"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.3.2.3.2.10.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p25391859406">Resource Tag</p>
</td>
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.3.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__cce_10_0363_p14909254174019">You can add resource tags to classify resources.</p>
<p id="cce_10_0012__cce_10_0363_p10327184710426">You can create <strong id="cce_10_0012__cce_10_0363_b6239155511710">predefined tags</strong> in Tag Management Service (TMS). Predefined tags are available to all service resources that support tags. You can use these tags to improve tagging and resource migration efficiency. </p>
<p id="cce_10_0012__cce_10_0363_p10327184710426">You can create <strong id="cce_10_0012__cce_10_0363_b6239155511710">predefined tags</strong> in TMS. Predefined tags are available to all service resources that support tags. You can use these tags to improve tagging and resource migration efficiency. </p>
<p id="cce_10_0012__cce_10_0363_p1738110524401">CCE will automatically create the "CCE-Dynamic-Provisioning-Node=<em id="cce_10_0012__cce_10_0363_i19542542112415">node id</em>" tag.</p>
</td>
</tr>

2
docs/cce/umn/cce_10_0014.html
View File

@ -12,6 +12,8 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0684.html">Configuring Health Check for Multiple Ports</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0729.html">Configuring Timeout for a LoadBalancer Service</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0355.html">Enabling Passthrough Networking for LoadBalancer Services</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0084.html">Enabling ICMP Security Group Rules</a></strong><br>

2
docs/cce/umn/cce_10_0015.html
View File

@ -161,7 +161,7 @@ spec:
</tr>
<tr id="cce_10_0015__row28091948181115"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p9813048191118">Add Container Path</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><div class="p" id="cce_10_0015__p6972055171410">Configure the following parameters:<ol type="a" id="cce_10_0015__ol18607172216391"><li id="cce_10_0015__li26161221390"><strong id="cce_10_0015__b1996660599627">Mount Path</strong>: Enter a path of the container, for example, <strong id="cce_10_0015__b178704526627">/tmp</strong>.<div class="p" id="cce_10_0015__en-us_topic_0000001199341206_p5157313628">This parameter indicates the container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0015__b172894059355716">/</strong> or <strong id="cce_10_0015__b207686195955716">/var/run</strong>; this action may cause container errors. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, causing container startup failures or workload creation failures.<div class="notice" id="cce_10_0015__en-us_topic_0000001199341206_note235158114415"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0015__en-us_topic_0000001199341206_p22751516234">When the container is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged.</p>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><div class="p" id="cce_10_0015__p6972055171410">Configure the following parameters:<ol type="a" id="cce_10_0015__ol18607172216391"><li id="cce_10_0015__li26161221390"><strong id="cce_10_0015__b1996660599627">Mount Path</strong>: Enter a path of the container, for example, <strong id="cce_10_0015__b178704526627">/tmp</strong>.<div class="p" id="cce_10_0015__en-us_topic_0000001199341206_p5157313628">This parameter indicates the container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0015__b172894059355716">/</strong> or <strong id="cce_10_0015__b207686195955716">/var/run</strong>; this action may cause container errors. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, causing container startup failures or workload creation failures.<div class="notice" id="cce_10_0015__en-us_topic_0000001199341206_note235158114415"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0015__en-us_topic_0000001199341206_p22751516234">If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host machine may be damaged.</p>
</div></div>
</div>
</li><li id="cce_10_0015__li842512390413"><strong id="cce_10_0015__b19514815706135">Subpath</strong>: Enter a subpath, for example, <strong id="cce_10_0015__b12219987736135">tmp</strong>.<ul id="cce_10_0015__ul19821342112914"><li id="cce_10_0015__li12982114218296">A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default.</li><li id="cce_10_0015__li79821942142920">The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.</li><li id="cce_10_0015__li129821442102910">The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.</li></ul>

2
docs/cce/umn/cce_10_0016.html
View File

@ -112,7 +112,7 @@ spec:
<tr id="cce_10_0016__row146458911015"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p46473921020">Add Container Path</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p15454317176">Configure the following parameters:</p>
<ol type="a" id="cce_10_0016__ol1365012913103"><li id="cce_10_0016__cce_10_0015_li26161221390"><strong id="cce_10_0016__cce_10_0015_b1996660599627">Mount Path</strong>: Enter a path of the container, for example, <strong id="cce_10_0016__cce_10_0015_b178704526627">/tmp</strong>.<div class="p" id="cce_10_0016__cce_10_0015_en-us_topic_0000001199341206_p5157313628">This parameter indicates the container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0016__cce_10_0015_b172894059355716">/</strong> or <strong id="cce_10_0016__cce_10_0015_b207686195955716">/var/run</strong>; this action may cause container errors. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, causing container startup failures or workload creation failures.<div class="notice" id="cce_10_0016__cce_10_0015_en-us_topic_0000001199341206_note235158114415"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0016__cce_10_0015_en-us_topic_0000001199341206_p22751516234">When the container is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged.</p>
<ol type="a" id="cce_10_0016__ol1365012913103"><li id="cce_10_0016__cce_10_0015_li26161221390"><strong id="cce_10_0016__cce_10_0015_b1996660599627">Mount Path</strong>: Enter a path of the container, for example, <strong id="cce_10_0016__cce_10_0015_b178704526627">/tmp</strong>.<div class="p" id="cce_10_0016__cce_10_0015_en-us_topic_0000001199341206_p5157313628">This parameter indicates the container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0016__cce_10_0015_b172894059355716">/</strong> or <strong id="cce_10_0016__cce_10_0015_b207686195955716">/var/run</strong>; this action may cause container errors. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, causing container startup failures or workload creation failures.<div class="notice" id="cce_10_0016__cce_10_0015_en-us_topic_0000001199341206_note235158114415"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0016__cce_10_0015_en-us_topic_0000001199341206_p22751516234">If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host machine may be damaged.</p>
</div></div>
</div>
</li><li id="cce_10_0016__cce_10_0015_li842512390413"><strong id="cce_10_0016__cce_10_0015_b19514815706135">Subpath</strong>: Enter a subpath, for example, <strong id="cce_10_0016__cce_10_0015_b12219987736135">tmp</strong>.<ul id="cce_10_0016__cce_10_0015_ul19821342112914"><li id="cce_10_0016__cce_10_0015_li12982114218296">A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default.</li><li id="cce_10_0016__cce_10_0015_li79821942142920">The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.</li><li id="cce_10_0016__cce_10_0015_li129821442102910">The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.</li></ul>

14
docs/cce/umn/cce_10_0018.html
View File

@ -4,7 +4,7 @@
<div id="body1522667123001"><p id="cce_10_0018__p78381781804">CCE works with AOM to collect workload logs. When creating a node, CCE installs the ICAgent for you (the DaemonSet named <strong id="cce_10_0018__b3710330164314">icagent</strong> in the kube-system namespace of the cluster). After the ICAgent collects workload logs and reports them to AOM, you can view workload logs on the CCE or AOM console.</p>
<div class="section" id="cce_10_0018__section17884754413"><h4 class="sectiontitle">Constraints</h4><p id="cce_10_0018__p23831558355">The ICAgent only collects <strong id="cce_10_0018__b39280572146">*.log</strong>, <strong id="cce_10_0018__b1793513574146">*.trace</strong>, and <strong id="cce_10_0018__b29351157191412">*.out</strong> text log files.</p>
</div>
<div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, set logging for the container.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000001695737369.png"></span> to add a log policy.</span><p><div class="p" id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary depending on workloads.<div class="fignone" id="cce_10_0018__fig19856172153216"><span class="figcap"><b>Figure 1 </b>Adding a log policy</span><br><span><img id="cce_10_0018__image664110265156" src="en-us_image_0000001691644354.png"></span></div>
<div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, set logging for the container.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000001695737369.png"></span> to add a log policy.</span><p><div class="p" id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary with workloads.<div class="fignone" id="cce_10_0018__fig19856172153216"><span class="figcap"><b>Figure 1 </b>Adding a log policy</span><br><span><img id="cce_10_0018__image664110265156" src="en-us_image_0000001691644354.png"></span></div>
</div>
</p></li><li id="cce_10_0018__li1479392315150"><span>Set <strong id="cce_10_0018__b5461630195419">Volume Type</strong> to <span class="uicontrol" id="cce_10_0018__uicontrol105212302547"><b>Host Path</b></span> or <span class="uicontrol" id="cce_10_0018__uicontrol1752103095410"><b>Container Path</b></span>.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0018__table115901715550" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Configuring log policies</caption><thead align="left"><tr id="cce_10_0018__row45851074554"><th align="left" class="cellrowborder" valign="top" width="22.12%" id="mcps1.3.3.2.3.2.1.2.3.1.1"><p id="cce_10_0018__p115843785517">Parameter</p>
@ -25,7 +25,7 @@
</tr>
<tr id="cce_10_0018__row19587147165512"><td class="cellrowborder" valign="top" width="22.12%" headers="mcps1.3.3.2.3.2.1.2.3.1.1 "><p id="cce_10_0018__p1158647155518">Mount Path</p>
</td>
<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><div class="p" id="cce_10_0018__p358711715554">Container path (for example, <strong id="cce_10_0018__b8656121314711">/tmp</strong>) to which the storage resources will be mounted.<div class="notice" id="cce_10_0018__note155879745516"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><ul id="cce_10_0018__ul14587570556"><li id="cce_10_0018__li95877735510">Do not mount storage to a system directory such as <strong id="cce_10_0018__b0630176102713">/</strong> or <strong id="cce_10_0018__b063118642719">/var/run</strong>; this action may cause a container error to occur. You are advised to mount the container to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload.</li><li id="cce_10_0018__li1258777175519">When the container is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged.</li><li id="cce_10_0018__li1943916477113">AOM collects only the first 20 log files that have been modified recently. It collects files from 2 levels of subdirectories by default.</li><li id="cce_10_0018__li545718441116">AOM only collects <span class="uicontrol" id="cce_10_0018__uicontrol27371025162017"><b>.log</b></span>, <span class="uicontrol" id="cce_10_0018__uicontrol874242592011"><b>.trace</b></span>, and <span class="uicontrol" id="cce_10_0018__uicontrol1974322522012"><b>.out</b></span> text log files in the mount paths.</li><li id="cce_10_0018__li866676185016">For details about how to set permissions for mount points in a container, see <a href="https://kubernetes.io/docs/tasks/configure-pod-container/security-context/" target="_blank" rel="noopener noreferrer">Configure a Security Context for a Pod or Container</a>.</li></ul>
<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><div class="p" id="cce_10_0018__p358711715554">Container path (for example, <strong id="cce_10_0018__b8656121314711">/tmp</strong>) to which the storage resources will be mounted.<div class="notice" id="cce_10_0018__note155879745516"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><ul id="cce_10_0018__ul14587570556"><li id="cce_10_0018__li95877735510">Do not mount a volume to a system directory such as <strong id="cce_10_0018__b127447289141">/</strong> or <strong id="cce_10_0018__b9744128201417">/var/run</strong>. Otherwise, an exception occurs. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, which leads to a container startup failure or workload creation failure.</li><li id="cce_10_0018__li1258777175519">If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host machine may be damaged.</li><li id="cce_10_0018__li1943916477113">AOM collects only the first 20 log files that have been modified recently. It collects files from 2 levels of subdirectories by default.</li><li id="cce_10_0018__li545718441116">AOM only collects <span class="uicontrol" id="cce_10_0018__uicontrol27371025162017"><b>.log</b></span>, <span class="uicontrol" id="cce_10_0018__uicontrol874242592011"><b>.trace</b></span>, and <span class="uicontrol" id="cce_10_0018__uicontrol1974322522012"><b>.out</b></span> text log files in the mount paths.</li><li id="cce_10_0018__li866676185016">For details about how to set permissions for mount points in a container, see <a href="https://kubernetes.io/docs/tasks/configure-pod-container/security-context/" target="_blank" rel="noopener noreferrer">Configure a Security Context for a Pod or Container</a>.</li></ul>
</div></div>
</div>
</td>
@ -51,7 +51,7 @@
</td>
<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><p id="cce_10_0018__p674918171418">Log dump refers to rotating log files on a local host.</p>
<ul id="cce_10_0018__ul1493171511410"><li id="cce_10_0018__li129311551416"><strong id="cce_10_0018__b14264156295">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped. A new <strong id="cce_10_0018__b194262015152911">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b9346139122920">.zip</strong> files. When the number of <strong id="cce_10_0018__b53461239162918">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1347539132915">.zip</strong> files will be deleted.</li><li id="cce_10_0018__li79301514142"><strong id="cce_10_0018__b1646121113016">Disabled</strong>: AOM does not dump log files.</li></ul>
<div class="note" id="cce_10_0018__note746743620142"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0018__ul148957434143"><li id="cce_10_0018__li3895243141410">AOM rotates log files using copytruncate. Before enabling log dumping, ensure that log files are written in the append mode. Otherwise, file holes may occur.</li><li id="cce_10_0018__li7895164351412">Currently, mainstream log components such as Log4j and Logback support log file rotation. If you have already set rotation for log files, skip the configuration. Otherwise, conflicts may occur.</li><li id="cce_10_0018__li589554311145">You are advised to configure log file rotation for your own services to flexibly control the size and number of rolled files.</li></ul>
<div class="note" id="cce_10_0018__note746743620142"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0018__ul148957434143"><li id="cce_10_0018__li3895243141410">AOM rotates log files using copytruncate. Before enabling log dumping, ensure that log files are written in the append mode. Otherwise, file holes may occur.</li><li id="cce_10_0018__li7895164351412">Currently, mainstream log components such as Log4j and Logback support log file rotation. If you have set rotation for log files, skip the configuration. Otherwise, conflicts may occur.</li><li id="cce_10_0018__li589554311145">You are advised to configure log file rotation for your own services to flexibly control the size and number of rolled files.</li></ul>
</div></div>
</td>
</tr>
@ -155,8 +155,8 @@ spec:
<td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p6329709512">Extended host path</p>
</td>
<td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p32881805119">Extended host paths contain pod IDs or container names to distinguish different containers into which the host path is mounted.</p>
<p id="cce_10_0018__p1728888115112">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword1954519765">Pod</span>.</p>
<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b975065369">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b1689154494">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b925397375">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b2107748081">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li528898175110"><strong id="cce_10_0018__b8818125942116">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
<p id="cce_10_0018__p1728888115112">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword900460630">Pod</span>.</p>
<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b401310075">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b376558177">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b325072308">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b671410775">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li528898175110"><strong id="cce_10_0018__b8818125942116">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
</td>
</tr>
<tr id="cce_10_0018__row732915085118"><td class="cellrowborder" valign="top" width="17.06%" headers="mcps1.3.4.7.2.4.1.1 "><p id="cce_10_0018__p17329004514">policy.logs.rotate</p>
@ -164,7 +164,7 @@ spec:
<td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p123292055113">Log dump</p>
</td>
<td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p1017113396539">Log dump refers to rotating log files on a local host.</p>
<ul id="cce_10_0018__ul1617120398533"><li id="cce_10_0018__li71711639105316"><strong id="cce_10_0018__b4837638192520">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new <strong id="cce_10_0018__b98429388254">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b2216332192917">.zip</strong> files. When the number of <strong id="cce_10_0018__b1621653252914">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1321623212917">.zip</strong> files will be deleted. After the dump is complete, the log file in AOM will be cleared.</li><li id="cce_10_0018__li817133985315"><strong id="cce_10_0018__b583150473">Disabled</strong>: AOM does not dump log files.</li></ul>
<ul id="cce_10_0018__ul1617120398533"><li id="cce_10_0018__li71711639105316"><strong id="cce_10_0018__b4837638192520">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new <strong id="cce_10_0018__b98429388254">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b2216332192917">.zip</strong> files. When the number of <strong id="cce_10_0018__b1621653252914">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1321623212917">.zip</strong> files will be deleted. After the dump is complete, the log file in AOM will be cleared.</li><li id="cce_10_0018__li817133985315"><strong id="cce_10_0018__b131164982">Disabled</strong>: AOM does not dump log files.</li></ul>
<div class="note" id="cce_10_0018__note121711639195319"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0018__ul817183918533"><li id="cce_10_0018__li9171183945310">AOM rotates log files using copytruncate. Before enabling log dumping, ensure that log files are written in the append mode. Otherwise, file holes may occur.</li><li id="cce_10_0018__li1117153914535">Currently, mainstream log components such as Log4j and Logback support log file rotation. If you have set rotation for log files, skip the configuration. Otherwise, conflicts may occur.</li><li id="cce_10_0018__li317113915532">You are advised to configure log file rotation for your own services to flexibly control the size and number of rolled files.</li></ul>
</div></div>
</td>
@ -174,7 +174,7 @@ spec:
<td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p14388112019519">Collection path</p>
</td>
<td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p63882201153">A collection path narrows down the scope of collection to specified logs. </p>
<ul id="cce_10_0018__ul73883209510"><li id="cce_10_0018__li14388162011513">If no collection path is specified, log files in <strong id="cce_10_0018__b2106395307">.log</strong>, <strong id="cce_10_0018__b553678455">.trace</strong>, and <strong id="cce_10_0018__b1169250673">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b378475335">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b1506880273">.log</strong>, <strong id="cce_10_0018__b251849409">.trace</strong>, and <strong id="cce_10_0018__b541073936">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li1938811201058">* in log file names indicates a fuzzy match.</li></ul>
<ul id="cce_10_0018__ul73883209510"><li id="cce_10_0018__li14388162011513">If no collection path is specified, log files in <strong id="cce_10_0018__b382896489">.log</strong>, <strong id="cce_10_0018__b938781710">.trace</strong>, and <strong id="cce_10_0018__b1578999925">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b37000745">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b252903613">.log</strong>, <strong id="cce_10_0018__b1347528775">.trace</strong>, and <strong id="cce_10_0018__b2013688139">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li1938811201058">* in log file names indicates a fuzzy match.</li></ul>
<p id="cce_10_0018__p17388152013515">Example: The collection path <strong id="cce_10_0018__b19951612237">/tmp/**/test*.log</strong> indicates that all <strong id="cce_10_0018__b49571315239">.log</strong> files prefixed with <strong id="cce_10_0018__b4958101202315">test</strong> will be collected from <strong id="cce_10_0018__b695815172316">/tmp</strong> and subdirectories at 5 levels deep.</p>
<div class="caution" id="cce_10_0018__note153881220751"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><p id="cce_10_0018__p938810204516">Ensure that the ICAgent version is 5.12.22 or later.</p>
</div></div>

2
docs/cce/umn/cce_10_0024.html
View File

@ -6,7 +6,7 @@
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by CTS</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Querying CTS Logs</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Querying Real-Time Traces</a></strong><br>
</li>
</ul>

24
docs/cce/umn/cce_10_0026.html
View File

@ -1,16 +1,20 @@
<a name="cce_10_0026"></a><a name="cce_10_0026"></a>
<h1 class="topictitle1">Querying CTS Logs</h1>
<div id="body1525226397666"><div class="section" id="cce_10_0026__section19908104613460"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0026__p1349415403233">After you enable CTS, the system starts recording operations on CCE resources. Operation records of the last 7 days can be viewed on the CTS management console.</p>
<h1 class="topictitle1">Querying Real-Time Traces</h1>
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p333055219577">After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven days.</p>
<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p3008599195238">This section describes how to query and export operation records of the last seven days on the CTS console.</p>
<ul id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul17577535194620"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li201409184718"><a href="#cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203">Viewing Real-Time Traces in the Trace List</a></li></ul>
</div>
<div class="section" id="cce_10_0026__section208814582456"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0026__ol968681862911"><li id="cce_10_0026__li18356228445"><span>Log in to the management console.</span></li><li id="cce_10_0026__li14905725134512"><span>Click <span><img id="cce_10_0026__image1180502423211" src="en-us_image_0000001647417272.gif"></span> in the upper left corner and select a region.</span></li><li id="cce_10_0026__li56856187296"><span>Choose <strong id="cce_10_0026__b161841334316020">Service List</strong> from the main menu. Choose <strong id="cce_10_0026__b14174101155814">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__b1917414113585">Cloud Trace Service</strong>.</span></li><li id="cce_10_0026__li6685018122920"><span>In the navigation pane of the CTS console, choose <strong id="cce_10_0026__b091641316584">Cloud Trace Service</strong> &gt; <strong id="cce_10_0026__b6917813165811">Trace List</strong>.</span></li><li id="cce_10_0026__li0686618152911"><span>On the <strong id="cce_10_0026__b156310494616044">Trace List</strong> page, query operation records based on the search criteria. Currently, the trace list supports trace query based on the combination of the following search criteria:</span><p><ul id="cce_10_0026__ul2686318142919"><li id="cce_10_0026__li9685018132914"><strong id="cce_10_0026__b147767585916113">Trace Source</strong>, <strong id="cce_10_0026__b33843206916113">Resource Type</strong>, and <strong id="cce_10_0026__b104136949616113">Search By</strong><p id="cce_10_0026__p068517181297">Select the search criteria from the drop-down lists. Select <strong id="cce_10_0026__b987393825817">CCE</strong> from the <strong id="cce_10_0026__b1287312387583">Trace Source</strong> drop-down list.</p>
<p id="cce_10_0026__p26851618102915">If you select <strong id="cce_10_0026__b23175131216221">Trace name</strong> from the <strong id="cce_10_0026__b172899127516221">Search By</strong> drop-down list, specify the trace name.</p>
<p id="cce_10_0026__p7685191818293">If you select <strong id="cce_10_0026__b33083335616231">Resource ID</strong> from the <strong id="cce_10_0026__b153919820216231">Search By</strong> drop-down list, select or enter a specific resource ID.</p>
<p id="cce_10_0026__p166851718102917">If you select <strong id="cce_10_0026__b50135831116238">Resource name</strong> from the <strong id="cce_10_0026__b186507588316238">Search By</strong> drop-down list, select or enter a specific resource name.</p>
</li><li id="cce_10_0026__li1968671815297"><strong id="cce_10_0026__b168444573616245">Operator</strong>: Select a specific operator (at user level rather than account level).</li><li id="cce_10_0026__li368641832910"><strong id="cce_10_0026__b113712261116258">Trace Status</strong>: Set this parameter to any of the following values: <strong id="cce_10_0026__b135890568716258">All trace statuses</strong>, <strong id="cce_10_0026__b192911413716258">normal</strong>, <strong id="cce_10_0026__b59570413316258">warning</strong>, and <strong id="cce_10_0026__b169117565716258">incident</strong>.</li><li id="cce_10_0026__li12686118112916">Time range: You can query traces generated during any time range in the last seven days.</li></ul>
</p></li><li id="cce_10_0026__li01301836122914"><span>Click <span><img id="cce_10_0026__image07291172331" src="en-us_image_0000001695896213.png"></span> on the left of a trace to expand its details, as shown below.</span><p><div class="fignone" id="cce_10_0026__fig1324117817394"><span class="figcap"><b>Figure 1 </b>Expanding trace details</span><br><span><img id="cce_10_0026__image19242788396" src="en-us_image_0000001695896201.png"></span></div>
</p></li><li id="cce_10_0026__li186863182294"><span>Click <strong id="cce_10_0026__b25871212163720">View Trace</strong> in the <strong id="cce_10_0026__b1597141217374">Operation</strong> column. The trace details are displayed.</span><p><div class="fignone" id="cce_10_0026__fig365411360512"><span class="figcap"><b>Figure 2 </b>Viewing event details</span><br><span><img id="cce_10_0026__image21436386418" src="en-us_image_0000001695736933.png"></span></div>
</p></li></ol>
<div class="section" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203"><a name="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203"></a><a name="en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ol4845175152710"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li791871844313">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li79188188435">Click <span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image2107213105014" src="en-us_image_0000001696838310.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1810717138505">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1310871313509">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li591831894316">Choose <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b09819412220">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li6936134194312">Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311">Figure 1</a>. The following filters are available:<div class="fignone" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311"><a name="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311"></a><a name="en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311"></a><span class="figcap"><b>Figure 1 </b>Filters</span><br><span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image14936144112433" src="en-us_image_0000001744598325.png"></span></div>
<div class="p" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p15936134119435"><ul class="subitemlist" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul20936164174314"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li99361417432"><strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b179671714141513">Trace Type</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b179671014191515">Trace Source</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b4968714141517">Resource Type</strong>, and <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b14968101411516">Search By</strong>: Select a filter from the drop-down list.<ul id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul158893433010"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li12760183118301">If you select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b389315891511">Resource ID</strong> for <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b3893858131515">Search By</strong>, specify a resource ID.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li12760203115305">If you select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b8997941831">Trace name</strong> for <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b199981541317">Search By</strong>, specify a trace name.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li197601031193019">If you select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b196612501258">Resource name</strong> for <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b177275015252">Search By</strong>, specify a resource name.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li15936204184311"><strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b98151395276">Operator</strong>: Select a user.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li6936184119437"><strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b6981161112286">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1298716111281">All trace statuses</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b7987181115281">Normal</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b2988181112810">Warning</strong>, or <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b99881511132820">Incident</strong>.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li1993654144315">Time range: You can query traces generated during any time range in the last seven days.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li8936104118436">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b861150123114">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li></ul>
</div>
</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li094111715448">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b55732514186">Query</strong>.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li29410170448">On the <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b176911834143214">Trace List</strong> page, you can also export and refresh the trace list.<ul id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul119414175448"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li12946170445">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b8907168171714">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li394151717445">Click <span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image109421716440" src="en-us_image_0000001696678850.png"></span> to view the latest information about traces.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li169491744418">Click <span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image9947176447" src="en-us_image_0000001744678489.jpg"></span> on the left of a trace to expand its details.<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p1294101714446"></p>
<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p1694171715446"><span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image49418175441" src="en-us_image_0000001696838318.png"></span></p>
<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p109481744411"></p>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li1094161784410">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b139145611337">View Trace</strong> in the <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1591756103313">Operation</strong> column. The trace details are displayed.<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p1695161714447"><span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image1904172011220" src="en-us_image_0000001758618249.png"></span></p>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li129561719446">For details about key fields in the trace structure, see section "Trace References" &gt; "Trace Structure" and section "Trace References" &gt; "Example Traces".</li></ol>
</div>
</div>
<div>

6
docs/cce/umn/cce_10_0028.html
View File

@ -5,16 +5,16 @@
<div class="section" id="cce_10_0028__section1386743114294"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0028__ul686414167496"><li id="cce_10_0028__li190817135320">During the node creation, software packages are downloaded from OBS using the domain name. Use a private DNS server to resolve the OBS domain name, and configure the DNS server address of the subnet where the node resides with a private DNS server address. When you create a subnet, the private DNS server is used by default. If you change the subnet DNS, ensure that the DNS server in use can resolve the OBS domain name.</li><li id="cce_10_0028__li124606217339">You can create a maximum of 50 clusters in a single region.</li><li id="cce_10_0028__li1186441616491">After a cluster is created, the following items cannot be changed:<ul id="cce_10_0028__ul1386431634910"><li id="cce_10_0028__li6864131614492">Cluster type</li><li id="cce_10_0028__li359558115311">Number of master nodes in the cluster</li><li id="cce_10_0028__li452948112016">AZ of a master node</li><li id="cce_10_0028__li1686412165496">Network configuration of the cluster, such as the VPC, subnet, container CIDR block, Service CIDR block, and kube-proxy (<a href="#cce_10_0028__li1895772174715">request forwarding</a>) settings.</li><li id="cce_10_0028__li1686451618494">Network model. For example, change <strong id="cce_10_0028__b16979154810810">Tunnel network</strong> to <strong id="cce_10_0028__b1297916485820">VPC network</strong>.</li></ul>
</li></ul>
</div>
<div class="section" id="cce_10_0028__section176228482126"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0028__ol1233331493511"><li id="cce_10_0028__li16411127162211"><span>Log in to the CCE console.</span></li><li id="cce_10_0028__li833491416359"><span>Choose <strong id="cce_10_0028__b1495755015314">Clusters</strong>. On the displayed page, select the type of the cluster to be created and click <strong id="cce_10_0028__b6697519153215">Create</strong>.</span></li><li id="cce_10_0028__li1569162220359"><span>Specify cluster parameters.</span><p><div class="p" id="cce_10_0028__p5653205823718"><strong id="cce_10_0028__b14641318112618">Basic Settings</strong><ul id="cce_10_0028__ul5395195853710"><li id="cce_10_0028__li1739455810379"><strong id="cce_10_0028__b2652101414325">Cluster Name</strong>: indicates the name of the cluster to be created. The cluster name must be unique under the same account.</li><li id="cce_10_0028__li163957587379"><strong id="cce_10_0028__b17378145120437">Cluster Version</strong>: Select the Kubernetes version used by the cluster.</li><li id="cce_10_0028__li5395358163711"><strong id="cce_10_0028__b1770657104313">Cluster Scale</strong>: maximum number of nodes that can be managed by the cluster. </li><li id="cce_10_0028__li467617271013">HA: distribution mode of master nodes. By default, master nodes are randomly distributed in different AZs to improve DR capabilities.<div class="p" id="cce_10_0028__p15811036101"><a name="cce_10_0028__li467617271013"></a><a name="li467617271013"></a>You can also expand advanced settings and customize the master node distribution mode. The following two modes are supported:<ul id="cce_10_0028__ul729432918812"><li id="cce_10_0028__li1529418293815"><strong id="cce_10_0028__b1929619586454">Random</strong>: Master nodes are created in different AZs for DR.</li><li id="cce_10_0028__li103958393117"><strong id="cce_10_0028__b5810610331">Custom</strong>: You can determine the location of each master node.<ul id="cce_10_0028__ul1220719413117"><li id="cce_10_0028__li62941529381"><strong id="cce_10_0028__b292085817517">Host</strong>: Master nodes are created on different hosts in the same AZ.</li><li id="cce_10_0028__li32946293815"><strong id="cce_10_0028__b01923920215">Custom</strong>: You can determine the location of each master node.</li></ul>
<div class="section" id="cce_10_0028__section176228482126"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0028__ol1233331493511"><li id="cce_10_0028__li16411127162211"><span>Log in to the CCE console.</span></li><li id="cce_10_0028__li833491416359"><span>Choose <strong id="cce_10_0028__b1495755015314">Clusters</strong>. On the displayed page, select the type of the cluster to be created and click <strong id="cce_10_0028__b6697519153215">Create</strong>.</span></li><li id="cce_10_0028__li1569162220359"><span>Specify cluster parameters.</span><p><div class="p" id="cce_10_0028__p5653205823718"><strong id="cce_10_0028__b14641318112618">Basic Settings</strong><ul id="cce_10_0028__ul5395195853710"><li id="cce_10_0028__li1739455810379"><strong id="cce_10_0028__b867717243124">Cluster Name</strong>: indicates the name of the cluster to be created. The cluster name must be unique under the same account.</li><li id="cce_10_0028__li163957587379"><strong id="cce_10_0028__b17378145120437">Cluster Version</strong>: Select the Kubernetes version used by the cluster.</li><li id="cce_10_0028__li5395358163711"><strong id="cce_10_0028__b1770657104313">Cluster Scale</strong>: maximum number of nodes that can be managed by the cluster. </li><li id="cce_10_0028__li467617271013"><strong id="cce_10_0028__b4655192215911">HA</strong>: distribution mode of master nodes. By default, master nodes are randomly distributed in different AZs to improve DR capabilities.<div class="p" id="cce_10_0028__p15811036101">You can also expand advanced settings and customize the master node distribution mode. The following two modes are supported:<ul id="cce_10_0028__ul729432918812"><li id="cce_10_0028__li1529418293815"><strong id="cce_10_0028__b1929619586454">Random</strong>: Master nodes are created in different AZs for DR.</li><li id="cce_10_0028__li103958393117"><strong id="cce_10_0028__b5810610331">Custom</strong>: You can determine the location of each master node.<ul id="cce_10_0028__ul1220719413117"><li id="cce_10_0028__li62941529381"><strong id="cce_10_0028__b292085817517">Host</strong>: Master nodes are created on different hosts in the same AZ.</li><li id="cce_10_0028__li32946293815"><strong id="cce_10_0028__b01923920215">Custom</strong>: You can determine the location of each master node.</li></ul>
</li></ul>
</div>
</li></ul>
</div>
<p id="cce_10_0028__p1816113443815"><strong id="cce_10_0028__b156891146112919">Network Settings</strong></p>
<p id="cce_10_0028__p850019415499">The cluster network settings cover nodes, containers, and Services. For details about the cluster networking and container network models, see <a href="cce_10_0010.html">Overview</a>.</p>
<ul id="cce_10_0028__ul1923917171387"><li id="cce_10_0028__li12239017103811">Network Model: CCE clusters support <span class="uicontrol" id="cce_10_0028__uicontrol19729415374"><b>VPC network</b></span> and <span class="uicontrol" id="cce_10_0028__uicontrol10972104133713"><b>Tunnel network</b></span>. CCE Turbo clusters support <span class="uicontrol" id="cce_10_0028__uicontrol7643123519375"><b>Cloud Native Network 2.0.</b></span>. For details, see <a href="cce_10_0281.html">Overview</a>.</li><li id="cce_10_0028__li551715378214"><strong id="cce_10_0028__b112892113017">VPC</strong>: Select the VPC to which the cluster belongs. If no VPC is available, click <strong id="cce_10_0028__b4281322305">Create VPC</strong> to create one. The value cannot be changed after creation.</li><li id="cce_10_0028__li270184618382"><strong id="cce_10_0028__b7755955308">Master Node Subnet</strong>: Select the subnet where the master node is deployed. If no subnet is available, click <strong id="cce_10_0028__b15755858308">Create Subnet</strong> to create one. The subnet cannot be changed after creation.</li><li id="cce_10_0028__li17658613185"><strong id="cce_10_0028__b7492195291610">Container CIDR Block</strong> (CCE Cluster): Specify the CIDR block used by containers, which determines the maximum number of containers in the cluster. </li><li id="cce_10_0028__li1915125922118"><strong id="cce_10_0028__b587920114287">Default Pod Subnet</strong> (CCE Turbo Cluster): Select the subnet where the container is located. If no subnet is available, click <span class="uicontrol" id="cce_10_0028__uicontrol1339574710456"><b>Create Subnet</b></span>. The pod subnet determines the maximum number of containers in the cluster. You can add pod subnets after creating the cluster.</li><li id="cce_10_0028__li411411954713"><strong id="cce_10_0028__b1371915515249">Service CIDR Block</strong>: CIDR block for Services used by containers in the same cluster to access each other. The value determines the maximum number of Services you can create. The value cannot be changed after creation.</li></ul>
<ul id="cce_10_0028__ul1923917171387"><li id="cce_10_0028__li12239017103811"><strong id="cce_10_0028__b194141262014">Network Model</strong>: CCE clusters support <span class="uicontrol" id="cce_10_0028__uicontrol19729415374"><b>VPC network</b></span> and <span class="uicontrol" id="cce_10_0028__uicontrol10972104133713"><b>Tunnel network</b></span>. CCE Turbo clusters support <span class="uicontrol" id="cce_10_0028__uicontrol7643123519375"><b>Cloud Native Network 2.0.</b></span>. For details, see <a href="cce_10_0281.html">Overview</a>.</li><li id="cce_10_0028__li551715378214"><strong id="cce_10_0028__b112892113017">VPC</strong>: Select the VPC to which the cluster belongs. If no VPC is available, click <strong id="cce_10_0028__b4281322305">Create VPC</strong> to create one. The value cannot be changed after creation.</li><li id="cce_10_0028__li270184618382"><strong id="cce_10_0028__b7755955308">Master Node Subnet</strong>: Select the subnet where the master node is deployed. If no subnet is available, click <strong id="cce_10_0028__b15755858308">Create Subnet</strong> to create one. The subnet cannot be changed after creation.</li><li id="cce_10_0028__li17658613185"><strong id="cce_10_0028__b7492195291610">Container CIDR Block</strong> (CCE Cluster): Specify the CIDR block used by containers, which determines the maximum number of containers in the cluster. </li><li id="cce_10_0028__li1915125922118"><strong id="cce_10_0028__b587920114287">Default Pod Subnet</strong> (CCE Turbo Cluster): Select the subnet where the container is located. If no subnet is available, click <span class="uicontrol" id="cce_10_0028__uicontrol1339574710456"><b>Create Subnet</b></span>. The pod subnet determines the maximum number of containers in the cluster. You can add pod subnets after creating the cluster.</li><li id="cce_10_0028__li411411954713"><strong id="cce_10_0028__b1371915515249">IPv4 Service CIDR Block</strong>: CIDR block for Services used by containers in the same cluster to access each other. The value determines the maximum number of Services you can create. The value cannot be changed after creation.</li></ul>
<p id="cce_10_0028__p3866175612467"><strong id="cce_10_0028__b0441658114611">Advanced Settings</strong></p>
<ul id="cce_10_0028__ul89571727475"><li id="cce_10_0028__li1895772174715"><a name="cce_10_0028__li1895772174715"></a><a name="li1895772174715"></a><strong id="cce_10_0028__b18677104202412">Request Forwarding</strong>: The IPVS and iptables modes are supported. For details, see <a href="cce_10_0349.html">Comparing iptables and IPVS</a>.</li><li id="cce_10_0028__li1736133045414"><strong id="cce_10_0028__b388665713297">CPU Manager</strong>: When enabled, CPU cores will be exclusively allocated to workload pods. For details, see <a href="cce_10_0351.html">CPU Policy</a>.</li><li id="cce_10_0028__li086416351551">Resource Tag:<p id="cce_10_0028__p1352104214110"><a name="cce_10_0028__li086416351551"></a><a name="li086416351551"></a>You can add resource tags to classify resources.</p>
<ul id="cce_10_0028__ul89571727475"><li id="cce_10_0028__li1895772174715"><a name="cce_10_0028__li1895772174715"></a><a name="li1895772174715"></a><strong id="cce_10_0028__b18677104202412">Request Forwarding</strong>: The IPVS and iptables modes are supported. For details, see <a href="cce_10_0349.html">Comparing iptables and IPVS</a>.</li><li id="cce_10_0028__li1736133045414"><strong id="cce_10_0028__b388665713297">CPU Manager</strong>: When enabled, CPU cores will be exclusively allocated to workload pods. For details, see <a href="cce_10_0351.html">CPU Policy</a>.</li><li id="cce_10_0028__li086416351551"><strong id="cce_10_0028__b1956917394210">Resource Tag</strong>:<p id="cce_10_0028__p1352104214110">You can add resource tags to classify resources.</p>
</li><li id="cce_10_0028__li1045281605310"><strong id="cce_10_0028__b6538204304212">Certificate Authentication</strong>:<ul id="cce_10_0028__ul8453616205317"><li id="cce_10_0028__li104539168533"><strong id="cce_10_0028__b220412510445">Default</strong>: The X509-based authentication mode is enabled by default. X509 is a commonly used certificate format.</li><li id="cce_10_0028__li8453141615535"><strong id="cce_10_0028__b16300163832117">Custom:</strong> The cluster can identify users based on the header in the request body for authentication. <p id="cce_10_0028__p184531416105312">Upload your <strong id="cce_10_0028__b845836182415">CA root certificate</strong>, <strong id="cce_10_0028__b164583622416">client certificate</strong>, and <strong id="cce_10_0028__b194581169243">private key</strong> of the client certificate.</p>
<div class="caution" id="cce_10_0028__note13453101613535"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="cce_10_0028__ul34531816155312"><li id="cce_10_0028__li114531516195313">Upload a file <strong id="cce_10_0028__b199411240122414">smaller than 1 MiB</strong>. The CA certificate and client certificate can be in <strong id="cce_10_0028__b1195014407247">.crt</strong> or <strong id="cce_10_0028__b15950140182418">.cer</strong> format. The private key of the client certificate can only be uploaded <strong id="cce_10_0028__b199501540102417">unencrypted</strong>.</li><li id="cce_10_0028__li18453516185319">The validity period of the client certificate must be longer than five years.</li><li id="cce_10_0028__li104531916125318">The uploaded CA certificate is used for both the authentication proxy and the kube-apiserver aggregation layer configuration. <strong id="cce_10_0028__b19737142016505">If the certificate is invalid, the cluster cannot be created</strong>.</li><li id="cce_10_0028__li6694716185918">Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. You are advised to use the SHA256 algorithm.</li></ul>
</div></div>

2
docs/cce/umn/cce_10_0036.html
View File

@ -5,7 +5,7 @@
</div>
<div class="section" id="cce_10_0036__section1489437103610"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0036__ul0917755162415"><li id="cce_10_0036__li1891719552246">Deleting a node will lead to pod migration, which may affect services. Therefore, delete nodes during off-peak hours.</li><li id="cce_10_0036__li791875552416">Unexpected risks may occur during node deletion. Back up related data in advance.</li><li id="cce_10_0036__li15918105582417">While the node is being deleted, the backend will set the node to the unschedulable state.</li><li id="cce_10_0036__li12918145520241">Only worker nodes can be stopped.</li></ul>
</div>
<div class="section" id="cce_10_0036__section14341135612442"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0036__ol5687174923613"><li id="cce_10_0036__li133915311359"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0036__li6687049203616"><span>In the navigation pane, choose <strong id="cce_10_0036__b0764291362">Nodes</strong>. In the right pane, click the name of the node to be stopped.</span></li><li id="cce_10_0036__li117301253183717"><span>In the upper right corner of the ECS details page, click <strong id="cce_10_0036__b109484372618">Stop</strong>. In the displayed dialog box, click <strong id="cce_10_0036__b29489372612">Yes</strong>.</span><p><div class="fignone" id="cce_10_0036__fig19269101385311"><span class="figcap"><b>Figure 1 </b>ECS details page</span><br><span><img id="cce_10_0036__image6847636155" src="en-us_image_0000001647417648.png"></span></div>
<div class="section" id="cce_10_0036__section14341135612442"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0036__ol5687174923613"><li id="cce_10_0036__li133915311359"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0036__li6687049203616"><span>In the navigation pane, choose <strong id="cce_10_0036__b0764291362">Nodes</strong>. In the right pane, click the name of the node to be stopped.</span></li><li id="cce_10_0036__li117301253183717"><span>In the upper right corner of the ECS details page, click <strong id="cce_10_0036__b109484372618">Stop</strong>. In the displayed dialog box, click <strong id="cce_10_0036__b29489372612">Yes</strong>.</span><p><div class="fignone" id="cce_10_0036__fig19269101385311"><span class="figcap"><b>Figure 1 </b>ECS details page</span><br><span><img id="cce_10_0036__image124001418192" src="en-us_image_0000001782097306.png"></span></div>
</p></li></ol>
</div>
</div>

46
docs/cce/umn/cce_10_0047.html
View File

@ -7,64 +7,64 @@
</div></div>
</li></ul>
</div>
<div class="section" id="cce_10_0047__section1996635141916"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0047__ol2012902601117"><li id="cce_10_0047__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0047__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0047__b1421120185819">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0047__b139221951155717">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0047__li67891737151520"><span>Set basic information about the workload. </span><p><div class="p" id="cce_10_0047__p1259466151612"><strong id="cce_10_0047__b1493704971917">Basic Info</strong><ul id="cce_10_0047__ul6954101318184"><li id="cce_10_0047__li11514131617185"><strong id="cce_10_0047__b17688966208">Workload Type</strong>: Select <strong id="cce_10_0047__b19319191110206">Deployment</strong>. For details about workload types, see <a href="cce_10_0006.html">Overview</a>.</li><li id="cce_10_0047__li129541213101814"><strong id="cce_10_0047__b12465144313510">Workload Name</strong>: Enter the name of the workload. Enter 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</li><li id="cce_10_0047__li179541813111814"><strong id="cce_10_0047__b20501185611511">Namespace</strong>: Select the namespace of the workload. The default value is <strong id="cce_10_0047__b1508155615514">default</strong>. You can also click <span class="uicontrol" id="cce_10_0047__uicontrol342862818214"><b>Create Namespace</b></span> to create one. For details, see <a href="cce_10_0278.html">Creating a Namespace</a>.</li><li id="cce_10_0047__li18955181315189"><strong id="cce_10_0047__b1997313316218">Pods</strong>: Enter the number of pods of the workload.</li><li id="cce_10_0047__li11753142112539"><strong id="cce_10_0047__b1111971612">Container Runtime</strong>: A CCE cluster uses runC by default, whereas a CCE Turbo cluster supports both runC and Kata. For details about the differences, see <a href="cce_10_0463.html">Kata Runtime and Common Runtime</a>.</li><li id="cce_10_0047__li1295571341818"><strong id="cce_10_0047__b4596419068">Time Zone Synchronization</strong>: Specify whether to enable time zone synchronization. After time zone synchronization is enabled, the container and node use the same time zone. The time zone synchronization function depends on the local disk mounted to the container. Do not modify or delete the time zone. For details, see <a href="cce_10_0354.html">Configuring Time Zone Synchronization</a>.</li></ul>
<div class="section" id="cce_10_0047__section1996635141916"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0047__ol2012902601117"><li id="cce_10_0047__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0047__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0047__b1421120185819">Workloads</strong> in the navigation pane, and click <strong id="cce_10_0047__b139221951155717">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0047__li67891737151520"><span>Set basic information about the workload. </span><p><div class="p" id="cce_10_0047__p1259466151612"><strong id="cce_10_0047__b1493704971917">Basic Info</strong><ul id="cce_10_0047__ul6954101318184"><li id="cce_10_0047__li11514131617185"><strong id="cce_10_0047__b17688966208">Workload Type</strong>: Select <strong id="cce_10_0047__b19319191110206">Deployment</strong>. For details about workload types, see <a href="cce_10_0006.html">Overview</a>.</li><li id="cce_10_0047__li129541213101814"><strong id="cce_10_0047__b12465144313510">Workload Name</strong>: Enter the name of the workload. Enter 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</li><li id="cce_10_0047__li179541813111814"><strong id="cce_10_0047__b20501185611511">Namespace</strong>: Select the namespace of the workload. The default value is <strong id="cce_10_0047__b1508155615514">default</strong>. You can also click <span class="uicontrol" id="cce_10_0047__uicontrol342862818214"><b>Create Namespace</b></span> to create one. For details, see <a href="cce_10_0278.html">Creating a Namespace</a>.</li><li id="cce_10_0047__li18955181315189"><strong id="cce_10_0047__b1997313316218">Pods</strong>: Enter the number of pods of the workload.</li><li id="cce_10_0047__li11753142112539"><strong id="cce_10_0047__b1111971612">Container Runtime</strong>: A CCE cluster uses runC by default, whereas a CCE Turbo cluster supports both runC and Kata. For details about the differences, see <a href="cce_10_0463.html">Kata Runtime and Common Runtime</a>.</li><li id="cce_10_0047__li1295571341818"><strong id="cce_10_0047__b4596419068">Time Zone Synchronization</strong>: Specify whether to enable time zone synchronization. After time zone synchronization is enabled, the container and node use the same time zone. The time zone synchronization function depends on the local disk mounted to the container. Do not modify or delete the time zone. For details, see <a href="cce_10_0354.html">Configuring Time Zone Synchronization</a>.</li></ul>
</div>
<div class="p" id="cce_10_0047__p206571518181616"><strong id="cce_10_0047__b062716554277">Container Settings</strong><ul id="cce_10_0047__ul42071022103320"><li id="cce_10_0047__li8770480458">Container Information<div class="p" id="cce_10_0047__p10493941854"><a name="cce_10_0047__li8770480458"></a><a name="li8770480458"></a>Multiple containers can be configured in a pod. You can click <span class="uicontrol" id="cce_10_0047__uicontrol2024214181967"><b>Add Container</b></span> on the right to configure multiple containers for the pod.<ul id="cce_10_0047__ul10714183717111"><li id="cce_10_0047__li1471463741113"><strong id="cce_10_0047__b2309121414294">Basic Info</strong>: Configure basic information about the container.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0047__table128216444815" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0047__row0282348486"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1"><p id="cce_10_0047__p3282147483">Parameter</p>
<div class="p" id="cce_10_0047__p206571518181616"><strong id="cce_10_0047__b062716554277">Container Settings</strong><ul id="cce_10_0047__ul42071022103320"><li id="cce_10_0047__li8770480458"><strong id="cce_10_0047__b1139817233377">Container Information</strong><div class="p" id="cce_10_0047__p10493941854">Multiple containers can be configured in a pod. You can click <span class="uicontrol" id="cce_10_0047__uicontrol2024214181967"><b>Add Container</b></span> on the right to configure multiple containers for the pod.<ul id="cce_10_0047__ul10714183717111"><li id="cce_10_0047__li1471463741113"><strong id="cce_10_0047__b2309121414294">Basic Info</strong>: Configure basic information about the container.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0047__table128216444815" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0047__row0282348486"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1"><p id="cce_10_0047__p3282147483">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2"><p id="cce_10_0047__p1828244144819">Description</p>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2"><p id="cce_10_0047__p1828244144819">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0047__row109911651125414"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p39922517546">Container Name</p>
<tbody><tr id="cce_10_0047__row109911651125414"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p39922517546">Container Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p13992551175414">Name the container.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p13992551175414">Name the container.</p>
</td>
</tr>
<tr id="cce_10_0047__row1129176194611"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p1945419542371">Pull Policy</p>
<tr id="cce_10_0047__row1129176194611"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p1945419542371">Pull Policy</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p1445445483719">Image update or pull policy. If you select <strong id="cce_10_0047__b1494134319294">Always</strong>, the image is pulled from the image repository each time. If you do not select <strong id="cce_10_0047__b694144313295">Always</strong>, the existing image of the node is preferentially used. If the image does not exist, the image is pulled from the image repository.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p1445445483719">Image update or pull policy. If you select <strong id="cce_10_0047__b1494134319294">Always</strong>, the image is pulled from the image repository each time. If you do not select <strong id="cce_10_0047__b694144313295">Always</strong>, the existing image of the node is preferentially used. If the image does not exist, the image is pulled from the image repository.</p>
</td>
</tr>
<tr id="cce_10_0047__row1844916557597"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p182837474815">Image Name</p>
<tr id="cce_10_0047__row1844916557597"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p182837474815">Image Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p1372913120568">Click <strong id="cce_10_0047__b8790125722910">Select Image</strong> and select the image used by the container.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p1372913120568">Click <strong id="cce_10_0047__b8790125722910">Select Image</strong> and select the image used by the container.</p>
<p id="cce_10_0047__p137884754811">To use a third-party image, see <a href="cce_10_0009.html">Using Third-Party Images</a>.</p>
</td>
</tr>
<tr id="cce_10_0047__row338117362515"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p1038143616517">Image Tag</p>
<tr id="cce_10_0047__row338117362515"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p1038143616517">Image Tag</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p1338110368519">Select the image tag to be deployed.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p1338110368519">Select the image tag to be deployed.</p>
</td>
</tr>
<tr id="cce_10_0047__row161110459565"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p56111845145612">CPU Quota</p>
<tr id="cce_10_0047__row161110459565"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p56111845145612">CPU Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><ul id="cce_10_0047__ul9168521572"><li id="cce_10_0047__li15168227577"><strong id="cce_10_0047__b3669018123014">Request</strong>: minimum number of CPU cores required by a container. The default value is 0.25 cores.</li><li id="cce_10_0047__li121681216579"><strong id="cce_10_0047__b833715229303">Limit</strong>: maximum number of CPU cores available for a container. Do not leave <strong id="cce_10_0047__b1257625123019">Limit</strong> unspecified. Otherwise, intensive use of container resources will occur and your workload may exhibit unexpected behavior.</li></ul>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><ul id="cce_10_0047__ul9168521572"><li id="cce_10_0047__li15168227577"><strong id="cce_10_0047__b3669018123014">Request</strong>: minimum number of CPU cores required by a container. The default value is 0.25 cores.</li><li id="cce_10_0047__li121681216579"><strong id="cce_10_0047__b833715229303">Limit</strong>: maximum number of CPU cores available for a container. Do not leave <strong id="cce_10_0047__b1257625123019">Limit</strong> unspecified. Otherwise, intensive use of container resources will occur and your workload may exhibit unexpected behavior.</li></ul>
<p id="cce_10_0047__p520715505213">If <strong id="cce_10_0047__b2160104553012">Request</strong> and <strong id="cce_10_0047__b16757125053014">Limit</strong> are not specified, the quota is not limited. For more information and suggestions about <strong id="cce_10_0047__b12633192718313">Request</strong> and <strong id="cce_10_0047__b3633227113119">Limit</strong>, see <a href="cce_10_0163.html">Setting Container Specifications</a>.</p>
</td>
</tr>
<tr id="cce_10_0047__row1119234316562"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p13193154315561">Memory Quota</p>
<tr id="cce_10_0047__row1119234316562"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p13193154315561">Memory Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><ul id="cce_10_0047__ul177605101578"><li id="cce_10_0047__li2760310155716"><strong id="cce_10_0047__b1482892418326">Request</strong>: minimum amount of memory required by a container. The default value is 512 MiB.</li><li id="cce_10_0047__li276012107576"><strong id="cce_10_0047__b89641128203220">Limit</strong>: maximum amount of memory available for a container. When memory usage exceeds the specified memory limit, the container will be terminated.</li></ul>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><ul id="cce_10_0047__ul177605101578"><li id="cce_10_0047__li2760310155716"><strong id="cce_10_0047__b1482892418326">Request</strong>: minimum amount of memory required by a container. The default value is 512 MiB.</li><li id="cce_10_0047__li276012107576"><strong id="cce_10_0047__b89641128203220">Limit</strong>: maximum amount of memory available for a container. When memory usage exceeds the specified memory limit, the container will be terminated.</li></ul>
<p id="cce_10_0047__p1974151022320">If <strong id="cce_10_0047__b1947843817326">Request</strong> and <strong id="cce_10_0047__b1347893819328">Limit</strong> are not specified, the quota is not limited. For more information and suggestions about <strong id="cce_10_0047__b1790014814322">Request</strong> and <strong id="cce_10_0047__b2900174810324">Limit</strong>, see <a href="cce_10_0163.html">Setting Container Specifications</a>.</p>
</td>
</tr>
<tr id="cce_10_0047__row272852945719"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p20728192912572">(Optional) GPU Quota</p>
<tr id="cce_10_0047__row272852945719"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p20728192912572">(Optional) GPU Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p53791055710">Configurable only when the cluster contains GPU nodes and the <a href="cce_10_0141.html">gpu-beta</a> add-on is installed.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p53791055710">Configurable only when the cluster contains GPU nodes and the <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a> add-on is installed.</p>
<ul id="cce_10_0047__ul19823440122219"><li id="cce_10_0047__li14823540152219"><strong id="cce_10_0047__b74394181358">All</strong>: The GPU is not used.</li><li id="cce_10_0047__li128232405222"><strong id="cce_10_0047__b2930224153512">Dedicated</strong>: GPU resources are exclusively used by the container.</li><li id="cce_10_0047__li13823440182213"><strong id="cce_10_0047__b1433212715356">Shared</strong>: percentage of GPU resources used by the container. For example, if this parameter is set to <strong id="cce_10_0047__b13332192713352">10%</strong>, the container uses 10% of GPU resources.</li></ul>
<p id="cce_10_0047__p91801538202613">For details about how to use GPU in the cluster, see <a href="cce_10_0345.html">Default GPU Scheduling in Kubernetes</a>.</p>
</td>
</tr>
<tr id="cce_10_0047__row1449911299503"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p53374336504">(Optional) Privileged Container</p>
<tr id="cce_10_0047__row1449911299503"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p53374336504">(Optional) Privileged Container</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p49887211526">Programs in a privileged container have certain privileges.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p49887211526">Programs in a privileged container have certain privileges.</p>
<p id="cce_10_0047__p65001729105011">If <strong id="cce_10_0047__b55525534015">Privileged Container</strong> is enabled, the container is assigned privileges. For example, privileged containers can manipulate network devices on the host machine and modify kernel parameters.</p>
</td>
</tr>
<tr id="cce_10_0047__row152831345485"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0047__p875325925918">(Optional) Init Container</p>
<tr id="cce_10_0047__row152831345485"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0047__p875325925918">(Optional) Init Container</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0047__p5379182494610">Indicates whether to use the container as an init container. The init container does not support health check.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0047__p5379182494610">Indicates whether to use the container as an init container. The init container does not support health check.</p>
<p id="cce_10_0047__p191910221439">An init container is a special container that runs before other app containers in a pod are started. Each pod can contain multiple containers. In addition, a pod can contain one or more Init containers. Application containers in a pod are started and run only after the running of all Init containers completes. For details, see <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/" target="_blank" rel="noopener noreferrer">Init Container</a>.</p>
</td>
</tr>
@ -81,7 +81,7 @@
<p id="cce_10_0047__p1447162741615"><strong id="cce_10_0047__b154561192487">(Optional) Service Settings</strong></p>
<p id="cce_10_0047__p102354303348">A Service provides external access for pods. With a static IP address, a Service forwards access traffic to pods and performs automatic load balancing for these pods.</p>
<p id="cce_10_0047__p13343123113612">You can also create a Service after creating a workload. For details about Services of different types, see <a href="cce_10_0249.html">Overview</a>.</p>
<div class="p" id="cce_10_0047__p310913521612"><strong id="cce_10_0047__b204881212144816">(Optional) Advanced Settings</strong><ul id="cce_10_0047__ul142811417"><li id="cce_10_0047__li0421513417">Upgrade: Specify the upgrade mode and upgrade parameters of the workload. <strong id="cce_10_0047__b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0047__b1621251402">Replace upgrade</strong> are supported. For details, see <a href="cce_10_0397.html">Configuring the Workload Upgrade Policy</a>.</li><li id="cce_10_0047__li5292111713411"><strong id="cce_10_0047__b1207102116016">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Node affinity, pod affinity, and pod anti-affinity are supported. For details, see <a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a>.</li><li id="cce_10_0047__li13285132913414"><strong id="cce_10_0047__b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Taints and Tolerations</a>.</li><li id="cce_10_0047__li179714209414"><a name="cce_10_0047__li179714209414"></a><a name="li179714209414"></a><strong id="cce_10_0047__b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0047__b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Labels and Annotations</a>.</li><li id="cce_10_0047__li1917237124111"><strong id="cce_10_0047__b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0047__li191696549535">Network configuration:<ul id="cce_10_0047__ul101792551538"><li id="cce_10_0047__li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS Rate Limiting for Inter-Pod Access</a>.</li></ul>
<div class="p" id="cce_10_0047__p310913521612"><strong id="cce_10_0047__b204881212144816">(Optional) Advanced Settings</strong><ul id="cce_10_0047__ul142811417"><li id="cce_10_0047__li0421513417"><strong id="cce_10_0047__b106642818334">Upgrade</strong>: Specify the upgrade mode and upgrade parameters of the workload. <strong id="cce_10_0047__b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0047__b1621251402">Replace upgrade</strong> are supported. For details, see <a href="cce_10_0397.html">Configuring the Workload Upgrade Policy</a>.</li><li id="cce_10_0047__li5292111713411"><strong id="cce_10_0047__b1207102116016">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Node affinity, pod affinity, and pod anti-affinity are supported. For details, see <a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a>.</li><li id="cce_10_0047__li13285132913414"><strong id="cce_10_0047__b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Taints and Tolerations</a>.</li><li id="cce_10_0047__li179714209414"><a name="cce_10_0047__li179714209414"></a><a name="li179714209414"></a><strong id="cce_10_0047__b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0047__b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Labels and Annotations</a>.</li><li id="cce_10_0047__li1917237124111"><strong id="cce_10_0047__b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0047__li191696549535"><strong id="cce_10_0047__b5838184390">Network Configuration</strong>:<ul id="cce_10_0047__ul101792551538"><li id="cce_10_0047__li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS Rate Limiting for Inter-Pod Access</a>.</li></ul>
</li></ul>
</div>
</p></li><li id="cce_10_0047__li01417411620"><span>Click <strong id="cce_10_0047__b5824103317919">Create Workload</strong> in the lower right corner.</span></li></ol>

48
docs/cce/umn/cce_10_0048.html
View File

@ -10,64 +10,64 @@
</div></div>
</li></ul>
</div>
<div class="section" id="cce_10_0048__section16385130102112"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0048__ol2012902601117"><li id="cce_10_0048__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0048__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0048__b94442390613">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0048__b1844413910614">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0048__li67891737151520"><span>Set basic information about the workload. </span><p><div class="p" id="cce_10_0048__p1259466151612"><strong id="cce_10_0048__b64930521915">Basic Info</strong><ul id="cce_10_0048__ul6954101318184"><li id="cce_10_0048__li11514131617185"><strong id="cce_10_0048__b19311135410116">Workload Type</strong>: Select <strong id="cce_10_0048__b0311195410110">StatefulSet</strong>. For details about workload types, see <a href="cce_10_0006.html">Overview</a>.</li><li id="cce_10_0048__li129541213101814"><strong id="cce_10_0048__cce_10_0047_b12465144313510">Workload Name</strong>: Enter the name of the workload. Enter 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</li><li id="cce_10_0048__li179541813111814"><strong id="cce_10_0048__cce_10_0047_b20501185611511">Namespace</strong>: Select the namespace of the workload. The default value is <strong id="cce_10_0048__cce_10_0047_b1508155615514">default</strong>. You can also click <span class="uicontrol" id="cce_10_0048__cce_10_0047_uicontrol342862818214"><b>Create Namespace</b></span> to create one. For details, see <a href="cce_10_0278.html">Creating a Namespace</a>.</li><li id="cce_10_0048__li18955181315189"><strong id="cce_10_0048__cce_10_0047_b1997313316218">Pods</strong>: Enter the number of pods of the workload.</li><li id="cce_10_0048__li11753142112539"><strong id="cce_10_0048__cce_10_0047_b1111971612">Container Runtime</strong>: A CCE cluster uses runC by default, whereas a CCE Turbo cluster supports both runC and Kata. For details about the differences, see <a href="cce_10_0463.html">Kata Runtime and Common Runtime</a>.</li><li id="cce_10_0048__li198695115505"><strong id="cce_10_0048__cce_10_0047_b4596419068">Time Zone Synchronization</strong>: Specify whether to enable time zone synchronization. After time zone synchronization is enabled, the container and node use the same time zone. The time zone synchronization function depends on the local disk mounted to the container. Do not modify or delete the time zone. For details, see <a href="cce_10_0354.html">Configuring Time Zone Synchronization</a>.</li></ul>
<div class="section" id="cce_10_0048__section16385130102112"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0048__ol2012902601117"><li id="cce_10_0048__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0048__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0048__b19521135283915">Workloads</strong> in the navigation pane, and click <strong id="cce_10_0048__b45211752153914">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0048__li67891737151520"><span>Set basic information about the workload. </span><p><div class="p" id="cce_10_0048__p1259466151612"><strong id="cce_10_0048__b64930521915">Basic Info</strong><ul id="cce_10_0048__ul6954101318184"><li id="cce_10_0048__li11514131617185"><strong id="cce_10_0048__b19311135410116">Workload Type</strong>: Select <strong id="cce_10_0048__b0311195410110">StatefulSet</strong>. For details about workload types, see <a href="cce_10_0006.html">Overview</a>.</li><li id="cce_10_0048__li129541213101814"><strong id="cce_10_0048__cce_10_0047_b12465144313510">Workload Name</strong>: Enter the name of the workload. Enter 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</li><li id="cce_10_0048__li179541813111814"><strong id="cce_10_0048__cce_10_0047_b20501185611511">Namespace</strong>: Select the namespace of the workload. The default value is <strong id="cce_10_0048__cce_10_0047_b1508155615514">default</strong>. You can also click <span class="uicontrol" id="cce_10_0048__cce_10_0047_uicontrol342862818214"><b>Create Namespace</b></span> to create one. For details, see <a href="cce_10_0278.html">Creating a Namespace</a>.</li><li id="cce_10_0048__li18955181315189"><strong id="cce_10_0048__cce_10_0047_b1997313316218">Pods</strong>: Enter the number of pods of the workload.</li><li id="cce_10_0048__li11753142112539"><strong id="cce_10_0048__cce_10_0047_b1111971612">Container Runtime</strong>: A CCE cluster uses runC by default, whereas a CCE Turbo cluster supports both runC and Kata. For details about the differences, see <a href="cce_10_0463.html">Kata Runtime and Common Runtime</a>.</li><li id="cce_10_0048__li198695115505"><strong id="cce_10_0048__cce_10_0047_b4596419068">Time Zone Synchronization</strong>: Specify whether to enable time zone synchronization. After time zone synchronization is enabled, the container and node use the same time zone. The time zone synchronization function depends on the local disk mounted to the container. Do not modify or delete the time zone. For details, see <a href="cce_10_0354.html">Configuring Time Zone Synchronization</a>.</li></ul>
</div>
<div class="p" id="cce_10_0048__p206571518181616"><strong id="cce_10_0048__b163231218124">Container Settings</strong><ul id="cce_10_0048__ul42071022103320"><li id="cce_10_0048__li8770480458">Container Information<div class="p" id="cce_10_0048__p10493941854"><a name="cce_10_0048__li8770480458"></a><a name="li8770480458"></a>Multiple containers can be configured in a pod. You can click <span class="uicontrol" id="cce_10_0048__uicontrol75255211621"><b>Add Container</b></span> on the right to configure multiple containers for the pod.<ul id="cce_10_0048__ul481018470119"><li id="cce_10_0048__li18101047191117"><strong id="cce_10_0048__cce_10_0047_b2309121414294">Basic Info</strong>: Configure basic information about the container.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0048__cce_10_0047_table128216444815" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0048__cce_10_0047_row0282348486"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1"><p id="cce_10_0048__cce_10_0047_p3282147483">Parameter</p>
<div class="p" id="cce_10_0048__p206571518181616"><strong id="cce_10_0048__b163231218124">Container Settings</strong><ul id="cce_10_0048__ul42071022103320"><li id="cce_10_0048__li8770480458"><strong id="cce_10_0048__b827317474012">Container Information</strong><div class="p" id="cce_10_0048__p10493941854">Multiple containers can be configured in a pod. You can click <span class="uicontrol" id="cce_10_0048__uicontrol75255211621"><b>Add Container</b></span> on the right to configure multiple containers for the pod.<ul id="cce_10_0048__ul481018470119"><li id="cce_10_0048__li18101047191117"><strong id="cce_10_0048__cce_10_0047_b2309121414294">Basic Info</strong>: Configure basic information about the container.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0048__cce_10_0047_table128216444815" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0048__cce_10_0047_row0282348486"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1"><p id="cce_10_0048__cce_10_0047_p3282147483">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2"><p id="cce_10_0048__cce_10_0047_p1828244144819">Description</p>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2"><p id="cce_10_0048__cce_10_0047_p1828244144819">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0048__cce_10_0047_row109911651125414"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p39922517546">Container Name</p>
<tbody><tr id="cce_10_0048__cce_10_0047_row109911651125414"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p39922517546">Container Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p13992551175414">Name the container.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p13992551175414">Name the container.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row1129176194611"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p1945419542371">Pull Policy</p>
<tr id="cce_10_0048__cce_10_0047_row1129176194611"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p1945419542371">Pull Policy</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p1445445483719">Image update or pull policy. If you select <strong id="cce_10_0048__cce_10_0047_b1494134319294">Always</strong>, the image is pulled from the image repository each time. If you do not select <strong id="cce_10_0048__cce_10_0047_b694144313295">Always</strong>, the existing image of the node is preferentially used. If the image does not exist, the image is pulled from the image repository.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p1445445483719">Image update or pull policy. If you select <strong id="cce_10_0048__cce_10_0047_b1494134319294">Always</strong>, the image is pulled from the image repository each time. If you do not select <strong id="cce_10_0048__cce_10_0047_b694144313295">Always</strong>, the existing image of the node is preferentially used. If the image does not exist, the image is pulled from the image repository.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row1844916557597"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p182837474815">Image Name</p>
<tr id="cce_10_0048__cce_10_0047_row1844916557597"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p182837474815">Image Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p1372913120568">Click <strong id="cce_10_0048__cce_10_0047_b8790125722910">Select Image</strong> and select the image used by the container.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p1372913120568">Click <strong id="cce_10_0048__cce_10_0047_b8790125722910">Select Image</strong> and select the image used by the container.</p>
<p id="cce_10_0048__cce_10_0047_p137884754811">To use a third-party image, see <a href="cce_10_0009.html">Using Third-Party Images</a>.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row338117362515"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p1038143616517">Image Tag</p>
<tr id="cce_10_0048__cce_10_0047_row338117362515"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p1038143616517">Image Tag</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p1338110368519">Select the image tag to be deployed.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p1338110368519">Select the image tag to be deployed.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row161110459565"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p56111845145612">CPU Quota</p>
<tr id="cce_10_0048__cce_10_0047_row161110459565"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p56111845145612">CPU Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><ul id="cce_10_0048__cce_10_0047_ul9168521572"><li id="cce_10_0048__cce_10_0047_li15168227577"><strong id="cce_10_0048__cce_10_0047_b3669018123014">Request</strong>: minimum number of CPU cores required by a container. The default value is 0.25 cores.</li><li id="cce_10_0048__cce_10_0047_li121681216579"><strong id="cce_10_0048__cce_10_0047_b833715229303">Limit</strong>: maximum number of CPU cores available for a container. Do not leave <strong id="cce_10_0048__cce_10_0047_b1257625123019">Limit</strong> unspecified. Otherwise, intensive use of container resources will occur and your workload may exhibit unexpected behavior.</li></ul>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><ul id="cce_10_0048__cce_10_0047_ul9168521572"><li id="cce_10_0048__cce_10_0047_li15168227577"><strong id="cce_10_0048__cce_10_0047_b3669018123014">Request</strong>: minimum number of CPU cores required by a container. The default value is 0.25 cores.</li><li id="cce_10_0048__cce_10_0047_li121681216579"><strong id="cce_10_0048__cce_10_0047_b833715229303">Limit</strong>: maximum number of CPU cores available for a container. Do not leave <strong id="cce_10_0048__cce_10_0047_b1257625123019">Limit</strong> unspecified. Otherwise, intensive use of container resources will occur and your workload may exhibit unexpected behavior.</li></ul>
<p id="cce_10_0048__cce_10_0047_p520715505213">If <strong id="cce_10_0048__cce_10_0047_b2160104553012">Request</strong> and <strong id="cce_10_0048__cce_10_0047_b16757125053014">Limit</strong> are not specified, the quota is not limited. For more information and suggestions about <strong id="cce_10_0048__cce_10_0047_b12633192718313">Request</strong> and <strong id="cce_10_0048__cce_10_0047_b3633227113119">Limit</strong>, see <a href="cce_10_0163.html">Setting Container Specifications</a>.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row1119234316562"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p13193154315561">Memory Quota</p>
<tr id="cce_10_0048__cce_10_0047_row1119234316562"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p13193154315561">Memory Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><ul id="cce_10_0048__cce_10_0047_ul177605101578"><li id="cce_10_0048__cce_10_0047_li2760310155716"><strong id="cce_10_0048__cce_10_0047_b1482892418326">Request</strong>: minimum amount of memory required by a container. The default value is 512 MiB.</li><li id="cce_10_0048__cce_10_0047_li276012107576"><strong id="cce_10_0048__cce_10_0047_b89641128203220">Limit</strong>: maximum amount of memory available for a container. When memory usage exceeds the specified memory limit, the container will be terminated.</li></ul>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><ul id="cce_10_0048__cce_10_0047_ul177605101578"><li id="cce_10_0048__cce_10_0047_li2760310155716"><strong id="cce_10_0048__cce_10_0047_b1482892418326">Request</strong>: minimum amount of memory required by a container. The default value is 512 MiB.</li><li id="cce_10_0048__cce_10_0047_li276012107576"><strong id="cce_10_0048__cce_10_0047_b89641128203220">Limit</strong>: maximum amount of memory available for a container. When memory usage exceeds the specified memory limit, the container will be terminated.</li></ul>
<p id="cce_10_0048__cce_10_0047_p1974151022320">If <strong id="cce_10_0048__cce_10_0047_b1947843817326">Request</strong> and <strong id="cce_10_0048__cce_10_0047_b1347893819328">Limit</strong> are not specified, the quota is not limited. For more information and suggestions about <strong id="cce_10_0048__cce_10_0047_b1790014814322">Request</strong> and <strong id="cce_10_0048__cce_10_0047_b2900174810324">Limit</strong>, see <a href="cce_10_0163.html">Setting Container Specifications</a>.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row272852945719"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p20728192912572">(Optional) GPU Quota</p>
<tr id="cce_10_0048__cce_10_0047_row272852945719"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p20728192912572">(Optional) GPU Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p53791055710">Configurable only when the cluster contains GPU nodes and the <a href="cce_10_0141.html">gpu-beta</a> add-on is installed.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p53791055710">Configurable only when the cluster contains GPU nodes and the <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a> add-on is installed.</p>
<ul id="cce_10_0048__cce_10_0047_ul19823440122219"><li id="cce_10_0048__cce_10_0047_li14823540152219"><strong id="cce_10_0048__cce_10_0047_b74394181358">All</strong>: The GPU is not used.</li><li id="cce_10_0048__cce_10_0047_li128232405222"><strong id="cce_10_0048__cce_10_0047_b2930224153512">Dedicated</strong>: GPU resources are exclusively used by the container.</li><li id="cce_10_0048__cce_10_0047_li13823440182213"><strong id="cce_10_0048__cce_10_0047_b1433212715356">Shared</strong>: percentage of GPU resources used by the container. For example, if this parameter is set to <strong id="cce_10_0048__cce_10_0047_b13332192713352">10%</strong>, the container uses 10% of GPU resources.</li></ul>
<p id="cce_10_0048__cce_10_0047_p91801538202613">For details about how to use GPU in the cluster, see <a href="cce_10_0345.html">Default GPU Scheduling in Kubernetes</a>.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row1449911299503"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p53374336504">(Optional) Privileged Container</p>
<tr id="cce_10_0048__cce_10_0047_row1449911299503"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p53374336504">(Optional) Privileged Container</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p49887211526">Programs in a privileged container have certain privileges.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p49887211526">Programs in a privileged container have certain privileges.</p>
<p id="cce_10_0048__cce_10_0047_p65001729105011">If <strong id="cce_10_0048__cce_10_0047_b55525534015">Privileged Container</strong> is enabled, the container is assigned privileges. For example, privileged containers can manipulate network devices on the host machine and modify kernel parameters.</p>
</td>
</tr>
<tr id="cce_10_0048__cce_10_0047_row152831345485"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p875325925918">(Optional) Init Container</p>
<tr id="cce_10_0048__cce_10_0047_row152831345485"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0048__cce_10_0047_p875325925918">(Optional) Init Container</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p5379182494610">Indicates whether to use the container as an init container. The init container does not support health check.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0048__cce_10_0047_p5379182494610">Indicates whether to use the container as an init container. The init container does not support health check.</p>
<p id="cce_10_0048__cce_10_0047_p191910221439">An init container is a special container that runs before other app containers in a pod are started. Each pod can contain multiple containers. In addition, a pod can contain one or more Init containers. Application containers in a pod are started and run only after the running of all Init containers completes. For details, see <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/" target="_blank" rel="noopener noreferrer">Init Container</a>.</p>
</td>
</tr>
@ -87,9 +87,9 @@
<p id="cce_10_0048__p1447162741615"><strong id="cce_10_0048__b4235027843479">(Optional) Service Settings</strong></p>
<p id="cce_10_0048__p102354303348">A Service provides external access for pods. With a static IP address, a Service forwards access traffic to pods and performs automatic load balancing for these pods.</p>
<p id="cce_10_0048__p13343123113612">You can also create a Service after creating a workload. For details about Services of different types, see <a href="cce_10_0249.html">Overview</a>.</p>
<div class="p" id="cce_10_0048__p310913521612"><strong id="cce_10_0048__b21631580735239">(Optional) Advanced Settings</strong><ul id="cce_10_0048__ul142811417"><li id="cce_10_0048__li0421513417">Upgrade: Specify the upgrade mode and upgrade parameters of the workload. <strong id="cce_10_0048__cce_10_0047_b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0048__cce_10_0047_b1621251402">Replace upgrade</strong> are supported. For details, see <a href="cce_10_0397.html">Configuring the Workload Upgrade Policy</a>.</li><li id="cce_10_0048__li206428507436"><strong id="cce_10_0048__b152411775114">Pod Management Policies</strong>:<p id="cce_10_0048__p151323251334">For some distributed systems, the StatefulSet sequence is unnecessary and/or should not occur. These systems require only uniqueness and identifiers.</p>
<div class="p" id="cce_10_0048__p310913521612"><strong id="cce_10_0048__b21631580735239">(Optional) Advanced Settings</strong><ul id="cce_10_0048__ul142811417"><li id="cce_10_0048__li0421513417"><strong id="cce_10_0048__cce_10_0047_b106642818334">Upgrade</strong>: Specify the upgrade mode and upgrade parameters of the workload. <strong id="cce_10_0048__cce_10_0047_b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0048__cce_10_0047_b1621251402">Replace upgrade</strong> are supported. For details, see <a href="cce_10_0397.html">Configuring the Workload Upgrade Policy</a>.</li><li id="cce_10_0048__li206428507436"><strong id="cce_10_0048__b152411775114">Pod Management Policies</strong>:<p id="cce_10_0048__p151323251334">For some distributed systems, the StatefulSet sequence is unnecessary and/or should not occur. These systems require only uniqueness and identifiers.</p>
<ul id="cce_10_0048__ul758812493316"><li id="cce_10_0048__li258832417338"><strong id="cce_10_0048__b13534251116">OrderedReady</strong>: The StatefulSet will deploy, delete, or scale pods in order and one by one. (The StatefulSet continues only after the previous pod is ready or deleted.) This is the default policy.</li><li id="cce_10_0048__li1558862416338"><strong id="cce_10_0048__b112293521039">Parallel</strong>: The StatefulSet will create pods in parallel to match the desired scale without waiting, and will delete all pods at once.</li></ul>
</li><li id="cce_10_0048__li7127180594"><strong id="cce_10_0048__cce_10_0047_b1207102116016">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Node affinity, pod affinity, and pod anti-affinity are supported. For details, see <a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a>.</li><li id="cce_10_0048__li13285132913414"><strong id="cce_10_0048__cce_10_0047_b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Taints and Tolerations</a>.</li><li id="cce_10_0048__li179714209414"><strong id="cce_10_0048__cce_10_0047_b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0048__cce_10_0047_b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Labels and Annotations</a>.</li><li id="cce_10_0048__li1917237124111"><strong id="cce_10_0048__cce_10_0047_b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0048__li1985863319162">Network configuration:<ul id="cce_10_0048__ul9870163414162"><li id="cce_10_0048__li8488616152">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS Rate Limiting for Inter-Pod Access</a>.</li></ul>
</li><li id="cce_10_0048__li7127180594"><strong id="cce_10_0048__cce_10_0047_b1207102116016">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Node affinity, pod affinity, and pod anti-affinity are supported. For details, see <a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a>.</li><li id="cce_10_0048__li13285132913414"><strong id="cce_10_0048__cce_10_0047_b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Taints and Tolerations</a>.</li><li id="cce_10_0048__li179714209414"><strong id="cce_10_0048__cce_10_0047_b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0048__cce_10_0047_b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Labels and Annotations</a>.</li><li id="cce_10_0048__li1917237124111"><strong id="cce_10_0048__cce_10_0047_b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0048__li1985863319162"><strong id="cce_10_0048__b1073694484113">Network Configuration</strong>:<ul id="cce_10_0048__ul9870163414162"><li id="cce_10_0048__li8488616152">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS Rate Limiting for Inter-Pod Access</a>.</li></ul>
</li></ul>
</div>
</p></li><li id="cce_10_0048__li01417411620"><span>Click <strong id="cce_10_0048__b2573105264313">Create Workload</strong> in the lower right corner.</span></li></ol>

3
docs/cce/umn/cce_10_0059.html
View File

@ -28,6 +28,7 @@
</td>
<td class="cellrowborder" valign="top" width="64.38000000000001%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.3 "><p id="cce_10_0059__p181413185315">4.18.0-147.5.1.6.h541.eulerosv2r9.x86_64</p>
<p id="cce_10_0059__p1589920212208">4.18.0-147.5.1.6.h766.eulerosv2r9.x86_64</p>
<p id="cce_10_0059__p175382488373">4.18.0-147.5.1.6.h998.eulerosv2r9.x86_64</p>
</td>
</tr>
</tbody>
@ -127,7 +128,7 @@ spec:
<p id="cce_10_0059__en-us_topic_0249851123_p17239137193116">The following figure shows how to use ingress and egress together.</p>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig14112102353618"><span class="figcap"><b>Figure 4 </b>Using both ingress and egress</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image103563915919" src="en-us_image_0000001695896533.png"></span></div>
</div>
<div class="section" id="cce_10_0059__section349662212313"><h4 class="sectiontitle">Creating a Network Policy on the Console</h4><ol id="cce_10_0059__ol10753729162012"><li id="cce_10_0059__li67621546123813"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0059__li275310297205"><span>Choose <strong id="cce_10_0059__b1684093473514">Networking</strong> in the navigation pane, click the <span class="uicontrol" id="cce_10_0059__uicontrol8840143418354"><b>Network Policies</b></span> tab, and click <strong id="cce_10_0059__b1684043412358">Create Network Policy</strong> in the upper right corner.</span><p><ul id="cce_10_0059__ul1275420367216"><li id="cce_10_0059__li207540368218"><strong id="cce_10_0059__b5858127617589">Policy Name</strong>: Specify a network policy name.</li><li id="cce_10_0059__li86551950162110"><strong id="cce_10_0059__b2485142065319">Namespace</strong>: Select a namespace in which the network policy is applied.</li><li id="cce_10_0059__li1811145118419"><strong id="cce_10_0059__b1082493183618">Selector</strong>: Enter a label, select the pod to be associated, and click <strong id="cce_10_0059__b39962039143613">Add</strong>. You can also click <span class="uicontrol" id="cce_10_0059__uicontrol127315410439"><b>Reference Workload Label</b></span> to reference the label of an existing workload.</li><li id="cce_10_0059__li20288331248"><strong id="cce_10_0059__b288315258371">Inbound Rule</strong>: Click <span><img id="cce_10_0059__image297081312440" src="en-us_image_0000001647417596.png"></span> to add an inbound rule. For details about parameter settings, see <a href="#cce_10_0059__table166419994515">Table 1</a>.<p id="cce_10_0059__p13464141094517"></p>
<div class="section" id="cce_10_0059__section349662212313"><h4 class="sectiontitle">Creating a Network Policy on the Console</h4><ol id="cce_10_0059__ol10753729162012"><li id="cce_10_0059__li67621546123813"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0059__li275310297205"><span>Choose <strong id="cce_10_0059__b1684093473514">Networking</strong> in the navigation pane, click the <span class="uicontrol" id="cce_10_0059__uicontrol8840143418354"><b>Network Policies</b></span> tab, and click <strong id="cce_10_0059__b1684043412358">Create Network Policy</strong> in the upper right corner.</span><p><ul id="cce_10_0059__ul1275420367216"><li id="cce_10_0059__li207540368218"><strong id="cce_10_0059__b5858127617589">Policy Name</strong>: Specify a network policy name.</li><li id="cce_10_0059__li86551950162110"><strong id="cce_10_0059__b2485142065319">Namespace</strong>: Select a namespace in which the network policy is applied.</li><li id="cce_10_0059__li1811145118419"><strong id="cce_10_0059__b1082493183618">Selector</strong>: Enter a label, select the pod to be associated, and click <strong id="cce_10_0059__b39962039143613">Confirm</strong>. You can also click <span class="uicontrol" id="cce_10_0059__uicontrol127315410439"><b>Reference Workload Label</b></span> to reference the label of an existing workload.</li><li id="cce_10_0059__li20288331248"><strong id="cce_10_0059__b288315258371">Inbound Rule</strong>: Click <span><img id="cce_10_0059__image297081312440" src="en-us_image_0000001647417596.png"></span> to add an inbound rule. For details about parameter settings, see <a href="#cce_10_0059__table166419994515">Table 1</a>.<p id="cce_10_0059__p13464141094517"></p>
<p id="cce_10_0059__p1251071818275"><span><img id="cce_10_0059__image3789195442716" src="en-us_image_0000001647417588.png"></span></p>
<div class="p" id="cce_10_0059__p16644759445">
<div class="tablenoborder"><a name="cce_10_0059__table166419994515"></a><a name="table166419994515"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0059__table166419994515" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Adding an inbound rule</caption><thead align="left"><tr id="cce_10_0059__row186401397458"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.8.2.2.2.1.4.6.1.2.3.1.1"><p id="cce_10_0059__p163919913452">Parameter</p>

2
docs/cce/umn/cce_10_0063.html
View File

@ -5,7 +5,7 @@
</div>
<div class="section" id="cce_10_0063__section102878407207"><h4 class="sectiontitle">Viewing a Node Scaling Policy</h4><p id="cce_10_0063__p713741135215">You can view the associated node pool, rules, and scaling history of a node scaling policy and rectify faults according to the error information displayed.</p>
<ol id="cce_10_0063__ol17409123885219"><li id="cce_10_0063__li148293318248"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li3967519744"><span>Choose <strong id="cce_10_0063__b75474128512">Node Scaling</strong> in the navigation pane and click <span><img id="cce_10_0063__image1254712122518" src="en-us_image_0000001695896485.png"></span> in front of the policy to be viewed.</span></li><li id="cce_10_0063__li641003813527"><span>In the expanded area, the <span class="uicontrol" id="cce_10_0063__uicontrol864413924614"><b>Associated Node Pools</b></span>, <span class="uicontrol" id="cce_10_0063__uicontrol1164419910465"><b>Rules</b></span>, and <span class="uicontrol" id="cce_10_0063__uicontrol1964516974613"><b>Scaling History</b></span> tab pages are displayed. If the policy is abnormal, locate and rectify the fault based on the error information.</span><p><div class="note" id="cce_10_0063__note13404926203311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0063__p268214718213">You can also disable or enable auto scaling on the <strong id="cce_10_0063__b57750163232">Node Pools</strong> page.</p>
<ol type="a" id="cce_10_0063__ol15169162582120"><li id="cce_10_0063__li13169425162117">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0063__li716942518219">In the navigation pane, choose <strong id="cce_10_0063__b189612560310">Nodes</strong> and switch to the <strong id="cce_10_0063__b19818721244">Node Pools</strong> tab.</li><li id="cce_10_0063__li498811231504">Locate the row containing the target node pool and click <span class="uicontrol" id="cce_10_0063__uicontrol95019393011"><b>Update Node Pool</b></span>. In the window that slides out from the right, enable <strong id="cce_10_0063__b66112515390">Auto Scaling</strong>, and configure <strong id="cce_10_0063__b754915540391">Max. Nodes</strong>, <strong id="cce_10_0063__b1444816563399">Min. Nodes</strong>, and <strong id="cce_10_0063__b1724785813397">Cooldown Period</strong>.</li></ol>
<ol type="a" id="cce_10_0063__ol15169162582120"><li id="cce_10_0063__li13169425162117">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0063__li716942518219">In the navigation pane, choose <strong id="cce_10_0063__b189612560310">Nodes</strong> and switch to the <strong id="cce_10_0063__b19818721244">Node Pools</strong> tab.</li><li id="cce_10_0063__li498811231504">Locate the row containing the target node pool and click <span class="uicontrol" id="cce_10_0063__uicontrol95019393011"><b>Update</b></span> in the <strong id="cce_10_0063__b1496428185012">Operation</strong> column. In the window that slides out from the right, enable <strong id="cce_10_0063__b66112515390">Auto Scaling</strong>, and configure <strong id="cce_10_0063__b754915540391">Max. Nodes</strong>, <strong id="cce_10_0063__b1444816563399">Min. Nodes</strong>, and <strong id="cce_10_0063__b1724785813397">Cooldown Period</strong>.</li></ol>
</div></div>
</p></li></ol>
</div>

16
docs/cce/umn/cce_10_0064.html
View File

@ -6,21 +6,21 @@
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cce_10_0277.html">Overview</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0129.html">coredns (System Resource Add-on, Mandatory)</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0129.html">CoreDNS</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0066.html">everest (System Resource Add-on, Mandatory)</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0066.html">CCE Container Storage (Everest)</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0132.html">npd</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0132.html">CCE Node Problem Detector</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0154.html">autoscaler</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0154.html">CCE Cluster Autoscaler</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0205.html">metrics-server</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0205.html">Kubernetes Metrics Server</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0141.html">gpu-beta</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0193.html">volcano</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0193.html">Volcano Scheduler</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0127.html">storage-driver(Flexvolume, Deprecated)</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0127.html">CCE Container Storage (FlexVolume)</a></strong><br>
</li>
</ul>
</div>

65
docs/cce/umn/cce_10_0066.html
View File

File diff suppressed because it is too large Load Diff

4
docs/cce/umn/cce_10_0068.html
View File

@ -4,13 +4,15 @@
<div id="body8662426"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cce_bulletin_0059.html">Kubernetes 1.27 Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_bulletin_0058.html">Kubernetes 1.25 Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_bulletin_0027.html">Kubernetes 1.23 Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_bulletin_0026.html">Kubernetes 1.21 Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_whsnew_0010.html">Kubernetes 1.19 Release Notes</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_whsnew_0010.html">Kubernetes 1.19 EOM Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_whsnew_0007.html">Kubernetes 1.17 (EOM) Release Notes</a></strong><br>
</li>

6
docs/cce/umn/cce_10_0083.html
View File

@ -4,7 +4,7 @@
<div id="body1508729244098"><div class="section" id="cce_10_0083__section11873141710246"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0083__p799618243249">After an HPA policy is created, you can update, clone, edit, and delete the policy, as well as edit the YAML file.</p>
</div>
<div class="section" id="cce_10_0083__section14993443181414"><h4 class="sectiontitle">Checking an HPA Policy</h4><p id="cce_10_0083__p713741135215">You can view the rules, status, and events of an HPA policy and handle exceptions based on the error information displayed.</p>
<ol id="cce_10_0083__ol17409123885219"><li id="cce_10_0083__li754610559213"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li4409153817525"><span>In the navigation pane, choose <strong id="cce_10_0083__b9595121512611">Policies</strong>. On the <span class="uicontrol" id="cce_10_0083__uicontrol124101738135219"><b>HPA Policies</b></span> tab page, click <span><img id="cce_10_0083__image1569143785619" src="en-us_image_0000001695737185.png"></span> next to the target HPA policy.</span></li><li id="cce_10_0083__li641003813527"><span>In the expanded area, view the <strong id="cce_10_0083__b3109121911720">Rule</strong> and <strong id="cce_10_0083__b1952313227174">Status</strong> tabs. Click <span class="uicontrol" id="cce_10_0083__uicontrol4974153615019"><b>View Events</b></span> in the <strong id="cce_10_0083__b1620814781718">Operation</strong> column. If the policy malfunctions, locate and rectify the fault based on the error message displayed on the page.</span><p><div class="note" id="cce_10_0083__note13404926203311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0083__p1793618441931">You can also view the created HPA policy on the workload details page.</p>
<ol id="cce_10_0083__ol17409123885219"><li id="cce_10_0083__li754610559213"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li4409153817525"><span>In the navigation pane, choose <strong id="cce_10_0083__b9595121512611">Workload Scaling</strong>. On the <span class="uicontrol" id="cce_10_0083__uicontrol124101738135219"><b>HPA Policies</b></span> tab, click <span><img id="cce_10_0083__image1569143785619" src="en-us_image_0000001695737185.png"></span> next to the target HPA policy.</span></li><li id="cce_10_0083__li641003813527"><span>In the expanded area, view the <strong id="cce_10_0083__b3109121911720">Rule</strong> and <strong id="cce_10_0083__b1952313227174">Status</strong> tabs. Click <span class="uicontrol" id="cce_10_0083__uicontrol4974153615019"><b>View Events</b></span> in the <strong id="cce_10_0083__b1620814781718">Operation</strong> column. If the policy malfunctions, locate and rectify the fault based on the error message displayed on the page.</span><p><div class="note" id="cce_10_0083__note13404926203311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0083__p1793618441931">You can also view the created HPA policy on the workload details page.</p>
<ol type="a" id="cce_10_0083__ol1691347738"><li id="cce_10_0083__li5468556932">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0083__li87313521749">In the navigation pane, choose <strong id="cce_10_0083__b01748420311">Workloads</strong>. Click the workload name to view its details.</li><li id="cce_10_0083__li1769110474318">On the workload details page, click the <strong id="cce_10_0083__b3716156354">Auto Scaling</strong> tab to view the HPA policies. You can also view the scaling policies you configured in the <strong id="cce_10_0083__b81591132105417">Workload Scaling</strong> page.</li></ol>
</div></div>
@ -93,9 +93,9 @@
<div class="section" id="cce_10_0083__section119901143111420"><h4 class="sectiontitle">Updating an HPA Policy</h4><p id="cce_10_0083__p18160164715245">An HPA policy is used as an example.</p>
<ol id="cce_10_0083__ol14644105712488"><li id="cce_10_0083__li584173114516"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li2619151017014"><span>On the cluster console, choose <strong id="cce_10_0083__b147314501477">Workload Scaling</strong> in the navigation pane. Locate the row that contains the target policy and choose <strong id="cce_10_0083__b1859319500414">More</strong> &gt; <strong id="cce_10_0083__b043275516414">Edit</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1275919157101"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li19809141991015"><span>On the <span class="uicontrol" id="cce_10_0083__uicontrol162451231134212"><b>Edit HPA Policy</b></span> page, configure the parameters as listed in <a href="cce_10_0208.html#cce_10_0208__table8638121213265">Table 1</a>.</span></li><li id="cce_10_0083__li1340513385528"><span>Click <strong id="cce_10_0083__b18186175524217">OK</strong>.</span></li></ol>
</div>
<div class="section" id="cce_10_0083__section14894314131710"><h4 class="sectiontitle">Editing the YAML File (HPA Policy)</h4><ol id="cce_10_0083__ol836024781710"><li id="cce_10_0083__li4747132218612"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li197478221868"><span>In the navigation pane, choose <strong id="cce_10_0083__b158614271186">Policies</strong>. Choose <span class="uicontrol" id="cce_10_0083__uicontrol173601547121714"><b>Edit YAML</b></span> in the <span class="uicontrol" id="cce_10_0083__uicontrol15862927288"><b>Operation</b></span> column of the target HPA policy.</span></li><li id="cce_10_0083__li3360104719175"><span>In the <span class="uicontrol" id="cce_10_0083__uicontrol19625193112511"><b>Edit YAML</b></span> dialog box displayed, edit or download the YAML file.</span></li></ol>
<div class="section" id="cce_10_0083__section14894314131710"><h4 class="sectiontitle">Editing the YAML File (HPA Policy)</h4><ol id="cce_10_0083__ol836024781710"><li id="cce_10_0083__li4747132218612"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li197478221868"><span>In the navigation pane, choose <strong id="cce_10_0083__b158614271186">Workload Scaling</strong>, locate the row containing the target policy, and click <span class="uicontrol" id="cce_10_0083__uicontrol173601547121714"><b>Edit YAML</b></span> in the <span class="uicontrol" id="cce_10_0083__uicontrol15862927288"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li3360104719175"><span>In the <span class="uicontrol" id="cce_10_0083__uicontrol19625193112511"><b>Edit YAML</b></span> dialog box displayed, edit or download the YAML file.</span></li></ol>
</div>
<div class="section" id="cce_10_0083__section13361947161717"><h4 class="sectiontitle">Deleting an HPA Policy</h4><ol id="cce_10_0083__ol86853731815"><li id="cce_10_0083__li15254352473"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li1725419521973"><span>In the navigation pane, choose <strong id="cce_10_0083__b26191366917">Policies</strong>. Choose <span class="uicontrol" id="cce_10_0083__uicontrol156193361795"><b>Delete</b></span> &gt; <strong id="cce_10_0083__b154116114551">Delete</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1462014361391"><b>Operation</b></span> column of the target policy.</span></li><li id="cce_10_0083__li96803718182"><span>In the dialog box displayed, click <strong id="cce_10_0083__b135291150994">Yes</strong>.</span></li></ol>
<div class="section" id="cce_10_0083__section13361947161717"><h4 class="sectiontitle">Deleting an HPA Policy</h4><ol id="cce_10_0083__ol86853731815"><li id="cce_10_0083__li15254352473"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li1725419521973"><span>In the navigation pane, choose <strong id="cce_10_0083__b26191366917">Workload Scaling</strong>. Locate the row containing the target policy and choose <span class="uicontrol" id="cce_10_0083__uicontrol156193361795"><b>More</b></span> &gt; <strong id="cce_10_0083__b154116114551">Delete</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1462014361391"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li96803718182"><span>In the dialog box displayed, click <strong id="cce_10_0083__b135291150994">Yes</strong>.</span></li></ol>
</div>
</div>
<div>

2
docs/cce/umn/cce_10_0113.html
View File

@ -7,7 +7,7 @@
<p id="cce_10_0113__p26271321192016">Configurations must be imported to a container as arguments. Otherwise, configurations will be lost after the container restarts.</p>
</div></div>
<p id="cce_10_0113__p78261119155911">Environment variables can be set in the following modes:</p>
<ul id="cce_10_0113__ul1669104610598"><li id="cce_10_0113__li266913468594"><strong id="cce_10_0113__b4564141914250">Custom</strong>: Enter the environment variable name and parameter value.</li><li id="cce_10_0113__li13148164912599"><strong id="cce_10_0113__b31161818143614">Added from ConfigMap key</strong>: Import all keys in a ConfigMap as environment variables.</li><li id="cce_10_0113__li1855315291026"><strong id="cce_10_0113__b5398577535">Added from ConfigMap</strong>: Import a key in a ConfigMap as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b67861335193619">configmap_value</strong> of <strong id="cce_10_0113__b478643513618">configmap_key</strong> in a ConfigMap as the value of environment variable <strong id="cce_10_0113__b7786133573616">key1</strong>, an environment variable named <strong id="cce_10_0113__b678683518364">key1</strong> whose value is <strong id="cce_10_0113__b1378615359362">configmap_value</strong> exists in the container.</li><li id="cce_10_0113__li1727795616592"><strong id="cce_10_0113__b675162614437">Added from secret</strong>: Import all keys in a secret as environment variables.</li><li id="cce_10_0113__li93353201773"><strong id="cce_10_0113__b0483141614480">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b12974122713812">secret_value</strong> of <strong id="cce_10_0113__b197472716385">secret_key</strong> in secret <strong id="cce_10_0113__b722441953910">secret-example</strong> as the value of environment variable <strong id="cce_10_0113__b8975627173810">key2</strong>, an environment variable named <strong id="cce_10_0113__b29756275384">key2</strong> whose value is <strong id="cce_10_0113__b097552703811">secret_value</strong> exists in the container.</li><li id="cce_10_0113__li1749760535"><strong id="cce_10_0113__b19931701407">Variable value/reference</strong>: Use the field defined by a pod as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if the pod name is imported as the value of environment variable <strong id="cce_10_0113__b1939710417283">key3</strong>, an environment variable named <strong id="cce_10_0113__b11252186142914">key3</strong> exists in the container and its value is the pod name.</li><li id="cce_10_0113__li16129071317"><strong id="cce_10_0113__b1625513417292">Resource Reference</strong>: The value of <strong id="cce_10_0113__b176281198307">Request</strong> or <strong id="cce_10_0113__b186221022193017">Limit</strong> defined by the container is used as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import the CPU limit of container-1 as the value of environment variable <strong id="cce_10_0113__b272674753017">key4</strong>, an environment variable named <strong id="cce_10_0113__b99015318423">key4</strong> exists in the container and its value is the CPU limit of container-1.</li></ul>
<ul id="cce_10_0113__ul1669104610598"><li id="cce_10_0113__li266913468594"><strong id="cce_10_0113__b4564141914250">Custom</strong>: Enter the environment variable name and parameter value.</li><li id="cce_10_0113__li13148164912599"><strong id="cce_10_0113__b31161818143614">Added from ConfigMap key</strong>: Import all keys in a ConfigMap as environment variables.</li><li id="cce_10_0113__li1855315291026"><strong id="cce_10_0113__b5398577535">Added from ConfigMap</strong>: Import a key in a ConfigMap as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b20936188125511">configmap_value</strong> of <strong id="cce_10_0113__b12936684553">configmap_key</strong> in a ConfigMap as the value of environment variable <strong id="cce_10_0113__b593614805511">key1</strong>, an environment variable named <strong id="cce_10_0113__b893617815559">key1</strong> whose value is <strong id="cce_10_0113__b1293619819551">configmap_value</strong> exists in the container.</li><li id="cce_10_0113__li1727795616592"><strong id="cce_10_0113__b675162614437">Added from secret</strong>: Import all keys in a secret as environment variables.</li><li id="cce_10_0113__li93353201773"><strong id="cce_10_0113__b0483141614480">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b2840352135512">secret_value</strong> of <strong id="cce_10_0113__b12840145235515">secret_key</strong> in secret <strong id="cce_10_0113__b2084020521557">secret-example</strong> as the value of environment variable <strong id="cce_10_0113__b198401752195514">key2</strong>, an environment variable named <strong id="cce_10_0113__b2840145212556">key2</strong> whose value is <strong id="cce_10_0113__b1484165212556">secret_value</strong> exists in the container.</li><li id="cce_10_0113__li1749760535"><strong id="cce_10_0113__b19931701407">Variable value/reference</strong>: Use the field defined by a pod as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if the pod name is imported as the value of environment variable <strong id="cce_10_0113__b10262145911552">key3</strong>, an environment variable named <strong id="cce_10_0113__b1226215914556">key3</strong> exists in the container and its value is the pod name.</li><li id="cce_10_0113__li16129071317"><strong id="cce_10_0113__b1625513417292">Resource Reference</strong>: The value of <strong id="cce_10_0113__b176281198307">Request</strong> or <strong id="cce_10_0113__b186221022193017">Limit</strong> defined by the container is used as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import the CPU limit of <strong id="cce_10_0113__b1112012595611">container-1</strong> as the value of environment variable <strong id="cce_10_0113__b1120153563">key4</strong>, an environment variable named <strong id="cce_10_0113__b5120154565">key4</strong> exists in the container and its value is the CPU limit of <strong id="cce_10_0113__b131219518562">container-1</strong>.</li></ul>
</div>
<div class="section" id="cce_10_0113__section13829152011595"><h4 class="sectiontitle">Adding Environment Variables</h4><ol id="cce_10_0113__ol4904646935"><li id="cce_10_0113__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0113__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0113__b1794501219430">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0113__b11945131216432">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0113__li190412461831"><span>When creating a workload, modify the container information in the <strong id="cce_10_0113__b101361766447">Container Settings</strong> area and click the <strong id="cce_10_0113__b8169124424315">Environment Variables</strong> tab.</span></li><li id="cce_10_0113__li468251942720"><span>Configure environment variables.</span><p><div class="fignone" id="cce_10_0113__fig164568529317"><a name="cce_10_0113__fig164568529317"></a><a name="fig164568529317"></a><span class="figcap"><b>Figure 1 </b>Configuring environment variables</span><br><span><img id="cce_10_0113__image486125516381" src="en-us_image_0000001695896581.png"></span></div>
</p></li></ol>

4
docs/cce/umn/cce_10_0127.html
View File

@ -1,10 +1,10 @@
<a name="cce_10_0127"></a><a name="cce_10_0127"></a>
<h1 class="topictitle1">storage-driver(Flexvolume, Deprecated)</h1>
<h1 class="topictitle1">CCE Container Storage (FlexVolume)</h1>
<div id="body1541037494110"><div class="section" id="cce_10_0127__section25311744154917"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0127__p1574910495496">storage-driver functions as a standard Kubernetes FlexVolume plug-in to allow containers to use EVS, SFS, OBS, and SFS Turbo storage resources. By installing and upgrading storage-driver, you can quickly install and update cloud storage capabilities.</p>
<p id="cce_10_0127__p5414123111414"><strong id="cce_10_0127__b2471165511315">storage-driver is a system resource add-on. It is installed by default when a cluster of Kubernetes v1.13 or earlier is created.</strong></p>
</div>
<div class="section" id="cce_10_0127__section3993231122718"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0127__ul113072911510"><li id="cce_10_0127__li10330171552010">For clusters created in CCE, Kubernetes v1.15.11 is a transitional version in which the FlexVolume add-on (storage-driver) is compatible with the CSI add-on (<a href="cce_10_0066.html">everest</a>). Clusters of v1.17 and later versions do not support FlexVolume anymore. Use the everest add-on.</li><li id="cce_10_0127__li25582642815">The FlexVolume add-on will be maintained by Kubernetes developers, but new functionality will only be added to <a href="cce_10_0066.html">everest (System Resource Add-on, Mandatory)</a>. Do not create CCE storage that connects to the FlexVolume add-on (storage-driver) anymore. Otherwise, storage may malfunction.</li><li id="cce_10_0127__li51302291158">This add-on can be installed only in <strong id="cce_10_0127__b363773505113">clusters of v1.13 or earlier</strong>. By default, the <a href="cce_10_0066.html">everest</a> add-on is installed when clusters of v1.15 or later are created.<div class="note" id="cce_10_0127__note1531776113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0127__p8532474112"><strong id="cce_10_0127__b411425325110">In a cluster of v1.13 or earlier</strong>, when an upgrade or bug fix is available for storage functionalities, you only need to install or upgrade the storage-driver add-on. Upgrading the cluster or creating a cluster is not required.</p>
<div class="section" id="cce_10_0127__section3993231122718"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0127__ul113072911510"><li id="cce_10_0127__li10330171552010">For clusters created in CCE, Kubernetes v1.15.11 is a transitional version in which the FlexVolume add-on (storage-driver) is compatible with the CSI add-on (<a href="cce_10_0066.html">everest</a>). Clusters of v1.17 and later versions do not support FlexVolume anymore. Use the everest add-on.</li><li id="cce_10_0127__li25582642815">The FlexVolume add-on will be maintained by Kubernetes developers, but new functionality will only be added to <a href="cce_10_0066.html">CCE Container Storage (Everest)</a>. Do not create CCE storage that connects to the FlexVolume add-on (storage-driver) anymore. Otherwise, storage may malfunction.</li><li id="cce_10_0127__li51302291158">This add-on can be installed only in <strong id="cce_10_0127__b363773505113">clusters of v1.13 or earlier</strong>. By default, the <a href="cce_10_0066.html">everest</a> add-on is installed when clusters of v1.15 or later are created.<div class="note" id="cce_10_0127__note1531776113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0127__p8532474112"><strong id="cce_10_0127__b411425325110">In a cluster of v1.13 or earlier</strong>, when an upgrade or bug fix is available for storage functionalities, you only need to install or upgrade the storage-driver add-on. Upgrading the cluster or creating a cluster is not required.</p>
</div></div>
</li></ul>
</div>

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

File diff suppressed because it is too large Load Diff

17
docs/cce/umn/cce_10_0132.html
View File

@ -1,7 +1,7 @@
<a name="cce_10_0132"></a><a name="cce_10_0132"></a>
<h1 class="topictitle1">npd</h1>
<div id="body1544406897523"><div class="section" id="cce_10_0132__section173631312185614"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0132__p37354218618">node-problem-detector (npd for short) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. The npd add-on can run as a DaemonSet or a daemon.</p>
<h1 class="topictitle1">CCE Node Problem Detector</h1>
<div id="body1544406897523"><div class="section" id="cce_10_0132__section173631312185614"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0132__p37354218618">CCE Node Problem Detector (NPD) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. The npd add-on can run as a DaemonSet or a daemon.</p>
<p id="cce_10_0132__p152804433415">For more information, see <a href="https://github.com/kubernetes/node-problem-detector" target="_blank" rel="noopener noreferrer">node-problem-detector</a>.</p>
</div>
<div class="section" id="cce_10_0132__section119671349192611"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0132__ul55121521141010"><li id="cce_10_0132__li8512142151010">When using this add-on, do not format or partition node disks.</li><li id="cce_10_0132__li151217213101">Each npd process occupies 30 m CPU and 100 MB memory.</li></ul>
@ -10,7 +10,7 @@
<p id="cce_10_0132__p1992131751419">In addition, CCE mitigates risks according to the least privilege principle. Only the following privileges are available for npd running:</p>
<ul id="cce_10_0132__ul57753573145"><li id="cce_10_0132__li077514576147">cap_dac_read_search: permission to access <strong id="cce_10_0132__b183144419493">/run/log/journal</strong>.</li><li id="cce_10_0132__li15775205761415">cap_sys_admin: permission to access <strong id="cce_10_0132__b173812584913">/dev/kmsg</strong>.</li></ul>
</div>
<div class="section" id="cce_10_0132__section189463341114"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0132__ol13949124616422"><li id="cce_10_0132__li13183153352515"><span>Log in to the CCE console and access the cluster console. Choose <span class="uicontrol" id="cce_10_0132__uicontrol18362548121"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0132__b1236844171210">npd</strong> on the right, and click <strong id="cce_10_0132__b23681045129">Install</strong>.</span></li><li id="cce_10_0132__li15556183414307"><span>On the <strong id="cce_10_0132__b24650148974234">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="section" id="cce_10_0132__section189463341114"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0132__ol13949124616422"><li id="cce_10_0132__li13183153352515"><span>Log in to the CCE console and access the cluster console. Choose <span class="uicontrol" id="cce_10_0132__uicontrol18362548121"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0132__b329115016392">CCE Node Problem Detector</strong> on the right, and click <strong id="cce_10_0132__b23681045129">Install</strong>.</span></li><li id="cce_10_0132__li15556183414307"><span>On the <strong id="cce_10_0132__b24650148974234">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0132__table924319911495" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Add-on configuration</caption><thead align="left"><tr id="cce_10_0132__row42442974913"><th align="left" class="cellrowborder" valign="top" width="24%" id="mcps1.3.4.2.2.2.1.2.3.1.1"><p id="cce_10_0132__p17244793496">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76%" id="mcps1.3.4.2.2.2.1.2.3.1.2"><p id="cce_10_0132__p42441596495">Description</p>
@ -27,6 +27,11 @@
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><p id="cce_10_0132__p93701640145120">If you select <strong id="cce_10_0132__b10427161195916">Custom</strong>, you can adjust the number of pods as required.</p>
</td>
</tr>
<tr id="cce_10_0132__row150601124214"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.2.2.2.1.2.3.1.1 "><p id="cce_10_0132__p15864134742615">Multi-AZ</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><ul id="cce_10_0132__ul4214181752714"><li id="cce_10_0132__li5214161718270"><strong id="cce_10_0132__b85941786571">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_0132__li4214917142716"><strong id="cce_10_0132__b1511319431572">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_0132__row4370840165119"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.2.2.2.1.2.3.1.1 "><p id="cce_10_0132__p937054045117">Containers</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><p id="cce_10_0132__p1437014065110">If you select <strong id="cce_10_0132__b76029242810411">Custom</strong>, you can adjust the container specifications as required.</p>
@ -98,7 +103,7 @@
</table>
</div>
</div>
<div class="section" id="cce_10_0132__section69115153399"><h4 class="sectiontitle">npd Check Items</h4><div class="note" id="cce_10_0132__note173963403394"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0132__p5396184020391">Check items are supported only in 1.16.0 and later versions.</p>
<div class="section" id="cce_10_0132__section69115153399"><a name="cce_10_0132__section69115153399"></a><a name="section69115153399"></a><h4 class="sectiontitle">npd Check Items</h4><div class="note" id="cce_10_0132__note173963403394"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0132__p5396184020391">Check items are supported only in 1.16.0 and later versions.</p>
</div></div>
<p id="cce_10_0132__p4958134764017">Check items cover events and statuses.</p>
<ul id="cce_10_0132__ul1699482505"><li id="cce_10_0132__li20691448115014">Event-related<p id="cce_10_0132__p9338344194514"><a name="cce_10_0132__li20691448115014"></a><a name="li20691448115014"></a>For event-related check items, when a problem occurs, npd reports an event to the API server. The event type can be <strong id="cce_10_0132__b0674907539">Normal</strong> (normal event) or <strong id="cce_10_0132__b264113215531">Warning</strong> (abnormal event).</p>
@ -127,7 +132,7 @@
<p id="cce_10_0132__p2317112419618">Typical scenario: Disk I/O suspension causes process suspension.</p>
</td>
<td class="cellrowborder" valign="top" width="36.57%" headers="mcps1.3.6.4.1.2.2.4.1.3 "><p id="cce_10_0132__p16872758114011">Warning event</p>
<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b1714839826">/dev/kmsg</strong></p>
<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b12969983">/dev/kmsg</strong></p>
<p id="cce_10_0132__p153079591241">Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."</p>
</td>
</tr>
@ -137,7 +142,7 @@
<p id="cce_10_0132__p15344719349">Typical scenario: A user detaches a data disk from a node by mistake on the ECS, and applications continuously write data to the mount point of the data disk. As a result, an I/O error occurs in the kernel and the disk is remounted as a read-only disk.</p>
</td>
<td class="cellrowborder" valign="top" width="36.57%" headers="mcps1.3.6.4.1.2.2.4.1.3 "><p id="cce_10_0132__p944535317711">Warning event</p>
<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b820165144">/dev/kmsg</strong></p>
<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b111350765">/dev/kmsg</strong></p>
<p id="cce_10_0132__p83993101042">Matching rule: <strong id="cce_10_0132__b15200817134219">Remounting filesystem read-only</strong></p>
</td>
</tr>

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

@ -1,11 +1,11 @@
<a name="cce_10_0141"></a><a name="cce_10_0141"></a>
<h1 class="topictitle1">gpu-beta</h1>
<div id="body1552976392137"><div class="section" id="cce_10_0141__section26181722164712"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0141__p12273103844718">gpu-beta is a device management add-on that supports GPUs in containers. If GPU nodes are used in the cluster, this add-on must be installed.</p>
<h1 class="topictitle1">CCE AI Suite (NVIDIA GPU)</h1>
<div id="body1552976392137"><div class="section" id="cce_10_0141__section26181722164712"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0141__p12273103844718">The CCE AI Suite (NVIDIA GPU) add-on is a device management add-on that supports GPUs in containers. If GPU nodes are used in the cluster, this add-on must be installed.</p>
</div>
<div class="section" id="cce_10_0141__section3200193614201"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0141__ul1815672612156"><li id="cce_10_0141__li1715622613151">The driver to be downloaded must be a <span class="uicontrol" id="cce_10_0141__uicontrol113611965581"><b>.run</b></span> file.</li><li id="cce_10_0141__li8619191610138">Only NVIDIA Tesla drivers are supported, not GRID drivers.</li><li id="cce_10_0141__li94891186187">When installing or reinstalling the add-on, ensure that the driver download address is correct and accessible. CCE does not verify the address validity.</li><li id="cce_10_0141__li1843718111247">The gpu-beta add-on only enables you to download the driver and execute the installation script. The add-on status only indicates that how the add-on is running, not whether the driver is successfully installed.</li><li id="cce_10_0141__li39662291701">CCE does not guarantee the compatibility between the GPU driver version and the CDUA library version of your application. You need to check the compatibility by yourself.</li><li id="cce_10_0141__li938214018284">If a GPU driver has been added to a custom OS image, CCE cannot ensure that the GPU driver is compatible with other GPU components such as the monitoring components used in CCE.</li></ul>
</div>
<div class="section" id="cce_10_0141__section14115341020"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0141__ol2011434603"><li id="cce_10_0141__li6116341702"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0141__uicontrol06719319429"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0141__b9333174013593">gpu-beta</strong><strong id="cce_10_0141__b5272114215910"></strong> on the right, and click <strong id="cce_10_0141__b15691331164219">Install</strong>.</span></li><li id="cce_10_0141__li178033014157"><span>On the <strong id="cce_10_0141__b1186715186499">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="section" id="cce_10_0141__section14115341020"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0141__ol2011434603"><li id="cce_10_0141__li6116341702"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0141__uicontrol06719319429"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0141__b46461289382"></strong><strong id="cce_10_0141__b7674112917382"></strong><strong id="cce_10_0141__b1812733117389">CCE AI Suite (NVIDIA GPU)</strong> on the right, and click <strong id="cce_10_0141__b15691331164219">Install</strong>.</span></li><li id="cce_10_0141__li178033014157"><span>On the <strong id="cce_10_0141__b1186715186499">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0141__table924319911495" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Add-on configuration</caption><thead align="left"><tr id="cce_10_0141__row42442974913"><th align="left" class="cellrowborder" valign="top" width="24%" id="mcps1.3.3.2.2.2.1.2.3.1.1"><p id="cce_10_0141__p17244793496">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76%" id="mcps1.3.3.2.2.2.1.2.3.1.2"><p id="cce_10_0141__p42441596495">Description</p>
@ -28,6 +28,8 @@
</div>
</p></li><li id="cce_10_0141__li6911527161717"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1129963191314"><li id="cce_10_0141__en-us_topic_0000001504601234_li1554416474556"><strong id="cce_10_0141__b1374472644917">NVIDIA Driver</strong>: Enter the link for downloading the NVIDIA driver. All GPU nodes in the cluster will use this driver.<div class="notice" id="cce_10_0141__en-us_topic_0000001504601234_note16659111785119"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1765951765114"><li id="cce_10_0141__en-us_topic_0000001504601234_li1865921713514">If the download link is a public network address, for example, <strong id="cce_10_0141__b1680185713186">https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</strong>, bind an EIP to each GPU node. For details about how to obtain the driver link, see <a href="cce_10_0141.html#cce_10_0141__section95451728192112">Obtaining the Driver Link from Public Network</a>.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li665981712519">If the download link is an OBS URL, you do not need to bind an EIP to GPU nodes. For details about how to obtain the driver link, see <a href="cce_10_0141.html#cce_10_0141__section14922133914508">Obtaining the Driver Link from OBS</a>.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li17659317165114">Ensure that the NVIDIA driver version matches the GPU node.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li76591517175120">After the driver version is changed, restart the node for the change to take effect.</li></ul>
</div></div>
</li><li id="cce_10_0141__en-us_topic_0000001504601234_li073402311310"><strong id="cce_10_0141__b1660772412307">Driver Selection</strong>: If you do not want all GPU nodes in a cluster to use the same driver, CCE allows you to install a different GPU driver for each node pool.<div class="note" id="cce_10_0141__en-us_topic_0000001504601234_note6635813585"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1883717714586"><li id="cce_10_0141__en-us_topic_0000001504601234_li14837117155815">The add-on installs the driver with the version specified by the node pool. The driver takes effect only for new pool nodes.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li48389715582">After the driver version of new nodes is updated, restart the nodes for the update to take effect. The driver version cannot be updated for non-new nodes.</li></ul>
</div></div>
</li></ul>
</p></li><li id="cce_10_0141__li151113411011"><span>Click <strong id="cce_10_0141__b1543017210355">Install</strong>.</span><p><div class="note" id="cce_10_0141__note17799123474219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0141__p107362261984">Uninstalling the add-on will clear the GPU driver on the nodes. As a result, GPU pods newly scheduled to the nodes cannot run properly, but running GPU pods are not affected.</p>
</div></div>

2
docs/cce/umn/cce_10_0142.html
View File

@ -7,7 +7,7 @@
<div class="section" id="cce_10_0142__section8501151104219"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0142__ul1685519569431"><li id="cce_10_0142__li1585575616436">By default, a NodePort Service is accessed within a VPC. To use an EIP to access a NodePort Service through public networks, bind an EIP to the node in the cluster in advance.</li><li id="cce_10_0142__li128551156114310">After a Service is created, if the affinity setting is switched from the cluster level to the node level, the connection tracing table will not be cleared. Do not modify the Service affinity setting after the Service is created. To modify it, create a Service again.</li><li id="cce_10_0142__li62831358182017">CCE Turbo clusters support only cluster-level service affinity.</li><li id="cce_10_0142__li217783916207">In VPC network mode, when container A is published through a NodePort service and the service affinity is set to the node level (that is, <strong id="cce_10_0142__b1291203218520">externalTrafficPolicy</strong> is set to <strong id="cce_10_0142__b11911632135217">local</strong>), container B deployed on the same node cannot access container A through the node IP address and NodePort service.</li><li id="cce_10_0142__li14613571073">When a NodePort service is created in a cluster of v1.21.7 or later, the port on the node is not displayed using <strong id="cce_10_0142__b13256143512525">netstat</strong> by default. If the cluster forwarding mode is <strong id="cce_10_0142__b42563350522">iptables</strong>, run the <strong id="cce_10_0142__b62561135115212">iptables -t nat -L</strong> command to view the port. If the cluster forwarding mode is <strong id="cce_10_0142__b925763515218">IPVS</strong>, run the <strong id="cce_10_0142__b23917223106">ipvsadm -Ln</strong> command to view the port.</li></ul>
</div>
<div class="section" id="cce_10_0142__section1325012312139"><h4 class="sectiontitle">Creating a NodePort Service</h4><ol id="cce_10_0142__ol751935681319"><li id="cce_10_0142__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0142__li1651955651312"><span>Choose <strong id="cce_10_0142__b59268208277">Networking</strong> in the navigation pane and click <strong id="cce_10_0142__b59321820182716">Create Service</strong> in the upper right corner.</span></li><li id="cce_10_0142__li185190567138"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0142__ul4446314017144"><li id="cce_10_0142__li6462394317144"><strong id="cce_10_0142__b845613814287">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0142__li89543531070"><strong id="cce_10_0142__b106597277362">Service Type</strong>: Select <span class="uicontrol" id="cce_10_0142__uicontrol5666142710366"><b>NodePort</b></span>.</li><li id="cce_10_0142__li4800017144"><strong id="cce_10_0142__b1263193014367">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0142__li1758110116149"><strong id="cce_10_0142__b38118349367">Service Affinity</strong>: For details, see <a href="cce_10_0249.html#cce_10_0249__section18134208069">externalTrafficPolicy (Service Affinity)</a>.<ul id="cce_10_0142__ul158101161412"><li id="cce_10_0142__li105815113141"><strong id="cce_10_0142__b2674164185210">Cluster level</strong>: The IP addresses and access ports of all nodes in a cluster can access the workload associated with the Service. Service access will cause performance loss due to route redirection, and the source IP address of the client cannot be obtained.</li><li id="cce_10_0142__li185817117145"><strong id="cce_10_0142__b465617445525">Node level</strong>: Only the IP address and access port of the node where the workload is located can access the workload associated with the Service. Service access will not cause performance loss due to route redirection, and the source IP address of the client can be obtained.</li></ul>
</li><li id="cce_10_0142__li43200017144"><strong id="cce_10_0142__b2600143835813">Selector</strong>: Add a label and click <strong id="cce_10_0142__b260020382582">Add</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0142__b354965233619">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0142__b16550125293615">OK</strong>.</li><li id="cce_10_0142__li388800117144"><strong id="cce_10_0142__b38881739133512">Port</strong><ul id="cce_10_0142__ul3499201217144"><li id="cce_10_0142__li4649265917144"><strong id="cce_10_0142__b28899114374">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0142__li353122153610"><strong id="cce_10_0142__b1852318551688">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0142__li1578074917144"><strong id="cce_10_0142__b19416443712">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li><li id="cce_10_0142__li780902117144"><strong id="cce_10_0142__b11763931199">Node Port</strong>: You are advised to select <strong id="cce_10_0142__b1198741292">Auto</strong>. You can also specify a port. The default port ranges from 30000 to 32767.</li></ul>
</li><li id="cce_10_0142__li43200017144"><strong id="cce_10_0142__b519871474713">Selector</strong>: Add a label and click <strong id="cce_10_0142__b0198191416479">Confirm</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0142__b354965233619">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0142__b16550125293615">OK</strong>.</li><li id="cce_10_0142__li388800117144"><strong id="cce_10_0142__b38881739133512">Port</strong><ul id="cce_10_0142__ul3499201217144"><li id="cce_10_0142__li4649265917144"><strong id="cce_10_0142__b28899114374">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0142__li353122153610"><strong id="cce_10_0142__b1852318551688">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0142__li1578074917144"><strong id="cce_10_0142__b19416443712">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li><li id="cce_10_0142__li780902117144"><strong id="cce_10_0142__b11763931199">Node Port</strong>: You are advised to select <strong id="cce_10_0142__b1198741292">Auto</strong>. You can also specify a port. The default port ranges from 30000 to 32767.</li></ul>
</li></ul>
</p></li><li id="cce_10_0142__li552017569135"><span>Click <strong id="cce_10_0142__b1012031216378">OK</strong>.</span></li></ol>
</div>

49
docs/cce/umn/cce_10_0150.html
View File

@ -8,64 +8,64 @@
</div>
<div class="section" id="cce_10_0150__s50bf087555b1437aa249c1259138706c"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0150__p1695632510556">Resources have been created. For details, see <a href="cce_10_0363.html">Creating a Node</a>. If clusters and nodes are available, you need not create them again.</p>
</div>
<div class="section" id="cce_10_0150__sb8a02965b2624dbbabab320046ca4973"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0150__ol2012902601117"><li id="cce_10_0150__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0150__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0150__b94442390613">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0150__b1844413910614">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0150__li67891737151520"><span>Set basic information about the workload. </span><p><div class="p" id="cce_10_0150__p1259466151612"><strong id="cce_10_0150__b784105815422">Basic Info</strong><ul id="cce_10_0150__ul6954101318184"><li id="cce_10_0150__li11514131617185"><strong id="cce_10_0150__b188592071436">Workload Type</strong>: Select <strong id="cce_10_0150__b117010384313">Job</strong>. For details about workload types, see <a href="cce_10_0006.html">Overview</a>.</li><li id="cce_10_0150__li1579915510168"><strong id="cce_10_0150__cce_10_0047_b12465144313510">Workload Name</strong>: Enter the name of the workload. Enter 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</li><li id="cce_10_0150__li47997541610"><strong id="cce_10_0150__cce_10_0047_b20501185611511">Namespace</strong>: Select the namespace of the workload. The default value is <strong id="cce_10_0150__cce_10_0047_b1508155615514">default</strong>. You can also click <span class="uicontrol" id="cce_10_0150__cce_10_0047_uicontrol342862818214"><b>Create Namespace</b></span> to create one. For details, see <a href="cce_10_0278.html">Creating a Namespace</a>.</li><li id="cce_10_0150__li11799254161"><strong id="cce_10_0150__cce_10_0047_b1997313316218">Pods</strong>: Enter the number of pods of the workload.</li><li id="cce_10_0150__li952215331573"><strong id="cce_10_0150__cce_10_0047_b1111971612">Container Runtime</strong>: A CCE cluster uses runC by default, whereas a CCE Turbo cluster supports both runC and Kata. For details about the differences, see <a href="cce_10_0463.html">Kata Runtime and Common Runtime</a>.</li></ul>
<div class="section" id="cce_10_0150__sb8a02965b2624dbbabab320046ca4973"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0150__ol2012902601117"><li id="cce_10_0150__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0150__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0150__b1256034012421">Workloads</strong> in the navigation pane, and click <strong id="cce_10_0150__b11560640174210">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0150__li67891737151520"><span>Set basic information about the workload. </span><p><div class="p" id="cce_10_0150__p1259466151612"><strong id="cce_10_0150__b784105815422">Basic Info</strong><ul id="cce_10_0150__ul6954101318184"><li id="cce_10_0150__li11514131617185"><strong id="cce_10_0150__b188592071436">Workload Type</strong>: Select <strong id="cce_10_0150__b117010384313">Job</strong>. For details about workload types, see <a href="cce_10_0006.html">Overview</a>.</li><li id="cce_10_0150__li1579915510168"><strong id="cce_10_0150__cce_10_0047_b12465144313510">Workload Name</strong>: Enter the name of the workload. Enter 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</li><li id="cce_10_0150__li47997541610"><strong id="cce_10_0150__cce_10_0047_b20501185611511">Namespace</strong>: Select the namespace of the workload. The default value is <strong id="cce_10_0150__cce_10_0047_b1508155615514">default</strong>. You can also click <span class="uicontrol" id="cce_10_0150__cce_10_0047_uicontrol342862818214"><b>Create Namespace</b></span> to create one. For details, see <a href="cce_10_0278.html">Creating a Namespace</a>.</li><li id="cce_10_0150__li11799254161"><strong id="cce_10_0150__cce_10_0047_b1997313316218">Pods</strong>: Enter the number of pods of the workload.</li><li id="cce_10_0150__li952215331573"><strong id="cce_10_0150__cce_10_0047_b1111971612">Container Runtime</strong>: A CCE cluster uses runC by default, whereas a CCE Turbo cluster supports both runC and Kata. For details about the differences, see <a href="cce_10_0463.html">Kata Runtime and Common Runtime</a>.</li></ul>
</div>
<div class="p" id="cce_10_0150__p206571518181616"><strong id="cce_10_0150__b855213715437">Container Settings</strong><ul id="cce_10_0150__ul42071022103320"><li id="cce_10_0150__li8770480458">Container Information<div class="p" id="cce_10_0150__p10493941854"><a name="cce_10_0150__li8770480458"></a><a name="li8770480458"></a>Multiple containers can be configured in a pod. You can click <span class="uicontrol" id="cce_10_0150__uicontrol1760133894311"><b>Add Container</b></span> on the right to configure multiple containers for the pod.<ul id="cce_10_0150__ul110012061719"><li id="cce_10_0150__li18101047191117"><strong id="cce_10_0150__cce_10_0047_b2309121414294">Basic Info</strong>: Configure basic information about the container.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0150__cce_10_0047_table128216444815" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0150__cce_10_0047_row0282348486"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1"><p id="cce_10_0150__cce_10_0047_p3282147483">Parameter</p>
<div class="p" id="cce_10_0150__p206571518181616"><strong id="cce_10_0150__b855213715437">Container Settings</strong><ul id="cce_10_0150__ul42071022103320"><li id="cce_10_0150__li8770480458"><strong id="cce_10_0150__b317117484420">Container Information</strong><div class="p" id="cce_10_0150__p10493941854">Multiple containers can be configured in a pod. You can click <span class="uicontrol" id="cce_10_0150__uicontrol1760133894311"><b>Add Container</b></span> on the right to configure multiple containers for the pod.<ul id="cce_10_0150__ul110012061719"><li id="cce_10_0150__li18101047191117"><strong id="cce_10_0150__cce_10_0047_b2309121414294">Basic Info</strong>: Configure basic information about the container.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0150__cce_10_0047_table128216444815" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0150__cce_10_0047_row0282348486"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1"><p id="cce_10_0150__cce_10_0047_p3282147483">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2"><p id="cce_10_0150__cce_10_0047_p1828244144819">Description</p>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2"><p id="cce_10_0150__cce_10_0047_p1828244144819">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0150__cce_10_0047_row109911651125414"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p39922517546">Container Name</p>
<tbody><tr id="cce_10_0150__cce_10_0047_row109911651125414"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p39922517546">Container Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p13992551175414">Name the container.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p13992551175414">Name the container.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row1129176194611"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p1945419542371">Pull Policy</p>
<tr id="cce_10_0150__cce_10_0047_row1129176194611"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p1945419542371">Pull Policy</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p1445445483719">Image update or pull policy. If you select <strong id="cce_10_0150__cce_10_0047_b1494134319294">Always</strong>, the image is pulled from the image repository each time. If you do not select <strong id="cce_10_0150__cce_10_0047_b694144313295">Always</strong>, the existing image of the node is preferentially used. If the image does not exist, the image is pulled from the image repository.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p1445445483719">Image update or pull policy. If you select <strong id="cce_10_0150__cce_10_0047_b1494134319294">Always</strong>, the image is pulled from the image repository each time. If you do not select <strong id="cce_10_0150__cce_10_0047_b694144313295">Always</strong>, the existing image of the node is preferentially used. If the image does not exist, the image is pulled from the image repository.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row1844916557597"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p182837474815">Image Name</p>
<tr id="cce_10_0150__cce_10_0047_row1844916557597"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p182837474815">Image Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p1372913120568">Click <strong id="cce_10_0150__cce_10_0047_b8790125722910">Select Image</strong> and select the image used by the container.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p1372913120568">Click <strong id="cce_10_0150__cce_10_0047_b8790125722910">Select Image</strong> and select the image used by the container.</p>
<p id="cce_10_0150__cce_10_0047_p137884754811">To use a third-party image, see <a href="cce_10_0009.html">Using Third-Party Images</a>.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row338117362515"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p1038143616517">Image Tag</p>
<tr id="cce_10_0150__cce_10_0047_row338117362515"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p1038143616517">Image Tag</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p1338110368519">Select the image tag to be deployed.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p1338110368519">Select the image tag to be deployed.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row161110459565"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p56111845145612">CPU Quota</p>
<tr id="cce_10_0150__cce_10_0047_row161110459565"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p56111845145612">CPU Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><ul id="cce_10_0150__cce_10_0047_ul9168521572"><li id="cce_10_0150__cce_10_0047_li15168227577"><strong id="cce_10_0150__cce_10_0047_b3669018123014">Request</strong>: minimum number of CPU cores required by a container. The default value is 0.25 cores.</li><li id="cce_10_0150__cce_10_0047_li121681216579"><strong id="cce_10_0150__cce_10_0047_b833715229303">Limit</strong>: maximum number of CPU cores available for a container. Do not leave <strong id="cce_10_0150__cce_10_0047_b1257625123019">Limit</strong> unspecified. Otherwise, intensive use of container resources will occur and your workload may exhibit unexpected behavior.</li></ul>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><ul id="cce_10_0150__cce_10_0047_ul9168521572"><li id="cce_10_0150__cce_10_0047_li15168227577"><strong id="cce_10_0150__cce_10_0047_b3669018123014">Request</strong>: minimum number of CPU cores required by a container. The default value is 0.25 cores.</li><li id="cce_10_0150__cce_10_0047_li121681216579"><strong id="cce_10_0150__cce_10_0047_b833715229303">Limit</strong>: maximum number of CPU cores available for a container. Do not leave <strong id="cce_10_0150__cce_10_0047_b1257625123019">Limit</strong> unspecified. Otherwise, intensive use of container resources will occur and your workload may exhibit unexpected behavior.</li></ul>
<p id="cce_10_0150__cce_10_0047_p520715505213">If <strong id="cce_10_0150__cce_10_0047_b2160104553012">Request</strong> and <strong id="cce_10_0150__cce_10_0047_b16757125053014">Limit</strong> are not specified, the quota is not limited. For more information and suggestions about <strong id="cce_10_0150__cce_10_0047_b12633192718313">Request</strong> and <strong id="cce_10_0150__cce_10_0047_b3633227113119">Limit</strong>, see <a href="cce_10_0163.html">Setting Container Specifications</a>.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row1119234316562"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p13193154315561">Memory Quota</p>
<tr id="cce_10_0150__cce_10_0047_row1119234316562"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p13193154315561">Memory Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><ul id="cce_10_0150__cce_10_0047_ul177605101578"><li id="cce_10_0150__cce_10_0047_li2760310155716"><strong id="cce_10_0150__cce_10_0047_b1482892418326">Request</strong>: minimum amount of memory required by a container. The default value is 512 MiB.</li><li id="cce_10_0150__cce_10_0047_li276012107576"><strong id="cce_10_0150__cce_10_0047_b89641128203220">Limit</strong>: maximum amount of memory available for a container. When memory usage exceeds the specified memory limit, the container will be terminated.</li></ul>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><ul id="cce_10_0150__cce_10_0047_ul177605101578"><li id="cce_10_0150__cce_10_0047_li2760310155716"><strong id="cce_10_0150__cce_10_0047_b1482892418326">Request</strong>: minimum amount of memory required by a container. The default value is 512 MiB.</li><li id="cce_10_0150__cce_10_0047_li276012107576"><strong id="cce_10_0150__cce_10_0047_b89641128203220">Limit</strong>: maximum amount of memory available for a container. When memory usage exceeds the specified memory limit, the container will be terminated.</li></ul>
<p id="cce_10_0150__cce_10_0047_p1974151022320">If <strong id="cce_10_0150__cce_10_0047_b1947843817326">Request</strong> and <strong id="cce_10_0150__cce_10_0047_b1347893819328">Limit</strong> are not specified, the quota is not limited. For more information and suggestions about <strong id="cce_10_0150__cce_10_0047_b1790014814322">Request</strong> and <strong id="cce_10_0150__cce_10_0047_b2900174810324">Limit</strong>, see <a href="cce_10_0163.html">Setting Container Specifications</a>.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row272852945719"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p20728192912572">(Optional) GPU Quota</p>
<tr id="cce_10_0150__cce_10_0047_row272852945719"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p20728192912572">(Optional) GPU Quota</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p53791055710">Configurable only when the cluster contains GPU nodes and the <a href="cce_10_0141.html">gpu-beta</a> add-on is installed.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p53791055710">Configurable only when the cluster contains GPU nodes and the <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a> add-on is installed.</p>
<ul id="cce_10_0150__cce_10_0047_ul19823440122219"><li id="cce_10_0150__cce_10_0047_li14823540152219"><strong id="cce_10_0150__cce_10_0047_b74394181358">All</strong>: The GPU is not used.</li><li id="cce_10_0150__cce_10_0047_li128232405222"><strong id="cce_10_0150__cce_10_0047_b2930224153512">Dedicated</strong>: GPU resources are exclusively used by the container.</li><li id="cce_10_0150__cce_10_0047_li13823440182213"><strong id="cce_10_0150__cce_10_0047_b1433212715356">Shared</strong>: percentage of GPU resources used by the container. For example, if this parameter is set to <strong id="cce_10_0150__cce_10_0047_b13332192713352">10%</strong>, the container uses 10% of GPU resources.</li></ul>
<p id="cce_10_0150__cce_10_0047_p91801538202613">For details about how to use GPU in the cluster, see <a href="cce_10_0345.html">Default GPU Scheduling in Kubernetes</a>.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row1449911299503"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p53374336504">(Optional) Privileged Container</p>
<tr id="cce_10_0150__cce_10_0047_row1449911299503"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p53374336504">(Optional) Privileged Container</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p49887211526">Programs in a privileged container have certain privileges.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p49887211526">Programs in a privileged container have certain privileges.</p>
<p id="cce_10_0150__cce_10_0047_p65001729105011">If <strong id="cce_10_0150__cce_10_0047_b55525534015">Privileged Container</strong> is enabled, the container is assigned privileges. For example, privileged containers can manipulate network devices on the host machine and modify kernel parameters.</p>
</td>
</tr>
<tr id="cce_10_0150__cce_10_0047_row152831345485"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p875325925918">(Optional) Init Container</p>
<tr id="cce_10_0150__cce_10_0047_row152831345485"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.1 "><p id="cce_10_0150__cce_10_0047_p875325925918">(Optional) Init Container</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.1.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p5379182494610">Indicates whether to use the container as an init container. The init container does not support health check.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.3.2.2.2.1.2.2.1.2.1.3.1.2 "><p id="cce_10_0150__cce_10_0047_p5379182494610">Indicates whether to use the container as an init container. The init container does not support health check.</p>
<p id="cce_10_0150__cce_10_0047_p191910221439">An init container is a special container that runs before other app containers in a pod are started. Each pod can contain multiple containers. In addition, a pod can contain one or more Init containers. Application containers in a pod are started and run only after the running of all Init containers completes. For details, see <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/" target="_blank" rel="noopener noreferrer">Init Container</a>.</p>
</td>
</tr>
@ -81,8 +81,9 @@
</li><li id="cce_10_0150__li5559101392014"><strong id="cce_10_0150__cce_10_0047_b479415459616">Image Access Credential</strong>: Select the credential used for accessing the image repository. The default value is <strong id="cce_10_0150__cce_10_0047_b157944451067">default-secret</strong>. You can use default-secret to access images in SWR. For details about <strong id="cce_10_0150__cce_10_0047_b582111347813">default-secret</strong>, see <a href="cce_10_0388.html#cce_10_0388__section11760122012591">default-secret</a>.</li><li id="cce_10_0150__li4559151310203">(Optional) <strong id="cce_10_0150__cce_10_0047_b513531164612">GPU</strong>: <strong id="cce_10_0150__cce_10_0047_b11135211134611">All</strong> is selected by default. The workload instance will be scheduled to the node with the specified GPU graphics card type.</li></ul>
</div>
<div class="p" id="cce_10_0150__p310913521612"><strong id="cce_10_0150__b104487882335241">(Optional) Advanced Settings</strong><ul id="cce_10_0150__ul67010503227"><li id="cce_10_0150__li179714209414"><strong id="cce_10_0150__cce_10_0047_b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0150__cce_10_0047_b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Labels and Annotations</a>.</li></ul>
<ul id="cce_10_0150__ul142811417"><li id="cce_10_0150__li1981131361"><strong id="cce_10_0150__b31333382212">Job Settings</strong><ul id="cce_10_0150__ul3224164372"><li id="cce_10_0150__li153401527710"><strong id="cce_10_0150__b58521141142118">Parallel Pods</strong>: Maximum number of pods that can run in parallel during job execution. The value cannot be greater than the total number of pods in the job.</li><li id="cce_10_0150__li10287691771"><strong id="cce_10_0150__b143534522119">Timeout (s)</strong>: Once a job reaches this time, the job status becomes failed and all pods in this job will be deleted. If you leave this parameter blank, the job will never time out.</li></ul>
</li><li id="cce_10_0150__li34513820295">Network configuration:<ul id="cce_10_0150__cce_10_0047_ul101792551538"><li id="cce_10_0150__cce_10_0047_li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS Rate Limiting for Inter-Pod Access</a>.</li></ul>
<ul id="cce_10_0150__ul142811417"><li id="cce_10_0150__li1981131361"><strong id="cce_10_0150__b31333382212">Job Settings</strong><ul id="cce_10_0150__ul3224164372"><li id="cce_10_0150__li153401527710"><strong id="cce_10_0150__b58521141142118">Parallel Pods</strong>: Maximum number of pods that can run in parallel during job execution. The value cannot be greater than the total number of pods in the job.</li><li id="cce_10_0150__li10287691771"><strong id="cce_10_0150__b143534522119">Timeout (s)</strong>: Once a job reaches this time, the job status becomes failed and all pods in this job will be deleted. If you leave this parameter blank, the job will never time out.</li><li id="cce_10_0150__li138103518153"><strong id="cce_10_0150__b36017415443">Completion Mode</strong><ul id="cce_10_0150__ul51723941512"><li id="cce_10_0150__li17920114315153"><strong id="cce_10_0150__b699913411252">Non-indexed</strong>: A job is considered complete when all the pods are successfully executed. Each pod completion is homologous to each other.</li><li id="cce_10_0150__li1358717341155"><strong id="cce_10_0150__b6574144582718">Indexed</strong>: Each pod gets an associated completion index from 0 to the number of pods minus 1. The job is considered complete when every pod allocated with an index is successfully executed. For an indexed job, pods are named in the format of $(job-name)-$(index).</li></ul>
</li><li id="cce_10_0150__li5539150161613"><strong id="cce_10_0150__b28515464300">Suspend Job</strong>: By default, a job is executed immediately after being created. The job's execution will be suspended if you enable this option, and resumed after you disable it.</li></ul>
</li><li id="cce_10_0150__li34513820295"><strong id="cce_10_0150__cce_10_0047_b5838184390">Network Configuration</strong>:<ul id="cce_10_0150__cce_10_0047_ul101792551538"><li id="cce_10_0150__cce_10_0047_li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS Rate Limiting for Inter-Pod Access</a>.</li></ul>
</li></ul>
</div>
</p></li><li id="cce_10_0150__li01417411620"><span>Click <strong id="cce_10_0150__b2573105264313">Create Workload</strong> in the lower right corner.</span></li></ol>

48
docs/cce/umn/cce_10_0151.html
View File

File diff suppressed because it is too large Load Diff

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

@ -36,7 +36,7 @@
<tr id="cce_10_0153__row133224252315"><td class="cellrowborder" valign="top" width="28.000000000000004%" headers="mcps1.3.3.2.3.2.1.2.3.1.1 "><p id="cce_10_0153__p23228259314">Secret Data</p>
</td>
<td class="cellrowborder" valign="top" width="72%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><p id="cce_10_0153__p133223251335">Workload secret data can be used in containers.</p>
<ul id="cce_10_0153__ul180611337469"><li id="cce_10_0153__li108069333468">If <strong id="cce_10_0153__b10282732165415">Secret Type</strong> is <strong id="cce_10_0153__b1449613357547">Opaque</strong>, click <span><img id="cce_10_0153__image12816235293" src="en-us_image_0000001695737281.png"></span>. In the dialog box displayed, enter a key-value pair and select <strong id="cce_10_0153__b31811921195517">Auto Base64 Encoding</strong>.</li><li id="cce_10_0153__li1536053764716">If <strong id="cce_10_0153__b17791104012492">Secret Type</strong> is <strong id="cce_10_0153__b722045644918">kubernetes.io/dockerconfigjson</strong>, enter the account and password of the private image repository.</li><li id="cce_10_0153__li17736104214478">If <strong id="cce_10_0153__b1214075424815">Secret Type</strong> is <strong id="cce_10_0153__b37767205275">kubernetes.io/tls</strong> or <strong id="cce_10_0153__b162903173270">IngressTLS</strong>, upload the certificate file and private key file.<div class="note" id="cce_10_0153__note1890215211325"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0153__ul1280017919332"><li id="cce_10_0153__li14977104417334">A certificate is a self-signed or CA-signed credential used for identity authentication.</li><li id="cce_10_0153__li6236332143310">A certificate request is a request for a signature with a private key.</li></ul>
<ul id="cce_10_0153__ul180611337469"><li id="cce_10_0153__li108069333468">If <strong id="cce_10_0153__b10282732165415">Secret Type</strong> is <strong id="cce_10_0153__b1449613357547">Opaque</strong>, click <span><img id="cce_10_0153__image12816235293" src="en-us_image_0000001695737281.png"></span>. In the dialog box displayed, enter a key-value pair and select <strong id="cce_10_0153__b31811921195517">Auto Base64 Encoding</strong>.</li><li id="cce_10_0153__li1536053764716">If <strong id="cce_10_0153__b184767329711">Secret Type</strong> is <strong id="cce_10_0153__b194771321571">kubernetes.io/dockerconfigjson</strong>, enter the account and password for logging in to the private image repository.</li><li id="cce_10_0153__li17736104214478">If <strong id="cce_10_0153__b1214075424815">Secret Type</strong> is <strong id="cce_10_0153__b37767205275">kubernetes.io/tls</strong> or <strong id="cce_10_0153__b162903173270">IngressTLS</strong>, upload the certificate file and private key file.<div class="note" id="cce_10_0153__note1890215211325"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0153__ul1280017919332"><li id="cce_10_0153__li14977104417334">A certificate is a self-signed or CA-signed credential used for identity authentication.</li><li id="cce_10_0153__li6236332143310">A certificate request is a request for a signature with a private key.</li></ul>
</div></div>
</li></ul>
</td>
@ -67,7 +67,7 @@ data:
kind: Secret
metadata:
name: mysecret #Secret name
namespace: default #Namespace. The default value is <strong id="cce_10_0153__b1488626037">default</strong>.
namespace: default #Namespace. The default value is <strong id="cce_10_0153__b2017317538">default</strong>.
data:
<strong id="cce_10_0153__b196671430132319">.dockerconfigjson: eyJh</strong><strong id="cce_10_0153__b1052142752319">*****</strong> # Content encoded using Base64.
<strong id="cce_10_0153__b18496153310233">type: kubernetes.io/dockerconfigjson</strong></pre>
@ -86,7 +86,7 @@ data:
apiVersion: v1
metadata:
name: mysecret #Secret name
namespace: default #Namespace. The default value is <strong id="cce_10_0153__b576248326">default</strong>.
namespace: default #Namespace. The default value is <strong id="cce_10_0153__b2123168700">default</strong>.
data:
tls.crt: <strong id="cce_10_0153__b1479454093611">LS0tLS1CRU*****FURS0tLS0t</strong> # Certificate content, which must be encoded using Base64.
tls.key: <strong id="cce_10_0153__b3794134014361">LS0tLS1CRU*****VZLS0tLS0=</strong> # Private key content, which must be encoded using Base64.
@ -96,7 +96,7 @@ data:
apiVersion: v1
metadata:
name: mysecret #Secret name
namespace: default #Namespace. The default value is <strong id="cce_10_0153__b954924090">default</strong>.
namespace: default #Namespace. The default value is <strong id="cce_10_0153__b406066445">default</strong>.
data:
tls.crt: <strong id="cce_10_0153__b4259755912">LS0tLS1CRU*****FURS0tLS0t</strong> # Certificate content, which must be encoded using Base64.
tls.key: <strong id="cce_10_0153__b1522022111010">LS0tLS1CRU*****VZLS0tLS0=</strong> # Private key content, which must be encoded using Base64.

99
docs/cce/umn/cce_10_0154.html
View File

File diff suppressed because it is too large Load Diff

2
docs/cce/umn/cce_10_0175.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Connecting to a Cluster Using an X.509 Certificate</h1>
<div id="body1556615866530"><div class="section" id="cce_10_0175__section160213214302"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0175__p1840111417517">This section describes how to obtain the cluster certificate from the console and use it access Kubernetes clusters.</p>
</div>
<div class="section" id="cce_10_0175__section1590914113306"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0175__ol898314521505"><li id="cce_10_0175__li4829928181812"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0175__li179831852301"><span>Choose <strong id="cce_10_0175__b367320164315">Cluster Information</strong> from the navigation pane and click <strong id="cce_10_0175__b1667311611319">Download</strong> next to <strong id="cce_10_0175__b067441613316">Authentication Mode</strong> in the <strong id="cce_10_0175__b1667491663119">Connection Information</strong> area.</span></li><li id="cce_10_0175__li1979910715109"><span>In the <span class="uicontrol" id="cce_10_0175__uicontrol13516511412"><b>Download X.509 Certificate</b></span> dialog box displayed, select the certificate expiration time and download the <span class="keyword" id="cce_10_0175__keyword2331112794610">X.509 certificate</span> of the cluster as prompted.</span><p><div class="fignone" id="cce_10_0175__fig873583013712"><span class="figcap"><b>Figure 1 </b>Downloading a certificate</span><br><span><img id="cce_10_0175__image282017212710" src="en-us_image_0000001647417220.png"></span></div>
<div class="section" id="cce_10_0175__section1590914113306"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0175__ol898314521505"><li id="cce_10_0175__li4829928181812"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0175__li179831852301"><span>Choose <strong id="cce_10_0175__b367320164315">Cluster Information</strong> from the navigation pane and click <strong id="cce_10_0175__b1667311611319">Download</strong> next to <strong id="cce_10_0175__b067441613316">Certificate Authentication</strong> in the <strong id="cce_10_0175__b1667491663119">Connection Information</strong> area.</span></li><li id="cce_10_0175__li1979910715109"><span>In the <span class="uicontrol" id="cce_10_0175__uicontrol13516511412"><b>Obtain Certificate</b></span> dialog box displayed, select the certificate expiration time and download the <span class="keyword" id="cce_10_0175__keyword2331112794610">X.509 certificate</span> of the cluster as prompted.</span><p><div class="fignone" id="cce_10_0175__fig873583013712"><span class="figcap"><b>Figure 1 </b>Downloading a certificate</span><br><span><img id="cce_10_0175__image5191162792910" src="en-us_image_0000001781916460.png"></span></div>
<div class="notice" id="cce_10_0175__note21816913343"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0175__ul45041635102414"><li id="cce_10_0175__li050403542411">The downloaded certificate contains three files: <strong id="cce_10_0175__b1790092752911">client.key</strong>, <strong id="cce_10_0175__b990002710298">client.crt</strong>, and <strong id="cce_10_0175__b690015272292">ca.crt</strong>. Keep these files secure.</li><li id="cce_10_0175__li150414359248">Certificates are not required for mutual access between containers in a cluster.</li></ul>
</div></div>
</p></li><li id="cce_10_0175__li067115818495"><span>Call native Kubernetes APIs using the cluster certificate.</span><p><p id="cce_10_0175__p1870145813497">For example, run the <strong id="cce_10_0175__b53321552399">curl</strong> command to call an API to view the pod information. In the following information,<i><span class="varname" id="cce_10_0175__varname149655191957">192.168.***.***:5443</span></i> indicates the IP address of the API server in the cluster.</p>

6
docs/cce/umn/cce_10_0182.html
View File

@ -4,6 +4,8 @@
<div id="body0000001175422840"><p id="cce_10_0182__p11459541508">CCE works with AOM to comprehensively monitor clusters. When a node is created, the ICAgent (the DaemonSet named <strong id="cce_10_0182__b271195119386">icagent</strong> in the kube-system namespace of the cluster) of AOM is installed by default. The ICAgent collects monitoring data of underlying resources and workloads running on the cluster. It also collects monitoring data of custom metrics of the workload.</p>
<ul id="cce_10_0182__ul92271168588"><li id="cce_10_0182__li139411131122317">Resource metrics<p id="cce_10_0182__p1522153372310"><a name="cce_10_0182__li139411131122317"></a><a name="li139411131122317"></a>Basic resource monitoring includes CPU, memory, and disk monitoring. For details, see <a href="#cce_10_0182__section205486212251">Resource Metrics</a>. You can view these metrics of clusters, nodes, and workloads on the CCE or AOM console.</p>
</li><li id="cce_10_0182__li05411539152316">Custom metrics<p id="cce_10_0182__p73224014238"><a name="cce_10_0182__li05411539152316"></a><a name="li05411539152316"></a>The ICAgent collects custom metrics of applications and uploads them to AOM. For details, see <a href="cce_10_0201.html">Monitoring Custom Metrics on AOM</a>.</p>
</li><li id="cce_10_0182__li15781103171819">NPD monitoring<p id="cce_10_0182__p37354218618"><a name="cce_10_0182__li15781103171819"></a><a name="li15781103171819"></a>node-problem-detector (npd for short) is an add-on that monitors and reports a node's health. It can connect to a third-party monitoring platform. It is a daemon running on each node. It collects node problems from different daemons and reports them to the API server. The npd add-on can run as a DaemonSet or a daemon.</p>
<p id="cce_10_0182__p1857655151814">CCE enhances npd in version 1.16.0, which now supports checks on node resources, components, and events, as well as fault isolation. For details, see <a href="cce_10_0132.html">CCE Node Problem Detector</a>.</p>
</li></ul>
<div class="section" id="cce_10_0182__section205486212251"><a name="cce_10_0182__section205486212251"></a><a name="section205486212251"></a><h4 class="sectiontitle">Resource Metrics</h4><p id="cce_10_0182__p2635126171117">On the CCE console, you can view the following metrics.</p>
<ul id="cce_10_0182__ul134260214312"><li id="cce_10_0182__li15426132194310"><a href="#cce_10_0182__section1932383618498">Viewing Cluster Monitoring Data</a></li><li id="cce_10_0182__li20609171544314"><a href="#cce_10_0182__section965517431154">Viewing Monitoring Data of Worker Nodes</a></li><li id="cce_10_0182__li17105316194314"><a href="#cce_10_0182__section2221948202013">Viewing Workload Monitoring Data</a></li><li id="cce_10_0182__li767741654310"><a href="#cce_10_0182__section1799803015267">Viewing Pod Monitoring Data</a></li></ul>
@ -168,7 +170,7 @@
</tr>
<tr id="cce_10_0182__row41151258144419"><td class="cellrowborder" valign="top" width="19.139999999999997%" headers="mcps1.3.6.3.3.2.2.2.3.1.1 "><p id="cce_10_0182__p14115155894419">Uplink Rate (BPS) (KB/s)</p>
</td>
<td class="cellrowborder" valign="top" width="80.86%" headers="mcps1.3.6.3.3.2.2.2.3.1.2 "><p id="cce_10_0182__p161151658164412">A metric indicates the speed at which data is uploaded from the node to the Internet</p>
<td class="cellrowborder" valign="top" width="80.86%" headers="mcps1.3.6.3.3.2.2.2.3.1.2 "><p id="cce_10_0182__p161151658164412">A metric indicates the speed at which data is uploaded from the node to the Internet.</p>
</td>
</tr>
<tr id="cce_10_0182__row7115155816442"><td class="cellrowborder" valign="top" width="19.139999999999997%" headers="mcps1.3.6.3.3.2.2.2.3.1.1 "><p id="cce_10_0182__p14115105810447">GPU Usage (%)</p>
@ -193,7 +195,7 @@
</p></li></ol>
</div>
<div class="section" id="cce_10_0182__section1799803015267"><a name="cce_10_0182__section1799803015267"></a><a name="section1799803015267"></a><h4 class="sectiontitle">Viewing Pod Monitoring Data</h4><p id="cce_10_0182__p86251397381">CCE allows you to view the monitoring date of your pods.</p>
<ol id="cce_10_0182__ol20859144815116"><li id="cce_10_0182__li1574217517514"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0182__li0321219195215"><span>Choose <strong id="cce_10_0182__b664512144213">Workloads</strong> from the navigation pane. Then click the workload name of the target workload to list the pods.</span></li><li id="cce_10_0182__li1843810105318"><span>Click <strong id="cce_10_0182__b88429912311">Monitor</strong> of the target pod to view the monitoring data.</span></li><li id="cce_10_0182__li19742151115119"><span>You can select statistical <strong id="cce_10_0182__b14990190111312">Dimension</strong> and choose time range to view the monitoring data. The data is provided by AOM. You can view the monitoring data of a pod, including the CPU, memory, disk, networking, and GPU.</span><p><div class="note" id="cce_10_0182__note89091145191511"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0182__p99091245121515">If multiple containers exist in a single pod, the monitoring data may vary according to the statistical <strong id="cce_10_0182__b1696144617257">Dimension</strong>. For example, if you select <strong id="cce_10_0182__b2831182817269">Maximum</strong> or <strong id="cce_10_0182__b2712142962610">Minimum</strong> for <strong id="cce_10_0182__b131671572292">Dimension</strong>, the value of each monitoring data is the maximum or minimum value of all containers under the pod. If <strong id="cce_10_0182__b1893834113120">Average</strong> is selected, the value of each monitoring data is the average value of all containers in the pod.</p>
<ol id="cce_10_0182__ol20859144815116"><li id="cce_10_0182__li1574217517514"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0182__li0321219195215"><span>Choose <strong id="cce_10_0182__b664512144213">Workloads</strong> in the navigation pane. Then click the workload name of the target workload to list the pods.</span></li><li id="cce_10_0182__li1843810105318"><span>Click <strong id="cce_10_0182__b88429912311">Monitor</strong> of the target pod to view the monitoring data.</span></li><li id="cce_10_0182__li19742151115119"><span>You can select statistical <strong id="cce_10_0182__b14990190111312">Dimension</strong> and choose time range to view the monitoring data. The data is provided by AOM. You can view the monitoring data of a pod, including the CPU, memory, disk, networking, and GPU.</span><p><div class="note" id="cce_10_0182__note89091145191511"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0182__p99091245121515">If there are multiple containers in a single pod, the monitoring data may vary according to the statistical <strong id="cce_10_0182__b1696144617257">Dimension</strong>. For example, if you select <strong id="cce_10_0182__b2831182817269">Maximum</strong> or <strong id="cce_10_0182__b2712142962610">Minimum</strong> for <strong id="cce_10_0182__b131671572292">Dimension</strong>, the value of each monitoring data is the maximum or minimum value of all containers under the pod. If <strong id="cce_10_0182__b1893834113120">Average</strong> is selected, the value of each monitoring data is the average value of all containers in the pod.</p>
</div></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0182__table175951013175613" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Pod monitoring metrics</caption><thead align="left"><tr id="cce_10_0182__row1359591317569"><th align="left" class="cellrowborder" valign="top" width="19.139999999999997%" id="mcps1.3.7.3.4.2.2.2.3.1.1"><p id="cce_10_0182__p7595121315611">Metric</p>

2
docs/cce/umn/cce_10_0184.html
View File

@ -6,7 +6,7 @@
</div>
<div class="section" id="cce_10_0184__section299918342346"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0184__ul121015107312"><li id="cce_10_0184__li3101810193119">Data, including the VM status, ECS names, number of CPUs, size of memory, ECS specifications, and public IP addresses, can be synchronized.</li><li id="cce_10_0184__li8102110103118">Data, such as the OS and image ID, cannot be synchronized. (Such parameters cannot be modified on the ECS console.)</li></ul>
</div>
<div class="section" id="cce_10_0184__section2076543461216"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0184__ol1882502762811"><li id="cce_10_0184__li849281818811"><span>Log in to the CCE console.</span></li><li id="cce_10_0184__li13907715194011"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0184__uicontrol129961721266"><b>Nodes</b></span> in the navigation pane.</span></li><li id="cce_10_0184__li1382582719286"><span>Choose <strong id="cce_10_0184__b13445369615">More</strong> &gt; <strong id="cce_10_0184__b144620614615">Sync Server Data</strong> next to the node.</span><p><div class="fignone" id="cce_10_0184__fig983933294015"><span class="figcap"><b>Figure 1 </b>Synchronizing server data</span><br><span><img id="cce_10_0184__image3503275220" src="en-us_image_0000001695737349.png"></span></div>
<div class="section" id="cce_10_0184__section2076543461216"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0184__ol1882502762811"><li id="cce_10_0184__li849281818811"><span>Log in to the CCE console.</span></li><li id="cce_10_0184__li13907715194011"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0184__uicontrol129961721266"><b>Nodes</b></span> in the navigation pane.</span></li><li id="cce_10_0184__li1382582719286"><span>Choose <strong id="cce_10_0184__b13445369615">More</strong> &gt; <strong id="cce_10_0184__b144620614615">Sync Server Data</strong> next to the node.</span><p><div class="fignone" id="cce_10_0184__fig983933294015"><span class="figcap"><b>Figure 1 </b>Synchronizing server data</span><br><span><img id="cce_10_0184__image13654123215117" src="en-us_image_0000001782089384.png"></span></div>
<p id="cce_10_0184__p17635154314012">After the synchronization is complete, the <strong id="cce_10_0184__b52353142615">ECS data synchronization requested</strong> message is displayed in the upper right corner.</p>
</p></li></ol>
</div>

2
docs/cce/umn/cce_10_0188.html
View File

@ -4,7 +4,7 @@
<div id="body1556099896059"><p id="cce_10_0188__p1524419446112">CCE cluster-level permissions are assigned based on <strong id="cce_10_0188__b06521521142312">IAM system policies</strong> and <strong id="cce_10_0188__b176531921112312">custom policies</strong>. You can use user groups to assign permissions to IAM users.</p>
<div class="caution" id="cce_10_0188__note560142111218"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="cce_10_0188__ul1098618193271"><li id="cce_10_0188__li11771193020279">Cluster permissions are granted for users to operate cluster-related resources only (such as clusters and nodes). To operate Kubernetes resources like workloads and Services, you must be granted the <a href="cce_10_0189.html">namespace permissions</a> at the same time.</li><li id="cce_10_0188__li121899852616">When viewing a cluster on the CCE console, the information displayed depends on the namespace permissions. If you have no namespace permissions, you cannot view the resources in the cluster. For details, see <a href="cce_10_0190.html">Permission Dependency of the CCE Console</a>.</li></ul>
</div></div>
<div class="section" id="cce_10_0188__section16601203895318"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0188__ul115321234510"><li id="cce_10_0188__li267771813457">A user with the Security Administrator role (for example, your account) has all IAM permissions except role switching. Only these users can view user groups and their permissions on the <strong id="cce_10_0188__b364011513384">Permissions</strong> page on the CCE console.</li></ul>
<div class="section" id="cce_10_0188__section16601203895318"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0188__ul115321234510"><li id="cce_10_0188__li267771813457">A user with the Security Administrator role (for example, your account) has all IAM permissions except role switching. Only these users can view user groups and their permissions on the <strong id="cce_10_0188__b9685148124514">Permissions</strong> page on the CCE console.</li></ul>
</div>
<div class="section" id="cce_10_0188__section638994317105"><h4 class="sectiontitle">Configuration</h4><p id="cce_10_0188__p686525014420">On the CCE console, when you choose <strong id="cce_10_0188__b197085371453">Permissions</strong> &gt; <strong id="cce_10_0188__b525314581453">Cluster-Level Permissions</strong> to create a user group, you will be directed to the IAM console to complete the process. After the user group is created and its permissions are configured, you can view the information on the <strong id="cce_10_0188__b78091143115016">Cluster-Level Permissions</strong> tab page. This section describes the operations in IAM.</p>
</div>

2
docs/cce/umn/cce_10_0189.html
View File

@ -40,7 +40,7 @@
</table>
</div>
</div>
<div class="section" id="cce_10_0189__section320111415506"><h4 class="sectiontitle">Precautions</h4><ul id="cce_10_0189__ul815212017513"><li id="cce_10_0189__li8127185819407">After you create a cluster, CCE automatically assigns the cluster-admin permission to you, which means you have full control on all resources in all namespaces in the cluster. The ID of a federated user changes upon each login and logout. Therefore, the user with the permissions is displayed as deleted. In this case, do not delete the permissions. Otherwise, the authentication fails. You are advised to grant the cluster-admin permission to a user group on CCE and add federated users to the user group.</li><li id="cce_10_0189__li9232193524714">A user with the Security Administrator role has all IAM permissions except role switching. For example, an account in the admin user group has this role by default. Only these users can assign permissions on the <strong id="cce_10_0189__b1874164883917">Permissions</strong> page on the CCE console.</li></ul>
<div class="section" id="cce_10_0189__section320111415506"><h4 class="sectiontitle">Precautions</h4><ul id="cce_10_0189__ul815212017513"><li id="cce_10_0189__li8127185819407">After you create a cluster, CCE automatically assigns the cluster-admin permission to you, which means you have full control on all resources in all namespaces in the cluster. The ID of a federated user changes upon each login and logout. Therefore, the user with the permissions is displayed as deleted. In this case, do not delete the permissions. Otherwise, the authentication fails. You are advised to grant the cluster-admin permission to a user group on CCE and add federated users to the user group.</li><li id="cce_10_0189__li9232193524714">A user with the Security Administrator role has all IAM permissions except role switching. For example, an account in the admin user group has this role by default. Only these users can assign permissions on the <strong id="cce_10_0189__b16754142318458">Permissions</strong> page on the CCE console.</li></ul>
</div>
<div class="section" id="cce_10_0189__section14142185815219"><h4 class="sectiontitle">Configuring Namespace Permissions (on the Console)</h4><p id="cce_10_0189__p4776162914454">You can regulate users' or user groups' access to Kubernetes resources in a single namespace based on their Kubernetes RBAC roles.</p>
<ol id="cce_10_0189__ol24786311219"><li id="cce_10_0189__li663920334397"><span>Log in to the CCE console. In the navigation pane, choose <strong id="cce_10_0189__b189414512310">Permissions</strong>.</span></li><li id="cce_10_0189__li1235093912444"><span>Select a cluster for which you want to add permissions from the drop-down list on the right.</span></li><li id="cce_10_0189__li4640173311392"><span>Click <strong id="cce_10_0189__b1474122216500">Add Permissions</strong> in the upper right corner.</span></li><li id="cce_10_0189__li156401033143920"><span>Confirm the cluster name and select the namespace to assign permissions for. For example, select <strong id="cce_10_0189__b119854248323">All namespaces</strong>, the target user or user group, and select the permissions.</span><p><div class="note" id="cce_10_0189__note2314729165419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0189__p731522905414">If you do not have IAM permissions, you cannot select users or user groups when configuring permissions for other users or user groups. In this case, you can enter a user ID or user group ID. </p>

4
docs/cce/umn/cce_10_0190.html
View File

@ -34,7 +34,7 @@
<p id="cce_10_0190__p117241658182817">Scalable File Service (SFS)</p>
</td>
<td class="cellrowborder" valign="top" width="49.45494549454945%" headers="mcps1.3.3.4.2.4.1.3 "><p id="cce_10_0190__p57471617102017">Except in the following cases, the user does not require any additional role to create workloads.</p>
<ul id="cce_10_0190__ul8113732182016"><li id="cce_10_0190__li1549293301">To create a Service using ELB, you must have ELB FullAccess or ELB Administrator plus VPC Administrator assigned.</li><li id="cce_10_0190__li211313282010">To use a Java probe, you must have AOM FullAccess and APM FullAccess assigned.</li><li id="cce_10_0190__li191131132132013">To create a Service using NAT Gateway, you must have NAT Gateway Administrator assigned.</li><li id="cce_10_0190__li1589180192710">To use OBS, you must have OBS Administrator globally assigned.<div class="note" id="cce_10_0190__note1215220141518"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0190__p0153120121518">Because of the cache, it takes about 13 minutes for the RBAC policy to take effect after being granted to users, enterprise projects, and user groups. After an OBS-related system policy is granted, it takes about 5 minutes for the policy to take effect.</p>
<ul id="cce_10_0190__ul8113732182016"><li id="cce_10_0190__li1549293301">To create a Service using ELB, you must have ELB FullAccess or ELB Administrator plus VPC Administrator assigned.</li><li id="cce_10_0190__li211313282010">To use a Java probe, you must have AOM FullAccess and APM FullAccess assigned.</li><li id="cce_10_0190__li191131132132013">To create a Service using NAT Gateway, you must have NAT Gateway Administrator assigned.</li><li id="cce_10_0190__li1589180192710">To use OBS, you must have OBS Administrator globally assigned.<div class="note" id="cce_10_0190__note1215220141518"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0190__p0153120121518">Because of the cache, it takes about 13 minutes for the RBAC policy to take effect after being granted to users and user groups. After an OBS-related system policy is granted, it takes about 5 minutes for the policy to take effect.</p>
</div></div>
</li><li id="cce_10_0190__li127085616265">To use SFS, you must have SFS FullAccess assigned.</li></ul>
</td>
@ -68,7 +68,7 @@
<p id="cce_10_0190__p126411556163811">Scalable File Service (SFS)</p>
<p id="cce_10_0190__p344642920405">SFS Turbo</p>
</td>
<td class="cellrowborder" valign="top" width="49.45494549454945%" headers="mcps1.3.3.4.2.4.1.3 "><ul id="cce_10_0190__ul146023714385"><li id="cce_10_0190__li161173711383">To use OBS, you must have OBS Administrator globally assigned.<div class="note" id="cce_10_0190__en-us_topic_0000001244101055_note1215220141518"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0190__en-us_topic_0000001244101055_p0153120121518">Because of the cache, it takes about 13 minutes for the RBAC policy to take effect after being granted to users, enterprise projects, and user groups. After an OBS-related system policy is granted, it takes about 5 minutes for the policy to take effect.</p>
<td class="cellrowborder" valign="top" width="49.45494549454945%" headers="mcps1.3.3.4.2.4.1.3 "><ul id="cce_10_0190__ul146023714385"><li id="cce_10_0190__li161173711383">To use OBS, you must have OBS Administrator globally assigned.<div class="note" id="cce_10_0190__en-us_topic_0000001244101055_note1215220141518"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0190__en-us_topic_0000001244101055_p0153120121518">Because of the cache, it takes about 13 minutes for the RBAC policy to take effect after being granted to users and user groups. After an OBS-related system policy is granted, it takes about 5 minutes for the policy to take effect.</p>
</div></div>
</li><li id="cce_10_0190__li1461183713810">To use SFS, you must have SFS FullAccess assigned.</li><li id="cce_10_0190__li13760119415">Using SFS Turbo requires the SFS Turbo Admin role.</li></ul>
<p id="cce_10_0190__p533161762815">The CCE Administrator role is required for importing storage devices.</p>

54
docs/cce/umn/cce_10_0193.html
View File

File diff suppressed because it is too large Load Diff

2
docs/cce/umn/cce_10_0198.html
View File

@ -88,7 +88,7 @@
<tr id="cce_10_0198__row25394514014"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.4.2.3.2.6.2.3.1.1 "><p id="cce_10_0198__p25391859406">Resource Tag</p>
</td>
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.4.2.3.2.6.2.3.1.2 "><p id="cce_10_0198__p275333410342">You can add resource tags to classify resources.</p>
<p id="cce_10_0198__p117537347346">You can create <strong id="cce_10_0198__cce_10_0363_b6239155511710">predefined tags</strong> in Tag Management Service (TMS). Predefined tags are available to all service resources that support tags. You can use these tags to improve tagging and resource migration efficiency. </p>
<p id="cce_10_0198__p117537347346">You can create <strong id="cce_10_0198__cce_10_0363_b6239155511710">predefined tags</strong> in TMS. Predefined tags are available to all service resources that support tags. You can use these tags to improve tagging and resource migration efficiency. </p>
<p id="cce_10_0198__p16753133419348">CCE will automatically create the "CCE-Dynamic-Provisioning-Node=<em id="cce_10_0198__i111451122126">node id</em>" tag.</p>
</td>
</tr>

6
docs/cce/umn/cce_10_0201.html
View File

@ -17,7 +17,7 @@ nginx_connections_active 2
nginx_connections_reading 0</pre>
<p id="cce_10_0201__p1358113105720">Prometheus provides clients in various languages. For details about the clients, see <a href="https://prometheus.io/docs/instrumenting/clientlibs/" target="_blank" rel="noopener noreferrer">Prometheus CLIENT LIBRARIES</a>. For details about how to develop an exporter, see <a href="https://prometheus.io/docs/instrumenting/writing_exporters/" target="_blank" rel="noopener noreferrer">WRITING EXPORTERS</a>. The Prometheus community provides various third-party exporters that can be directly used. For details, see <a href="https://prometheus.io/docs/instrumenting/exporters/" target="_blank" rel="noopener noreferrer">EXPORTERS AND INTEGRATIONS</a>.</p>
</div>
<div class="section" id="cce_10_0201__section14984815298"><a name="cce_10_0201__section14984815298"></a><a name="section14984815298"></a><h4 class="sectiontitle">Preparing an Application</h4><p id="cce_10_0201__p12799784716">User-developed applications must provide a metric monitoring API for ICAgent to collect data, and the monitoring data must comply with the Prometheus specifications. For details, see <a href="#cce_10_0201__section173671127160">Prometheus Monitoring Data Collection</a>.</p>
<div class="section" id="cce_10_0201__section14984815298"><a name="cce_10_0201__section14984815298"></a><a name="section14984815298"></a><h4 class="sectiontitle">Preparing an Application</h4><p id="cce_10_0201__p12799784716">Self-developed applications must provide a metric monitoring API for ICAgent to collect data, and the monitoring data must comply with the Prometheus specifications. For details, see <a href="#cce_10_0201__section173671127160">Prometheus Monitoring Data Collection</a>.</p>
<p id="cce_10_0201__p869125518296">This document uses Nginx as an example to describe how to collect monitoring data. There is a module named<strong id="cce_10_0201__b3952153014374"> ngx_http_stub_status_module</strong> in Nginx, which provides basic monitoring functions. You can configure the <strong id="cce_10_0201__b1057321884510">nginx.conf </strong>file to provide an interface for external systems to access Nginx monitoring data.</p>
<ol id="cce_10_0201__ol47741617716"><li id="cce_10_0201__li172914434716"><span>Log in to a Linux VM that can access to the Internet and run Docker commands.</span></li><li id="cce_10_0201__li5774511276"><span>Create an <strong id="cce_10_0201__b1576091111477">nginx.conf</strong> file. Add the server configuration under <strong id="cce_10_0201__b982818481210">http</strong> to enable Nginx to provide an interface for the external systems to access the monitoring data.</span><p><pre class="screen" id="cce_10_0201__screen1773195816508">user nginx;
worker_processes auto;
@ -58,11 +58,11 @@ ADD nginx.conf /etc/nginx/nginx.conf
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]</pre>
</div>
</p></li><li id="cce_10_0201__li171513248917"><span>Use this Dockerfile to build an image and upload it to SWR. The image name is <strong id="cce_10_0201__b19241320133619">nginx:exporter</strong>. </span><p><ol type="a" id="cce_10_0201__ol111731405102"><li id="cce_10_0201__en-us_topic_0000001148755333_li187221141362">In the navigation pane, choose <strong id="cce_10_0201__b1011640000114645">My Images</strong> and then click <strong id="cce_10_0201__b1093525753114645">Upload Through Client</strong>in the upper right corner. On the page displayed, click <strong id="cce_10_0201__b420143385114645">Generate a temporary login command</strong> and click <span><img id="cce_10_0201__en-us_topic_0000001148755333_image18751161714" src="en-us_image_0000001695896249.png"></span> to copy the command.</li><li id="cce_10_0201__en-us_topic_0000001148755333_li4452185981216">Run the login command copied in the previous step on the node. If the login is successful, the message "Login Succeeded" is displayed.</li><li id="cce_10_0201__li820205451013">Run the following command to build an image named nginx. The image version is exporter.<pre class="screen" id="cce_10_0201__screen12404356141220">docker build -t nginx:exporter .</pre>
</p></li><li id="cce_10_0201__li171513248917"><span>Use this Dockerfile to build an image and upload it to SWR. The image name is <strong id="cce_10_0201__b19241320133619">nginx:exporter</strong>. </span><p><ol type="a" id="cce_10_0201__ol111731405102"><li id="cce_10_0201__en-us_topic_0000001148755333_li187221141362">In the navigation pane, choose <strong id="cce_10_0201__b1011640000114645">My Images</strong>. Click <strong id="cce_10_0201__b1093525753114645">Upload Through Client</strong> in the upper right corner. On the page displayed, click <strong id="cce_10_0201__b420143385114645">Generate a temporary login command</strong> and click <span><img id="cce_10_0201__en-us_topic_0000001148755333_image18751161714" src="en-us_image_0000001695896249.png"></span> to copy the command.</li><li id="cce_10_0201__en-us_topic_0000001148755333_li4452185981216">Run the login command copied in the previous step on the node. If the login is successful, the message "Login Succeeded" is displayed.</li><li id="cce_10_0201__li820205451013">Run the following command to build an image named nginx. The image version is exporter.<pre class="screen" id="cce_10_0201__screen12404356141220">docker build -t nginx:exporter .</pre>
</li><li id="cce_10_0201__li195490338118">Tag the image and upload it to the image repository. Change the image repository address and organization name based on your requirements.<pre class="screen" id="cce_10_0201__screen0590911161715">docker tag nginx:exporter {swr-address}/{group}/nginx:exporter
docker push {swr-address}/{group}/nginx:exporter</pre>
</li></ol>
</p></li><li id="cce_10_0201__li3673432142319"><span>View application metrics.</span><p><ol type="a" id="cce_10_0201__ol93905514234"><li id="cce_10_0201__li20154355142319">Use <strong id="cce_10_0201__b20613053114315">nginx:exporter</strong> to create a workload.</li><li id="cce_10_0201__li839005118236"><a href="cce_10_00356.html">Access the container </a>and use http://&lt;ip_address&gt;:8080/stub_status to obtain nginx monitoring data. <strong id="cce_10_0201__b1256517213537">&lt;ip_address&gt;</strong> indicates the IP address of the container. Information similar to the following is displayed.<pre class="screen" id="cce_10_0201__screen99889917190"># curl http://127.0.0.1:8080/stub_status
</p></li><li id="cce_10_0201__li3673432142319"><span>View application metrics.</span><p><ol type="a" id="cce_10_0201__ol93905514234"><li id="cce_10_0201__li20154355142319">Use <strong id="cce_10_0201__b20613053114315">nginx:exporter</strong> to create a workload.</li><li id="cce_10_0201__li839005118236"><a href="cce_10_00356.html">Access the container</a> and use http://&lt;ip_address&gt;:8080/stub_status to obtain nginx monitoring data. <strong id="cce_10_0201__b1256517213537">&lt;ip_address&gt;</strong> indicates the IP address of the container. Information similar to the following is displayed.<pre class="screen" id="cce_10_0201__screen99889917190"># curl http://127.0.0.1:8080/stub_status
Active connections: 3
server accepts handled requests
146269 146269 212

4
docs/cce/umn/cce_10_0205.html
View File

@ -1,11 +1,11 @@
<a name="cce_10_0205"></a><a name="cce_10_0205"></a>
<h1 class="topictitle1">metrics-server</h1>
<h1 class="topictitle1">Kubernetes Metrics Server</h1>
<div id="body1574828037707"><p id="cce_10_0205__p8803328425">From version 1.8 onwards, Kubernetes provides resource usage metrics, such as the container CPU and memory usage, through the Metrics API. These metrics can be directly accessed by users (for example, by using the <strong id="cce_10_0205__b5101142911575">kubectl top</strong> command) or used by controllers (for example, Horizontal Pod Autoscaler) in a cluster for decision-making. The specific component is metrics-server, which is used to substitute for heapster for providing the similar functions. heapster has been gradually abandoned since v1.11.</p>
<p id="cce_10_0205__p183161841122110">metrics-server is an aggregator for monitoring data of core cluster resources. You can quickly install this add-on on the CCE console.</p>
<p id="cce_10_0205__p136871139141318">After metrics-server is installed, you can create an HPA policy on the <strong id="cce_10_0205__b93481922984">Workload Scaling</strong> tab page of the <strong id="cce_10_0205__b1534812214813">Auto Scaling</strong> page. For details, see <a href="cce_10_0208.html">HPA</a>.</p>
<p id="cce_10_0205__p185802028346">The official community project and documentation are available at <a href="https://github.com/kubernetes-sigs/metrics-server" target="_blank" rel="noopener noreferrer">https://github.com/kubernetes-sigs/metrics-server</a>.</p>
<div class="section" id="cce_10_0205__section1962241123816"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0205__ol13949124616422"><li id="cce_10_0205__li13183153352515"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0205__uicontrol165791523193718"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0205__b1122125895819">metrics-server</strong><strong id="cce_10_0205__b72631507599"></strong> on the right, and click <strong id="cce_10_0205__b1558032343718">Install</strong>.</span></li><li id="cce_10_0205__li178033014157"><span>On the <strong id="cce_10_0205__b117371290610654">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="section" id="cce_10_0205__section1962241123816"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0205__ol13949124616422"><li id="cce_10_0205__li13183153352515"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0205__uicontrol165791523193718"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0205__b37191426133316">Kubernetes Metrics Server</strong> on the right, and click <strong id="cce_10_0205__b1558032343718">Install</strong>.</span></li><li id="cce_10_0205__li178033014157"><span>On the <strong id="cce_10_0205__b117371290610654">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0205__table924319911495" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Add-on configuration</caption><thead align="left"><tr id="cce_10_0205__row42442974913"><th align="left" class="cellrowborder" valign="top" width="24%" id="mcps1.3.5.2.2.2.1.2.3.1.1"><p id="cce_10_0205__p17244793496">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76%" id="mcps1.3.5.2.2.2.1.2.3.1.2"><p id="cce_10_0205__p42441596495">Description</p>

2
docs/cce/umn/cce_10_0208.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">HPA</h1>
<div id="body1569380890256"><p id="cce_10_0208__p1850115535712"><span class="keyword" id="cce_10_0208__keyword6471735144918">Horizontal Pod Autoscaling</span> (HPA) in Kubernetes implements <span class="keyword" id="cce_10_0208__keyword12871240154910">horizontal scaling of pods</span>. In a CCE HPA policy, you can configure different cooldown time windows and scaling thresholds for different applications based on the Kubernetes HPA.</p>
<div class="section" id="cce_10_0208__section194973810277"><h4 class="sectiontitle">Prerequisites</h4><div class="p" id="cce_10_0208__p128711617615">To use HPA, install an add-on that provides metrics APIs. Select one of the following add-ons based on your cluster version and actual requirements.<ul id="cce_10_0208__ul12333184219617"><li id="cce_10_0208__li57914431362"><a href="cce_10_0205.html">metrics-server</a>: provides basic resource usage metrics, such as container CPU and memory usage. It is supported by all cluster versions.</li></ul>
<div class="section" id="cce_10_0208__section194973810277"><h4 class="sectiontitle">Prerequisites</h4><div class="p" id="cce_10_0208__p128711617615">To use HPA, install an add-on that provides metrics APIs. Select one of the following add-ons based on your cluster version and actual requirements.<ul id="cce_10_0208__ul12333184219617"><li id="cce_10_0208__li57914431362"><a href="cce_10_0205.html">Kubernetes Metrics Server</a>: provides basic resource usage metrics, such as container CPU and memory usage. It is supported by all cluster versions.</li></ul>
</div>
</div>
<div class="section" id="cce_10_0208__section107429267459"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0208__ul14111945007"><li id="cce_10_0208__li191134512018">HPA policies can be created only for clusters of v1.13 or later.</li><li id="cce_10_0208__li92774437495">For clusters earlier than v1.19.10, if an HPA policy is used to scale out a workload with EVS volumes mounted, the existing pods cannot be read or written when a new pod is scheduled to another node.<p id="cce_10_0208__p11921144194914"><a name="cce_10_0208__li92774437495"></a><a name="li92774437495"></a>For clusters of v1.19.10 and later, if an HPA policy is used to scale out a workload with EVS volume mounted, a new pod cannot be started because EVS disks cannot be attached.</p>

6
docs/cce/umn/cce_10_0209.html
View File

@ -12,9 +12,9 @@
<div class="section" id="cce_10_0209__section4444195220142"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0209__ol29784442018"><li id="cce_10_0209__li148293318248"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0209__li3967519744"><span>Choose <strong id="cce_10_0209__b17415920121417">Node Scaling</strong> in the navigation pane.</span><p><ul id="cce_10_0209__ul2895102913469"><li id="cce_10_0209__li10895529174618">If <span class="uicontrol" id="cce_10_0209__uicontrol178213815103"><b>Uninstalled</b></span> is displayed next to the add-on name, click <strong id="cce_10_0209__b58853891018">Install</strong>, set add-on parameters as required, and click <strong id="cce_10_0209__b689338151015">Install</strong> to install the add-on.</li><li id="cce_10_0209__li389532914466">If <span class="uicontrol" id="cce_10_0209__uicontrol415614446107"><b>Installed</b></span> is displayed next to the add-on name, the add-on has been installed.</li></ul>
</p></li><li id="cce_10_0209__li1233834472"><span>Click <strong id="cce_10_0209__b1735993131112">Create Node Scaling Policy</strong> in the upper right corner and set the parameters as follows:</span><p><ul id="cce_10_0209__ul17966105632820"><li id="cce_10_0209__li1396619568287"><strong id="cce_10_0209__b3656118114412">Policy Name</strong>: name of the policy to be created, which can be customized.</li><li id="cce_10_0209__li179668567286"><strong id="cce_10_0209__b19311184991110">Associated Node Pools</strong>: Select the node pool to be associated. You can associate multiple node pools to use the same scaling policy.</li><li id="cce_10_0209__li39669567288"><strong id="cce_10_0209__b13105141142720">Rules</strong>: Click <strong id="cce_10_0209__b53511037117">Add Rule</strong>. In the dialog box displayed, set the following parameters:<p id="cce_10_0209__p1971102016286"><strong id="cce_10_0209__b46681421144">Rule Name</strong>: Enter a rule name.</p>
<p id="cce_10_0209__p129711920172811"><strong id="cce_10_0209__b18955153710117">Rule Type</strong>: You can select <strong id="cce_10_0209__b959911421113">Metric-based</strong> or <strong id="cce_10_0209__b17771245817">Periodic</strong>. The differences between the two types are as follows:</p>
<ul id="cce_10_0209__ul1597352072812"><li id="cce_10_0209__li1397213202289"><strong id="cce_10_0209__b1598011319536">Metric-based</strong>:<div class="p" id="cce_10_0209__p1817714544282"><strong id="cce_10_0209__b1268835520117">Condition</strong>: Select <strong id="cce_10_0209__b10461001029">CPU allocation rate</strong> or <strong id="cce_10_0209__b1947947211">Memory allocation rate</strong> and enter a value. The value must be greater than the scale-in percentage configured in the autoscaler add-on.<div class="note" id="cce_10_0209__note17972182052813"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0209__ul85014395310"><li id="cce_10_0209__li350103953119">Resource allocation (%) = Resources requested by pods in the node pool/Resources allocatable to pods in the node pool</li><li id="cce_10_0209__li1650118397311"><strong id="cce_10_0209__b1610316979">If multiple rules meet the conditions, the rules are executed in either of the following modes:</strong><p id="cce_10_0209__p31941933210">If rules based on the <strong id="cce_10_0209__b1745414646">CPU allocation rate</strong> and <strong id="cce_10_0209__b970574213">memory allocation rate</strong> are configured and two or more rules meet the scale-out conditions, the rule that will add the most nodes will be executed.</p>
<p id="cce_10_0209__p8194179193215">If a rule based on the <strong id="cce_10_0209__b1869577827">CPU allocation rate</strong> and <strong id="cce_10_0209__b1219578654">a periodic rule</strong> are configured and they both meet the scale-out conditions, one of them will be executed randomly. The rule executed first (rule A) changes the node pool to the scaling state. As a result, the other rule (rule B) cannot be executed. After rule A is executed and the node pool status becomes normal, rule B will not be executed.</p>
</li><li id="cce_10_0209__li9179142215243">If rules based on the <strong id="cce_10_0209__b2112418653">CPU allocation rate</strong> and <strong id="cce_10_0209__b536514425">memory allocation rate</strong> are configured, the policy detection period varies with the processing logic of each loop of the autoscaler add-on. Scale-out is triggered once the conditions are met, but it is constrained by other factors such as the cool-down interval and node pool status.</li></ul>
<ul id="cce_10_0209__ul1597352072812"><li id="cce_10_0209__li1397213202289"><strong id="cce_10_0209__b1598011319536">Metric-based</strong>:<div class="p" id="cce_10_0209__p1817714544282"><strong id="cce_10_0209__b1268835520117">Condition</strong>: Select <strong id="cce_10_0209__b10461001029">CPU allocation rate</strong> or <strong id="cce_10_0209__b1947947211">Memory allocation rate</strong> and enter a value. The value must be greater than the scale-in percentage configured in the autoscaler add-on.<div class="note" id="cce_10_0209__note17972182052813"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0209__ul85014395310"><li id="cce_10_0209__li350103953119">Resource allocation (%) = Resources requested by pods in the node pool/Resources allocatable to pods in the node pool</li><li id="cce_10_0209__li1650118397311"><strong id="cce_10_0209__b1575155769">If multiple rules meet the conditions, the rules are executed in either of the following modes:</strong><p id="cce_10_0209__p31941933210">If rules based on the <strong id="cce_10_0209__b758872967">CPU allocation rate</strong> and <strong id="cce_10_0209__b928308002">memory allocation rate</strong> are configured and two or more rules meet the scale-out conditions, the rule that will add the most nodes will be executed.</p>
<p id="cce_10_0209__p8194179193215">If a rule based on the <strong id="cce_10_0209__b794956005">CPU allocation rate</strong> and <strong id="cce_10_0209__b2028391006">a periodic rule</strong> are configured and they both meet the scale-out conditions, one of them will be executed randomly. The rule executed first (rule A) changes the node pool to the scaling state. As a result, the other rule (rule B) cannot be executed. After rule A is executed and the node pool status becomes normal, rule B will not be executed.</p>
</li><li id="cce_10_0209__li9179142215243">If rules based on the <strong id="cce_10_0209__b551544177">CPU allocation rate</strong> and <strong id="cce_10_0209__b2097556177">memory allocation rate</strong> are configured, the policy detection period varies with the processing logic of each loop of the autoscaler add-on. Scale-out is triggered once the conditions are met, but it is constrained by other factors such as the cool-down interval and node pool status.</li></ul>
</div></div>
</div>
</li><li id="cce_10_0209__li1597332019284"><strong id="cce_10_0209__b113913177298">Periodic</strong>:<p id="cce_10_0209__p427705616284"><strong id="cce_10_0209__b49851527135515">Trigger Time</strong>: You can select a specific time point every day, every week, every month, or every year.</p>

30
docs/cce/umn/cce_10_0213.html
View File

@ -42,7 +42,7 @@
<tr id="cce_10_0213__row2907181302414"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.3.2.3.2.1.2.4.1.1 "><p id="cce_10_0213__p18907171317248">max-requests-inflight</p>
</td>
<td class="cellrowborder" valign="top" width="48%" headers="mcps1.3.3.2.3.2.1.2.4.1.2 "><p id="cce_10_0213__p390717131244">Maximum number of concurrent non-mutating requests. When the value of this parameter is exceeded, the server rejects requests.</p>
<p id="cce_10_0213__p169071513192417">The value <strong id="cce_10_0213__b572680712">0</strong> indicates no limitation. This parameter is related to the cluster scale. You are advised not to change the value.</p>
<p id="cce_10_0213__p169071513192417">The value <strong id="cce_10_0213__b624706611">0</strong> indicates no limitation. This parameter is related to the cluster scale. You are advised not to change the value.</p>
</td>
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.3.2.3.2.1.2.4.1.3 "><p id="cce_10_0213__p849913017407">Manual configuration is no longer supported since cluster v1.21. The value is automatically specified based on the cluster scale.</p>
<ul id="cce_10_0213__ul1499163013407"><li id="cce_10_0213__li104999309408"><strong id="cce_10_0213__b19493144511246">400</strong> for clusters with 50 or 200 nodes</li><li id="cce_10_0213__li1549913308409"><strong id="cce_10_0213__b1733775131015">1000</strong> for clusters with 1,000 nodes</li><li id="cce_10_0213__li8499230174010"><strong id="cce_10_0213__b0469348172411">2000</strong> for clusters with 2,000 nodes</li></ul>
@ -59,6 +59,18 @@
<p id="cce_10_0213__p189071413132419">Max &lt; 32768</p>
</td>
</tr>
<tr id="cce_10_0213__row1289763717386"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.3.2.3.2.1.2.4.1.1 "><p id="cce_10_0213__p14897537133818">request-timeout</p>
</td>
<td class="cellrowborder" valign="top" width="48%" headers="mcps1.3.3.2.3.2.1.2.4.1.2 "><p id="cce_10_0213__p3897113763811">Default request timeout interval of kube-apiserver. Exercise caution when changing the value of this parameter. Ensure that the changed value is proper to prevent frequent API timeout or other errors.</p>
<p id="cce_10_0213__p0172192315217">This parameter is supported only by clusters of v1.19.16-r30, v1.21.10-r10, v1.23.8-r10, v1.25.3-r10, and later versions.</p>
</td>
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.3.2.3.2.1.2.4.1.3 "><p id="cce_10_0213__p88971437163815">Default:</p>
<p id="cce_10_0213__p9311843154214">1m0s</p>
<p id="cce_10_0213__p16769184025116">Value range:</p>
<p id="cce_10_0213__p06431841115116">Min ≥ 1s</p>
<p id="cce_10_0213__p19671104912514">Max ≤ 1 hour</p>
</td>
</tr>
<tr id="cce_10_0213__row17903726114212"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.3.2.3.2.1.2.4.1.1 "><p id="cce_10_0213__p20903726144217">support-overload</p>
</td>
<td class="cellrowborder" valign="top" width="48%" headers="mcps1.3.3.2.3.2.1.2.4.1.2 "><p id="cce_10_0213__p17903112624220">Cluster overload control. If enabled, concurrent requests are dynamically controlled based on the resource pressure of master nodes to keep them and the cluster available.</p>
@ -93,6 +105,14 @@
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.3.2.3.2.2.2.4.1.3 "><ul id="cce_10_0213__ul10944115410176"><li id="cce_10_0213__li9944954101710">If the number of nodes in a cluster is less than 1000, the default value is <strong id="cce_10_0213__b2577132320188">100</strong>.</li><li id="cce_10_0213__li09441354111715">If a cluster contains 1000 or more nodes, the default value is <strong id="cce_10_0213__b1223517424188">200</strong>.</li></ul>
</td>
</tr>
<tr id="cce_10_0213__row51731335114"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.3.2.3.2.2.2.4.1.1 "><p id="cce_10_0213__p9173173341118">enable-gpu-share</p>
</td>
<td class="cellrowborder" valign="top" width="48%" headers="mcps1.3.3.2.3.2.2.2.4.1.2 "><p id="cce_10_0213__p87441819102418">Whether to enable GPU sharing. This parameter is supported only by clusters of v1.23.7-r10, v1.25.3-r0, and later.</p>
<ul id="cce_10_0213__ul1452133715442"><li id="cce_10_0213__li1645283717441">When disabled, ensure that pods in the cluster do not use the shared GPU (that is, the annotation of <strong id="cce_10_0213__b31355414576">cce.io/gpu-decision</strong> does not exist in pods).</li><li id="cce_10_0213__li19671939164413">When enabled, ensure that the annotation of <strong id="cce_10_0213__b19527172510579">cce.io/gpu-decision</strong> exists in pods that use GPU resources in the cluster.</li></ul>
</td>
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.3.2.3.2.2.2.4.1.3 "><p id="cce_10_0213__p1417316338116">Default: <strong id="cce_10_0213__b118226595819">true</strong></p>
</td>
</tr>
</tbody>
</table>
</div>
@ -213,6 +233,14 @@
<td class="cellrowborder" valign="top" width="30.693069306930692%" headers="mcps1.3.3.2.3.2.3.2.4.1.3 "><p id="cce_10_0213__p14999154912253">Default: 1000</p>
</td>
</tr>
<tr id="cce_10_0213__row116881253144616"><td class="cellrowborder" valign="top" width="21.782178217821784%" headers="mcps1.3.3.2.3.2.3.2.4.1.1 "><p id="cce_10_0213__p10688145311460">concurrent-horizontal-pod-autoscaler-syncs</p>
</td>
<td class="cellrowborder" valign="top" width="47.524752475247524%" headers="mcps1.3.3.2.3.2.3.2.4.1.2 "><p id="cce_10_0213__p20476132019484">Number of HPA auto scaling requests that can be concurrently processed. This parameter is available only in clusters of v1.27 or later.</p>
<p id="cce_10_0213__p1688175354612">The maximum value is <strong id="cce_10_0213__b9817141202616">50</strong> and the minimum value is <strong id="cce_10_0213__b11818131232617">1</strong>.</p>
</td>
<td class="cellrowborder" valign="top" width="30.693069306930692%" headers="mcps1.3.3.2.3.2.3.2.4.1.3 "><p id="cce_10_0213__p106884536469">Default: 5</p>
</td>
</tr>
</tbody>
</table>
</div>

50
docs/cce/umn/cce_10_0216.html
View File

File diff suppressed because it is too large Load Diff

5
docs/cce/umn/cce_10_0251.html
View File

@ -10,7 +10,8 @@
<p id="cce_10_0251__p6788462284">Dedicated load balancers must support HTTP or HTTPS and the network type must support private networks.</p>
<div class="p" id="cce_10_0251__p17322141651718">The CCE console supports automatic creation of load balancers. Select <strong id="cce_10_0251__b148521412611127">Auto create</strong> from the drop-down list box and configure the following parameters:<ul id="cce_10_0251__en-us_topic_0000001583656029_ul1198623291819"><li id="cce_10_0251__en-us_topic_0000001583656029_li4186123618226"><strong id="cce_10_0251__b139504595911127">Instance Name</strong>: Enter a load balancer name.</li><li id="cce_10_0251__en-us_topic_0000001583656029_li199871232141811"><strong id="cce_10_0251__b80613900411127">Public Access</strong>: If enabled, an EIP with 5 Mbit/s bandwidth will be created. </li><li id="cce_10_0251__en-us_topic_0000001583656029_li1543101361919"><strong id="cce_10_0251__b1799123274319">Subnet</strong>, <strong id="cce_10_0251__b999113321433">AZ</strong>, and <strong id="cce_10_0251__b7992123274318">Specifications</strong> (available only for dedicated load balancers): Configure the subnet AZ, and specifications. Only HTTP- or HTTPS-compliant dedicated load balancers can be automatically created.</li></ul>
</div>
</li><li id="cce_10_0251__li6851318392"><strong id="cce_10_0251__b1624620012154">Listener</strong>: Ingress configures a listener for the load balancer, which listens to requests from the load balancer and distributes traffic. After the configuration is complete, a listener is created on the load balancer. The default listener name is <em id="cce_10_0251__i12144307313">k8s__&lt;Protocol type&gt;_&lt;Port number&gt;</em>, for example, <em id="cce_10_0251__i1453831916301">k8s_HTTP_80</em>.<ul id="cce_10_0251__ul98515181097"><li id="cce_10_0251__li128514181093"><strong id="cce_10_0251__b121551828142814">External Protocol</strong>: <strong id="cce_10_0251__b1016142862813">HTTP</strong> and <strong id="cce_10_0251__b016102822819">HTTPS</strong> are available.</li><li id="cce_10_0251__li128531815910"><strong id="cce_10_0251__b614751917275">External Port</strong>: Port number that is open to the ELB service address. The port number can be specified randomly.</li><li id="cce_10_0251__li17853181895"><strong id="cce_10_0251__b81461344202720">Server Certificate</strong>: When an HTTPS listener is created for a load balancer, bind a certificate to the load balancer to support encrypted authentication for HTTPS data transmission.<div class="note" id="cce_10_0251__note1381944192911"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0251__p5381104492915">If there is already an HTTPS ingress for the chosen port on the load balancer, the certificate of the new HTTPS ingress must be the same as the certificate of the existing ingress. This means that a listener has only one certificate. If two certificates, each with a different ingress, are added to the same listener of the same load balancer, only the certificate added earliest takes effect on the load balancer.</p>
</li><li id="cce_10_0251__li6851318392"><a name="cce_10_0251__li6851318392"></a><a name="li6851318392"></a><strong id="cce_10_0251__b1624620012154">Listener</strong>: Ingress configures a listener for the load balancer, which listens to requests from the load balancer and distributes traffic. After the configuration is complete, a listener is created on the load balancer. The default listener name is <em id="cce_10_0251__i12144307313">k8s__&lt;Protocol type&gt;_&lt;Port number&gt;</em>, for example, <em id="cce_10_0251__i1453831916301">k8s_HTTP_80</em>.<ul id="cce_10_0251__ul98515181097"><li id="cce_10_0251__li128514181093"><strong id="cce_10_0251__b121551828142814">External Protocol</strong>: <strong id="cce_10_0251__b1016142862813">HTTP</strong> and <strong id="cce_10_0251__b016102822819">HTTPS</strong> are available.</li><li id="cce_10_0251__li128531815910"><strong id="cce_10_0251__b614751917275">External Port</strong>: Port number that is open to the ELB service address. The port number can be specified randomly.</li><li id="cce_10_0251__li118464019253"><strong id="cce_10_0251__b12943103073017">Certificate Source</strong>: TLS secret and ELB server certificate are supported.</li><li id="cce_10_0251__li17853181895"><strong id="cce_10_0251__b81461344202720">Server Certificate</strong>: When an HTTPS listener is created for a load balancer, bind a certificate to the load balancer to support encrypted authentication for HTTPS data transmission.<ul id="cce_10_0251__ul235654512294"><li id="cce_10_0251__li9565398277"><strong id="cce_10_0251__b1349763618306">TLS secret</strong>: For details about how to create a secret certificate, see <a href="cce_10_0153.html">Creating a Secret</a>.</li><li id="cce_10_0251__li835644511298"><strong id="cce_10_0251__b57551495301">ELB server certificate</strong>: Use the certificate created in the ELB service.</li></ul>
<div class="note" id="cce_10_0251__note1381944192911"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0251__p5381104492915">If there is already an HTTPS ingress for the chosen port on the load balancer, the certificate of the new HTTPS ingress must be the same as the certificate of the existing ingress. This means that a listener has only one certificate. If two certificates, each with a different ingress, are added to the same listener of the same load balancer, only the certificate added earliest takes effect on the load balancer.</p>
</div></div>
</li><li id="cce_10_0251__li7651155094013"><strong id="cce_10_0251__b514020733120">SNI</strong>: Server Name Indication (SNI) is an extended protocol of TLS. It allows multiple TLS-based access domain names to be provided for external systems using the same IP address and port. Different domain names can use different security certificates. After SNI is enabled, the client is allowed to submit the requested domain name when initiating a TLS handshake request. After receiving the TLS request, the load balancer searches for the certificate based on the domain name in the request. If the certificate corresponding to the domain name is found, the load balancer returns the certificate for authorization. Otherwise, the default certificate (server certificate) is returned for authorization.<div class="note" id="cce_10_0251__note59161057134120"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0251__ul341785816517"><li id="cce_10_0251__li1541715805115">The <strong id="cce_10_0251__b17512414311">SNI</strong> option is available only when <strong id="cce_10_0251__b77525411312">HTTPS</strong> is selected.</li></ul>
<ul id="cce_10_0251__ul2041716583512"><li id="cce_10_0251__li541725835112">This function is supported only for clusters of v1.15.11 and later.</li><li id="cce_10_0251__li1265688165219">Specify the domain name for the SNI certificate. Only one domain name can be specified for each certificate. Wildcard-domain certificates are supported.</li></ul>
@ -18,6 +19,8 @@
</li><li id="cce_10_0251__li58516183919"><strong id="cce_10_0251__b1962254816312">Security Policy</strong>: combinations of different TLS versions and supported cipher suites available to HTTPS listeners.<p id="cce_10_0251__p15856189913">For details about security policies, see ELB User Guide.</p>
<div class="note" id="cce_10_0251__note885111811917"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0251__ul6851018492"><li id="cce_10_0251__li15851118697"><strong id="cce_10_0251__b145331732163211">Security Policy</strong> is available only when <strong id="cce_10_0251__b7534173216327">HTTPS</strong> is selected.</li><li id="cce_10_0251__li285171815918">This function is supported only for clusters of v1.17.9 and later.</li></ul>
</div></div>
</li><li id="cce_10_0251__li03351122552"><strong id="cce_10_0251__b1594853416493">Backend Protocol</strong><p id="cce_10_0251__p53133720554">When <a href="#cce_10_0251__li6851318392">Listener</a> uses HTTP protocols, only <strong id="cce_10_0251__b1711814563211">HTTP</strong> can be selected.</p>
<p id="cce_10_0251__p5316376559">When <a href="#cce_10_0251__li6851318392">Listener</a> uses HTTPS protocols, you can select <strong id="cce_10_0251__b01051193415">HTTP</strong> or <strong id="cce_10_0251__b29128535345">HTTPS</strong>.</p>
</li></ul>
</li><li id="cce_10_0251__li78601812913"><strong id="cce_10_0251__b186201409327">Forwarding Policy</strong>: When the access address of a request matches the forwarding policy (a forwarding policy consists of a domain name and URL, for example, <em id="cce_10_0251__i15296930104219">10.XXX.XXX.XXX:80</em><em id="cce_10_0251__i182961130144218">/helloworld</em>), the request is forwarded to the corresponding Service for processing. You can click <span><img id="cce_10_0251__image72611039165513" src="en-us_image_0000001647417544.png"></span> to add multiple forwarding policies.<ul id="cce_10_0251__ul486131819915"><li id="cce_10_0251__li3858186912"><strong id="cce_10_0251__b17856971330">Domain Name</strong>: actual domain name. Ensure that the domain name has been registered and archived. Once a domain name rule is configured, you must use the domain name for access.</li><li id="cce_10_0251__li2086218897">URL Matching Rule<ul id="cce_10_0251__ul5861518393"><li id="cce_10_0251__li168511815919"><strong id="cce_10_0251__b2029617457339">Prefix match</strong>: If the URL is set to <strong id="cce_10_0251__b1329618455339">/healthz</strong>, the URL that meets the prefix can be accessed. For example, <strong id="cce_10_0251__b16184165019335">/healthz/v1</strong> and <strong id="cce_10_0251__b118495019332">/healthz/v2</strong>.</li><li id="cce_10_0251__li14861818798"><strong id="cce_10_0251__b19144235496">Exact match</strong>: The URL can be accessed only when it is fully matched. For example, if the URL is set to <strong id="cce_10_0251__b18474185653313">/healthz</strong>, only /healthz can be accessed.</li><li id="cce_10_0251__li108612185917"><strong id="cce_10_0251__b365113814616">Regular expression</strong>: The URL is matched based on the regular expression. For example, if the regular expression is <strong id="cce_10_0251__b88616181699">/[A-Za-z0-9_.-]+/test</strong>, all URLs that comply with this rule can be accessed, for example, <strong id="cce_10_0251__b340611323410">/abcA9/test</strong> and <strong id="cce_10_0251__b1940610303419">/v1-Ab/test</strong>. Two regular expression standards are supported: POSIX and Perl.</li></ul>
</li><li id="cce_10_0251__li188619181495"><strong id="cce_10_0251__b1031418943419">URL</strong>: access path to be registered, for example, <strong id="cce_10_0251__b731413963417">/healthz</strong>.<div class="note" id="cce_10_0251__note17563145615169"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0251__p103613018260">The access path added here must exist in the backend application. Otherwise, the forwarding fails.</p>

16
docs/cce/umn/cce_10_0277.html
View File

@ -11,42 +11,42 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0277__row729811268202"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p329812632011"><a href="cce_10_0129.html">coredns (System Resource Add-on, Mandatory)</a></p>
<tbody><tr id="cce_10_0277__row729811268202"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p329812632011"><a href="cce_10_0129.html">CoreDNS</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p12981726192017"><span class="keyword" id="cce_10_0277__keyword115741854194216">CoreDNS</span> is a <span class="keyword" id="cce_10_0277__keyword131672816501">DNS server</span> that provides <span class="keyword" id="cce_10_0277__keyword17138202585015">domain name resolution</span> for <span class="keyword" id="cce_10_0277__keyword1746722115501">Kubernetes</span> clusters through chain plug-ins.</p>
</td>
</tr>
<tr id="cce_10_0277__row1729822612200"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p929842682017"><a href="cce_10_0127.html">storage-driver(Flexvolume, Deprecated)</a></p>
<tr id="cce_10_0277__row1729822612200"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p929842682017"><a href="cce_10_0127.html">CCE Container Storage (FlexVolume)</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p0298122602020">storage-driver is a FlexVolume driver used to support IaaS storage services such as EVS, SFS, and OBS.</p>
</td>
</tr>
<tr id="cce_10_0277__row1129818265202"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p172981226192012"><a href="cce_10_0066.html">everest (System Resource Add-on, Mandatory)</a></p>
<tr id="cce_10_0277__row1129818265202"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p172981226192012"><a href="cce_10_0066.html">CCE Container Storage (Everest)</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p17298172618205">everest is a cloud native container storage system, which enables clusters of Kubernetes v1.15.6 or later to use cloud storage through the Container Storage Interface (CSI).</p>
</td>
</tr>
<tr id="cce_10_0277__row82981726162015"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p19298172662014"><a href="cce_10_0132.html">npd</a></p>
<tr id="cce_10_0277__row82981726162015"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p19298172662014"><a href="cce_10_0132.html">CCE Node Problem Detector</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p0298202672017">node-problem-detector (npd for short) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. The npd add-on can run as a DaemonSet or a daemon.</p>
</td>
</tr>
<tr id="cce_10_0277__row517991010214"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p818051013218"><a href="cce_10_0154.html">autoscaler</a></p>
<tr id="cce_10_0277__row517991010214"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p818051013218"><a href="cce_10_0154.html">CCE Cluster Autoscaler</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p33062213567">The autoscaler add-on resizes a cluster based on pod scheduling status and resource usage.</p>
</td>
</tr>
<tr id="cce_10_0277__row718031012117"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p1718012101214"><a href="cce_10_0205.html">metrics-server</a></p>
<tr id="cce_10_0277__row718031012117"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p1718012101214"><a href="cce_10_0205.html">Kubernetes Metrics Server</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p8803328425">metrics-server is an aggregator for monitoring data of core cluster resources.</p>
</td>
</tr>
<tr id="cce_10_0277__row2256219162517"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p182565193254"><a href="cce_10_0141.html">gpu-device-plugin (formerly gpu-beta)</a></p>
<tr id="cce_10_0277__row2256219162517"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p182565193254"><a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p12273103844718">gpu-device-plugin is a device management add-on that supports GPUs in containers. It supports only NVIDIA drivers.</p>
</td>
</tr>
<tr id="cce_10_0277__row1525615191253"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p1725617192257"><a href="cce_10_0193.html">volcano</a></p>
<tr id="cce_10_0277__row1525615191253"><td class="cellrowborder" valign="top" width="23.34%" headers="mcps1.3.3.2.3.1.1 "><p id="cce_10_0277__p1725617192257"><a href="cce_10_0193.html">Volcano Scheduler</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.66%" headers="mcps1.3.3.2.3.1.2 "><p id="cce_10_0277__p7256161917253">Volcano provides general-purpose, high-performance computing capabilities, such as job scheduling, heterogeneous chip management, and job running management, serving end users through computing frameworks for different industries, such as AI, big data, gene sequencing, and rendering.</p>
</td>

Some files were not shown because too many files have changed in this diff Show More