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

CCE UMN update -20241024 Version

Browse Source 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
This commit is contained in:
Dong, Qiu Jian 2024-11-27 11:46:27 +00:00 committed by zuul
parent 18611c92c5
commit a405f3b3c5
121 changed files with 3549 additions and 1930 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

File diff suppressed because it is too large Load Diff

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

File diff suppressed because it is too large Load Diff

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

@ -8,7 +8,23 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_01_0300__row196562925719"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1565620945712">2024-08-30</p>
<tbody><tr id="cce_01_0300__row12382285577"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p6239182811572">2024-11-25</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p2023952875710">Update:</p>
<p id="cce_01_0300__p740273811578">Updated the <strong id="cce_01_0300__b1132371515018">Specifications</strong> field in <a href="cce_10_0363.html">Creating a Node</a> and <a href="cce_10_0012.html">Creating a Node Pool</a>.</p>
</td>
</tr>
<tr id="cce_01_0300__row094535514106"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p19946855181017">2024-10-30</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p91722346115">Add:</p>
<p id="cce_01_0300__p15897172622212">Added <a href="cce_10_0034.html">NGINX Ingress Controller</a>.</p>
<p id="cce_01_0300__p20417102112418">Added <a href="cce_10_0692.html">Nginx Ingresses</a>.</p>
<p id="cce_01_0300__p1606529121812">Added <a href="cce_10_0508.html">nginx-ingress Upgrade</a>.</p>
<p id="cce_01_0300__p89468554106">Update:</p>
<ul id="cce_01_0300__ul13617102410314"><li id="cce_01_0300__li18626356833">Supported the NGINX Ingress Controller add-on. Updated <a href="cce_10_0277.html">Overview</a>, <a href="cce_bulletin_0061.html">CCE Console Upgrade</a>.</li><li id="cce_01_0300__li12162133812224">Supported Nginx Ingress. Updated <a href="cce_10_0094.html">Overview</a>, <a href="cce_10_0251.html">Creating a LoadBalancer Ingress on the Console</a>, <a href="cce_10_0695.html">Configuring a LoadBalancer Ingress Using Annotations</a>.</li><li id="cce_01_0300__li146172024237">The EVS disk type supports <strong id="cce_01_0300__b1047922821711">General Purpose SSD</strong> and <strong id="cce_01_0300__b18374164641717">Extreme SSD</strong>. Updated <a href="cce_10_0613.html">Overview</a>, <a href="cce_10_0614.html">Using an Existing EVS Disk Through a Static PV</a>, <a href="cce_10_0615.html">Using an EVS Disk Through a Dynamic PV</a>, <a href="cce_10_0616.html">Dynamically Mounting an EVS Disk to a StatefulSet</a>.</li><li id="cce_01_0300__li22671214175220">Updated <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_01_0300__li18397152611527">Updated <a href="cce_10_0012.html">Creating a Node Pool</a>.</li><li id="cce_01_0300__li147530281527">Updated <a href="cce_bestpractice_0320.html">Configuration Suggestions on CCE Secret Security</a>.</li></ul>
</td>
</tr>
<tr id="cce_01_0300__row196562925719"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1565620945712">2024-08-30</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p975316296574">Update:</p>
<ul id="cce_01_0300__ul13776134813571"><li id="cce_01_0300__li17522205165713">Updated <a href="cce_10_0406.html">Cloud Native Cluster Monitoring</a>.</li><li id="cce_01_0300__li913815612582">Updated <a href="cce_10_0789.html">Load-aware Scheduling</a>.</li></ul>

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

@ -1,7 +1,8 @@
<a name="cce_10_0004"></a><a name="cce_10_0004"></a>
<h1 class="topictitle1">Managing Node Labels</h1>
<div id="body1523168310157"><div class="section" id="cce_10_0004__section825504204814"><h4 class="sectiontitle">Node Label Usage Scenario</h4><p id="cce_10_0004__p780125519482">Node labels are mainly used in the following scenarios:</p>
<div id="body1523168310157"><p id="shortdesc139984301190">You can add different labels to nodes and define different attributes for labels. By using these <span class="keyword" id="keyword161492666714287">node labels</span>, you can quickly understand the characteristics of each node.</p>
<div class="section" id="cce_10_0004__section825504204814"><h4 class="sectiontitle">Node Label Usage Scenario</h4><p id="cce_10_0004__p780125519482">Node labels are mainly used in the following scenarios:</p>
<ul id="cce_10_0004__ul1269074720287"><li id="cce_10_0004__li1269054722816">Node management: Node labels are used to classify nodes.</li><li id="cce_10_0004__li13690184719287">Node affinity or anti-affinity for workloads: By adding labels to nodes, you can schedule pods to specific nodes through node affinity or prevent pods from being scheduled to specific nodes through node anti-affinity. For details, see <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</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>

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

@ -1,7 +1,8 @@
<a name="cce_10_0006"></a><a name="cce_10_0006"></a>
<h1 class="topictitle1">Overview</h1>
<div id="body1522665832344"><p id="cce_10_0006__p11116113204610">CCE provides Kubernetes-native container deployment and management and supports lifecycle management of container workloads, including creation, configuration, monitoring, auto scaling, upgrade, uninstall, service discovery, and load balancing.</p>
<div id="body1522665832344"><p id="shortdesc12779194282617">A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is an abstract model of a group of pods in Kubernetes. Workloads in Kubernetes are classified as <span class="keyword" id="keyword1293375712468">Deployments</span>, <span class="keyword" id="keyword1541920224714">StatefulSets</span>, <span class="keyword" id="keyword1273972479">DaemonSets</span>, <span class="keyword" id="keyword21491010164711">jobs</span>, and <span class="keyword" id="keyword19556171584711">cron jobs</span>.</p>
<p id="cce_10_0006__p11116113204610">CCE provides Kubernetes-native container deployment and management and supports lifecycle management of container workloads, including creation, configuration, monitoring, auto scaling, upgrade, uninstall, service discovery, and load balancing.</p>
<div class="section" id="cce_10_0006__section9645114684816"><h4 class="sectiontitle">Overview of Pod</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">A pod is the smallest and simplest unit in the Kubernetes object model that you create or deploy. A pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. Each pod has a separate IP address.</p>
<p id="cce_10_0006__en-us_topic_0254767870_p4629172611480">Pods can be used in either of the following ways:</p>
<ul id="cce_10_0006__en-us_topic_0254767870_ul062982617481"><li id="cce_10_0006__en-us_topic_0254767870_li1629172611482">A pod runs only one container. This is the most common usage of pods in Kubernetes. You can consider a pod as a container, but Kubernetes directly manages pods instead of containers.</li><li id="cce_10_0006__en-us_topic_0254767870_li1962932615480">A pod runs multiple containers that need to be tightly coupled. In this scenario, a pod contains a main container and several sidecar containers, as shown in <a href="#cce_10_0006__en-us_topic_0254767870_fig347141918551">Figure 1</a>. For example, the main container is a web server that provides file services from a fixed directory, and sidecar containers periodically download files to this fixed directory.<div class="fignone" id="cce_10_0006__en-us_topic_0254767870_fig347141918551"><a name="cce_10_0006__en-us_topic_0254767870_fig347141918551"></a><a name="en-us_topic_0254767870_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>Pod running multiple containers</span><br><span><img id="cce_10_0006__en-us_topic_0254767870_image1835215316361" src="en-us_image_0258392378.png"></span></div>

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

@ -16,11 +16,6 @@
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="cce_10_0012__p17949173819260">Name of a node pool. By default, the name is in the format of <em id="cce_10_0012__i149877146013">Cluster name</em>-nodepool-<em id="cce_10_0012__i19923141302">Random number</em>. If you do not want to use the default name format, you can customize the name.</p>
</td>
</tr>
<tr id="cce_10_0012__row17944198172620"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="cce_10_0012__p189442818264">Expected Initial Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="cce_10_0012__p851534252620">Number of nodes to be created in this node pool. A maximum of 50 nodes that can be created at a time.</p>
</td>
</tr>
</tbody>
</table>
</div>
@ -43,7 +38,7 @@
</tr>
<tr id="cce_10_0012__row156691178589"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0012__p1669177185817">Specifications</p>
</td>
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0012__p156695715814">Select a node flavor based on service requirements. The available node flavors vary depending on regions or AZs. For details, see the CCE console. <div class="note" id="cce_10_0012__note11800133115339"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__ul58111778349"><li id="cce_10_0012__li646111116412">If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.</li><li id="cce_10_0012__li371317328359">A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.</li><li id="cce_10_0012__li170272454517">Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.</li><li id="cce_10_0012__li1755415220815">After a node pool is created, the flavors of existing nodes cannot be deleted.</li></ul>
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0012__p156695715814">Select a node flavor based on service requirements. The available node flavors vary depending on regions or AZs. For details, see the CCE console. For the supported node flavors, see <a href="https://docs.otc.t-systems.com/en-us/api2/cce/cce_02_0368.html" target="_blank" rel="noopener noreferrer">Node Flavor Description</a>.<div class="note" id="cce_10_0012__note11800133115339"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__ul58111778349"><li id="cce_10_0012__li646111116412">If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.</li><li id="cce_10_0012__li371317328359">A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.</li><li id="cce_10_0012__li170272454517">Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.</li><li id="cce_10_0012__li1755415220815">After a node pool is created, the flavors of existing nodes cannot be deleted.</li></ul>
</div></div>
</div>
</td>
@ -95,10 +90,10 @@
</div></div>
<p id="cce_10_0012__cce_10_0363_p20408122884010"><strong id="cce_10_0012__cce_10_0363_b168590318488">Advanced Settings</strong></p>
<p id="cce_10_0012__cce_10_0363_p3752312011">Expand the area and configure the following parameters:</p>
<ul id="cce_10_0012__cce_10_0363_ul197721145155911"><li id="cce_10_0012__cce_10_0363_li12110343014"><strong id="cce_10_0012__cce_10_0363_b158191435122117">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</li><li id="cce_10_0012__cce_10_0363_li1095641711169"><strong id="cce_10_0012__cce_10_0363_b8672113734817">Data Disk Encryption</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. BMS nodes do not support data disk encryption that is available only in certain regions. For details, see the console.<ul id="cce_10_0012__cce_10_0363_ul1924511512168"><li id="cce_10_0012__cce_10_0363_li4245181561611"><strong id="cce_10_0012__cce_10_0363_b1573516333164">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_li172751284225">If you select <strong id="cce_10_0012__cce_10_0363_b16761923958">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b1267610231951">Data Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b76761231051">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li><li id="cce_10_0012__cce_10_0363_li22751687228">If you select <strong id="cce_10_0012__cce_10_0363_b79545611132">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b129547621311">Data Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
<ul id="cce_10_0012__cce_10_0363_ul197721145155911"><li id="cce_10_0012__cce_10_0363_li12110343014"><strong id="cce_10_0012__cce_10_0363_b158191435122117">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</li><li id="cce_10_0012__cce_10_0363_li1095641711169"><strong id="cce_10_0012__cce_10_0363_b8672113734817">Data Disk Encryption</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <ul id="cce_10_0012__cce_10_0363_ul1924511512168"><li id="cce_10_0012__cce_10_0363_li4245181561611"><strong id="cce_10_0012__cce_10_0363_b1573516333164">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_li172751284225">If you select <strong id="cce_10_0012__cce_10_0363_b16761923958">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b1267610231951">Data Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b76761231051">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li><li id="cce_10_0012__cce_10_0363_li22751687228">If you select <strong id="cce_10_0012__cce_10_0363_b79545611132">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b129547621311">Data Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
</li></ul>
<p id="cce_10_0012__cce_10_0363_p1391618153118"><strong id="cce_10_0012__cce_10_0363_b698132517473">Adding data disks</strong></p>
<p id="cce_10_0012__cce_10_0363_p45741654112612">A maximum of 16 data disks can be attached to an ECS and 10 to a BMS. By default, a raw disk is created without any processing. You can also click <strong id="cce_10_0012__cce_10_0363_b1353214375715">Expand</strong> and select any of the following options:</p>
<p id="cce_10_0012__cce_10_0363_p45741654112612">A maximum of 16 data disks can be attached to an ECS. By default, a raw disk is created without any processing. You can also click <strong id="cce_10_0012__cce_10_0363_b1353214375715">Expand</strong> and select any of the following options:</p>
<ul id="cce_10_0012__cce_10_0363_ul198131191414"><li id="cce_10_0012__cce_10_0363_li1681481912112"><strong id="cce_10_0012__cce_10_0363_b650951155715">Default</strong>: By default, a raw disk is created without any processing.</li><li id="cce_10_0012__cce_10_0363_li108141119311"><strong id="cce_10_0012__cce_10_0363_b1791414137595">Mount Disk</strong>: The data disk is attached to a specified directory.</li><li id="cce_10_0012__cce_10_0363_li18141219612"><strong id="cce_10_0012__cce_10_0363_b12108139105910">Use as PV</strong>: applicable when there is a high performance requirement on PVs. The <strong id="cce_10_0012__cce_10_0363_b57411338611">node.kubernetes.io/local-storage-persistent</strong> label is added to the node with PV configured. The value is <strong id="cce_10_0012__cce_10_0363_b0496143919615">linear</strong> or <strong id="cce_10_0012__cce_10_0363_b2800194113618">striped</strong>.</li><li id="cce_10_0012__cce_10_0363_li17814619119"><strong id="cce_10_0012__cce_10_0363_b154131531010">Use as ephemeral volume</strong>: applicable when there is a high performance requirement on emptyDir.</li></ul>
<div class="note" id="cce_10_0012__cce_10_0363_note18158650124116"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__cce_10_0363_ul1242510314572"><li id="cce_10_0012__cce_10_0363_li0425203125719">Local PVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 2.1.23 or later. Version 2.1.23 or later is recommended.</li><li id="cce_10_0012__cce_10_0363_li64131222577">Local EVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 1.2.29 or later.</li></ul>
</div></div>
@ -138,7 +133,7 @@
</td>
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.8.1.2.3.1.2 "><p id="cce_10_0012__p1714618560184">Security group used by the nodes created in the node pool. A maximum of five security groups can be selected.</p>
<p id="cce_10_0012__p227516318263">When a cluster is created, a node security group named <strong id="cce_10_0012__b878895718814">{</strong><strong id="cce_10_0012__b16788135714813"><em id="cce_10_0012__i1625212482089">Cluster name</em></strong><strong id="cce_10_0012__b578815576810">}-cce-node-{</strong><strong id="cce_10_0012__b27887573817"><em id="cce_10_0012__i1446185417812">Random ID</em></strong><strong id="cce_10_0012__b20788257585">}</strong> is created and used by default.</p>
<p id="cce_10_0012__p124938720207">Traffic needs to pass through certain ports in the node security group to ensure node communications. Ensure that you have enabled these ports if you select another security group.</p>
<p id="cce_10_0012__p124938720207">Traffic needs to pass through certain ports in the node security group to ensure node communications. Ensure that you have enabled these ports if you select another security group. For details, see <a href="cce_faq_00265.html">Configuring Cluster Security Group Rules</a>.</p>
<div class="note" id="cce_10_0012__note3612182014171"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0012__p1161542001715">After a node pool is created, its associated security group cannot be modified.</p>
</div></div>
</td>

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

@ -1,7 +1,8 @@
<a name="cce_10_0015"></a><a name="cce_10_0015"></a>
<h1 class="topictitle1">Using a ConfigMap</h1>
<div id="body1523236302435"><ul id="cce_10_0015__ul784252913353"><li id="cce_10_0015__li0842229163518"><a href="#cce_10_0015__section1737733192813">Configuring Environment Variables of a Workload</a></li><li id="cce_10_0015__li56474053519"><a href="#cce_10_0015__section17930105710189">Configuring Command Line Parameters</a></li><li id="cce_10_0015__li1855144412358"><a href="#cce_10_0015__section1490261161916">Mounting a ConfigMap to the Workload Data Volume</a></li></ul>
<div id="body1523236302435"><p id="shortdesc15876143794213">After a ConfigMap is created, it can be used in three workload scenarios: <span class="keyword" id="keyword213237704511448">environment variables</span>, <span class="keyword" id="keyword1458163128114411">command line parameters</span>, and <span class="keyword" id="keyword538320223114413">data volumes</span>.</p>
<ul id="cce_10_0015__ul784252913353"><li id="cce_10_0015__li0842229163518"><a href="#cce_10_0015__section1737733192813">Configuring Environment Variables of a Workload</a></li><li id="cce_10_0015__li56474053519"><a href="#cce_10_0015__section17930105710189">Configuring Command Line Parameters</a></li><li id="cce_10_0015__li1855144412358"><a href="#cce_10_0015__section1490261161916">Mounting a ConfigMap to the Workload Data Volume</a></li></ul>
<p id="cce_10_0015__p1119921953413">The following example shows how to use a ConfigMap.</p>
<pre class="screen" id="cce_10_0015__screen1245419316221">apiVersion: v1
kind: ConfigMap

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

@ -1,7 +1,8 @@
<a name="cce_10_0016"></a><a name="cce_10_0016"></a>
<h1 class="topictitle1">Using a Secret</h1>
<div id="body1523236302435"><div class="notice" id="cce_10_0016__note13556115019429"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0016__p39918120437">Do not perform any operation on the following secrets. For details, see <a href="cce_10_0388.html">Cluster Secrets</a>.</p>
<div id="body1523236302435"><p id="shortdesc11673121711466">After secrets are created, they can be mounted as <span class="keyword" id="keyword37518294516">data volumes</span> or be exposed as <span class="keyword" id="keyword19590446124414">environment variables</span> to be used by a container in a pod.</p>
<div class="notice" id="cce_10_0016__note13556115019429"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0016__p39918120437">Do not perform any operation on the following secrets. For details, see <a href="cce_10_0388.html">Cluster Secrets</a>.</p>
<ul id="cce_10_0016__ul13678122414717"><li id="cce_10_0016__li19678132424718">Do not operate secrets under kube-system.</li><li id="cce_10_0016__li206781324204718">Do not operate default-secret and paas.elb in any of the namespaces. The default-secret is used to pull the private image of SWR, and the paas.elb is used to connect the service in the namespace to the ELB service.</li></ul>
</div></div>
<ul id="cce_10_0016__ul784252913353"><li id="cce_10_0016__li56474053519"><a href="#cce_10_0016__section207271352141216">Configuring Environment Variables of a Workload</a></li><li id="cce_10_0016__li0842229163518"><a href="#cce_10_0016__section472505211214">Configuring the Data Volume of a Workload</a></li></ul>

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

@ -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__keyword1772976139">Pod</span>.</p>
<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b1197707643">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b1247156547">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b1115375169">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b481519217">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__keyword794706769">Pod</span>.</p>
<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b1402185631">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b1868207742">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b1874430595">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b1735619381">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__b1930637705">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__b1701440828">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 already 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__b1467704559">.log</strong>, <strong id="cce_10_0018__b1015947165">.trace</strong>, and <strong id="cce_10_0018__b441913230">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b1440530493">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b358580375">.log</strong>, <strong id="cce_10_0018__b843315747">.trace</strong>, and <strong id="cce_10_0018__b436971263">.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__b2074831367">.log</strong>, <strong id="cce_10_0018__b1268946909">.trace</strong>, and <strong id="cce_10_0018__b1916570637">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b1348669150">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b1576016562">.log</strong>, <strong id="cce_10_0018__b1678875580">.trace</strong>, and <strong id="cce_10_0018__b515549583">.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 ICAgent is of v5.12.22 or later.</p>
</div></div>
@ -203,7 +203,7 @@ spec:
<div class="section" id="cce_10_0018__section25851847232"><h4 class="sectiontitle">Viewing Logs</h4><p id="cce_10_0018__p209669599247">After a log collection path is configured and the workload is created, the ICAgent collects log files from the configured path. The collection takes about 1 minute.</p>
<p id="cce_10_0018__p242194515304">After the log collection is complete, go to the workload details page and click <strong id="cce_10_0018__b13484541192818">Logs</strong> in the upper right corner to view logs.</p>
<p id="cce_10_0018__p32989282515">You can also view logs on the AOM console.</p>
<p id="cce_10_0018__p160613416815">You can also run the <strong id="cce_10_0018__b9741144192912">kubectl logs</strong> command to view the standard output of a container.</p>
<p id="cce_10_0018__p160613416815">You can also run the <strong id="cce_10_0018__b12443114301613">kubectl logs</strong> command to view the container stdout.</p>
<pre class="screen" id="cce_10_0018__screen1210248152712"># View logs of a specified pod.
kubectl logs &lt;pod_name&gt;
kubectl logs -f &lt;pod_name&gt; # Similar to <strong id="cce_10_0018__b34131514579">tail -f</strong>

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

@ -5,8 +5,8 @@
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by Cloud Trace Service</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Querying Real-Time Traces</a></strong><br>
Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the management console or open APIs as well as responses to the requests.</li>
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Viewing CTS Traces in the Trace List</a></strong><br>
</li>
</ul>

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

@ -1,7 +1,8 @@
<a name="cce_10_0025"></a><a name="cce_10_0025"></a>
<h1 class="topictitle1">CCE Operations Supported by Cloud Trace Service</h1>
<div id="body1525226397666">
<div id="body1525226397666"><p id="shortdesc11299535155610">Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the management console or open APIs as well as responses to the requests.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0025__table10122133613599" frame="border" border="1" rules="all"><caption><b>Table 1 </b>CCE Operations Supported by CTS</caption><thead align="left"><tr id="cce_10_0025__row1612243618593"><th align="left" class="cellrowborder" valign="top" width="28.37%" id="mcps1.4.1.2.4.1.1"><p id="cce_10_0025__p5122153665915">Operation</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="25.230000000000004%" id="mcps1.4.1.2.4.1.2"><p id="cce_10_0025__p11394135314515">Resource Type</p>

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

@ -1,20 +1,31 @@
<a name="cce_10_0026"></a><a name="cce_10_0026"></a>
<h1 class="topictitle1">Querying Real-Time Traces</h1>
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__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_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_0179639644_ul17577535194620"><li id="cce_10_0026__en-us_topic_0179639644_li201409184718"><a href="#cce_10_0026__en-us_topic_0179639644_section19271975203">Viewing Real-Time Traces in the Trace List</a></li></ul>
<h1 class="topictitle1">Viewing CTS Traces in the Trace List</h1>
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0179639644_p333055219577">After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.</p>
<div class="note" id="cce_10_0026__en-us_topic_0179639644_note1438715448188"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0026__en-us_topic_0179639644_p1138754410182">These operation records are retained for seven days on the CTS console and are automatically deleted upon expiration. Manual deletion is not supported.</p>
</div></div>
<p id="cce_10_0026__en-us_topic_0179639644_p3008599195238">This section describes how to query or export operation records of the last seven days on the CTS console.</p>
<ul id="cce_10_0026__en-us_topic_0179639644_ul17577535194620"><li id="cce_10_0026__en-us_topic_0179639644_li195771235174613"><a href="#cce_10_0026__en-us_topic_0179639644_section6300091795238">Viewing Real-Time Traces in the Trace List of the New Edition</a></li><li id="cce_10_0026__en-us_topic_0179639644_li201409184718"><a href="#cce_10_0026__en-us_topic_0179639644_section19271975203">Viewing Real-Time Traces in the Trace List of the Old Edition</a></li></ul>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><a name="cce_10_0026__en-us_topic_0179639644_section19271975203"></a><a name="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_0179639644_ol4845175152710"><li id="cce_10_0026__en-us_topic_0179639644_li791871844313">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0179639644_li79188188435">Click <span><img id="cce_10_0026__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_0179639644_b1810717138505">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b1310871313509">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0179639644_li591831894316">Choose <strong id="cce_10_0026__en-us_topic_0179639644_b09819412220">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0179639644_li6936134194312">Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>. The following filters are available:<div class="fignone" id="cce_10_0026__en-us_topic_0179639644_fig139361441134311"><a name="cce_10_0026__en-us_topic_0179639644_fig139361441134311"></a><a name="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_0179639644_image14936144112433" src="en-us_image_0000001744598325.png"></span></div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section17513919143614"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0026__en-us_topic_0179639644_ul10927192364611"><li id="cce_10_0026__en-us_topic_0179639644_li9927223134614">You can only query operation records of the last seven days on the CTS console. To store operation records for longer than seven days, you must configure transfer to OBS or Log Tank Service (LTS) so that you can view them in OBS buckets or LTS log groups.</li><li id="cce_10_0026__en-us_topic_0179639644_li8852101625020">After performing operations on the cloud, you can query management traces on the CTS console one minute later.</li></ul>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section6300091795238"><a name="cce_10_0026__en-us_topic_0179639644_section6300091795238"></a><a name="en-us_topic_0179639644_section6300091795238"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List of the New Edition</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol3001478295238"><li id="cce_10_0026__en-us_topic_0179639644_li3954991595238">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0179639644_li3694304795238">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image18230310103219" src="en-us_image_0000001187249376.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0179639644_b1248293451010">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b176581110111019">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0179639644_li4560416895238">Choose <strong id="cce_10_0026__en-us_topic_0179639644_b1548161231117">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0179639644_li877858395238">On the <strong id="cce_10_0026__en-us_topic_0179639644_b1537711461318">Trace List</strong> page, use advanced search to query traces. You can combine one or more filters.<ul class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_ul13105101342515"><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li470415162610"><strong id="cce_10_0026__en-us_topic_0179639644_b121811341812">Trace Name</strong>: Enter a trace name.</li><li id="cce_10_0026__en-us_topic_0179639644_li5845153914283"><strong id="cce_10_0026__en-us_topic_0179639644_b1868642096">Trace ID</strong>: Enter a trace ID.</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li121812712610"><strong id="cce_10_0026__en-us_topic_0179639644_b149256147919">Resource Name</strong>: Enter a resource name. If the cloud resource involved in the trace does not have a resource name or the corresponding API operation does not involve the resource name parameter, leave this field empty.</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li11791482268"><strong id="cce_10_0026__en-us_topic_0179639644_b08609468911">Resource ID</strong>: Enter a resource ID. Leave this field empty if the resource has no resource ID or if resource creation failed.</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li619185017272"><strong id="cce_10_0026__en-us_topic_0179639644_b280617118104">Trace Source</strong>: Select a cloud service name from the drop-down list.</li><li id="cce_10_0026__en-us_topic_0179639644_li18193203903417"><strong id="cce_10_0026__en-us_topic_0179639644_b13863421131010">Resource Type</strong>: Select a resource type from the drop-down list.</li><li id="cce_10_0026__en-us_topic_0179639644_li14105141392513"><strong id="cce_10_0026__en-us_topic_0179639644_b179165641114">Operator</strong>: Select one or more operators from the drop-down list.</li><li id="cce_10_0026__en-us_topic_0179639644_li110591317255"><strong id="cce_10_0026__en-us_topic_0179639644_b377193202212">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0179639644_b107818329223">normal</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b1378113272212">warning</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b2787327222">incident</strong>.<ul id="cce_10_0026__en-us_topic_0179639644_ul7141162215312"><li id="cce_10_0026__en-us_topic_0179639644_li145201024135111"><strong id="cce_10_0026__en-us_topic_0179639644_b143575532314">normal</strong>: The operation succeeded.</li><li id="cce_10_0026__en-us_topic_0179639644_li10846192555119"><strong id="cce_10_0026__en-us_topic_0179639644_b426712462235">warning</strong>: The operation failed.</li><li id="cce_10_0026__en-us_topic_0179639644_li19512310115116"><strong id="cce_10_0026__en-us_topic_0179639644_b1252219416241">incident</strong>: The operation caused a fault that is more serious than the operation failure, for example, causing other faults.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0179639644_li12161950321">Time range: Select <strong id="cce_10_0026__en-us_topic_0179639644_b1602115041017">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b46024507108">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b2060235013102">Last 1 week</strong>, or specify a custom time range within the last seven days.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0179639644_li17684227175818">On the <strong id="cce_10_0026__en-us_topic_0179639644_b1922182591118">Trace List</strong> page, you can also export and refresh the trace list, and customize columns to display.<ul id="cce_10_0026__en-us_topic_0179639644_ul171014569599"><li id="cce_10_0026__en-us_topic_0179639644_li68555243511">Enter any keyword in the search box and press <strong id="cce_10_0026__en-us_topic_0179639644_b2365948135712">Enter</strong> to filter desired traces.</li><li id="cce_10_0026__en-us_topic_0179639644_li13101185685914">Click <strong id="cce_10_0026__en-us_topic_0179639644_b18601848191112">Export</strong> to export all traces in the query result as an .xlsx file. The file can contain up to 5,000 records.</li><li id="cce_10_0026__en-us_topic_0179639644_li86171118016">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image1874712381601" src="en-us_image_0000001667734001.png"></span> to view the latest information about traces.</li><li id="cce_10_0026__en-us_topic_0179639644_li209831840119">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image564420481812" src="en-us_image_0000001619094530.png"></span> to customize the information to be displayed in the trace list. If <strong id="cce_10_0026__en-us_topic_0179639644_b67271845111312">Auto wrapping</strong> is enabled (<span><img id="cce_10_0026__en-us_topic_0179639644_image12727174571318" src="en-us_image_0000001667694873.png"></span>), excess text will move down to the next line; otherwise, the text will be truncated. By default, this function is disabled.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0179639644_li1714145242219">For details about key fields in the trace structure, see and section "Trace References" &gt; "Example Traces".</li><li id="cce_10_0026__en-us_topic_0179639644_li343919722319">(Optional) On the <strong id="cce_10_0026__en-us_topic_0179639644_b39126353206">Trace List</strong> page of the new edition, click <strong id="cce_10_0026__en-us_topic_0179639644_b573342114">Go to Old Edition</strong> in the upper right corner to switch to the <strong id="cce_10_0026__en-us_topic_0179639644_b4747415172118">Trace List</strong> page of the old edition.</li></ol>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><a name="cce_10_0026__en-us_topic_0179639644_section19271975203"></a><a name="en-us_topic_0179639644_section19271975203"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List of the Old Edition</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol4845175152710"><li id="cce_10_0026__en-us_topic_0179639644_li791871844313">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0179639644_li79188188435">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image2091881811436" src="en-us_image_0000001696838310.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0179639644_b12821731121516">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b178213191512">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0179639644_li591831894316">Choose <strong id="cce_10_0026__en-us_topic_0179639644_b09819412220">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0179639644_li20323199115315">Each time you log in to the CTS console, the new edition is displayed by default. Click <strong id="cce_10_0026__en-us_topic_0179639644_b72452318231">Go to Old Edition</strong> in the upper right corner to switch to the trace list of the old edition.</li><li id="cce_10_0026__en-us_topic_0179639644_li6936134194312">Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>. The following filters are available.<div class="fignone" id="cce_10_0026__en-us_topic_0179639644_fig139361441134311"><a name="cce_10_0026__en-us_topic_0179639644_fig139361441134311"></a><a name="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_0179639644_image14936144112433" src="en-us_image_0000001744598325.png"></span></div>
<div class="p" id="cce_10_0026__en-us_topic_0179639644_p15936134119435"><ul class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_ul20936164174314"><li id="cce_10_0026__en-us_topic_0179639644_li99361417432"><strong id="cce_10_0026__en-us_topic_0179639644_b179671714141513">Trace Type</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b179671014191515">Trace Source</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b4968714141517">Resource Type</strong>, and <strong id="cce_10_0026__en-us_topic_0179639644_b14968101411516">Search By</strong>: Select a filter from the drop-down list.<ul id="cce_10_0026__en-us_topic_0179639644_ul158893433010"><li id="cce_10_0026__en-us_topic_0179639644_li12760183118301">If you select <strong id="cce_10_0026__en-us_topic_0179639644_b389315891511">Resource ID</strong> for <strong id="cce_10_0026__en-us_topic_0179639644_b3893858131515">Search By</strong>, specify a resource ID.</li><li id="cce_10_0026__en-us_topic_0179639644_li12760203115305">If you select <strong id="cce_10_0026__en-us_topic_0179639644_b8997941831">Trace name</strong> for <strong id="cce_10_0026__en-us_topic_0179639644_b199981541317">Search By</strong>, specify a trace name.</li><li id="cce_10_0026__en-us_topic_0179639644_li197601031193019">If you select <strong id="cce_10_0026__en-us_topic_0179639644_b196612501258">Resource name</strong> for <strong id="cce_10_0026__en-us_topic_0179639644_b177275015252">Search By</strong>, specify a resource name.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0179639644_li15936204184311"><strong id="cce_10_0026__en-us_topic_0179639644_b98151395276">Operator</strong>: Select a user.</li><li id="cce_10_0026__en-us_topic_0179639644_li6936184119437"><strong id="cce_10_0026__en-us_topic_0179639644_b6981161112286">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0179639644_b1298716111281">All trace statuses</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b7987181115281">Normal</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b2988181112810">Warning</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b99881511132820">Incident</strong>.</li><li id="cce_10_0026__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_0179639644_li8936104118436">Click <strong id="cce_10_0026__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>
</li><li id="cce_10_0026__en-us_topic_0179639644_li15936204184311"><strong id="cce_10_0026__en-us_topic_0179639644_b98151395276">Operator</strong>: Select a user.</li><li id="cce_10_0026__en-us_topic_0179639644_li6936184119437"><strong id="cce_10_0026__en-us_topic_0179639644_b6981161112286">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0179639644_b1298716111281">All trace statuses</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b7987181115281">Normal</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b2988181112810">Warning</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b99881511132820">Incident</strong>.</li><li id="cce_10_0026__en-us_topic_0179639644_li1993654144315">Time range: Select <strong id="cce_10_0026__en-us_topic_0179639644_b107601514121615">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b1676021410164">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b37601914121610">Last 1 week</strong>, or specify a custom time range within the last seven days.</li><li id="cce_10_0026__en-us_topic_0179639644_li8936104118436">Click <strong id="cce_10_0026__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 5,000 records.</li></ul>
</div>
</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li094111715448">Click <strong id="cce_10_0026__en-us_topic_0179639644_b55732514186">Query</strong>.</li><li id="cce_10_0026__en-us_topic_0179639644_li29410170448">On the <strong id="cce_10_0026__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_0179639644_ul119414175448"><li id="cce_10_0026__en-us_topic_0179639644_li12946170445">Click <strong id="cce_10_0026__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_0179639644_li394151717445">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image109421716440" src="en-us_image_0000001696678850.png"></span> to view the latest information about traces.</li></ul>
</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li094111715448">Click <strong id="cce_10_0026__en-us_topic_0179639644_b55732514186">Query</strong>.</li><li id="cce_10_0026__en-us_topic_0179639644_li29410170448">On the <strong id="cce_10_0026__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_0179639644_ul119414175448"><li id="cce_10_0026__en-us_topic_0179639644_li12946170445">Click <strong id="cce_10_0026__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 5,000 records.</li><li id="cce_10_0026__en-us_topic_0179639644_li394151717445">Click <span><img id="cce_10_0026__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_0179639644_li169491744418">Click <span><img id="cce_10_0026__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_0179639644_p1294101714446"></p>
<p id="cce_10_0026__en-us_topic_0179639644_p1694171715446"><span><img id="cce_10_0026__en-us_topic_0179639644_image49418175441" src="en-us_image_0000001696838318.png"></span></p>
<p id="cce_10_0026__en-us_topic_0179639644_p1694171715446"><span><img id="cce_10_0026__en-us_topic_0179639644_image1767234653119" src="en-us_image_0000001942942816.png"></span></p>
<p id="cce_10_0026__en-us_topic_0179639644_p145491156142711"></p>
<p id="cce_10_0026__en-us_topic_0179639644_p1352018181294"></p>
<p id="cce_10_0026__en-us_topic_0179639644_p109481744411"></p>
</li><li id="cce_10_0026__en-us_topic_0179639644_li1094161784410">Click <strong id="cce_10_0026__en-us_topic_0179639644_b139145611337">View Trace</strong> in the <strong id="cce_10_0026__en-us_topic_0179639644_b1591756103313">Operation</strong> column. The trace details are displayed.<p id="cce_10_0026__en-us_topic_0179639644_p1695161714447"><span><img id="cce_10_0026__en-us_topic_0179639644_image1904172011220" src="en-us_image_0000001758618249.png"></span></p>
</li><li id="cce_10_0026__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" in the <em id="cce_10_0026__en-us_topic_0179639644_i949883013810">CTS User Guide</em>.</li></ol>
</li><li id="cce_10_0026__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" in the <em id="cce_10_0026__en-us_topic_0179639644_i149551042114218">CTS User Guide</em>.</li><li id="cce_10_0026__en-us_topic_0179639644_li11635104116013">(Optional) On the <strong id="cce_10_0026__en-us_topic_0179639644_b128618229347">Trace List</strong> page of the old edition, click <strong id="cce_10_0026__en-us_topic_0179639644_b1186112216341">New Edition</strong> in the upper right corner to switch to the <strong id="cce_10_0026__en-us_topic_0179639644_b886118225346">Trace List</strong> page of the new edition.</li></ol>
</div>
</div>
<div>

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

@ -42,7 +42,7 @@
</td>
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.4.1.3.1.2 "><p id="cce_10_0028__p11922720121010">Select the number of master nodes. The master nodes are automatically hosted by CCE and deployed with Kubernetes cluster management components such as kube-apiserver, kube-controller-manager, and kube-scheduler.</p>
<ul id="cce_10_0028__ul592282031013"><li id="cce_10_0028__li9706202816307"><strong id="cce_10_0028__b741055618291">3 Masters</strong>: Three master nodes will be created for high cluster availability.</li><li id="cce_10_0028__li29225205107"><strong id="cce_10_0028__b1859615018366">Single</strong>: Only one master node will be created in your cluster.</li></ul>
<div class="p" id="cce_10_0028__p6922192001020">You can also select AZs for the master nodes. By default, AZs are allocated automatically for the master nodes.<ul id="cce_10_0028__ul16922182051017"><li id="cce_10_0028__li149221020151014"><strong id="cce_10_0028__b82531791387">Automatic</strong>: Master nodes are randomly distributed in different AZs for cluster DR. If the number of available AZs is less than the number of nodes to be created, CCE will create the nodes in the AZs with sufficient resources to preferentially ensure cluster creation. In this case, AZ-level DR may not be ensured.</li><li id="cce_10_0028__li12922920151015"><strong id="cce_10_0028__b181966766871353">Custom</strong>: Master nodes are deployed in specific AZs.<div class="p" id="cce_10_0028__p159229208105">If there is one master node in your cluster, you can select one AZ for the master node. If there are multiple master nodes in your cluster, you can select multiple AZs for the master nodes.<ul id="cce_10_0028__ul7922320191015"><li id="cce_10_0028__li149221220101019"><strong id="cce_10_0028__b28486679971353">AZ</strong>: Master nodes are deployed in different AZs for cluster DR.</li><li id="cce_10_0028__li99221420111018"><strong id="cce_10_0028__b212140326871353">Host</strong>: Master nodes are deployed on different hosts in the same AZ for cluster DR.</li><li id="cce_10_0028__li1292242021018"><strong id="cce_10_0028__b1048015443112">Custom</strong>: Master nodes are deployed in the AZs you specified.</li></ul>
<div class="p" id="cce_10_0028__p6922192001020">You can also select AZs for the master nodes. By default, AZs are allocated automatically for the master nodes.<ul id="cce_10_0028__ul16922182051017"><li id="cce_10_0028__li149221020151014"><strong id="cce_10_0028__b82531791387">Automatic</strong>: Master nodes are randomly distributed in different AZs for cluster DR. If there are not enough AZs available, CCE will prioritize assigning nodes in AZs with enough resources to ensure cluster creation. However, this may result in AZ-level DR not being guaranteed.</li><li id="cce_10_0028__li12922920151015"><strong id="cce_10_0028__b181966766871353">Custom</strong>: Master nodes are deployed in specific AZs.<div class="p" id="cce_10_0028__p159229208105">If there is one master node in your cluster, you can select one AZ for the master node. If there are multiple master nodes in your cluster, you can select multiple AZs for the master nodes.<ul id="cce_10_0028__ul7922320191015"><li id="cce_10_0028__li149221220101019"><strong id="cce_10_0028__b28486679971353">AZ</strong>: Master nodes are deployed in different AZs for cluster DR.</li><li id="cce_10_0028__li99221420111018"><strong id="cce_10_0028__b212140326871353">Host</strong>: Master nodes are deployed on different hosts in the same AZ for cluster DR.</li><li id="cce_10_0028__li1292242021018"><strong id="cce_10_0028__b1048015443112">Custom</strong>: Master nodes are deployed in the AZs you specified.</li></ul>
</div>
</li></ul>
</div>
@ -72,7 +72,7 @@
</tr>
<tr id="cce_10_0028__row193881250141720"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.7.2.3.1.1 "><p id="cce_10_0028__p626015111172">Default Security Group</p>
</td>
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.7.2.3.1.2 "><div class="p" id="cce_10_0028__p12260105119173">Select the security group automatically generated by CCE or use the existing one as the default security group of the node.<div class="notice" id="cce_10_0028__note1426035117179"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0028__p102601451191715">The default security group must allow traffic from certain ports to ensure normal communication. Otherwise, the node cannot be created. </p>
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.7.2.3.1.2 "><div class="p" id="cce_10_0028__p12260105119173">Select the security group automatically generated by CCE or use the existing one as the default security group of the node.<div class="notice" id="cce_10_0028__note1426035117179"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0028__p102601451191715">The default security group must allow traffic from certain ports to ensure normal communication. Otherwise, the node cannot be created. For details, see <a href="cce_faq_00265.html">Configuring Cluster Security Group Rules</a>.</p>
</div></div>
</div>
</td>
@ -263,7 +263,7 @@
</tbody>
</table>
</div>
<div class="p" id="cce_10_0028__p22941723154710"><strong id="cce_10_0028__b1229417236473">Observability</strong>
<div class="p" id="cce_10_0028__p22941723154710"><strong id="cce_10_0028__b15986181710298">Observability</strong>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0028__table1829412235476" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0028__row329515231478"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.6.5.2.1.3.1.1"><p id="cce_10_0028__p3295723124717">Add-on Name</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="80%" id="mcps1.3.6.5.2.1.3.1.2"><p id="cce_10_0028__p192951423194719">Description</p>

191
docs/cce/umn/cce_10_0034.html Normal file
View File

File diff suppressed because it is too large Load Diff

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

@ -7,11 +7,11 @@
<li class="ulchildlink"><strong><a href="cce_10_0152.html">Creating a ConfigMap</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0015.html">Using a ConfigMap</a></strong><br>
</li>
After a ConfigMap is created, it can be used in three workload scenarios: <span class="keyword">environment variables</span>, <span class="keyword">command line parameters</span>, and <span class="keyword">data volumes</span>.</li>
<li class="ulchildlink"><strong><a href="cce_10_0153.html">Creating a Secret</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0016.html">Using a Secret</a></strong><br>
</li>
After secrets are created, they can be mounted as <span class="keyword">data volumes</span> or be exposed as <span class="keyword">environment variables</span> to be used by a container in a pod.</li>
<li class="ulchildlink"><strong><a href="cce_10_0388.html">Cluster Secrets</a></strong><br>
</li>
</ul>

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

@ -5,7 +5,7 @@
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cce_10_0006.html">Overview</a></strong><br>
</li>
A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is an abstract model of a group of pods in Kubernetes. Workloads in Kubernetes are classified as <span class="keyword">Deployments</span>, <span class="keyword">StatefulSets</span>, <span class="keyword">DaemonSets</span>, <span class="keyword">jobs</span>, and <span class="keyword">cron jobs</span>.</li>
<li class="ulchildlink"><strong><a href="cce_10_0673.html">Creating a Workload</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0130.html">Configuring a Workload</a></strong><br>

163
docs/cce/umn/cce_10_0094.html
View File

File diff suppressed because it is too large Load Diff

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

@ -156,7 +156,7 @@
<p id="cce_10_0132__p2317112419618">Typical scenario: Disk I/O suspension causes process suspension.</p>
</td>
<td class="cellrowborder" valign="top" width="33%" 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__b1661385069">/dev/kmsg</strong></p>
<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b1660010870">/dev/kmsg</strong></p>
<p id="cce_10_0132__p153079591241">Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."</p>
</td>
</tr>
@ -168,7 +168,7 @@
</div></div>
</td>
<td class="cellrowborder" valign="top" width="33%" 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__b443575880">/dev/kmsg</strong></p>
<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b1620520385">/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>
@ -408,7 +408,6 @@
<td class="cellrowborder" rowspan="2" valign="top" width="36.393639363936394%" headers="mcps1.3.6.4.2.6.2.4.1.3 "><p id="cce_10_0132__p18976103221315">Default threshold: 10 abnormal processes detected for three consecutive times</p>
<p id="cce_10_0132__p173704791313">Source:</p>
<ul id="cce_10_0132__ul1737010716138"><li id="cce_10_0132__li137012741320">/proc/{PID}/stat</li><li id="cce_10_0132__li83707781318">Alternately, you can run the <strong id="cce_10_0132__b731118224388">ps aux</strong> command.</li></ul>
<p id="cce_10_0132__p73703718137">Exceptional scenario: The ProcessD check item ignores the resident D processes (heartbeat and update) on which the SDI driver on the BMS node depends.</p>
<p id="cce_10_0132__p1860519498129"></p>
</td>
</tr>

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

@ -199,7 +199,7 @@
<p id="cce_10_0154__p259072620339">The interval after a failed scale-in indicates the period during which the cluster cannot be scaled in after the Autoscaler add-on triggers scale-in. This interval takes effect at the cluster level.</p>
</div>
<div class="section" id="cce_10_0154__section183121449435"><h4 class="sectiontitle">Change History</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table1435681832" frame="border" border="1" rules="all"><caption><b>Table 6 </b>Updates of the add-on adapted to clusters 1.29</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row732362810397"><th align="left" class="cellrowborder" valign="top" width="17.76%" id="mcps1.3.7.2.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p1732452843914">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table1435681832" frame="border" border="1" rules="all"><caption><b>Table 6 </b>Release history for add-on adapted to clusters 1.29</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row732362810397"><th align="left" class="cellrowborder" valign="top" width="17.76%" id="mcps1.3.7.2.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p1732452843914">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.67%" id="mcps1.3.7.2.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p7324142811396">Supported Cluster Version</p>
</th>
@ -231,7 +231,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table2071511354195" frame="border" border="1" rules="all"><caption><b>Table 7 </b>Updates of the add-on adapted to clusters 1.28</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row1210819286217"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.3.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p181088281820">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table2071511354195" frame="border" border="1" rules="all"><caption><b>Table 7 </b>Release history for add-on adapted to clusters 1.28</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row1210819286217"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.3.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p181088281820">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.650000000000002%" id="mcps1.3.7.3.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p8108152816215">Supported Cluster Version</p>
</th>
@ -281,7 +281,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table123381757132916" frame="border" border="1" rules="all"><caption><b>Table 8 </b>Updates of the add-on adapted to clusters 1.27</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row11181162282619"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.4.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p118132292610">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table123381757132916" frame="border" border="1" rules="all"><caption><b>Table 8 </b>Release history for add-on adapted to clusters 1.27</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row11181162282619"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.4.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p118132292610">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.650000000000002%" id="mcps1.3.7.4.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p121811222263">Supported Cluster Version</p>
</th>
@ -331,7 +331,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table88489551792" frame="border" border="1" rules="all"><caption><b>Table 9 </b>Updates of the add-on adapted to clusters 1.25</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row7265602229"><th align="left" class="cellrowborder" valign="top" width="17.82178217821782%" id="mcps1.3.7.5.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p11265300229">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table88489551792" frame="border" border="1" rules="all"><caption><b>Table 9 </b>Release history for add-on adapted to clusters 1.25</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row7265602229"><th align="left" class="cellrowborder" valign="top" width="17.82178217821782%" id="mcps1.3.7.5.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p11265300229">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.801980198019802%" id="mcps1.3.7.5.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p92651009224">Supported Cluster Version</p>
</th>
@ -399,7 +399,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table14498151142711" frame="border" border="1" rules="all"><caption><b>Table 10 </b>Updates of the add-on adapted to clusters 1.23</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row115011525112215"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.6.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p75017251229">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table14498151142711" frame="border" border="1" rules="all"><caption><b>Table 10 </b>Release history for add-on adapted to clusters 1.23</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row115011525112215"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.6.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p75017251229">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.650000000000002%" id="mcps1.3.7.6.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p1501102512217">Supported Cluster Version</p>
</th>
@ -476,7 +476,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table4943143014277" frame="border" border="1" rules="all"><caption><b>Table 11 </b>Updates of the add-on adapted to clusters 1.21</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row1815685612216"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.7.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p51561656122219">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table4943143014277" frame="border" border="1" rules="all"><caption><b>Table 11 </b>Release history for add-on adapted to clusters 1.21</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row1815685612216"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.7.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p51561656122219">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.63%" id="mcps1.3.7.7.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p101561556142218">Supported Cluster Version</p>
</th>
@ -562,7 +562,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table1927615272812" frame="border" border="1" rules="all"><caption><b>Table 12 </b>Updates of the add-on adapted to clusters 1.19</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row14876163042314"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.8.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p11876130102319">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table1927615272812" frame="border" border="1" rules="all"><caption><b>Table 12 </b>Release history for add-on adapted to clusters 1.19</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row14876163042314"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.8.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p11876130102319">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.650000000000002%" id="mcps1.3.7.8.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p118761830142318">Supported Cluster Version</p>
</th>
@ -648,7 +648,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table187149303281" frame="border" border="1" rules="all"><caption><b>Table 13 </b>Updates of the add-on adapted to clusters 1.17</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row16283442331"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.9.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p4294151015419">Add-on Version</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0154__table187149303281" frame="border" border="1" rules="all"><caption><b>Table 13 </b>Release history for add-on adapted to clusters 1.17</caption><thead align="left"><tr id="cce_10_0154__en-us_topic_0000001609894169_row16283442331"><th align="left" class="cellrowborder" valign="top" width="17.78%" id="mcps1.3.7.9.2.5.1.1"><p id="cce_10_0154__en-us_topic_0000001609894169_p4294151015419">Add-on Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="19.650000000000002%" id="mcps1.3.7.9.2.5.1.2"><p id="cce_10_0154__en-us_topic_0000001609894169_p1029413104417">Supported Cluster Version</p>
</th>

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

@ -5,7 +5,7 @@
<div class="notice" id="cce_10_0198__note1330184411443"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0198__ul633194413448"><li id="cce_10_0198__li23542217126">When accepting an ECS, you can reset the ECS OS to a standard public image offered by CCE. If you choose to do so, you need to reset the password or key pair, and the previous password or key pair will become invalid.</li><li id="cce_10_0198__li444515326218">LVM information, including volume groups (VGs), logical volumes (LVs), and physical volumes (PVs), will be deleted from the system disks and data disks attached to the selected ECSs during acceptance. Ensure that the information has been backed up.</li><li id="cce_10_0198__li64453322214">During the acceptance of an ECS, do not perform any operation on the ECS through the ECS console.</li></ul>
</div></div>
</div>
<div class="section" id="cce_10_0198__section11440230173714"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0198__ul2953113112618"><li id="cce_10_0198__li13953123162613">ECSs and BMSs can be managed.</li></ul>
<div class="section" id="cce_10_0198__section11440230173714"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0198__ul2953113112618"><li id="cce_10_0198__li13953123162613">ECSs can be managed.</li></ul>
</div>
<div class="section" id="cce_10_0198__section4156147355"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0198__p1580241831016">The cloud servers to be managed must meet the following requirements:</p>
<ul id="cce_10_0198__ul238633332817"><li id="cce_10_0198__li8766115612119">The node to be accepted must be in the <strong id="cce_10_0198__b9828916182413">Running</strong> state and not used by other clusters. In addition, the node to be accepted does not carry the CCE-Dynamic-Provisioning-Node tag.</li><li id="cce_10_0198__li5758231102718">The node to be accepted and the cluster must be in the same VPC. (If the cluster version is earlier than v1.13.10, the node to be accepted and the CCE cluster must be in the same subnet.)</li><li id="cce_10_0198__li16348171016518">Data disks must be attached to the nodes to be managed. A local disk (disk-intensive disk) or a data disk of at least 20 GiB can be attached to the node, and any data disks already attached cannot be smaller than 10 GiB. </li><li id="cce_10_0198__li77666565110">The node to be accepted has 2-core or higher CPU, 4 GiB or larger memory, and only one NIC.</li><li id="cce_10_0198__li62969501137">Only cloud servers with the same data disk configurations can be added in batches.</li><li id="cce_10_0198__li1583010973316">If IPv6 is enabled for a cluster, only nodes in a subnet with IPv6 enabled can be accepted and managed. If IPv6 is not enabled for the cluster, only nodes in a subnet without IPv6 enabled can be accepted.</li><li id="cce_10_0198__li7830189173313">Nodes in a CCE Turbo cluster must support sub-ENIs or be bound to at least 16 ENIs. For details about the node flavors, see the node flavors that can be selected on the console when you create a node. </li><li id="cce_10_0198__li20995152811337">Data disks that have been partitioned will be ignored during node management. Ensure that there is at least one unpartitioned data disk meeting the specifications is attached to the node.</li></ul>

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

@ -71,8 +71,8 @@
<p id="cce_10_0209__p3247181715367">The interval after a node is deleted indicates the period during which the cluster cannot be scaled in after the Autoscaler add-on triggers a scale-in. This setting takes effect in the entire cluster.</p>
<p id="cce_10_0209__p259072620339">The interval after a failed scale-in indicates the period during which the cluster cannot be scaled in after the Autoscaler add-on triggers a scale-in. This setting takes effect in the entire cluster.</p>
</div>
<div class="section" id="cce_10_0209__section1195811504617"><h4 class="sectiontitle">Period for Autoscaler to Retry a Scale-out</h4><p id="cce_10_0209__p5938123464612">If a node pool failed to scale out, for example, due to insufficient resources or quota, or an error occurred during node installation, Autoscaler can retry the scale-out in the node pool or switch to another node pool. The retry period varies depending on failure causes:</p>
<ul id="cce_10_0209__ul208524403461"><li id="cce_10_0209__li11852340174616">When resources in a node pool are sold out or the user quota is insufficient, Autoscaler cools down the node pool for 5 minutes, 10 minutes, or 20 minutes. The maximum cooldown duration is 30 minutes. Then, Autoscaler switches to another node pool for a scale-out in the next 10 seconds until the expected node is added or all node pools are cooled down.</li><li id="cce_10_0209__li188521340204613">If an error occurred during node installation in a node pool, the node pool enters a 5-minute cooldown period. After the period expires, Autoscaler can trigger a node pool scale-out again. If the faulty node is automatically reclaimed, Cluster Autoscaler re-evaluates the cluster status within 1 minute and triggers a node pool scale-out as needed.</li><li id="cce_10_0209__li10852140114617">During a node pool scale-out, if a node remains in the installing state for a long time, Cluster Autoscaler tolerates the node for a maximum of 15 minutes. After the tolerance period expires, Cluster Autoscaler re-evaluates the cluster status and triggers a node pool scale-out as needed.</li></ul>
<div class="section" id="cce_10_0209__section1195811504617"><h4 class="sectiontitle">Period for Autoscaler to Retry a Scale-out</h4><p id="cce_10_0209__p5938123464612">If a node pool failed to scale out, for example, due to insufficient quota, or an error occurred during node installation, Autoscaler can retry the scale-out in the node pool or switch to another node pool. The retry period varies depending on failure causes:</p>
<ul id="cce_10_0209__ul208524403461"><li id="cce_10_0209__li11852340174616">When the user quota is insufficient, Autoscaler cools down the node pool for 5 minutes, 10 minutes, or 20 minutes. The maximum cooldown duration is 30 minutes. Then, Autoscaler switches to another node pool for a scale-out in the next 10 seconds until the expected node is added or all node pools are cooled down.</li><li id="cce_10_0209__li188521340204613">If an error occurred during node installation in a node pool, the node pool enters a 5-minute cooldown period. After the period expires, Autoscaler can trigger a node pool scale-out again. If the faulty node is automatically reclaimed, Cluster Autoscaler re-evaluates the cluster status within 1 minute and triggers a node pool scale-out as needed.</li><li id="cce_10_0209__li10852140114617">During a node pool scale-out, if a node remains in the installing state for a long time, Cluster Autoscaler tolerates the node for a maximum of 15 minutes. After the tolerance period expires, Cluster Autoscaler re-evaluates the cluster status and triggers a node pool scale-out as needed.</li></ul>
</div>
<div class="section" id="cce_10_0209__section3613595209"><h4 class="sectiontitle">Example YAML</h4><p id="cce_10_0209__p117581998202">The following is a YAML example of a node scaling policy:</p>
<pre class="screen" id="cce_10_0209__screen2076018942015">apiVersion: autoscaling.cce.io/v1alpha1

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

@ -8,6 +8,8 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0686.html">LoadBalancer Ingresses</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0692.html">Nginx Ingresses</a></strong><br>
</li>
</ul>
<div class="familylinks">

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

File diff suppressed because it is too large Load Diff

1
docs/cce/umn/cce_10_0252.html
View File

@ -103,6 +103,7 @@ metadata:
<strong id="cce_10_0252__b1046533152014"> ],</strong>
<strong id="cce_10_0252__b64616331204"> "l7_flavor_name": "L7_flavor.elb.s1.small"</strong>
}'
kubernetes.io/elb.tags: key1=value1,key2=value2 # ELB resource tags
spec:
rules:
- host: ''

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

@ -84,6 +84,11 @@
<td class="cellrowborder" valign="top" width="76.67%" headers="mcps1.3.6.2.1.3.1.2 "><p id="cce_10_0277__p1924815022620"><span class="keyword" id="cce_10_0277__keyword116431134387">CoreDNS</span> is a <span class="keyword" id="cce_10_0277__keyword7643913163814">DNS server</span> that provides <span class="keyword" id="cce_10_0277__keyword56441913163814">domain name resolution</span> for <span class="keyword" id="cce_10_0277__keyword4644613183820">Kubernetes</span> clusters through a <span class="keyword" id="cce_10_0277__keyword76441513123814">chain add-on</span>.</p>
</td>
</tr>
<tr id="cce_10_0277__row92491850122618"><td class="cellrowborder" valign="top" width="23.330000000000002%" headers="mcps1.3.6.2.1.3.1.1 "><p id="cce_10_0277__p124995092619"><a href="cce_10_0034.html">NGINX Ingress Controller</a></p>
</td>
<td class="cellrowborder" valign="top" width="76.67%" headers="mcps1.3.6.2.1.3.1.2 "><p id="cce_10_0277__p1024916503263">This add-on forwards application data such as the data of virtual hosts, load balancers, SSL proxy, and HTTP routing for Services that can be directly accessed outside a cluster.</p>
</td>
</tr>
</tbody>
</table>
</div>

314
docs/cce/umn/cce_10_0302.html
View File

File diff suppressed because it is too large Load Diff

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

@ -100,9 +100,9 @@
</tr>
<tr id="cce_10_0307__row285818816813"><td class="cellrowborder" valign="top" width="12.195121951219512%" headers="mcps1.3.4.2.1.6.1.1 "><p id="cce_10_0307__p15858186817">Access mode</p>
</td>
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.2 "><p id="cce_10_0307__p085813810814">Accessible only after being mounted to ECSs or BMSs and initialized.</p>
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.2 "><p id="cce_10_0307__p085813810814">Accessible only after being attached to ECSs and initialized.</p>
</td>
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.3 "><p id="cce_10_0307__p98591186815">Mounted to ECSs or BMSs using network protocols. A network address must be specified or mapped to a local directory for access.</p>
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.3 "><p id="cce_10_0307__p98591186815">Mounted to ECSs using network protocols. A network address must be specified or mapped to a local directory for access.</p>
</td>
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.4 "><p id="cce_10_0307__p3755175310424">Supports the Network File System (NFS) protocol (NFSv3 only). You can seamlessly integrate existing applications and tools with SFS Turbo.</p>
</td>

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

@ -1,7 +1,7 @@
<a name="cce_10_0351"></a><a name="cce_10_0351"></a>
<h1 class="topictitle1">CPU Policy</h1>
<div id="body0000001148804376"><div class="section" id="cce_10_0351__section7579153155615"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0351__p43401139173617">By default, kubelet uses <a href="https://www.kernel.org/doc/html/latest/scheduler/sched-design-CFS.html" target="_blank" rel="noopener noreferrer">CFS quotas</a> to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the pod is throttled and which CPU cores are available at scheduling time. Many workloads are not sensitive to this migration and thus work fine without any intervention. Some applications are CPU-sensitive. They are sensitive to:</p>
<div id="body0000001148804376"><div class="section" id="cce_10_0351__section7579153155615"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0351__p43401139173617">By default, kubelet uses <a href="https://www.kernel.org/doc/html/next/scheduler/sched-design-CFS.html" target="_blank" rel="noopener noreferrer">CFS quotas</a> to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the pod is throttled and which CPU cores are available at scheduling time. Many workloads are not sensitive to this migration and thus work fine without any intervention. Some applications are CPU-sensitive. They are sensitive to:</p>
<ul id="cce_10_0351__ul144721771494"><li id="cce_10_0351__li8472377496">CPU throttling</li><li id="cce_10_0351__li547213710498">Context switching</li><li id="cce_10_0351__li54722078499">Processor cache misses</li><li id="cce_10_0351__li20472127184918">Cross-socket memory access</li><li id="cce_10_0351__li647211754916">Hyperthreads that are expected to run on the same physical CPU card</li></ul>
<p id="cce_10_0351__p84721273491">If your workloads are sensitive to any of these items and CPU cache affinity and scheduling latency significantly affect workload performance, kubelet allows alternative CPU management policies (CPU binding) to determine some placement preferences on the node. The CPU manager preferentially allocates resources on a socket and full physical cores to avoid interference.</p>
</div>

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

@ -34,7 +34,7 @@
</tr>
<tr id="cce_10_0363__row1694611446181"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.3.3.2.2.1.2.3.1.1 "><p id="cce_10_0363__p108541345121815">Specifications</p>
</td>
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.3.3.2.2.1.2.3.1.2 "><p id="cce_10_0363__p2854164541817">Select node flavors as needed. A node needs at least two vCPU cores and 4 GiB of memory. </p>
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.3.3.2.2.1.2.3.1.2 "><p id="cce_10_0363__p2854164541817">Select node flavors as needed. A node needs at least two vCPU cores and 4 GiB of memory. For the supported node flavors, see <a href="https://docs.otc.t-systems.com/en-us/api2/cce/cce_02_0368.html" target="_blank" rel="noopener noreferrer">Node Flavor Description</a>.</p>
<p id="cce_10_0363__p485494511188">The available node flavors vary depending on AZs. Obtain the flavors displayed on the console.</p>
</td>
</tr>
@ -92,10 +92,10 @@
</div></div>
<p id="cce_10_0363__p20408122884010"><strong id="cce_10_0363__b168590318488">Advanced Settings</strong></p>
<p id="cce_10_0363__p3752312011">Expand the area and configure the following parameters:</p>
<ul id="cce_10_0363__ul197721145155911"><li id="cce_10_0363__li12110343014"><strong id="cce_10_0363__b158191435122117">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</li><li id="cce_10_0363__li1095641711169"><strong id="cce_10_0363__b8672113734817">Data Disk Encryption</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. BMS nodes do not support data disk encryption that is available only in certain regions. For details, see the console.<ul id="cce_10_0363__ul1924511512168"><li id="cce_10_0363__li4245181561611"><strong id="cce_10_0363__b1573516333164">Not encrypted</strong> is selected by default.</li><li id="cce_10_0363__li172751284225">If you select <strong id="cce_10_0363__b16761923958">Enabled (key)</strong> for <strong id="cce_10_0363__b1267610231951">Data Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0363__b76761231051">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li><li id="cce_10_0363__li22751687228">If you select <strong id="cce_10_0363__b79545611132">Enabled (KMS key ID)</strong> for <strong id="cce_10_0363__b129547621311">Data Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
<ul id="cce_10_0363__ul197721145155911"><li id="cce_10_0363__li12110343014"><strong id="cce_10_0363__b158191435122117">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</li><li id="cce_10_0363__li1095641711169"><strong id="cce_10_0363__b8672113734817">Data Disk Encryption</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <ul id="cce_10_0363__ul1924511512168"><li id="cce_10_0363__li4245181561611"><strong id="cce_10_0363__b1573516333164">Not encrypted</strong> is selected by default.</li><li id="cce_10_0363__li172751284225">If you select <strong id="cce_10_0363__b16761923958">Enabled (key)</strong> for <strong id="cce_10_0363__b1267610231951">Data Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0363__b76761231051">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li><li id="cce_10_0363__li22751687228">If you select <strong id="cce_10_0363__b79545611132">Enabled (KMS key ID)</strong> for <strong id="cce_10_0363__b129547621311">Data Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
</li></ul>
<p id="cce_10_0363__p1391618153118"><strong id="cce_10_0363__b698132517473">Adding data disks</strong></p>
<p id="cce_10_0363__p45741654112612">A maximum of 16 data disks can be attached to an ECS and 10 to a BMS. By default, a raw disk is created without any processing. You can also click <strong id="cce_10_0363__b1353214375715">Expand</strong> and select any of the following options:</p>
<p id="cce_10_0363__p45741654112612">A maximum of 16 data disks can be attached to an ECS. By default, a raw disk is created without any processing. You can also click <strong id="cce_10_0363__b1353214375715">Expand</strong> and select any of the following options:</p>
<ul id="cce_10_0363__ul198131191414"><li id="cce_10_0363__li1681481912112"><strong id="cce_10_0363__b650951155715">Default</strong>: By default, a raw disk is created without any processing.</li><li id="cce_10_0363__li108141119311"><strong id="cce_10_0363__b1791414137595">Mount Disk</strong>: The data disk is attached to a specified directory.</li><li id="cce_10_0363__li18141219612"><strong id="cce_10_0363__b12108139105910">Use as PV</strong>: applicable when there is a high performance requirement on PVs. The <strong id="cce_10_0363__b57411338611">node.kubernetes.io/local-storage-persistent</strong> label is added to the node with PV configured. The value is <strong id="cce_10_0363__b0496143919615">linear</strong> or <strong id="cce_10_0363__b2800194113618">striped</strong>.</li><li id="cce_10_0363__li17814619119"><strong id="cce_10_0363__b154131531010">Use as ephemeral volume</strong>: applicable when there is a high performance requirement on emptyDir.</li></ul>
<div class="note" id="cce_10_0363__note18158650124116"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0363__ul1242510314572"><li id="cce_10_0363__li0425203125719">Local PVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 2.1.23 or later. Version 2.1.23 or later is recommended.</li><li id="cce_10_0363__li64131222577">Local EVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 1.2.29 or later.</li></ul>
</div></div>

154
docs/cce/umn/cce_10_0364.html Normal file
View File

File diff suppressed because it is too large Load Diff

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

@ -170,8 +170,8 @@ metadata:
<strong id="cce_10_0378__b11409823104618">everest.io/reclaim-policy: retain-volume-only</strong>
name: pv-evs-test
labels:
<strong id="cce_10_0378__b830530119"> </strong>failure-domain.beta.kubernetes.io/region: <i><span class="varname" id="cce_10_0378__varname798800052">&lt;your_region&gt;</span></i> # Region of the node where the application is to be deployed
failure-domain.beta.kubernetes.io/zone: <i><span class="varname" id="cce_10_0378__varname1138654092">&lt;your_zone&gt;</span></i> # AZ of the node where the application is to be deployed
<strong id="cce_10_0378__b1127041321"> </strong>failure-domain.beta.kubernetes.io/region: <i><span class="varname" id="cce_10_0378__varname722552459">&lt;your_region&gt;</span></i> # Region of the node where the application is to be deployed
failure-domain.beta.kubernetes.io/zone: <i><span class="varname" id="cce_10_0378__varname1794895439">&lt;your_zone&gt;</span></i> # AZ of the node where the application is to be deployed
spec:
accessModes:
- ReadWriteOnce

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

@ -82,6 +82,9 @@ csi.storage.k8s.io/fstype: ext4 # (Optional) Set the file system type to <str
</tr>
</thead>
<tbody><tr id="cce_10_0380__row941612810542"><td class="cellrowborder" rowspan="4" valign="top" width="11%" headers="mcps1.3.2.5.3.2.5.1.1 "><p id="cce_10_0380__p102718119016">EVS</p>
<p id="cce_10_0380__p16681171714591"></p>
<p id="cce_10_0380__p196814173596"></p>
<p id="cce_10_0380__p168151718599"></p>
</td>
<td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.2.5.3.2.5.1.2 "><p id="cce_10_0380__p17416168135419">csi.storage.k8s.io/csi-driver-name</p>
</td>
@ -103,7 +106,7 @@ csi.storage.k8s.io/fstype: ext4 # (Optional) Set the file system type to <str
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.5.3.2.5.1.2 "><p id="cce_10_0380__p19658750105513">Yes</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.5.3.2.5.1.3 "><div class="p" id="cce_10_0380__p191376271512">EVS disk type. All letters are in uppercase.<ul id="cce_10_0380__cce_10_0614_ul1099913293217"><li id="cce_10_0380__cce_10_0614_li769621143010"><strong id="cce_10_0380__cce_10_0614_b571854437105541">SATA</strong>: common I/O</li><li id="cce_10_0380__cce_10_0614_li11999525321"><strong id="cce_10_0380__cce_10_0614_b1568717650105541">SAS</strong>: high I/O</li><li id="cce_10_0380__cce_10_0614_li199991629326"><strong id="cce_10_0380__cce_10_0614_b595954424105541">SSD</strong>: ultra-high I/O</li></ul>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.5.3.2.5.1.3 "><div class="p" id="cce_10_0380__p191376271512">EVS disk type. All letters are in uppercase.<ul id="cce_10_0380__cce_10_0614_ul1099913293217"><li id="cce_10_0380__cce_10_0614_li769621143010"><strong id="cce_10_0380__cce_10_0614_b571854437105541">SATA</strong>: common I/O</li><li id="cce_10_0380__cce_10_0614_li11999525321"><strong id="cce_10_0380__cce_10_0614_b1568717650105541">SAS</strong>: high I/O</li><li id="cce_10_0380__cce_10_0614_li199991629326"><strong id="cce_10_0380__cce_10_0614_b595954424105541">SSD</strong>: ultra-high I/O</li><li id="cce_10_0380__cce_10_0614_li10999628327"><strong id="cce_10_0380__cce_10_0614_b1904387706105541">GPSSD</strong>: general-purpose SSD</li><li id="cce_10_0380__cce_10_0614_li59995243214"><strong id="cce_10_0380__cce_10_0614_b1385856157105541">ESSD</strong>: extreme SSD</li></ul>
</div>
</td>
</tr>

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

@ -45,7 +45,7 @@ metadata:
namespace: default
annotations:
<strong id="cce_10_0381__b9310826144315">everest.io/disk-volume-type: <i><span class="varname" id="cce_10_0381__varname20948152913434">SSD</span></i></strong> # EVS disk type, which must be the same as that of the snapshot's source EVS disk.
everest.io/disk-volume-tags: <i><span class="varname" id="cce_10_0381__varname0815731172312">'{"key1":"value1","key2":"value2"}'</span></i> # (Optional) Custom resource tags
everest.io/disk-volume-tags: <i><span class="varname" id="cce_10_0381__varname20731102664213">'{"key1":"value1","key2":"value2"}'</span></i> # (Optional) Custom resource tags
csi.storage.k8s.io/fstype: xfs # (Optional) Configure this field when the snapshot file system is of the <strong id="cce_10_0381__b127888712233">xfs</strong> type.
labels:
<strong id="cce_10_0381__b1368025311292">failure-domain.beta.kubernetes.io/region: <i><span class="varname" id="cce_10_0381__varname122441125134419">&lt;your_region&gt;</span></i></strong> # Replace the region with the one where the EVS disk is located.

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

@ -507,7 +507,7 @@ spec:
</td>
<td class="cellrowborder" valign="top" width="56.99999999999999%" headers="mcps1.3.11.2.2.5.1.3 "><p id="cce_10_0385__p18882328885">If the pod uses <strong id="cce_10_0385__b192375332571">hostNetwork</strong>, the ELB forwards the request to the host network after this annotation is used.</p>
<p id="cce_10_0385__p128822282088">Options:</p>
<ul id="cce_10_0385__ul6882202812817"><li id="cce_10_0385__li1888220285811"><strong id="cce_10_0385__b2080528995">true</strong>: enabled</li><li id="cce_10_0385__li1988219284818"><strong id="cce_10_0385__b131375249434210">false</strong> (default): disabled</li></ul>
<ul id="cce_10_0385__ul6882202812817"><li id="cce_10_0385__li1888220285811"><strong id="cce_10_0385__b1604205605">true</strong>: enabled</li><li id="cce_10_0385__li1988219284818"><strong id="cce_10_0385__b131375249434210">false</strong> (default): disabled</li></ul>
</td>
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.11.2.2.5.1.4 "><p id="cce_10_0385__p1688232810812">v1.9 or later</p>
</td>

26
docs/cce/umn/cce_10_0390.html Normal file
View File

@ -0,0 +1,26 @@
<a name="cce_10_0390"></a><a name="cce_10_0390"></a>
<h1 class="topictitle1">Creating Nginx Ingresses on the Console</h1>
<div id="body0000001238074915"><div class="section" id="cce_10_0390__section7120205117104"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0390__ul14674003499"><li id="cce_10_0390__li1578113511562">An ingress provides network access for backend workloads. Ensure that a workload is available in a cluster. If no workload is available, deploy a workload by referring to <a href="cce_10_0047.html">Creating a Deployment</a>, <a href="cce_10_0048.html">Creating a StatefulSet</a>, or <a href="cce_10_0216.html">Creating a DaemonSet</a>.</li><li id="cce_10_0390__li79178855112">A ClusterIP or NodePort Service has been configured for the workload. For details about how to configure the Service, see <a href="cce_10_0011.html">ClusterIP</a> or <a href="cce_10_0142.html">NodePort</a>.</li><li id="cce_10_0390__li1522285385015">To add Nginx Ingress, ensure that the Nginx Ingress Controller add-on has been installed in the cluster. For details, see <a href="cce_10_0034.html#cce_10_0034__section1152424015224">Installing the Add-on</a>.</li></ul>
</div>
<div class="section" id="cce_10_0390__section2042610683912"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0390__ul7976181182416"><li id="cce_10_0390__li79769111246"><strong id="cce_10_0390__b12592954183519">It is not recommended modifying any configuration of a load balancer on the ELB console. Otherwise, the Service will be abnormal.</strong> If you have modified the configuration, uninstall the nginx-ingress add-on and reinstall it.</li><li id="cce_10_0390__li48993226403">The URL registered in an ingress forwarding policy must be the same as the URL used to access the backend Service. Otherwise, a 404 error will be returned.</li><li id="cce_10_0390__li947614550453">The selected or created load balancer must be in the same VPC as the current cluster, and it must match the load balancer type (private or public network).</li><li id="cce_10_0390__li1819319101224">The load balancer has at least two listeners, and ports 80 and 443 are not occupied by listeners.</li></ul>
</div>
<div class="section" id="cce_10_0390__section13728162710151"><h4 class="sectiontitle">Creating an Nginx Ingress</h4><p id="cce_10_0390__p1792391045213">This section uses an Nginx workload as an example to describe how to create an <span class="keyword" id="cce_10_0390__keyword11453175217431">Nginx ingress</span>.</p>
<ol id="cce_10_0390__ol1692371065214"><li id="cce_10_0390__li1949795913511"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0390__li174971959357"><span>Choose <strong id="cce_10_0390__b2043283813271">Services &amp; Ingresses</strong> in the navigation pane, click the <span class="uicontrol" id="cce_10_0390__uicontrol1643315383276"><b>Ingresses</b></span> tab, and click <strong id="cce_10_0390__b24333383278">Create Ingress</strong> in the upper right corner.</span></li><li id="cce_10_0390__li1892361010526"><span>Configure ingress parameters.</span><p><ul id="cce_10_0390__ul1152462114420"><li id="cce_10_0390__li1520221343"><strong id="cce_10_0390__b17536756163712">Name</strong>: Customize the name of an ingress, for example, <strong id="cce_10_0390__b10536165617378">nginx-ingress-demo</strong>.</li><li id="cce_10_0390__li2052032110414"><strong id="cce_10_0390__b263319118385">Namespace</strong>: Select the namespace to which the ingress is to be added.</li><li id="cce_10_0390__li13960184616244"><strong id="cce_10_0390__b15447133854410">nginx-ingress</strong>: This option is displayed only after the <a href="cce_10_0034.html">NGINX Ingress Controller</a> add-on is installed in the cluster.<ul id="cce_10_0390__ul1968865852511"><li id="cce_10_0390__li4327131465519"><strong id="cce_10_0390__b1885525105520">Ingress Class</strong>: Select the name of the Nginx Ingress controller installed in the cluster. You can <a href="cce_10_0034.html#cce_10_0034__section1057051834311">install multiple Nginx Ingress controllers</a> and customize controller names as needed.</li><li id="cce_10_0390__li612625822519"><strong id="cce_10_0390__b78523020264">External Protocol</strong>: The options are <strong id="cce_10_0390__b167653165218">HTTP</strong> and <strong id="cce_10_0390__b649173417525">HTTPS</strong>. The default number of the listening port reserved when Nginx Ingress Controller is installed is 80 for HTTP and 443 for HTTPS. To use HTTPS, configure a certificate.</li><li id="cce_10_0390__li16443181117484"><strong id="cce_10_0390__b144421114814">Certificate Source</strong>: source of a certificate for encrypting and authenticating HTTPS data transmission.<ul id="cce_10_0390__ul1616815195484"><li id="cce_10_0390__li255111619486">If you select a TLS key, you must create a key certificate of the IngressTLS or kubernetes.io/tls type beforehand. For details, see <a href="cce_10_0153.html">Creating a Secret</a>.</li><li id="cce_10_0390__li145511616194820">If you select the default certificate, Nginx Ingress Controller will use its default certificate for encryption and authentication. You can configure the default certificate during <a href="cce_10_0034.html">NGINX Ingress Controller</a> installation. If the default certificate is not configured, the certificate provided by Nginx Ingress Controller will be used.</li></ul>
</li><li id="cce_10_0390__li1390259142518"><strong id="cce_10_0390__b11146182175010">SNI</strong>: stands for Server Name Indication (SNI), which is an extended protocol of TLS. SNI allows multiple TLS-compliant domain names for external access using the same IP address and port number, and 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.</li></ul>
</li><li id="cce_10_0390__li14524162115419"><strong id="cce_10_0390__b85411435123911">Forwarding Policy</strong>: When the access address of a request matches the forwarding policy (a forwarding policy consists of a domain name and URL), the request is forwarded to the corresponding target Service for processing. Click <span class="uicontrol" id="cce_10_0390__uicontrol176115406399"><b>Add Forwarding Policies</b></span> to add multiple forwarding policies.<ul id="cce_10_0390__ul236504652711"><li id="cce_10_0390__li11364144612274"><strong id="cce_10_0390__b113231644143911">Domain Name</strong>: actual domain name. Ensure that the entered domain name has been registered and archived. After the ingress is created, bind the domain name to the IP address of the automatically created load balancer (IP address of the ingress access address). If a domain name rule is configured, the domain name must always be used for access.</li><li id="cce_10_0390__li2086218897"><strong id="cce_10_0390__b1604202165314">Path Matching Rule</strong>:<ul id="cce_10_0390__ul5861518393"><li id="cce_10_0390__li42981329124510"><strong id="cce_10_0390__b191142012273">Default</strong>: Prefix match is used by default.</li><li id="cce_10_0390__li168511815919"><strong id="cce_10_0390__b1474204218261">Prefix match</strong>: If the URL is set to <strong id="cce_10_0390__b447434242618">/healthz</strong>, the URL that meets the prefix can be accessed, for example, <strong id="cce_10_0390__b050814416260">/healthz/v1</strong> and <strong id="cce_10_0390__b175086444262">/healthz/v2</strong>.</li><li id="cce_10_0390__li14861818798"><strong id="cce_10_0390__b6328185662612">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_0390__b146616586264">/healthz</strong>, only <strong id="cce_10_0390__b20748749283">/healthz</strong> can be accessed.</li></ul>
</li><li id="cce_10_0390__li10365446202715"><strong id="cce_10_0390__b764653745317">Path</strong>: access path to be registered, for example, <strong id="cce_10_0390__b1082255217510">/healthz</strong>.<div class="note" id="cce_10_0390__note189762586487"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0390__ul19920195522918"><li id="cce_10_0390__li109201551299">The access path matching rule of Nginx Ingress is based on the path prefix separated by the slash (/) and is case-sensitive. If the subpath separated by a slash (/) matches the prefix, the access is normal. However, if the prefix is only a part of the character string in the subpath, the access is not matched. For example, if the URL is set to /healthz, /healthz/v1 is matched, but /healthzv1 is not matched.</li><li id="cce_10_0390__li196066598299">The access path added here must exist in the backend application. Otherwise, the forwarding fails.<p id="cce_10_0390__p15563156181615"><a name="cce_10_0390__li196066598299"></a><a name="li196066598299"></a>For example, the default access URL of the Nginx application is <strong id="cce_10_0390__b64131021569">/usr/share/nginx/html</strong>. When adding <strong id="cce_10_0390__b141315216610">/test</strong> to the ingress forwarding policy, ensure the access URL of your Nginx application contains <strong id="cce_10_0390__b14141221769">/usr/share/nginx/html/test</strong>. Otherwise, error 404 will be returned.</p>
</li></ul>
</div></div>
</li><li id="cce_10_0390__li936512466271"><strong id="cce_10_0390__b815129184017">Destination Service</strong>: Select an existing Service or create a Service. Services that do not meet search criteria are automatically filtered out.</li><li id="cce_10_0390__li183659465276"><strong id="cce_10_0390__b114133312403">Destination Service Port</strong>: Select the access port of the destination Service.</li><li id="cce_10_0390__li133652046172715"><strong id="cce_10_0390__b19654173419408">Operation</strong>: Click <span class="uicontrol" id="cce_10_0390__uicontrol12654183424011"><b>Delete</b></span> to delete the configuration.</li></ul>
</li><li id="cce_10_0390__li20550227393"><strong id="cce_10_0390__b179359816510">Annotation</strong>: The value is in the format of key:value. You can use <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/" target="_blank" rel="noopener noreferrer">annotations</a> to query the configurations supported by nginx-ingress.</li></ul>
</p></li><li id="cce_10_0390__li6925710175218"><span>Click <span class="uicontrol" id="cce_10_0390__uicontrol26585373408"><b>OK</b></span>.</span><p><p id="cce_10_0390__p1392511025212">After the ingress is created, it is displayed in the ingress list.</p>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0692.html">Nginx Ingresses</a></div>
</div>
</div>

56
docs/cce/umn/cce_10_0405.html
View File

File diff suppressed because it is too large Load Diff

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

@ -1,9 +1,10 @@
<a name="cce_10_0435"></a><a name="cce_10_0435"></a>
<h1 class="topictitle1">SSH Connectivity of Master Nodes</h1>
<div id="body0000001392413474"><div class="section" id="cce_10_0435__section10606429876"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0435__p6857185644115">Check whether CCE can connect to your master nodes.</p>
<div id="body0000001392413474"><div class="section" id="cce_10_0435__en-us_topic_0000001392413474_section10606429876"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0435__en-us_topic_0000001392413474_p6857185644115">Check whether your master nodes can be accessed using SSH.</p>
</div>
<div class="section" id="cce_10_0435__section12561223685"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0435__p2397135717294">Contact technical support.</p>
<div class="section" id="cce_10_0435__en-us_topic_0000001392413474_section12561223685"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0435__en-us_topic_0000001392413474_p49628021318">There is a low probability that the SSH connectivity check fails due to network fluctuations. Perform the pre-upgrade check again.</p>
<p id="cce_10_0435__en-us_topic_0000001392413474_p2397135717294">If the check still fails, submit a service ticket to contact technical support.</p>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0452"></a><a name="cce_10_0452"></a>
<h1 class="topictitle1">Node CPUs</h1>
<div id="body0000001442412957"><div class="section" id="cce_10_0452__section0617132211218"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0452__p321195515155">Check whether the number of CPUs on the master node is greater than 2.</p>
<h1 class="topictitle1">Node CPU Cores</h1>
<div id="body0000001442412957"><div class="section" id="cce_10_0452__en-us_topic_0000001442412957_section0617132211218"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0452__en-us_topic_0000001442412957_p321195515155">Check and make sure that the master nodes in your cluster have more than 2 CPU cores.</p>
</div>
<div class="section" id="cce_10_0452__section426012117229"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0452__p1890915305588">If the number of CPUs on the master node is 2, contact technical support to expand the number to 4 or more.</p>
<div class="section" id="cce_10_0452__en-us_topic_0000001442412957_section426012117229"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0452__en-us_topic_0000001442412957_p2433515158">The number of CPU cores on the master nodes is 2, which may lead to a cluster upgrade failure.</p>
<p id="cce_10_0452__en-us_topic_0000001442412957_p1890915305588">Contact technical support to expand the number of CPU cores to four or more.</p>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0458"></a><a name="cce_10_0458"></a>
<h1 class="topictitle1">Internal Errors</h1>
<div id="body0000001442654321"><div class="section" id="cce_10_0458__section2069913581447"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0458__p16105382453">Before the upgrade, check whether an internal error occurs.</p>
<h1 class="topictitle1">Internal Error</h1>
<div id="body0000001442654321"><div class="section" id="cce_10_0458__en-us_topic_0000001442654321_section2069913581447"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0458__en-us_topic_0000001442654321_p16105382453">This check item is not typical and implies that an internal error was found during the pre-upgrade check.</p>
</div>
<div class="section" id="cce_10_0458__section162661321104510"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0458__p1866524104512">If this check fails, contact technical support.</p>
<div class="section" id="cce_10_0458__en-us_topic_0000001442654321_section162661321104510"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0458__en-us_topic_0000001442654321_p17857165182113">Perform the pre-upgrade check again.</p>
<p id="cce_10_0458__en-us_topic_0000001442654321_p1866524104512">If it fails again, submit a service ticket to contact technical support.</p>
</div>
</div>
<div>

28
docs/cce/umn/cce_10_0476.html
View File

File diff suppressed because it is too large Load Diff

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

@ -1,9 +1,10 @@
<a name="cce_10_0479"></a><a name="cce_10_0479"></a>
<h1 class="topictitle1">cce-hpa-controller Restrictions</h1>
<div id="body0000001421382006"><div class="section" id="cce_10_0479__section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0479__p112379577523">Check whether the current cce-controller-hpa add-on has compatibility restrictions.</p>
<h1 class="topictitle1">cce-hpa-controller Limitations</h1>
<div id="body0000001421382006"><div class="section" id="cce_10_0479__en-us_topic_0000001421382006_section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0479__en-us_topic_0000001421382006_p112379577523">Check whether there are compatibility limitations between the current and target cce-controller-hpa add-on versions.</p>
</div>
<div class="section" id="cce_10_0479__section13523191085314"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0479__p13956103481011">The current cce-controller-hpa add-on has compatibility restrictions. An add-on that can provide metric APIs, for example, metric-server, must be installed in the cluster.</p>
<div class="section" id="cce_10_0479__en-us_topic_0000001421382006_section13523191085314"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0479__en-us_topic_0000001421382006_p740913396272">There are compatibility limitations between the current and target versions of the cce-controller-hpa add-on. To address this, install an add-on that provides metrics APIs, like metrics-server, in the cluster.</p>
<p id="cce_10_0479__en-us_topic_0000001421382006_p13956103481011">Install the metrics add-on in the cluster and try again.</p>
</div>
</div>
<div>

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

@ -1,9 +1,13 @@
<a name="cce_10_0484"></a><a name="cce_10_0484"></a>
<h1 class="topictitle1">Health of Worker Node Components</h1>
<div id="body0000001421064718"><div class="section" id="cce_10_0484__section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0484__p112379577523">Check whether the container runtime and network components on the worker nodes are healthy.</p>
<div id="body0000001421064718"><div class="section" id="cce_10_0484__en-us_topic_0000001421064718_section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0484__en-us_topic_0000001421064718_p112379577523">Check whether the container runtime and network components on the worker nodes are healthy.</p>
</div>
<div class="section" id="cce_10_0484__section13523191085314"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0484__p13956103481011">If a worker node component malfunctions, log in to the node to check the status of the component and rectify the fault.</p>
<div class="section" id="cce_10_0484__en-us_topic_0000001421064718_section13523191085314"><h4 class="sectiontitle">Solution</h4><ul id="cce_10_0484__en-us_topic_0000001421064718_ul196721478317"><li id="cce_10_0484__en-us_topic_0000001421064718_li1767217471935">Issue 1: CNI Agent is not active.<p id="cce_10_0484__en-us_topic_0000001421064718_p158895476381"><a name="cce_10_0484__en-us_topic_0000001421064718_li1767217471935"></a><a name="en-us_topic_0000001421064718_li1767217471935"></a>If your cluster version is earlier than v1.17.17, or you are using the underlay_ipvlan network model and your cluster version is later than v1.17.17, log in to the node and run the <strong id="cce_10_0484__en-us_topic_0000001421064718_b988934783814">systemctl status canal</strong> command to check the status of canal. If you encounter an error, run the <strong id="cce_10_0484__en-us_topic_0000001421064718_b198895477385">systemctl restart canal</strong> command and check the status again.</p>
<p id="cce_10_0484__en-us_topic_0000001421064718_p185971114131016">If you are using the VPC or Cloud Native 2.0 network model and your cluster version is later than v1.17.17, log in to the node and run the <strong id="cce_10_0484__en-us_topic_0000001421064718_b1637241092119">systemctl status yangtse</strong> command to check the status of Yangtse. If you encounter an error, run the <strong id="cce_10_0484__en-us_topic_0000001421064718_b437215104210">systemctl restart yangtse</strong> command and check the status again.</p>
</li><li id="cce_10_0484__en-us_topic_0000001421064718_li61022071156">Issue 2: kube-proxy is not active.<p id="cce_10_0484__en-us_topic_0000001421064718_p1759325902311"><a name="cce_10_0484__en-us_topic_0000001421064718_li61022071156"></a><a name="en-us_topic_0000001421064718_li61022071156"></a>Log in to the node and run the <strong id="cce_10_0484__en-us_topic_0000001421064718_b1959210599233">systemctl is-active kube-proxy</strong> command to check the status of kube-proxy. If you encounter an error, run the <strong id="cce_10_0484__en-us_topic_0000001421064718_b9593859102316">systemctl restart kube-proxy</strong> command and check the status again.</p>
<p id="cce_10_0484__en-us_topic_0000001421064718_p19943863248">If the fault persists, reset the node. For details, see <a href="cce_10_0003.html">Resetting a Node</a>.</p>
</li></ul>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0485"></a><a name="cce_10_0485"></a>
<h1 class="topictitle1">Health of Master Node Components</h1>
<div id="body0000001456366278"><div class="section" id="cce_10_0485__section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0485__p112379577523">Check whether the Kubernetes, container runtime, and network components of the master nodes are healthy.</p>
<div id="body0000001456366278"><div class="section" id="cce_10_0485__en-us_topic_0000001456366278_section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0485__en-us_topic_0000001456366278_p112379577523">Check whether cluster components such as the Kubernetes component, container runtime component, and network component are running properly before the upgrade.</p>
</div>
<div class="section" id="cce_10_0485__section13523191085314"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0485__p13956103481011">If a master node component malfunctions, contact technical support.</p>
<div class="section" id="cce_10_0485__en-us_topic_0000001456366278_section13523191085314"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0485__en-us_topic_0000001456366278_p742811113618">Perform the pre-upgrade check again.</p>
<p id="cce_10_0485__en-us_topic_0000001456366278_p13956103481011">If it fails again, submit a service ticket to contact technical support.</p>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0501"></a><a name="cce_10_0501"></a>
<h1 class="topictitle1">Historical Upgrade Records</h1>
<div id="body0000001622338738"><div class="section" id="cce_10_0501__section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0501__p1495525585">Check whether the source version of the cluster is earlier than v1.11 and the target version is later than v1.23.</p>
<div id="body0000001622338738"><div class="section" id="cce_10_0501__en-us_topic_0000001622338738_section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0501__en-us_topic_0000001622338738_p1495525585">Check the historical upgrade records of the cluster and confirm that the current version of the cluster meets the requirements for upgrading to the target version.</p>
</div>
<div class="section" id="cce_10_0501__section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0501__p058610113312">If the source version of the cluster is earlier than v1.11, it is risky to upgrade the cluster to a version later than v1.23. In this case, contact technical support.</p>
<div class="section" id="cce_10_0501__en-us_topic_0000001622338738_section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0501__en-us_topic_0000001622338738_p261718112394">Upgrading your cluster from an earlier version can be risky and may result in this issue. To avoid this, it is recommended that you migrate the cluster beforehand.</p>
<p id="cce_10_0501__en-us_topic_0000001622338738_p058610113312">If you still want to proceed with the cluster upgrade, submit a service ticket to contact technical support for evaluation.</p>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0502"></a><a name="cce_10_0502"></a>
<h1 class="topictitle1">CIDR Block of the Cluster Management Plane</h1>
<div id="body0000001670618637"><div class="section" id="cce_10_0502__section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0502__p1495525585">Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.</p>
<div id="body0000001670618637"><div class="section" id="cce_10_0502__en-us_topic_0000001670618637_section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0502__en-us_topic_0000001670618637_p1495525585">Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.</p>
</div>
<div class="section" id="cce_10_0502__section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0502__p23861220144616">If the CIDR block of the cluster management plane is different from that configured on the backbone network, contact technical support.</p>
<div class="section" id="cce_10_0502__en-us_topic_0000001670618637_section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0502__en-us_topic_0000001670618637_p5670643194111">The CIDR block of the management plane has been modified in your region. As a result, the CIDR block of the management plane and that of the backbone network are inconsistent.</p>
<p id="cce_10_0502__en-us_topic_0000001670618637_p23861220144616">Submit a service ticket to contact technical support to modify the settings, and recheck the configurations.</p>
</div>
</div>
<div>

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

@ -1,10 +1,10 @@
<a name="cce_10_0504"></a><a name="cce_10_0504"></a>
<h1 class="topictitle1">Nodes' System Parameters</h1>
<div id="body0000001675961621"><div class="section" id="cce_10_0504__section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0504__p1495525585">Check whether the default system parameter settings on your nodes are modified.</p>
<div id="body0000001675961621"><div class="section" id="cce_10_0504__en-us_topic_0000001675961621_section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0504__en-us_topic_0000001675961621_p1495525585">Check whether the default system parameter settings on your nodes are modified.</p>
</div>
<div class="section" id="cce_10_0504__section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0504__p0747125216233">If the MTU value of the bond0 network on your BMS node is not the default value 1500, this check item failed.</p>
<p id="cce_10_0504__p210705922620">Non-default parameter settings may lead to service packet loss. Change them back to the default values.</p>
<div class="section" id="cce_10_0504__en-us_topic_0000001675961621_section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0504__en-us_topic_0000001675961621_p0747125216233">If the MTU value of the bond0 network on your BMS node is not the default value 1500, this check item failed.</p>
<p id="cce_10_0504__en-us_topic_0000001675961621_p210705922620">Non-default parameter settings may lead to service packet loss. Change them back to the default values.</p>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0507"></a><a name="cce_10_0507"></a>
<h1 class="topictitle1">Node Swap</h1>
<div id="body0000001676281801"><div class="section" id="cce_10_0507__section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0507__p1495525585">Check whether swap has been enabled on cluster nodes.</p>
<div id="body0000001676281801"><div class="section" id="cce_10_0507__en-us_topic_0000001676281801_section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0507__en-us_topic_0000001676281801_p1495525585">Check whether swap has been enabled on CCE nodes.</p>
</div>
<div class="section" id="cce_10_0507__section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0507__p495182410235">By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of disabling this function. Run the <strong id="cce_10_0507__b4281165610499">swapoff -a</strong> command to disable swap.</p>
<div class="section" id="cce_10_0507__en-us_topic_0000001676281801_section1451562220117"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0507__en-us_topic_0000001676281801_p14296835184619">By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of disabling this function.</p>
<p id="cce_10_0507__en-us_topic_0000001676281801_p495182410235">If there is no impact, run the <strong id="cce_10_0507__en-us_topic_0000001676281801_b4281165610499">swapoff -a</strong> command to disable swap and perform the check again.</p>
</div>
</div>
<div>

75
docs/cce/umn/cce_10_0508.html Normal file
View File

@ -0,0 +1,75 @@
<a name="cce_10_0508"></a><a name="cce_10_0508"></a>
<h1 class="topictitle1">nginx-ingress Upgrade</h1>
<div id="body0000001710199777"><div class="section" id="cce_10_0508__section76841181396"><h4 class="sectiontitle">Check Items</h4><ul id="cce_10_0508__ul163819465252"><li id="cce_10_0508__li12381746142517">Check item 1: Check whether there is an Nginx Ingress route whose ingress type is not specified (<strong id="cce_10_0508__b184899485261">kubernetes.io/ingress.class: nginx</strong> is not added to <strong id="cce_10_0508__b84891748172611">annotations</strong>) in the cluster.</li><li id="cce_10_0508__li132081848162519">Check item 2: Check whether the DefaultBackend Service specified by the Nginx Ingress Controller backend is available.</li></ul>
</div>
<div class="section" id="cce_10_0508__section18775201773016"><a name="cce_10_0508__section18775201773016"></a><a name="section18775201773016"></a><h4 class="sectiontitle">Fault Locating</h4><p id="cce_10_0508__p1404152415276"><strong id="cce_10_0508__b196250221531">For Check Item 1</strong></p>
<p id="cce_10_0508__en-us_topic_0000001659189684_p149811003016">For Nginx Ingress, check the YAML. If the ingress type is not specified in the YAML file and the ingress is managed by the Nginx Ingress Controller, the ingress is at risk. </p>
<ol id="cce_10_0508__en-us_topic_0000001659189684_ol11526201531211"><li id="cce_10_0508__cce_faq_00430_li177352415163"><span>Check the Ingress type.</span><p><div class="p" id="cce_10_0508__cce_faq_00430_p175448512165">Run the following command:<pre class="screen" id="cce_10_0508__cce_faq_00430_screen8197154313243">kubectl get ingress &lt;ingress-name&gt; -oyaml | grep -E ' kubernetes.io/ingress.class: | ingressClassName:'</pre>
<ul id="cce_10_0508__cce_faq_00430_ul3905353102420"><li id="cce_10_0508__cce_faq_00430_li1872018417254">Fault scenario: If the command output is empty, the Ingress type is not specified.</li><li id="cce_10_0508__cce_faq_00430_li11773102015174">Normal scenario: The command output is not empty, indicating that the Ingress type has been specified by <strong id="cce_10_0508__cce_faq_00430_b14573103412297">annotations</strong> or <strong id="cce_10_0508__cce_faq_00430_b18757136122913">ingressClassName</strong>.<p id="cce_10_0508__cce_faq_00430_p1593022211170"><span><img id="cce_10_0508__cce_faq_00430_image16676201821713" src="en-us_image_0000001981275653.png"></span></p>
</li></ul>
</div>
</p></li><li id="cce_10_0508__cce_faq_00430_li56502032131211"><span>Ensure that the Ingress is managed by the Nginx Ingress Controller. The LoadBalancer Ingresses are not affected by this issue.</span><p><ul id="cce_10_0508__cce_faq_00430_ul17621181381814"><li id="cce_10_0508__cce_faq_00430_li1162117132189">For clusters of v1.19, confirm this issue using <strong id="cce_10_0508__cce_faq_00430_b7997452193014">managedFields</strong>.<pre class="screen" id="cce_10_0508__cce_faq_00430_screen1714335831816">kubectl get ingress &lt;ingress-name&gt; -oyaml | grep 'manager: nginx-ingress-controller'</pre>
<p id="cce_10_0508__cce_faq_00430_p5836155781714"><span><img id="cce_10_0508__cce_faq_00430_image168361457171717" src="en-us_image_0000001981275657.png"></span></p>
</li><li id="cce_10_0508__cce_faq_00430_li3621413161816">For clusters of other versions, check the logs of the Nginx Ingress Controller pod.<pre class="screen" id="cce_10_0508__cce_faq_00430_screen1232816121915"> kubectl logs -nkube-system cceaddon-nginx-ingress-controller-545db6b4f7-bv74t | grep 'updating Ingress status'</pre>
<p id="cce_10_0508__cce_faq_00430_p186373269187"><span><img id="cce_10_0508__cce_faq_00430_image263772641816" src="en-us_image_0000001981435505.png"></span></p>
</li></ul>
<p id="cce_10_0508__cce_faq_00430_p059415271181">If the fault persists, contact technical support personnel.</p>
</p></li></ol>
<p id="cce_10_0508__p147351424273"><strong id="cce_10_0508__b1628152835313">For Check Item 2</strong></p>
<ol id="cce_10_0508__ol18116183214285"><li id="cce_10_0508__li1811612323280"><span>View the DefaultBackend Service in the namespace where the Nginx Ingress Controller is deployed.</span><p><pre class="screen" id="cce_10_0508__screen13699195913315">kubectl get pod cceaddon-nginx-ingress-<i><span class="varname" id="cce_10_0508__varname46501538195311">&lt;controller-name&gt;</span></i>-controller-*** -n <i><span class="varname" id="cce_10_0508__varname11962144285312">&lt;namespace&gt;</span></i> -oyaml | grep 'default-backend'</pre>
<p id="cce_10_0508__p5642241103713">In the preceding command, <em id="cce_10_0508__i12761134319220">cceaddon-nginx-ingress-&lt;controller-name&gt;-controller-***</em> is the controller pod name, <em id="cce_10_0508__i17482154712216">&lt;controller-name&gt;</em> is the controller name specified during add-on installation, and <em id="cce_10_0508__i9673152431">&lt;namespace&gt;</em> is the namespace where the controller is deployed.</p>
<p id="cce_10_0508__p28531613339">Command output:</p>
<pre class="screen" id="cce_10_0508__screen1157916595321">- '--default-backend-service=<i><span class="varname" id="cce_10_0508__varname4513164855312">&lt;namespace&gt;</span></i>/<i><span class="varname" id="cce_10_0508__varname62195235314">&lt;backend-svc-name&gt;</span></i>'</pre>
<p id="cce_10_0508__p162311656113313">In the preceding command, <em id="cce_10_0508__i764919241832">&lt;backend-svc-name&gt;</em> is the name of the DefaultBackend Service for the Nginx Ingress Controller.</p>
</p></li><li id="cce_10_0508__li2843182413916"><span>Check whether the DefaultBackend Service of the Nginx Ingress Controller is available.</span><p><pre class="screen" id="cce_10_0508__screen469419113514">kubectl get svc <i><span class="varname" id="cce_10_0508__varname789715418567">&lt;backend-svc-name&gt;</span></i> -n <i><span class="varname" id="cce_10_0508__varname957715711567">&lt;namespace&gt;</span></i></pre>
<p id="cce_10_0508__p77091259360">If the Service is unavailable, this check item failed.</p>
</p></li></ol>
</div>
<div class="section" id="cce_10_0508__section8973926101120"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0508__p17629183393519"><strong id="cce_10_0508__b088118476538">For Check Item 1</strong></p>
<p id="cce_10_0508__en-us_topic_0000001659189684_p13346153819912">Add an annotation to the Nginx ingresses as follows:</p>
<pre class="screen" id="cce_10_0508__en-us_topic_0000001659189684_screen93945694">kubectl annotate ingress &lt;ingress-name&gt; kubernetes.io/ingress.class=nginx</pre>
<div class="notice" id="cce_10_0508__en-us_topic_0000001659189684_note034817533515"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0508__en-us_topic_0000001659189684_p434815583516">There is no need to add this annotation to LoadBalancer ingresses. <a href="#cce_10_0508__section18775201773016">Verify</a> that these ingresses are managed by Nginx Ingress Controller.</p>
</div></div>
<p id="cce_10_0508__p64774443359"><strong id="cce_10_0508__b15470125017537">For Check Item 2</strong></p>
<div class="p" id="cce_10_0508__p18271347173710">Create the DefaultBackend Service again.<ul id="cce_10_0508__ul10268210388"><li id="cce_10_0508__li6301153512388">If a custom DefaultBackend Service has been specified in the default 404 service configuration during add-on installation, create the same Service.</li><li id="cce_10_0508__li13262023382">If the default DefaultBackend Service is used during add-on installation, the re-created YAML example is as follows:<pre class="screen" id="cce_10_0508__screen1948212387435">apiVersion: v1
kind: Service
metadata:
name: cceaddon-nginx-ingress-<i><span class="varname" id="cce_10_0508__varname16591155052">&lt;controller-name&gt;</span></i>-default-backend # <i><span class="varname" id="cce_10_0508__varname14403621195720">&lt;controller-name&gt;</span></i> is the controller name.
namespace: kube-system
labels:
app: nginx-ingress-<i><span class="varname" id="cce_10_0508__varname754571311510">&lt;controller-name&gt;</span></i>
app.kubernetes.io/managed-by: Helm
chart: nginx-ingress-<i><span class="varname" id="cce_10_0508__varname1650410357">&lt;version&gt;</span></i> # <i><span class="varname" id="cce_10_0508__varname1557833675716">&lt;version&gt;</span></i> is the add-on version.
component: default-backend
heritage: Helm
release: cceaddon-nginx-ingress-<i><span class="varname" id="cce_10_0508__varname146776511558">&lt;controller-name&gt;</span></i>
annotations:
meta.helm.sh/release-name: cceaddon-nginx-ingress-<i><span class="varname" id="cce_10_0508__varname18195551856">&lt;controller-name&gt;</span></i>
meta.helm.sh/release-namespace: <i><span class="varname" id="cce_10_0508__varname67781110980">kube-system</span></i> # Namespace where the add-on is installed
spec:
ports:
- name: http
protocol: TCP
port: 80
targetPort: http
selector:
app: nginx-ingress-<i><span class="varname" id="cce_10_0508__varname123506231062">&lt;controller-name&gt;</span></i>
component: default-backend
release: cceaddon-nginx-ingress-<i><span class="varname" id="cce_10_0508__varname1796135712711">&lt;controller-name&gt;</span></i>
type: ClusterIP
sessionAffinity: None
ipFamilies:
- IPv4
ipFamilyPolicy: SingleStack
internalTrafficPolicy: Cluster</pre>
</li></ul>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0550.html">Troubleshooting for Pre-upgrade Check Exceptions</a></div>
</div>
</div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0510"></a><a name="cce_10_0510"></a>
<h1 class="topictitle1">containerd Pod Restart Risks</h1>
<div id="body0000001662120186"><div class="section" id="cce_10_0510__section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0510__p4249288588">Check whether the service pods running on a containerd node are restarted when containerd is upgraded.</p>
<div id="body0000001662120186"><div class="section" id="cce_10_0510__en-us_topic_0000001662120186_section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0510__en-us_topic_0000001662120186_p4249288588">Check whether the service pods running on a containerd node are restarted when containerd is upgraded.</p>
</div>
<div class="section" id="cce_10_0510__section1468413994110"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0510__p76841796418">Upgrade the cluster when the impact on services is controllable (for example, during off-peak hours) to minimize the impact. If you need help, contact O&amp;M personnel.</p>
<div class="section" id="cce_10_0510__en-us_topic_0000001662120186_section1468413994110"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0510__en-us_topic_0000001662120186_p5624217204816">containerd on your node may need to be restarted. To minimize the impact on service containers, upgrade the cluster during controllable times, such as off-peak hours.</p>
<p id="cce_10_0510__en-us_topic_0000001662120186_p76841796418">If you need help, submit a service ticket to contact O&amp;M personnel.</p>
</div>
</div>
<div>

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

@ -1,9 +1,10 @@
<a name="cce_10_0512"></a><a name="cce_10_0512"></a>
<h1 class="topictitle1">GPU Pod Rebuild Risks</h1>
<div id="body0000001710199781"><div class="section" id="cce_10_0512__section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0512__p4249288588">Check whether GPU service pods are rebuilt in a cluster when kubelet is restarted during the upgrade of the cluster.</p>
<div id="body0000001710199781"><div class="section" id="cce_10_0512__en-us_topic_0000001710199781_section76841181396"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0512__en-us_topic_0000001710199781_p4249288588">Check whether GPU service pods are rebuilt in a cluster when kubelet is restarted during the upgrade of the cluster.</p>
</div>
<div class="section" id="cce_10_0512__section1468413994110"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0512__p76841796418">Upgrade the cluster when the impact on services is controllable (for example, during off-peak hours) to minimize the impact. If you need help, contact O&amp;M personnel.</p>
<div class="section" id="cce_10_0512__en-us_topic_0000001710199781_section1468413994110"><h4 class="sectiontitle">Solution</h4><p id="cce_10_0512__en-us_topic_0000001710199781_p1982664214919">Upgrade the cluster when the impact on services is controllable (for example, during off-peak hours) to minimize the impact.</p>
<p id="cce_10_0512__en-us_topic_0000001710199781_p76841796418">If you need help, submit a service ticket to contact O&amp;M personnel.</p>
</div>
</div>
<div>

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