removing blank line

Reviewed-by: Gode, Sebastian <sebastian.gode@t-systems.com>
Reviewed-by: Tino Schreiber <tino.schreiber@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>

.spectral.yaml

@@ -0,0 +1,11 @@
+rules:
+  path-starts-with-slash-no-spaces:
+    description: Path must start with / and contain no spaces
+    message: "Path '{{property}}' must start with '/' and must not contain spaces"
+    severity: error
+    given: $.paths
+    then:
+      field: "@key"
+      function: pattern
+      functionOptions:
+        match: "^\\/[^\\s]*$"

.yamllint

@@ -0,0 +1,17 @@
+# .yamllint
+extends: default
+
+yaml-files:
+  - '*.yaml'
+  - '*.yml'
+
+rules:
+  line-length:
+    max: 120
+    level: warning
+  indentation:
+    spaces: 2        # number of spaces per indent level
+    indent-sequences: consistent  # or true/false/whatever
+    level: error
+  document-start:
+    level: warning

docs/bms/api-ref/ALL_META.TXT.json

@@ -1168,7 +1168,7 @@
 		"code":"64",
 		"des":"This API is used to query BMS flavors.The flavors you obtained using this API are all the flavors in the system. The flavors whose names starting with physical are BMS fl",
 		"doc_type":"api",
-		"kw":"QueryingBMS Flavors,BMS Flavor Query (OpenStack Nova APIs),API Reference",
+		"kw":"Querying BMS Flavors,BMS Flavor Query (OpenStack Nova APIs),API Reference",
 		"search_title":"",
 		"metedata":[
 			{
@@ -1177,7 +1177,7 @@
 				"opensource":"false;true"
 			}
 		],
-		"title":"QueryingBMS Flavors",
+		"title":"Querying BMS Flavors",
 		"githuburl":""
 	},
 	{

docs/bms/api-ref/CLASS.TXT.json

@@ -569,7 +569,7 @@
 	{
 		"desc":"This API is used to query BMS flavors.The flavors you obtained using this API are all the flavors in the system. The flavors whose names starting with physical are BMS fl",
 		"product_code":"bms",
-		"title":"QueryingBMS Flavors",
+		"title":"Querying BMS Flavors",
 		"uri":"en-us_topic_0000002374101029.html",
 		"doc_type":"api",
 		"p_code":"63",

docs/bms/api-ref/en-us_topic_0000002340063012.html

@@ -66,7 +66,7 @@
 <td class="cellrowborder" valign="top" width="18.75%" headers="mcps1.3.4.2.1.5.1.3 "><p id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_p15406610135318">String</p>
 </td>
 <td class="cellrowborder" valign="top" width="41.010000000000005%" headers="mcps1.3.4.2.1.5.1.4 "><p id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_p1040881015311">Specifies the flavor ID.</p>
-<p id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_p7741128113511">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_text9235625735">BMS</span><span id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_text32351725734"></span><span id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_text1726413615226"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">QueryingBMS Flavors</a> API.</p>
+<p id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_p7741128113511">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_text9235625735">BMS</span><span id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_text32351725734"></span><span id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_text1726413615226"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">Querying BMS Flavors</a> API.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_row058811420527"><td class="cellrowborder" valign="top" width="19.85%" headers="mcps1.3.4.2.1.5.1.1 "><p id="EN-US_TOPIC_0000002340063012__en-us_topic_0053158693_p5413201085313">name</p>

docs/bms/api-ref/en-us_topic_0000002340063032.html

@@ -4,7 +4,7 @@
 <div id="body8662426"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="en-us_topic_0000002374101029.html">QueryingBMS Flavors</a></strong><br>
+<li class="ulchildlink"><strong><a href="en-us_topic_0000002374101029.html">Querying BMS Flavors</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="en-us_topic_0000002374260893.html">Querying Details About a BMS Flavor</a></strong><br>
 </li>

docs/bms/api-ref/en-us_topic_0000002340063052.html

@@ -40,7 +40,7 @@
 </div>
 <div class="section" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_section61879170105534"><h4 class="sectiontitle">Request Parameters</h4><p id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_p740355415918">None</p>
 </div>
-<div class="section" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_section558544482614"><h4 class="sectiontitle">Example Request</h4><div class="p" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_p10597356103517">Deleting tags from a <span id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_text198292661016">BMS</span><span id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_text1582192631015"></span><span id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_text128252611106"></span> (ID: 53206ed0-56de-4d6b-b7ee-ffc62ca26f43)<div class="codecoloring" codetype="Java" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_screen464516211288"><div class="highlight"><table class="highlighttable"><tr><td class="linenos"><div class="linenodiv"><pre><span class="normal">1</span></pre></div></td><td class="code"><div><pre><span></span><span class="n">DELETE</span><span class="w"> </span><span class="n">https</span><span class="p">:</span><span class="c1">//{ECS Endpoint}/v2.1/bbf1946d374b44a0a2a95533562ba954/servers/53206ed0-56de-4d6b-b7ee-ffc62ca26f43/tags</span>
+<div class="section" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_section558544482614"><h4 class="sectiontitle">Example Request</h4><div class="p" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_p10597356103517">Deleting tags from a <span id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_text8992548111218">BMS</span><span id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_text15803221423"></span><span id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_text205161451161216"></span> (ID: 53206ed0-56de-4d6b-b7ee-ffc62ca26f43)<div class="codecoloring" codetype="Java" id="EN-US_TOPIC_0000002340063052__en-us_topic_0060410928_screen464516211288"><div class="highlight"><table class="highlighttable"><tr><td class="linenos"><div class="linenodiv"><pre><span class="normal">1</span></pre></div></td><td class="code"><div><pre><span></span><span class="n">DELETE</span><span class="w"> </span><span class="n">https</span><span class="p">:</span><span class="c1">//{ECS Endpoint}/v2.1/bbf1946d374b44a0a2a95533562ba954/servers/53206ed0-56de-4d6b-b7ee-ffc62ca26f43/tags</span>
 </pre></div></td></tr></table></div>
 </div>
 </div>

docs/bms/api-ref/en-us_topic_0000002340222784.html

@@ -1,7 +1,7 @@
 <a name="EN-US_TOPIC_0000002340222784"></a><a name="EN-US_TOPIC_0000002340222784"></a>
 
-<h1 class="topictitle1">Querying Details About a <span id="en-us_topic_0053158707_text1027592519399">BMS</span><span id="en-us_topic_0053158707_text15747146155714"></span><span id="en-us_topic_0053158707_text140512416526"></span></h1>
-<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_section11242227"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p58120972">This API is used to query details about a <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1255371312571">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text655311138571"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text3250194116527"></span> based on the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1616071111576">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1968164914717"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text17913193345212"></span> ID.</p>
+<h1 class="topictitle1">Querying Details About a <span id="en-us_topic_0053158707_text82769982712">BMS</span><span id="en-us_topic_0053158707_text464425125113"></span><span id="en-us_topic_0053158707_text17210351154415"></span></h1>
+<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_section11242227"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p58120972">This API is used to query details about a <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text13300726142719">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text330072616275"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text13003268277"></span> based on the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1027592519399">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text9288151912716"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text18288111910277"></span> ID.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_section34071180"><h4 class="sectiontitle">URI</h4><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p60095679153449">GET /v2.1/{project_id}/servers/{server_id}</p>
 <p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p166491815184611"><a href="#EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_table17908225144614">Table 1</a> lists the parameters.</p>
@@ -26,7 +26,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.2 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p44882061">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p11568292">Specifies the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text4643191910575">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1164321920576"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1160810541523"></span> ID.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p11568292">Specifies the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1374115752718">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text974165702718"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text874195762714"></span> ID.</p>
 <p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p29791113277">You can obtain the BMS ID from the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_en-us_topic_0113746489_text895314101319">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_en-us_topic_0113746489_text1695320481317"></span> console or by calling the API <a href="en-us_topic_0000002340063012.html">Querying BMSs</a>.</p>
 </td>
 </tr>
@@ -54,7 +54,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="25.872587258725872%" headers="mcps1.3.5.2.1.4.1.2 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p17222571164727">Object</p>
 </td>
-<td class="cellrowborder" valign="top" width="51.28512851285129%" headers="mcps1.3.5.2.1.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p36377578">Specifies <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text16186172419575">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text61861241579"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text086211516530"></span> information. For details, see <a href="#EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_table6149040">Table 2</a>.</p>
+<td class="cellrowborder" valign="top" width="51.28512851285129%" headers="mcps1.3.5.2.1.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p36377578">Specifies <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text106691417152810">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text11670121720283"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text126701017192816"></span> information. For details, see <a href="#EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_table6149040">Table 2</a>.</p>
 </td>
 </tr>
 </tbody>
@@ -73,7 +73,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="25.94%" headers="mcps1.3.5.3.2.4.1.2 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p58359570">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.5.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p29504734">Specifies the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text7317182665718">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text133181026145719"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text84953103537"></span> name.</p>
+<td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.5.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p29504734">Specifies the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1777322332818">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1877422372818"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1477482392813"></span> name.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_row64216018"><td class="cellrowborder" valign="top" width="22.99%" headers="mcps1.3.5.3.2.4.1.1 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p34114937">id</p>
@@ -126,7 +126,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="25.94%" headers="mcps1.3.5.3.2.4.1.2 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p64678211">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.5.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p4443775">Specifies the ID of the tenant owning the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text2081565516571">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text6815185511572"></span>. The value is in UUID format.</p>
+<td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.5.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p4443775">Specifies the ID of the tenant owning the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text5484324182912">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text17484524112916"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1484524172910"></span>. The value is in UUID format.</p>
 <p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p3869154710124">This parameter specifies the same meaning as <strong id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_b77201547172520">project_id</strong>.</p>
 </td>
 </tr>
@@ -164,7 +164,7 @@
 <td class="cellrowborder" valign="top" width="25.94%" headers="mcps1.3.5.3.2.4.1.2 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p56232959">Map&lt;String,Array of <a href="#EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_table1656029015527">address</a> objects&gt;</p>
 </td>
 <td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.5.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p57420266">Specifies <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1415758145810">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text51579895819"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1892589115415"></span> network addresses. Specifies the VPC used by the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text165043251041">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text4504325344"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text0739191765416"></span>.</p>
-<ul id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_ul1374698716"><li id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_li19748786115"><strong id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_b4513174116384">key</strong>: indicates the ID of the VPC used by the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text11581151634614">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text32761321124610"></span>.</li><li id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_li417552217213"><strong id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_b438874712486">value</strong> indicates the VPC details.</li></ul>
+<ul id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_ul1374698716"><li id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_li19748786115"><strong id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_b4513174116384">key</strong>: indicates the ID of the VPC used by the <span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1012201113306">BMS</span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text1212171113305"></span><span id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_text17121811183017"></span>.</li><li id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_li417552217213"><strong id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_b438874712486">value</strong> indicates the VPC details.</li></ul>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_row61793156165818"><td class="cellrowborder" valign="top" width="22.99%" headers="mcps1.3.5.3.2.4.1.1 "><p id="EN-US_TOPIC_0000002340222784__en-us_topic_0053158707_p39189735165818">security_groups</p>

docs/bms/api-ref/en-us_topic_0000002340222808.html

@@ -27,7 +27,7 @@
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.2 "><p id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0057973064_p60507121">Yes</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0057973064_p2129750">Specifies the flavor ID.</p>
-<p id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_p1461914516495">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0053158674_text374914110111">BMS</span><span id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0053158674_text1749131818"></span><span id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0053158674_text2096916710416"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">QueryingBMS Flavors</a> API.</p>
+<p id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_p1461914516495">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0053158674_text374914110111">BMS</span><span id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0053158674_text1749131818"></span><span id="EN-US_TOPIC_0000002340222808__en-us_topic_0114885743_en-us_topic_0053158674_text2096916710416"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">Querying BMS Flavors</a> API.</p>
 </td>
 </tr>
 </tbody>

docs/bms/api-ref/en-us_topic_0000002340222816.html

@@ -29,7 +29,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.4.2.4.1.2 "><p id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_p64913614151519">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_p23511349151519">Specifies the <span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_text16563976299145">BMS</span><span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_text13363426949145"></span><span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_text10498469789145"></span> ID.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.4.2.4.1.3 "><p id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_p23511349151519">Specifies the <span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_text650552035611">BMS</span><span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_text750520202567"></span><span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_text1750542012566"></span> ID.</p>
 <p id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_p29791113277">You can obtain the BMS ID from the <span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_en-us_topic_0113746489_text895314101319">BMS</span><span id="EN-US_TOPIC_0000002340222816__en-us_topic_0053158611_en-us_topic_0113746489_text1695320481317"></span> console or by calling the API <a href="en-us_topic_0000002340063012.html">Querying BMSs</a>.</p>
 </td>
 </tr>

docs/bms/api-ref/en-us_topic_0000002374101009.html

@@ -1,6 +1,6 @@
 <a name="EN-US_TOPIC_0000002374101009"></a><a name="EN-US_TOPIC_0000002374101009"></a>
 
-<h1 class="topictitle1">Querying Details About <span id="en-us_topic_0053158679_text15957111672810">BMS</span><span id="en-us_topic_0053158679_text89571016162815"></span><span id="en-us_topic_0053158679_text12957316202813"></span>s</h1>
+<h1 class="topictitle1">Querying Details About <span id="en-us_topic_0053158679_text1027592519399">BMS</span><span id="en-us_topic_0053158679_text4856929649"></span><span id="en-us_topic_0053158679_text1254014314258"></span>s</h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_section33716833"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_p67077904152933">This API is used to query details about <span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text892812331348">BMS</span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text1968164914717"></span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text131001882253"></span>s.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_section29822855153557"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_ul45877015153613"><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_li4809898812125">The query result returned by this API includes both ECSs and BMSs. You need to filter out the BMSs using the flavor used to create the BMSs or the tags added to the BMSs during BMS creation.</li><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_li53072464153613">If the image is used as the search criteria, other search criteria and pagination criteria are not supported. If both the image and other filter criteria are specified, the image filter criterion is used. If the query criteria do not contain the image filter criterion, API functions are not restricted.</li></ul>
@@ -66,7 +66,7 @@
 <td class="cellrowborder" valign="top" width="18.75%" headers="mcps1.3.4.2.1.5.1.3 "><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_p15406610135318">String</p>
 </td>
 <td class="cellrowborder" valign="top" width="41.010000000000005%" headers="mcps1.3.4.2.1.5.1.4 "><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_p1040881015311">Specifies the flavor ID.</p>
-<p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_p7741128113511">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_text9235625735">BMS</span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_text32351725734"></span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_text1726413615226"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">QueryingBMS Flavors</a> API.</p>
+<p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_p7741128113511">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_text9235625735">BMS</span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_text32351725734"></span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_text1726413615226"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">Querying BMS Flavors</a> API.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_row058811420527"><td class="cellrowborder" valign="top" width="19.85%" headers="mcps1.3.4.2.1.5.1.1 "><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158693_p5413201085313">name</p>
@@ -449,7 +449,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="25.94%" headers="mcps1.3.6.3.2.4.1.2 "><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_p43090708192944">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.6.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_p55603620192944">Specifies the status of the<span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_text129271650165813">BMS</span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_text10927150135811"></span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text141991929162811"></span> host.</p>
+<td class="cellrowborder" valign="top" width="51.07000000000001%" headers="mcps1.3.6.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_p55603620192944">Specifies the status of the host that accommodates the <span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text96155695712">BMS</span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text46105655713"></span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text186135610577"></span>.</p>
 <ul id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_ul30670539192944"><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_li7599401192944"><strong id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_b842352706183126">UP</strong>: The host is normal.</li><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_li1285751192944"><strong id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_b1498018510183149">UNKNOWN</strong>: The host status is unknown.</li><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_li11571767192944"><strong id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_b842352706183156">DOWN</strong>: the host is abnormal.</li><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_li37037040192944"><strong id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_b842352706183211">MAINTENANCE</strong>: The host is being maintained.</li><li id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_li64897909192944">Empty string: There is no <span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_text184142536587">BMS</span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_text1841435385810"></span><span id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_text5546034112815"></span> host information.</li></ul>
 <p id="EN-US_TOPIC_0000002374101009__en-us_topic_0053158679_en-us_topic_0053158707_p47210269192944">This is a new parameter in micro version 2.16.</p>
 </td>

docs/bms/api-ref/en-us_topic_0000002374101029.html

@@ -1,6 +1,6 @@
 <a name="EN-US_TOPIC_0000002374101029"></a><a name="EN-US_TOPIC_0000002374101029"></a>
 
-<h1 class="topictitle1">Querying<span id="en-us_topic_0053158684_text68606276113">BMS</span><span id="en-us_topic_0053158684_text1947382572"></span> Flavors</h1>
+<h1 class="topictitle1">Querying <span id="en-us_topic_0053158684_text68606276113">BMS</span><span id="en-us_topic_0053158684_text1947382572"></span> Flavors</h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_section57769674"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_p6915811">This API is used to query <span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text1310274425711">BMS</span><span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text12102184410575"></span><span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text844715419398"></span> flavors.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_section60580832213029"><h4 class="sectiontitle">Constraints</h4><p id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_p91137314513">The flavors you obtained using this API are all the flavors in the system. The flavors whose names starting with <strong id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_b774618481833">physical</strong> are <span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text2011614481575">BMS</span><span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text9116154865713"></span><span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text163229599390"></span> flavors and can be used to create <span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text8552165010578">BMS</span><span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text35525504572"></span><span id="EN-US_TOPIC_0000002374101029__en-us_topic_0053158684_text1862149408"></span>s.</p>

docs/bms/api-ref/en-us_topic_0000002374260885.html

@@ -136,7 +136,7 @@
 <td class="cellrowborder" valign="top" width="24.43%" headers="mcps1.3.7.3.2.4.1.2 "><p id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_p43431730185333">String</p>
 </td>
 <td class="cellrowborder" valign="top" width="51.74999999999999%" headers="mcps1.3.7.3.2.4.1.3 "><p id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_p5719410617654">Specifies the key and value pair of the metadata.</p>
-<ul id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_ul1049861817191"><li id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_li1413563592416">Each key or value contains fewer than 256 characters.</li><li id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_li2073683916242">The value does not support the following special characters:<p id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_p1821315403243"><a name="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_li2073683916242"></a><a name="en-us_topic_0053158712_li2073683916242"></a>\"</p>
+<ul id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_ul1049861817191"><li id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_li1413563592416">Each key or value contains fewer than 256 characters and cannot be left blank.</li><li id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_li2073683916242">The value does not support the following special characters:<p id="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_p1821315403243"><a name="EN-US_TOPIC_0000002374260885__en-us_topic_0053158712_li2073683916242"></a><a name="en-us_topic_0053158712_li2073683916242"></a>\"</p>
 </li></ul>
 </td>
 </tr>

docs/bms/api-ref/en-us_topic_0000002374260889.html

@@ -64,7 +64,7 @@
 </table>
 </div>
 
-<div class="tablenoborder"><a name="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_table22651992144025"></a><a name="en-us_topic_0053158696_table22651992144025"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_table22651992144025" frame="border" border="1" rules="all"><caption><b>Table 2 </b><strong id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_b355592318">address</strong> parameter structure description</caption><thead align="left"><tr id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_row15576094144025"><th align="left" class="cellrowborder" valign="top" width="25.41%" id="mcps1.3.6.3.2.4.1.1"><p id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_p355273111016">Parameter</p>
+<div class="tablenoborder"><a name="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_table22651992144025"></a><a name="en-us_topic_0053158696_table22651992144025"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_table22651992144025" frame="border" border="1" rules="all"><caption><b>Table 2 </b><strong id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_b1932703555">address</strong> parameter structure description</caption><thead align="left"><tr id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_row15576094144025"><th align="left" class="cellrowborder" valign="top" width="25.41%" id="mcps1.3.6.3.2.4.1.1"><p id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_p355273111016">Parameter</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="23.419999999999998%" id="mcps1.3.6.3.2.4.1.2"><p id="EN-US_TOPIC_0000002374260889__en-us_topic_0053158696_p16554153131017">Type</p>
 </th>

docs/bms/api-ref/en-us_topic_0000002374260893.html

@@ -1,6 +1,6 @@
 <a name="EN-US_TOPIC_0000002374260893"></a><a name="EN-US_TOPIC_0000002374260893"></a>
 
-<h1 class="topictitle1">Querying Details About a <span id="en-us_topic_0053158674_text6424161564610">BMS</span><span id="en-us_topic_0053158674_text1242451564617"></span><span id="en-us_topic_0053158674_text54243150461"></span> Flavor</h1>
+<h1 class="topictitle1">Querying Details About a <span id="en-us_topic_0053158674_text68606276113">BMS</span><span id="en-us_topic_0053158674_text611312477019"></span><span id="en-us_topic_0053158674_text858612512404"></span> Flavor</h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_section64833508"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_p40261524">This API is used to query details about a <span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text14401156606">BMS</span><span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text1947382572"></span><span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text183631256124010"></span> flavor, such as the flavor name, CPU cores, and memory.</p>
 </div>
 <div class="section" id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_section46630661"><h4 class="sectiontitle">URI</h4><p id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_p6133425516420">GET /v2.1/{project_id}/flavors/{flavor_id}</p>
@@ -27,7 +27,7 @@
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.2 "><p id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_p60507121">Yes</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.4.2.4.1.3 "><p id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_p2129750">Specifies the flavor ID.</p>
-<p id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_p1153834112450">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text374914110111">BMS</span><span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text1749131818"></span><span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text2096916710416"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">QueryingBMS Flavors</a> API.</p>
+<p id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_p1153834112450">You can obtain the flavor ID from the <span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text374914110111">BMS</span><span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text1749131818"></span><span id="EN-US_TOPIC_0000002374260893__en-us_topic_0053158674_text2096916710416"></span> console or using the <a href="en-us_topic_0000002374101029.html#EN-US_TOPIC_0000002374101029">Querying BMS Flavors</a> API.</p>
 </td>
 </tr>
 </tbody>

docs/bms/api-ref/en-us_topic_0000002374260901.html

@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Attaching an EVS Disk to a <span id="en-us_topic_0053158614_text8992548111218">BMS</span><span id="en-us_topic_0053158614_text15803221423"></span><span id="en-us_topic_0053158614_text205161451161216"></span></h1>
 <div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_section53922917165259"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_p5680132165259">This API is used to attach an EVS disk to a <span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text3616164295413">BMS</span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text8616204205420"></span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text2616204215547"></span>.</p>
 </div>
-<div class="section" id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_section64211377173223"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_ul45433461184122"><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li65034385184126">A bootable disk cannot be attached to a BMS.</li><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li11902061184128">A disk cannot be attached to a <span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text1787395995413">BMS</span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text787317594541"></span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text12873135985417"></span> when the <span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text61177810">BMS</span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text191874111"></span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text41107713"></span> is in the <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706104522">PAUSED</strong> state, which is specified using the <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706104549">OS-EXT-STS:vm_state</strong> parameter.</li><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li5370819184122">Only a shared disk or a disk in the <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706104614">available</strong> state can be attached to a BMS.</li><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li917464102326">Only EVS disks whose device type is <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706105525">SCSI</strong> can be attached to a BMS.</li></ul>
+<div class="section" id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_section64211377173223"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_ul45433461184122"><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li65034385184126">A bootable disk cannot be attached to a BMS.</li><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li11902061184128">A disk cannot be attached to a <span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text1787395995413">BMS</span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text787317594541"></span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text12873135985417"></span> when the <span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text1501203611317">BMS</span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text45011636153117"></span><span id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_text1550115360315"></span> is in the <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706104522">PAUSED</strong> state, which is specified using the <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706104549">OS-EXT-STS:vm_state</strong> parameter.</li><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li5370819184122">Only a shared disk or a disk in the <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706104614">available</strong> state can be attached to a BMS.</li><li id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_li917464102326">Only EVS disks whose device type is <strong id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_b842352706105525">SCSI</strong> can be attached to a BMS.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_section51121191165259"><h4 class="sectiontitle">URI</h4><p id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_p63141473165259">POST /v2.1/{project_id}/servers/{server_id}/os-volume_attachments</p>
 <p id="EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_p468643935114"><a href="#EN-US_TOPIC_0000002374260901__en-us_topic_0053158614_table12701051155110">Table 1</a> lists the parameters.</p>

docs/bms/api-ref/en-us_topic_0106040941.html

@@ -104,7 +104,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="59%" headers="mcps1.3.5.3.2.5.1.4 "><p id="EN-US_TOPIC_0106040941__p6589115412241">Specifies the <span id="EN-US_TOPIC_0106040941__text141115463223">BMS</span><span id="EN-US_TOPIC_0106040941__text124111446182219"></span> name.</p>
 <p id="EN-US_TOPIC_0106040941__p205901254132419">Value range:</p>
-<ul id="EN-US_TOPIC_0106040941__ul115905548245"><li id="EN-US_TOPIC_0106040941__li467912154411">The value can contain a maximum of 63 characters consisting of letters (case-insensitive), digits, underscores (_), hyphens (-), and periods (.).</li><li id="EN-US_TOPIC_0106040941__li205901454102415">If more than one <span id="EN-US_TOPIC_0106040941__text1183394942216">BMS</span><span id="EN-US_TOPIC_0106040941__text8833124972220"></span> is to be created, suffixes similar to <strong id="EN-US_TOPIC_0106040941__b842352706144049">-0000</strong> will be automatically added to the end of the <span id="EN-US_TOPIC_0106040941__text101132053132210">BMS</span><span id="EN-US_TOPIC_0106040941__text1611315312229"></span> names during the <span id="EN-US_TOPIC_0106040941__text2028613121563">BMS</span><span id="EN-US_TOPIC_0106040941__text72860120618"></span> creation. In this case, the BMS name contains 1 to 58 characters.</li></ul>
+<ul id="EN-US_TOPIC_0106040941__ul115905548245"><li id="EN-US_TOPIC_0106040941__li467912154411">The value can contain 1 to 63 characters, consisting of letters, digits, underscores (_), hyphens (-), and periods (.).</li><li id="EN-US_TOPIC_0106040941__li205901454102415">If more than one <span id="EN-US_TOPIC_0106040941__text1183394942216">BMS</span><span id="EN-US_TOPIC_0106040941__text8833124972220"></span> is to be created, suffixes similar to <strong id="EN-US_TOPIC_0106040941__b842352706144049">-0000</strong> will be automatically added to the end of the <span id="EN-US_TOPIC_0106040941__text101132053132210">BMS</span><span id="EN-US_TOPIC_0106040941__text1611315312229"></span> names during the <span id="EN-US_TOPIC_0106040941__text2028613121563">BMS</span><span id="EN-US_TOPIC_0106040941__text72860120618"></span> creation. In this case, the BMS name contains 1 to 58 characters.</li></ul>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0106040941__row13447228112013"><td class="cellrowborder" valign="top" width="13%" headers="mcps1.3.5.3.2.5.1.1 "><p id="EN-US_TOPIC_0106040941__p1744719286208">metadata</p>
@@ -166,7 +166,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.5.3.2.5.1.3 "><p id="EN-US_TOPIC_0106040941__p2121950193514">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="59%" headers="mcps1.3.5.3.2.5.1.4 "><p id="EN-US_TOPIC_0106040941__p183831662478">Specifies the name of a key pair. This is an extended attribute. To log in to a <span id="EN-US_TOPIC_0106040941__text681273122316">BMS</span> using an SSH key pair, set the value to the name of an existing private key.</p>
+<td class="cellrowborder" valign="top" width="59%" headers="mcps1.3.5.3.2.5.1.4 "><p id="EN-US_TOPIC_0106040941__p183831662478">Specifies the name of a key pair. This is an extended attribute. To log in to a <span id="EN-US_TOPIC_0106040941__text39535427610">BMS</span><span id="EN-US_TOPIC_0106040941__text69536421564"></span><span id="EN-US_TOPIC_0106040941__text109531042063"></span> using an SSH key pair, set the value to the name of an existing private key.</p>
 <p id="EN-US_TOPIC_0106040941__p2721134615450">You can create a key pair using the <a href="en-us_topic_0000002340222820.html">Creating or Importing an SSH Key Pair (Native OpenStack API)</a> API, or query existing key pairs using the <a href="en-us_topic_0000002374101041.html">Querying SSH Key Pairs (Native OpenStack API)</a> API.</p>
 <p id="EN-US_TOPIC_0106040941__p121011469384">Constraints:</p>
 <ul id="EN-US_TOPIC_0106040941__ul81019468382"><li id="EN-US_TOPIC_0106040941__li176396585388">If both <strong id="EN-US_TOPIC_0106040941__b84235270616385">key_name</strong> and <strong id="EN-US_TOPIC_0106040941__b84235270616388">user_data</strong> are specified, <strong id="EN-US_TOPIC_0106040941__b1204886164163819">user_data</strong> only injects user data.</li></ul>
@@ -251,7 +251,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="59%" headers="mcps1.3.5.3.2.5.1.4 "><p id="EN-US_TOPIC_0106040941__p19300107125018">Specifies data disk details of the <span id="EN-US_TOPIC_0106040941__text3707635182515">BMS</span><span id="EN-US_TOPIC_0106040941__text16707133510253"></span>. Each data structure represents a data disk to be created. For details, see <a href="#EN-US_TOPIC_0106040941__table16541153834413">Table 8</a>.</p>
 <p id="EN-US_TOPIC_0106040941__p1630019710504">Constraints:</p>
-<p id="EN-US_TOPIC_0106040941__p6554115142519">A maximum of 40 EVS disks (including the system disk and data disks) can be attached to a <span id="EN-US_TOPIC_0106040941__text821724155811">BMS</span><span id="EN-US_TOPIC_0106040941__text142152485818"></span>.</p>
+<p id="EN-US_TOPIC_0106040941__p6554115142519">A maximum of 40 EVS disks (including the system disk and data disks) can be attached to a <span id="EN-US_TOPIC_0106040941__text1154773913253">BMS</span><span id="EN-US_TOPIC_0106040941__text8547339132514"></span>.</p>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0106040941__row78434565482"><td class="cellrowborder" valign="top" width="13%" headers="mcps1.3.5.3.2.5.1.1 "><p id="EN-US_TOPIC_0106040941__p28434560482">extendparam</p>
@@ -358,7 +358,7 @@
 <td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.5.5.2.5.1.3 "><p id="EN-US_TOPIC_0106040941__p29019273159">String</p>
 </td>
 <td class="cellrowborder" valign="top" width="57.99999999999999%" headers="mcps1.3.5.5.2.5.1.4 "><p id="EN-US_TOPIC_0106040941__p1890162741513">Specifies a security group ID, which takes effect for all NICs configured for the <span id="EN-US_TOPIC_0106040941__text1528634763119">BMS</span><span id="EN-US_TOPIC_0106040941__text6286154783110"></span>.</p>
-<ul id="EN-US_TOPIC_0106040941__ul3918152155712"><li id="EN-US_TOPIC_0106040941__li11918524574">If this parameter is not specified, the default security group is bound to the <span id="EN-US_TOPIC_0106040941__text17858133219">BMS</span><span id="EN-US_TOPIC_0106040941__text386171123220"></span>.</li><li id="EN-US_TOPIC_0106040941__li1985895345718">If this parameter is required (in UUID format), use the ID of an existing security group. For details about how to obtain existing security groups, see "Querying Security Groups" in <em id="EN-US_TOPIC_0106040941__i31449211678">Virtual Private Cloud </em><em id="EN-US_TOPIC_0106040941__i21440211072">API</em><em id="EN-US_TOPIC_0106040941__i21447211577"></em><em id="EN-US_TOPIC_0106040941__i314419211716"> Reference</em>.</li></ul>
+<ul id="EN-US_TOPIC_0106040941__ul3918152155712"><li id="EN-US_TOPIC_0106040941__li11918524574">If this parameter is not specified, the default security group is bound to the <span id="EN-US_TOPIC_0106040941__text17858133219">BMS</span><span id="EN-US_TOPIC_0106040941__text386171123220"></span>.</li><li id="EN-US_TOPIC_0106040941__li1985895345718">If this parameter is required (in UUID format), use the ID of an existing security group. For details about how to obtain existing security groups, see "Querying Security Groups" in <em id="EN-US_TOPIC_0106040941__i31449211678">Virtual Private Cloud</em> <em id="EN-US_TOPIC_0106040941__i21440211072">API</em><em id="EN-US_TOPIC_0106040941__i21447211577"></em> <em id="EN-US_TOPIC_0106040941__i314419211716">Reference</em>.</li></ul>
 </td>
 </tr>
 </tbody>

docs/bms/api-ref/en-us_topic_0107654006.html

@@ -666,7 +666,8 @@
 </td>
 <td class="cellrowborder" valign="top" width="24.740000000000002%" headers="mcps1.3.7.11.2.4.1.2 "><p id="EN-US_TOPIC_0107654006__p24362133165012">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="51.5%" headers="mcps1.3.7.11.2.4.1.3 "><p id="EN-US_TOPIC_0107654006__p27175732165012">Specifies the IP address assignment mode. This is an extended attribute.</p>
+<td class="cellrowborder" valign="top" width="51.5%" headers="mcps1.3.7.11.2.4.1.3 "><p id="EN-US_TOPIC_0107654006__p27175732165012">Specifies the IP address allocation type. This is an extended attribute.</p>
+<ul id="EN-US_TOPIC_0107654006__ul3596123318119"><li id="EN-US_TOPIC_0107654006__li1559643311113"><strong id="EN-US_TOPIC_0107654006__b126031019154316">fixed</strong>: A fixed private IP address is allocated to the BMS.</li><li id="EN-US_TOPIC_0107654006__li359653331115"><strong id="EN-US_TOPIC_0107654006__b1632917297420">floating</strong>: A floating IP address is allocated to the BMS.</li></ul>
 </td>
 </tr>
 <tr id="EN-US_TOPIC_0107654006__row866710425267"><td class="cellrowborder" valign="top" width="23.76%" headers="mcps1.3.7.11.2.4.1.1 "><p id="EN-US_TOPIC_0107654006__p850932318373">OS-EXT-IPS:port_id</p>

docs/bms/api-ref/en-us_topic_0107658564.html

@@ -1,9 +1,9 @@
 <a name="EN-US_TOPIC_0107658564"></a><a name="EN-US_TOPIC_0107658564"></a>
 
-<h1 class="topictitle1">Attaching an EVS Disk to a <span id="text1027592519399">BMS</span><span id="text1210135115116"></span><span id="text183331113458"></span></h1>
-<div id="body1524140134038"><div class="section" id="EN-US_TOPIC_0107658564__section324443512515"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0107658564__p1141412350518">This API is used to attach EVS disks to a <span id="EN-US_TOPIC_0107658564__text721194017514">BMS</span><span id="EN-US_TOPIC_0107658564__text1968164914717"></span> as data disks after the <span id="EN-US_TOPIC_0107658564__text1871347193412">BMS</span><span id="EN-US_TOPIC_0107658564__text171377143414"></span> is created if existing data disks are insufficient or cannot meet requirements.</p>
+<h1 class="topictitle1">Attaching an EVS Disk to a <span id="text3801317756">BMS</span><span id="text464425125113"></span><span id="text17210351154415"></span></h1>
+<div id="body1524140134038"><div class="section" id="EN-US_TOPIC_0107658564__section324443512515"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0107658564__p1141412350518">This API is used to attach EVS disks to a <span id="EN-US_TOPIC_0107658564__text1027592519399">BMS</span><span id="EN-US_TOPIC_0107658564__text103892321159"></span><span id="EN-US_TOPIC_0107658564__text938923211510"></span> as data disks after the <span id="EN-US_TOPIC_0107658564__text18418043855">BMS</span><span id="EN-US_TOPIC_0107658564__text841814431453"></span><span id="EN-US_TOPIC_0107658564__text2418943654"></span> is created if existing data disks are insufficient or cannot meet requirements.</p>
 </div>
-<div class="section" id="EN-US_TOPIC_0107658564__section9247103511511"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0107658564__ul941413351651"><li id="EN-US_TOPIC_0107658564__li6219103112326">EVS disks cannot be attached to a BMS in a batch.</li><li id="EN-US_TOPIC_0107658564__li1855353817812">A maximum of 40 EVS disks can be attached to a <span id="EN-US_TOPIC_0107658564__text8654625117">BMS</span><span id="EN-US_TOPIC_0107658564__text1604655115"></span>.</li><li id="EN-US_TOPIC_0107658564__li841415351951">A bootable disk cannot be attached to a BMS.</li><li id="EN-US_TOPIC_0107658564__li94151835755">A disk cannot be attached to a <span id="EN-US_TOPIC_0107658564__text1571649175118">BMS</span><span id="EN-US_TOPIC_0107658564__text57104965115"></span> in the <strong id="EN-US_TOPIC_0107658564__b8703416172">PAUSED</strong> state, which is specified using the <strong id="EN-US_TOPIC_0107658564__b16703719179">OS-EXT-STS:vm_state</strong> parameter.</li><li id="EN-US_TOPIC_0107658564__li141514351157">Only a shared disk or a disk in the <strong id="EN-US_TOPIC_0107658564__b842352706104614">available</strong> state can be attached to a BMS.</li><li id="EN-US_TOPIC_0107658564__li54151535655">Only EVS disks whose device type is <strong id="EN-US_TOPIC_0107658564__b842352706105525">SCSI</strong> can be attached to a BMS.</li></ul>
+<div class="section" id="EN-US_TOPIC_0107658564__section9247103511511"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0107658564__ul941413351651"><li id="EN-US_TOPIC_0107658564__li6219103112326">EVS disks cannot be attached to a BMS in a batch.</li><li id="EN-US_TOPIC_0107658564__li1855353817812">A maximum of 40 EVS disks can be attached to a <span id="EN-US_TOPIC_0107658564__text1234125418511">BMS</span><span id="EN-US_TOPIC_0107658564__text1346541156"></span><span id="EN-US_TOPIC_0107658564__text1634165413512"></span>.</li><li id="EN-US_TOPIC_0107658564__li841415351951">A bootable disk cannot be attached to a BMS.</li><li id="EN-US_TOPIC_0107658564__li94151835755">A disk cannot be attached to a <span id="EN-US_TOPIC_0107658564__text48819111765">BMS</span><span id="EN-US_TOPIC_0107658564__text14881171118612"></span><span id="EN-US_TOPIC_0107658564__text788117111563"></span> in the <strong id="EN-US_TOPIC_0107658564__b8703416172">PAUSED</strong> state, which is specified using the <strong id="EN-US_TOPIC_0107658564__b16703719179">OS-EXT-STS:vm_state</strong> parameter.</li><li id="EN-US_TOPIC_0107658564__li141514351157">Only a shared disk or a disk in the <strong id="EN-US_TOPIC_0107658564__b842352706104614">available</strong> state can be attached to a BMS.</li><li id="EN-US_TOPIC_0107658564__li54151535655">Only EVS disks whose device type is <strong id="EN-US_TOPIC_0107658564__b842352706105525">SCSI</strong> can be attached to a BMS.</li></ul>
 </div>
 <div class="section" id="EN-US_TOPIC_0107658564__section10254193517515"><h4 class="sectiontitle">URI</h4><p id="EN-US_TOPIC_0107658564__p5841957114915">POST /v1/{project_id}/baremetalservers/{server_id}/attachvolume</p>
 <p id="EN-US_TOPIC_0107658564__p16151182351115"><a href="#EN-US_TOPIC_0107658564__table228013461112">Table 1</a> lists the parameters.</p>

docs/bms/api-ref/en-us_topic_0113746488.html

@@ -1,6 +1,6 @@
 <a name="EN-US_TOPIC_0113746488"></a><a name="EN-US_TOPIC_0113746488"></a>
 
-<h1 class="topictitle1"><span id="text8992548111218">BMS</span><span id="text15803221423"></span><span id="text13501134163519"></span> Lifecycle Management</h1>
+<h1 class="topictitle1"><span id="text1599144017517">BMS</span><span id="text109954011517"></span><span id="text205161451161216"></span> Lifecycle Management</h1>
 <div id="body1527065098172"></div>
 <div>
 <ul class="ullinks">

docs/bms/api-ref/en-us_topic_0129082263.html

@@ -28,7 +28,7 @@
 </div>
 </div>
 
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0129082263__table49939793" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Parameters for querying BMS details</caption><thead align="left"><tr id="EN-US_TOPIC_0129082263__row40936054"><th align="left" class="cellrowborder" valign="top" width="18.81188118811881%" id="mcps1.3.3.2.5.1.1"><p id="EN-US_TOPIC_0129082263__p27486043">Parameter</p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0129082263__table49939793" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Query parameters</caption><thead align="left"><tr id="EN-US_TOPIC_0129082263__row40936054"><th align="left" class="cellrowborder" valign="top" width="18.81188118811881%" id="mcps1.3.3.2.5.1.1"><p id="EN-US_TOPIC_0129082263__p27486043">Parameter</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15.841584158415841%" id="mcps1.3.3.2.5.1.2"><p id="EN-US_TOPIC_0129082263__p11776988">Mandatory</p>
 </th>

docs/bms/api-ref/en-us_topic_0131326852.html

@@ -51,7 +51,7 @@
 </div>
 <div class="section" id="EN-US_TOPIC_0131326852__section22265380"><h4 class="sectiontitle">Request Parameters</h4><p id="EN-US_TOPIC_0131326852__p1220010297370">None</p>
 </div>
-<div class="section" id="EN-US_TOPIC_0131326852__section18817143116520"><h4 class="sectiontitle">Example Request</h4><div class="p" id="EN-US_TOPIC_0131326852__p169011833115715">Querying BMS flavor details and extended flavor information in the <strong id="EN-US_TOPIC_0131326852__b1783110216111">az1</strong> AZ<div class="codecoloring" codetype="Java" id="EN-US_TOPIC_0131326852__screen145810814132"><div class="highlight"><table class="highlighttable"><tr><td class="linenos"><div class="linenodiv"><pre><span class="normal">1</span></pre></div></td><td class="code"><div><pre><span></span><span class="n">GET</span><span class="w"> </span><span class="n">https</span><span class="p">:</span><span class="c1">//{BMS Endpoint}/v1/c685484a8cc2416b97260938705deb65/baremetalservers/flavors?availability_zone=az1</span>
+<div class="section" id="EN-US_TOPIC_0131326852__section18817143116520"><h4 class="sectiontitle">Example Request</h4><div class="p" id="EN-US_TOPIC_0131326852__p169011833115715">Querying BMS flavor details and extended flavor information in the <strong id="EN-US_TOPIC_0131326852__b101614313597">az1</strong> AZ<div class="codecoloring" codetype="Java" id="EN-US_TOPIC_0131326852__screen145810814132"><div class="highlight"><table class="highlighttable"><tr><td class="linenos"><div class="linenodiv"><pre><span class="normal">1</span></pre></div></td><td class="code"><div><pre><span></span><span class="n">GET</span><span class="w"> </span><span class="n">https</span><span class="p">:</span><span class="c1">//{BMS Endpoint}/v1/c685484a8cc2416b97260938705deb65/baremetalservers/flavors?availability_zone=az1</span>
 </pre></div></td></tr></table></div>
 </div>
 </div>

docs/bms/api-ref/en-us_topic_0131356391.html

@@ -1,6 +1,6 @@
 <a name="EN-US_TOPIC_0131356391"></a><a name="EN-US_TOPIC_0131356391"></a>
 
-<h1 class="topictitle1">Starting <span id="text266731472811">BMS</span><span id="text7802430369"></span><span id="text549771912419"></span>s</h1>
+<h1 class="topictitle1">Starting <span id="text1027592519399">BMS</span><span id="text1799111044611"></span><span id="text1968164914717"></span>s</h1>
 <div id="body1536986565099"><div class="section" id="EN-US_TOPIC_0131356391__section18389930"><h4 class="sectiontitle">Function</h4><p id="EN-US_TOPIC_0131356391__p16246551">This API is used to start <span id="EN-US_TOPIC_0131356391__text13951163912614">BMS</span><span id="EN-US_TOPIC_0131356391__text5951183912269"></span><span id="EN-US_TOPIC_0131356391__text89511139122611"></span>s of specified IDs. You can start a maximum of 1000 BMSs at a time.</p>
 <div class="note" id="EN-US_TOPIC_0131356391__note06811723135712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0131356391__p7681123165713">This is an asynchronous API. Calling the API successfully indicates that the task is delivered successfully. To check whether the task is successful, call the <a href="en-us_topic_0118696596.html">Querying Task Statuses</a> API.</p>
 </div></div>

docs/bms/api-ref/en-us_topic_0131356393.html

@@ -79,8 +79,9 @@
 </td>
 <td class="cellrowborder" valign="top" width="24.437556244375564%" headers="mcps1.3.3.4.2.5.1.3 "><p id="EN-US_TOPIC_0131356393__p59240589141926">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="39.28607139286072%" headers="mcps1.3.3.4.2.5.1.4 "><p id="EN-US_TOPIC_0131356393__p33758406141926">Specifies the BMS stop type.</p>
-<ul id="EN-US_TOPIC_0131356393__ul251735085216"><li id="EN-US_TOPIC_0131356393__li105171350125220"><strong id="EN-US_TOPIC_0131356393__b276545204513">SOFT</strong>: soft stop (invalid)</li><li id="EN-US_TOPIC_0131356393__li1751745015524"><strong id="EN-US_TOPIC_0131356393__b425544614512">HARD</strong>: hard stop (default)</li></ul>
+<td class="cellrowborder" valign="top" width="39.28607139286072%" headers="mcps1.3.3.4.2.5.1.4 "><p id="EN-US_TOPIC_0131356393__p33758406141926">Specifies how BMSs are stopped. The default value is <strong id="EN-US_TOPIC_0131356393__b25324389812">HARD</strong>.</p>
+<p id="EN-US_TOPIC_0131356393__p18197223814">Value:</p>
+<p id="EN-US_TOPIC_0131356393__p1127517317416"><strong id="EN-US_TOPIC_0131356393__b93754241771">HARD</strong>: forcible stop</p>
 </td>
 </tr>
 </tbody>

docs/cce/umn/cce_01_0300.html

@@ -8,7 +8,33 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_01_0300__row1055918131549"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p165591013125418">2025-09-12</p>
+<tbody><tr id="cce_01_0300__row69530118317"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p164617189313">2025-12-30</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p1159438173119">Add:</p>
+<ul id="cce_01_0300__ul25923810310"><li id="cce_01_0300__li185953819317">Added <a href="cce_bulletin_0105.html">Kubernetes 1.33 Release Notes</a>.</li><li id="cce_01_0300__li0892436153316">Added <a href="cce_10_1062.html">Obtaining Pod Network Interfaces in a CCE Turbo Cluster</a>, <a href="cce_10_1063.html">Deploying Hubble for DataPlane V2 Network Observability</a> and <a href="cce_10_1064.html">Enabling Observability for cilium-agent in a Cluster with DataPlane V2 Enabled</a>.</li><li id="cce_01_0300__li686113193414">Added <a href="cce_10_1088.html">Modifying the Node Scale-In Concurrency Settings</a>.</li><li id="cce_01_0300__li171425313415">Added <a href="cce_10_1027.html">Switching the AOM Instance Connected to Grafana</a>.</li><li id="cce_01_0300__li198713463417">Added <a href="cce_10_1060.html">Add-on Upgrade Checks</a>.</li><li id="cce_01_0300__li151091759347">Added <a href="cce_10_0556.html">System Agencies</a> and <a href="cce_10_1069.html">Custom Agencies</a>.</li></ul>
+<p id="cce_01_0300__p18670125403915">Update:</p>
+<ul id="cce_01_0300__ul624365714405"><li id="cce_01_0300__li156811043114811">Updated <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_01_0300__li106221415165118">Supported the creation of clusters of v1.33. Updated <a href="cce_10_0405.html">Patch Version Release Notes</a> and <a href="cce_10_0476.html">Node OSs</a>.</li><li id="cce_01_0300__li3855818115819">Updated <a href="cce_10_0012.html">Creating a Node Pool</a>.</li><li id="cce_01_0300__li1537013385113">Updated <a href="cce_10_0653.html">Updating a Node Pool</a> and <a href="cce_10_0652.html">Managing Node Pool Configurations</a>.</li><li id="cce_01_0300__li18249174619313">Updated <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a>.</li><li id="cce_01_0300__li8243165712405">Supported the Editing Reclaim Policy and Synchronizing PVC capacity, Updated <a href="cce_10_0374.html">Storage</a>.</li></ul>
+</td>
+</tr>
+<tr id="cce_01_0300__row12906854912"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p14906954214">2025-12-17</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p49969164218">Add:</p>
+<ul id="cce_01_0300__ul999631617219"><li id="cce_01_0300__li159969161923">Added <a href="cce_10_0387.html">Adding a Secondary VPC CIDR Block for a Cluster</a></li></ul>
+</td>
+</tr>
+<tr id="cce_01_0300__row0450154865616"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p19808154710245">2025-11-06</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p4808144792419">Update:</p>
+<ul id="cce_01_0300__ul176161854580"><li id="cce_01_0300__li1161625125819">Updated the <strong id="cce_01_0300__b1798215131">"</strong>Mapping between OS and Container Storage Rootfs" in <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</li></ul>
+</td>
+</tr>
+<tr id="cce_01_0300__row194411208441"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p594412015441">2025-10-16</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p99447205442">Add:</p>
+<ul id="cce_01_0300__ul1451911135810"><li id="cce_01_0300__li74518117582">Added <a href="cce_10_0408.html">Optimizing Node System Parameters</a>.</li></ul>
+</td>
+</tr>
+<tr id="cce_01_0300__row1055918131549"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p165591013125418">2025-09-12</p>
 </td>
 <td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p8808123612548">Add:</p>
 <ul id="cce_01_0300__ul6808113614540"><li id="cce_01_0300__li1180893615416">Added <a href="cce_bulletin_0104.html">Kubernetes 1.32 Release Notes</a>.</li><li id="cce_01_0300__li14475257175413">Added <a href="cce_10_0961.html">Cluster Access Overview</a>.</li><li id="cce_01_0300__li1057882518561">Added <a href="cce_10_0962.html">Cluster Management Overview</a>.</li><li id="cce_01_0300__li23891526145617">Added <a href="cce_10_1006.html">Using AppArmor to Confine Container Access to Resources</a>.</li><li id="cce_01_0300__li1058418519163">Added <a href="cce_10_0845.html">GPU Driver Version</a>.</li><li id="cce_01_0300__li2145182713568">Added <a href="cce_10_0643.html">GPU Virtualization</a>.</li><li id="cce_01_0300__li6978102710567">Added <a href="cce_10_1016.html">GPU Monitoring</a> , <a href="cce_10_0741.html">Comprehensive Monitoring of GPU, Virtualization, and Pod Resource Metrics</a>.</li><li id="cce_01_0300__li12195183213567">Added <a href="cce_10_1017.html">GPU Auto Scaling</a>, <a href="cce_10_0844.html">Configuring Workload Scaling Based on GPU Monitoring Metrics</a>.</li><li id="cce_01_0300__li5448105217338">Added <a href="cce_10_0779.html">GPU Fault Handling</a>.</li><li id="cce_01_0300__li103001722173511">Added <a href="cce_10_1077.html">Configuring a Security Group for a Workload in a CCE Turbo Cluster</a>, <a href="cce_10_1078.html">Comparison of Workload Security Group Configuration Methods</a>, <a href="cce_10_1079.html">Using Node Pool Settings to Bind the Default Security Group to Pods in the Node Pool</a>.</li><li id="cce_01_0300__li06903525610">Added <a href="cce_10_0857.html">Nginx Ingress Usage Suggestions</a>.</li><li id="cce_01_0300__li1691213352563">Supported the <strong id="cce_01_0300__b477112161114">NodeLocal DNSCache</strong> add-on. Added <a href="cce_10_0404.html">NodeLocal DNSCache</a>, <a href="cce_10_0362.html">Using NodeLocal DNSCache to Improve DNS Performance</a>,<p id="cce_01_0300__p129961300614"><a href="cce_10_0959.html">Changing the Default NodeLocal DNSCache Port</a>, <a href="cce_bestpractice_0351.html">Using NodeLocal DNSCache</a>.</p>

docs/cce/umn/cce_10_0003.html

@@ -61,13 +61,13 @@
 </td>
 <td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><p id="cce_10_0003__cce_10_0198_p324785392516">Select a disk for storing system components.</p>
 <ul id="cce_10_0003__cce_10_0198_ul566328102615"><li id="cce_10_0003__cce_10_0198_li3931805278"><strong id="cce_10_0003__cce_10_0198_b10296098794455">Data Disk</strong>: added for storing container runtime and kubelet components by default. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</li><li id="cce_10_0003__cce_10_0198_li20663168152611"><strong id="cce_10_0003__cce_10_0198_b6415056124102">System Disk</strong>: stores CCE resources such as downloaded images, ephemeral storage for containers, and container stdout logs. If the system disk is fully occupied, it will negatively affect the stability of the node.</li></ul>
-<div class="note" id="cce_10_0003__cce_10_0198_note6478170183416"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0003__cce_10_0198_p5437848286">In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, you can select a disk for storing system components. If <a href="cce_10_0132.html">CCE Node Problem Detector</a> is used, ensure that its version is 1.19.2 or later.</p>
+<div class="note" id="cce_10_0003__cce_10_0198_note6478170183416"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0003__cce_10_0198_p5437848286">In clusters v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, you can select a disk for storing system components. If <a href="cce_10_0132.html">CCE Node Problem Detector</a> is used, ensure that its version is 1.19.2 or later.</p>
 </div></div>
 </td>
 </tr>
 <tr id="cce_10_0003__cce_10_0198_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.1 "><p id="cce_10_0003__cce_10_0198_p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><ul id="cce_10_0003__cce_10_0198_ul184351126605"><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0003__cce_10_0198_b6314038347415">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_uicontrol79783262393"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_uicontrol179781326143914"><b>Data Disk</b></span>. <strong id="cce_10_0003__cce_10_0198_b7501571957415">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> </li><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><ul id="cce_10_0003__cce_10_0198_ul184351126605"><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li103472126407">At least one default data disk must be added for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol136828018182"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol1268215016180"><b>Data Disk</b></span>. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</li><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
 <p id="cce_10_0003__cce_10_0198_p3752312011">Click <strong id="cce_10_0003__cce_10_0198_b513813367555">Expand</strong> to configure <strong id="cce_10_0003__cce_10_0198_b13265825195416">Data Disk Space Allocation</strong>. This allocates space for container engines, images, and ephemeral storage to ensure their proper running. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
 <p id="cce_10_0003__cce_10_0198_p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0003__cce_10_0198_b16127101911540">Expand</strong> and select <strong id="cce_10_0003__cce_10_0198_b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. </p>
 </td>
@@ -86,7 +86,7 @@
 <tbody><tr id="cce_10_0003__en-us_topic_0000001244141037_row25394514014"><td class="cellrowborder" valign="top" width="23.66%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.1 "><p id="cce_10_0003__en-us_topic_0000001244141037_p25391859406">Resource Tag</p>
 </td>
 <td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p275333410342">You can add resource tags to classify resources. A maximum of eight resource tags can be added.</p>
-<p id="cce_10_0003__en-us_topic_0000001244141037_p117537347346">You can create <span class="uicontrol" id="cce_10_0003__en-us_topic_0000001244141037_uicontrol1975314345344"><b>predefined tags</b></span> on the TMS console. These tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency. </p>
+<p id="cce_10_0003__en-us_topic_0000001244141037_p117537347346">You can create <span class="uicontrol" id="cce_10_0003__uicontrol2091210163205"><b>predefined tags</b></span> on the TMS console. These tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency. </p>
 <p id="cce_10_0003__en-us_topic_0000001244141037_p16753133419348">CCE will automatically create the <strong id="cce_10_0003__b955154034416">CCE-Dynamic-Provisioning-Node=</strong><em id="cce_10_0003__i69622340388">Node ID</em> tag.</p>
 </td>
 </tr>
@@ -98,7 +98,7 @@
 </tr>
 <tr id="cce_10_0003__en-us_topic_0000001244141037_row115391952402"><td class="cellrowborder" valign="top" width="23.66%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.1 "><p id="cce_10_0003__en-us_topic_0000001244141037_p55391457404">Taint</p>
 </td>
-<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><div class="p" id="cce_10_0003__en-us_topic_0000001244141037_p2875141354415">This parameter is left blank by default. You can add taints to configure anti-affinity for the node. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters:<ul id="cce_10_0003__en-us_topic_0000001244141037_ul17274222121015"><li id="cce_10_0003__en-us_topic_0000001244141037_li227482216106"><strong id="cce_10_0003__b8739656480">Key</strong>: A key must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key.</li><li id="cce_10_0003__en-us_topic_0000001244141037_li7274112241020"><strong id="cce_10_0003__b535114014814">Value</strong>: A value must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</li><li id="cce_10_0003__en-us_topic_0000001244141037_li2274182211010"><strong id="cce_10_0003__b1793141415492">Effect</strong>: Available options are <strong id="cce_10_0003__b12931141444914">NoSchedule</strong>, <strong id="cce_10_0003__b1593116145494">PreferNoSchedule</strong>, and <strong id="cce_10_0003__b993111141495">NoExecute</strong>.</li></ul>
+<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><div class="p" id="cce_10_0003__en-us_topic_0000001244141037_p2875141354415">This parameter is left blank by default. You can add taints to configure anti-affinity for the node. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters:<ul id="cce_10_0003__en-us_topic_0000001244141037_ul17274222121015"><li id="cce_10_0003__en-us_topic_0000001244141037_li227482216106"><strong id="cce_10_0003__b1315422610202">Taint key</strong>: A key must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key.</li><li id="cce_10_0003__en-us_topic_0000001244141037_li7274112241020"><strong id="cce_10_0003__b06488303207">Taint value</strong>: A value must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</li><li id="cce_10_0003__en-us_topic_0000001244141037_li2274182211010"><strong id="cce_10_0003__b1793141415492">Effect</strong>: Available options are <strong id="cce_10_0003__b12931141444914">NoSchedule</strong>, <strong id="cce_10_0003__b1593116145494">PreferNoSchedule</strong>, and <strong id="cce_10_0003__b993111141495">NoExecute</strong>.</li></ul>
 <div class="notice" id="cce_10_0003__en-us_topic_0000001244141037_note77443231113"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><ul id="cce_10_0003__en-us_topic_0000001244141037_ul104271158181515"><li id="cce_10_0003__en-us_topic_0000001244141037_li042725811158">If taints are used, you must configure tolerations of pods. Otherwise, a scale-out may fail or pods cannot be scheduled onto the added nodes.</li><li id="cce_10_0003__en-us_topic_0000001244141037_li642712581152">After a node pool is created, you can click <strong id="cce_10_0003__b1941413124528">Edit</strong> to modify its configuration. The modification will be synchronized to all nodes in the node pool.</li></ul>
 </div></div>
 </div>
@@ -106,7 +106,7 @@
 </tr>
 <tr id="cce_10_0003__en-us_topic_0000001244141037_row155390520404"><td class="cellrowborder" valign="top" width="23.66%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.1 "><p id="cce_10_0003__en-us_topic_0000001244141037_p054015516406">Max. Pods</p>
 </td>
-<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p18611194424216">Maximum number of pods that can run on the node, including the default system pods. </p>
+<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p18611194424216">Maximum number of pods that can run on the node, including the default system pods.</p>
 <p id="cce_10_0003__en-us_topic_0000001244141037_p272611351429">This limit prevents the node from being overloaded with pods.</p>
 </td>
 </tr>

docs/cce/umn/cce_10_0007.html

@@ -105,7 +105,7 @@
 <ol id="cce_10_0007__en-us_topic_0107283638_ol1188315418332"><li id="cce_10_0007__en-us_topic_0107283638_li1388334119335"><span>Log in to the <span id="cce_10_0007__ph181175457307">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b11769141672918">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1588424111338"><span>Click the <strong id="cce_10_0007__b199921814299">Deployments</strong> tab and choose <strong id="cce_10_0007__b1799951820293">More</strong> &gt; <strong id="cce_10_0007__b17031913299">Disable/Enable Upgrade</strong> in the <strong id="cce_10_0007__b180719162911">Operation</strong> column of the workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1288404118334"><span>In the dialog box that is displayed, click <strong id="cce_10_0007__b1688621162914">Yes</strong>.</span></li></ol>
 </div>
 <div class="section" id="cce_10_0007__en-us_topic_0107283638_section5931193015488"><a name="cce_10_0007__en-us_topic_0107283638_section5931193015488"></a><a name="en-us_topic_0107283638_section5931193015488"></a><h4 class="sectiontitle"><span class="keyword" id="cce_10_0007__en-us_topic_0107283638_keyword141731324132418">Managing Labels</span></h4><p id="cce_10_0007__en-us_topic_0107283638_p13735621112611">Labels are key-value pairs and can be attached to workloads. You can manage and select workloads by labels. You can add labels to multiple workloads or a specified workload.</p>
-<ol id="cce_10_0007__en-us_topic_0107283638_ol6251112511220"><li id="cce_10_0007__en-us_topic_0107283638_li53548551606"><span>Log in to the <span id="cce_10_0007__ph3930134823011">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b1335702382915">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li22871259152611"><span>Click the <strong id="cce_10_0007__b1838219256291">Deployments</strong> tab and choose <strong id="cce_10_0007__b4383162552919">More</strong> &gt; <strong id="cce_10_0007__b2383225142917">Manage Label</strong> in the <strong id="cce_10_0007__b18383182512912">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li47616189277"><span>Click <span><img id="cce_10_0007__image3143153919236" src="en-us_image_0000002434239840.png"></span>, enter a key and a value, and click <span class="uicontrol" id="cce_10_0007__uicontrol1277618274294"><b>OK</b></span>.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note163751811133416"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0007__en-us_topic_0107283638_p03751011133411">A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</p>
+<ol id="cce_10_0007__en-us_topic_0107283638_ol6251112511220"><li id="cce_10_0007__en-us_topic_0107283638_li53548551606"><span>Log in to the <span id="cce_10_0007__ph3930134823011">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b1335702382915">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li22871259152611"><span>Click the <strong id="cce_10_0007__b1838219256291">Deployments</strong> tab and choose <strong id="cce_10_0007__b4383162552919">More</strong> &gt; <strong id="cce_10_0007__b2383225142917">Manage Label</strong> in the <strong id="cce_10_0007__b18383182512912">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li47616189277"><span>Click <span><img id="cce_10_0007__image3143153919236" src="en-us_image_0000002483959098.png"></span>, enter a key and a value, and click <span class="uicontrol" id="cce_10_0007__uicontrol1277618274294"><b>OK</b></span>.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note163751811133416"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0007__en-us_topic_0107283638_p03751011133411">A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</p>
 </div></div>
 </p></li></ol>
 </div>

docs/cce/umn/cce_10_0010.html

@@ -6,7 +6,7 @@
 <ul id="cce_10_0010__ul65247121891"><li id="cce_10_0010__li14524161214917">Cluster network structure (<strong id="cce_10_0010__b1593645719381"><a href="#cce_10_0010__section1131733719195">Cluster Network Structure</a></strong>): A cluster consists of multiple nodes, and each node runs multiple pods (containers). To ensure the communications between nodes, between nodes and pods, and between pods, a cluster requires:<ul id="cce_10_0010__ul4887053103815"><li id="cce_10_0010__li2887853183810"><strong id="cce_10_0010__b2088745343815">A node network</strong>: enables all nodes in a cluster to communicate with each other.</li><li id="cce_10_0010__li289312539384"><strong id="cce_10_0010__b0887155318385">A container network</strong>: enables all pods in a cluster to communicate with each other using IP addresses without NAT.</li><li id="cce_10_0010__li2887205333818"><strong id="cce_10_0010__b688755323810">A Service network</strong>: ensures Services in a cluster can be accessed by other pods or Services in that cluster through stable virtual IP addresses.</li></ul>
 </li><li id="cce_10_0010__li55241612391"><strong id="cce_10_0010__b1433181819395">Pod access in a cluster</strong>: Kubernetes provides Services (<a href="#cce_10_0010__section1860619221134">Service</a>) and ingresses (<a href="#cce_10_0010__section1248852094313">Ingress</a>) for pod access. This section summarizes common network access scenarios. You can select the appropriate scenario based on site requirements. For details about the network access scenarios, see <a href="#cce_10_0010__section1286493159">Access Scenarios</a>.</li></ul>
 <div class="section" id="cce_10_0010__section1131733719195"><a name="cce_10_0010__section1131733719195"></a><a name="section1131733719195"></a><h4 class="sectiontitle">Cluster Network Structure</h4><p id="cce_10_0010__p1299218814417">Cluster networks are the core of Kubernetes. They ensure that containers in a cluster can communicate with each other and with external systems. There are:</p>
-<ul id="cce_10_0010__ul71285348441"><li id="cce_10_0010__li9128173413440"><strong id="cce_10_0010__b766151614472">Node network</strong>: CCE uses VPC subnets as the node network of a cluster. The available IP addresses of a subnet limit the maximum number of nodes that can be created in a cluster. For example, a subnet with a mask of /24 can allocate a maximum of 254 node IP addresses. The number of nodes that can be created in a cluster is also affected by the container network. For details, see container network models.</li><li id="cce_10_0010__li36181922104819"><strong id="cce_10_0010__b890355844712">Container network</strong>: Pods in a cluster are allocated independent IP addresses. All pods in a cluster are on a flat network and can be accessed using their IP addresses without NAT. Kubernetes uses <a href="https://github.com/containernetworking/cni" target="_blank" rel="noopener noreferrer">Container Network Interface (CNI)</a> to standardize the network between containers. Network model plugins are used to allocate independent IP addresses to pods for flat network communications in a cluster. Different network models have different allocation principles.<div class="fignone" id="cce_10_0010__fig3527185315566"><span class="figcap"><b>Figure 1 </b>Container network</span><br><span><img class="eddx" id="cce_10_0010__image7527145315613" src="en-us_image_0000002467719141.png"></span></div>
+<ul id="cce_10_0010__ul71285348441"><li id="cce_10_0010__li9128173413440"><strong id="cce_10_0010__b766151614472">Node network</strong>: CCE uses VPC subnets as the node network of a cluster. The available IP addresses of a subnet limit the maximum number of nodes that can be created in a cluster. For example, a subnet with a mask of /24 can allocate a maximum of 254 node IP addresses. The number of nodes that can be created in a cluster is also affected by the container network. For details, see container network models.</li><li id="cce_10_0010__li36181922104819"><strong id="cce_10_0010__b890355844712">Container network</strong>: Pods in a cluster are allocated independent IP addresses. All pods in a cluster are on a flat network and can be accessed using their IP addresses without NAT. Kubernetes uses <a href="https://github.com/containernetworking/cni" target="_blank" rel="noopener noreferrer">Container Network Interface (CNI)</a> to standardize the network between containers. Network model plugins are used to allocate independent IP addresses to pods for flat network communications in a cluster. Different network models have different allocation principles.<div class="fignone" id="cce_10_0010__fig3527185315566"><span class="figcap"><b>Figure 1 </b>Container network</span><br><span><img class="eddx" id="cce_10_0010__image7527145315613" src="en-us_image_0000002483959592.png"></span></div>
 <p id="cce_10_0010__p17931122014208">Currently, CCE supports the following container network models:</p>
 <ul id="cce_10_0010__ul10464211245"><li id="cce_10_0010__li124613292414"><a href="cce_10_0282.html">Container tunnel network</a>: This network model is constructed based on the node network through tunnel encapsulation, but it is independent of the node network. It uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.</li><li id="cce_10_0010__li11464220244"><a href="cce_10_0283.html">VPC network</a>: This network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node in a cluster that uses a VPC network is running in a subnet with a fixed number of IP addresses. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. In addition, as the routes destined for nodes and containers are added to a VPC route table, containers can be directly accessed from outside the cluster.</li><li id="cce_10_0010__li174612102411"><a href="cce_10_0284.html">Cloud Native Network 2.0</a> is a next-generation model developed by CCE and combines the network interfaces and supplementary network interfaces of VPC. Pod IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to forward requests to containers. Security groups and EIPs are associated to deliver high performance.</li></ul>
 <p id="cce_10_0010__p14408316536">The performance, networking scale, and application scenarios of a container network vary depending on the container network model. For details about the functions and features of different container network models, see <a href="cce_10_0281.html">Overview</a>.</p>
@@ -20,17 +20,17 @@
 <p id="cce_10_0010__p1677717174140">For details about the Service, see <a href="cce_10_0249.html">Service Overview</a>.</p>
 </div>
 <div class="section" id="cce_10_0010__section1248852094313"><a name="cce_10_0010__section1248852094313"></a><a name="section1248852094313"></a><h4 class="sectiontitle">Ingress</h4><p id="cce_10_0010__p96672218193">Services forward requests using TCP and UDP at Layer 4. Ingresses forward requests using HTTP and HTTPS at Layer 7. Domain names and paths can be used for access of finer granularities.</p>
-<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 3 </b>An ingress and associated Services</span><br><span><img id="cce_10_0010__en-us_topic_0249851122_image8371183511310" src="en-us_image_0258961458.png"></span></div>
+<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 3 </b>An ingress and its associated Services</span><br><span><img id="cce_10_0010__en-us_topic_0249851122_image8371183511310" src="en-us_image_0258961458.png"></span></div>
 <p id="cce_10_0010__p174691141141410">For details about the ingress, see <a href="cce_10_0094.html">Ingress Overview</a>.</p>
 </div>
 <div class="section" id="cce_10_0010__section19359105124011"><h4 class="sectiontitle">DNS</h4><p id="cce_10_0010__p783620210412">CCE uses CoreDNS to implement service discovery in a cluster. For example, a client can access backend pods through a ClusterIP Service whose name is mapped to a cluster-scoped virtual IP address. This approach decouples the invoking between applications in a cluster from specific IP addresses and deployment environments. For details about the cluster DNS settings, see <a href="cce_10_0360.html">DNS Overview</a>.</p>
-<div class="fignone" id="cce_10_0010__fig56221517187"><span class="figcap"><b>Figure 4 </b>Example of domain name resolution in a cluster</span><br><span><img id="cce_10_0010__cce_10_0360_image13391194511278" src="en-us_image_0000002467679373.png"></span></div>
+<div class="fignone" id="cce_10_0010__fig56221517187"><span class="figcap"><b>Figure 4 </b>Example of domain name resolution in a cluster</span><br><span><img id="cce_10_0010__cce_10_0360_image13391194511278" src="en-us_image_0000002516079535.png"></span></div>
 </div>
 <div class="section" id="cce_10_0010__section1286493159"><a name="cce_10_0010__section1286493159"></a><a name="section1286493159"></a><h4 class="sectiontitle">Access Scenarios</h4><p id="cce_10_0010__p1558001514155">Workload access scenarios can be categorized as follows:</p>
 <ul id="cce_10_0010__ul125010117542"><li id="cce_10_0010__li1466355519018">Intra-cluster access: A ClusterIP Service is used for workloads in the same cluster to access each other.</li><li id="cce_10_0010__li1014011111110">Access from outside a cluster: A Service (NodePort or LoadBalancer type) or an ingress is recommended for a workload outside a cluster to access workloads in the cluster.<ul id="cce_10_0010__ul101426119117"><li id="cce_10_0010__li8904911447">Access through the public network: An EIP should be bound to the node or load balancer.</li><li id="cce_10_0010__li2501311125411">Access through the private network: The workload can be accessed through the internal IP address of the node or load balancer. If workloads are located in different VPCs, a peering connection is required to enable communication between different VPCs.</li></ul>
 </li><li id="cce_10_0010__li1066365520014">The workload can access the external network as follows:<ul id="cce_10_0010__ul17529512239"><li id="cce_10_0010__li26601017165619">Accessing a private network: The workload accesses the private network address, but the implementation method varies depending on container network models. Ensure that the peer security group allows access from the container CIDR block.</li><li id="cce_10_0010__li8257105318237">Accessing a public network: Assign an EIP to the node where the workload runs (when a VPC network or tunnel network is used), bind an EIP to the pod IP address (when Cloud Native Network 2.0 is used), or configure an SNAT rule on the NAT gateway. For details, see <a href="cce_10_0400.html">Accessing the Internet from a Container</a>.</li></ul>
 </li></ul>
-<div class="fignone" id="cce_10_0010__fig13795829151515"><span class="figcap"><b>Figure 5 </b>Network access diagram</span><br><span><img id="cce_10_0010__image445972519529" src="en-us_image_0000002434080684.png"></span></div>
+<div class="fignone" id="cce_10_0010__fig13795829151515"><span class="figcap"><b>Figure 5 </b>Network access diagram</span><br><span><img id="cce_10_0010__image445972519529" src="en-us_image_0000002516199539.png"></span></div>
 </div>
 </div>
 <div>

docs/cce/umn/cce_10_0011.html

@@ -4,7 +4,7 @@
 <div id="body1522736584192"><p id="cce_10_0011__p03821416270"><span class="keyword" id="cce_10_0011__keyword1546144019373">ClusterIP</span> is the default Service type of Kubernetes and provides stable intra-cluster access. Kubernetes assigns a virtual IP address (cluster-scoped IP address) that can only be accessed within the cluster from the Service CIDR block of the cluster. CoreDNS maps the <span class="uicontrol" id="cce_10_0011__uicontrol789033512616"><b>cluster-internal domain name</b></span> to the assigned cluster IP address. The domain name format is <em id="cce_10_0011__i111021242407">&lt;Service-name&gt;</em>.<em id="cce_10_0011__i210234114014">&lt;namespace-of-the-workload&gt;</em><strong id="cce_10_0011__b16102844404">.svc.cluster.local:</strong><em id="cce_10_0011__i91029414016">&lt;port&gt;</em>, for example, <strong id="cce_10_0011__b610215434010">nginx.default.svc.cluster.local:80</strong>.</p>
 <p id="cce_10_0011__p326011246819">If pods need to communicate with each other within a cluster, you can create a ClusterIP Service. For example, if a frontend pod in a cluster needs to access a backend database in the same cluster, you can create a ClusterIP Service.</p>
 <p id="cce_10_0011__p1778412445517"><a href="#cce_10_0011__fig192245420557">Figure 1</a> shows how ClusterIP works. You can learn about the access channel, container port, and access port mapping rules of this type of Service.</p>
-<div class="fignone" id="cce_10_0011__fig192245420557"><a name="cce_10_0011__fig192245420557"></a><a name="fig192245420557"></a><span class="figcap"><b>Figure 1 </b>Intra-cluster access (ClusterIP)</span><br><span><img id="cce_10_0011__image1942163010278" src="en-us_image_0000002434081104.png"></span></div>
+<div class="fignone" id="cce_10_0011__fig192245420557"><a name="cce_10_0011__fig192245420557"></a><a name="fig192245420557"></a><span class="figcap"><b>Figure 1 </b>Intra-cluster access (ClusterIP)</span><br><span><img id="cce_10_0011__image1942163010278" src="en-us_image_0000002516079663.png"></span></div>
 <div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li64402531616"><span>Log in to the <span id="cce_10_0011__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0011__li836916478329"><span>In the navigation pane, choose <strong id="cce_10_0011__b18658321171411"><span id="cce_10_0011__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0011__uicontrol132971717714"><b>Create Service</b></span>.</span></li><li id="cce_10_0011__li3476651017144"><span>Configure intra-cluster access parameters.</span><p>
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0011__table23887196361" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0011__row33881619203617"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.5.2.3.2.1.1.3.1.1"><p id="cce_10_0011__p17388131914369">Parameter</p>
 </th>
@@ -41,7 +41,7 @@
 </tr>
 <tr id="cce_10_0011__row1961420125396"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p14614141216391">Port</p>
 </td>
-<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><ul id="cce_10_0011__ul6289131916397"><li id="cce_10_0011__li2289619143917"><strong id="cce_10_0011__b914900566">Protocol</strong>: the protocol supported by the Service.</li><li id="cce_10_0011__li628915191395"><strong id="cce_10_0011__b569396568">Container Port</strong>: the listening port of the service containers. The port ranges from 1 to 65535. You need to determine the port based on the container image. For example, the default port of Nginx is 80, and the default port of MySQL is 3306.</li><li id="cce_10_0011__li86391810174111"><strong id="cce_10_0011__b1066262561">Service Port</strong>: the port used to access the ClusterIP Service. You can customize the port as required. The port ranges from 1 to 65535.</li></ul>
+<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><ul id="cce_10_0011__ul6289131916397"><li id="cce_10_0011__li2289619143917"><strong id="cce_10_0011__b97693479">Protocol</strong>: the protocol supported by the Service.</li><li id="cce_10_0011__li628915191395"><strong id="cce_10_0011__b1279989584">Container Port</strong>: the listening port of the service containers. The port ranges from 1 to 65535. You need to determine the port based on the container image. For example, the default port of Nginx is 80, and the default port of MySQL is 3306.</li><li id="cce_10_0011__li86391810174111"><strong id="cce_10_0011__b732021731">Service Port</strong>: the port used to access the ClusterIP Service. You can customize the port as required. The port ranges from 1 to 65535.</li></ul>
 </td>
 </tr>
 </tbody>

docs/cce/umn/cce_10_0012.html

@@ -16,6 +16,12 @@
 <td class="cellrowborder" valign="top" width="75.47%" 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__row1099113459418"><td class="cellrowborder" valign="top" width="24.529999999999998%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="cce_10_0012__p1921320131017">Enterprise Project</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.47%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="cce_10_0012__p199211620111019">This parameter is available only for enterprise users who have enabled an enterprise project, and the cluster version must be v1.21.15-r0, v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.</p>
+<p id="cce_10_0012__p1692192011107">After an enterprise project is selected, nodes will be created in the node pool within that project. To manage clusters and other resources like nodes, load balancers, and node security groups, you can use the Enterprise Project Management Service (EPS). </p>
+</td>
+</tr>
 </tbody>
 </table>
 </div>
@@ -77,37 +83,38 @@
 </thead>
 <tbody><tr id="cce_10_0012__cce_10_0363_row5669170585"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p666916719588">System Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><p id="cce_10_0012__cce_10_0363_p590942616323">System disk used by the node OS. The value ranges from 40 GiB to 1024 GiB. The default value is 50 GiB.</p>
-<div class="p" id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_p196385417139"><strong id="cce_10_0012__cce_10_0363_b11690144943516">System Disk Encryption</strong>: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <strong id="cce_10_0012__cce_10_0363_b682192012018">Only the nodes of the Elastic Cloud Server (VM) type in certain regions support system disk encryption. For details, see the console.</strong><ul id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_ul6195114261211"><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195194211127"><strong id="cce_10_0012__cce_10_0363_b3414281726">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195184201217">If you select <strong id="cce_10_0012__cce_10_0363_b1914143518545">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b116539323544">System Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b1741811243462">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_li143358157216">If you select <strong id="cce_10_0012__cce_10_0363_b1034961319913">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b6349513895">System Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><p id="cce_10_0012__cce_10_0363_p590942616323">System disk used by the node OS. The value ranges from 40 GiB to 1,024 GiB. The default value is 50 GiB.</p>
+<div class="p" id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_p196385417139"><strong id="cce_10_0012__cce_10_0363_b11690144943516">System Disk Encryption</strong>: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. Only the nodes of the Elastic Cloud Server (VM) type in certain regions support system disk encryption. For details, see the console.<ul id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_ul6195114261211"><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195194211127"><strong id="cce_10_0012__cce_10_0363_b3414281726">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195184201217">If you select <strong id="cce_10_0012__cce_10_0363_b1914143518545">Enable (key name)</strong> for <strong id="cce_10_0012__cce_10_0363_b116539323544">System Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b1741811243462">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_li143358157216">If you select <strong id="cce_10_0012__cce_10_0363_b1034961319913">Enable (key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b6349513895">System Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
 </div>
 </td>
 </tr>
 <tr id="cce_10_0012__cce_10_0363_row913318122514"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p1413315892519">System Component Storage</p>
 </td>
 <td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><p id="cce_10_0012__cce_10_0363_p324785392516">Select a disk for storing system components.</p>
-<ul id="cce_10_0012__cce_10_0363_ul566328102615"><li id="cce_10_0012__cce_10_0363_li3931805278"><strong id="cce_10_0012__cce_10_0363_b354258318">Data Disk</strong>: added for storing container runtime and kubelet components by default. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</li><li id="cce_10_0012__cce_10_0363_li20663168152611"><strong id="cce_10_0012__cce_10_0363_b724291716512">System Disk</strong>: stores CCE resources such as downloaded images, ephemeral storage for containers, and container stdout logs. If the system disk is fully occupied, it will negatively affect the stability of the node.</li></ul>
-<div class="note" id="cce_10_0012__cce_10_0363_note6478170183416"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0012__cce_10_0363_p5437848286">In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, you can select a disk for storing system components. If <a href="cce_10_0132.html">CCE Node Problem Detector</a> is used, ensure that its version is 1.19.2 or later.</p>
+<ul id="cce_10_0012__cce_10_0363_ul566328102615"><li id="cce_10_0012__cce_10_0363_li3931805278"><strong id="cce_10_0012__cce_10_0363_b354258318">Data Disk</strong>: added for storing container runtime and kubelet components by default. The disk size ranges from 20 GiB to 32,768 GiB. The default value is 100 GiB. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</li><li id="cce_10_0012__cce_10_0363_li20663168152611"><strong id="cce_10_0012__cce_10_0363_b724291716512">System Disk</strong>: stores CCE resources such as downloaded images, ephemeral storage for containers, and container stdout logs. If the system disk is fully occupied, it will negatively affect the stability of the node.</li></ul>
+<div class="note" id="cce_10_0012__cce_10_0363_note6478170183416"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0012__cce_10_0363_p5437848286">Clusters v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0 and later support the selection of the storage location of system components. If the CCE Node Problem Detector add-on is required in the cluster, install v1.19.2 or a later version. For details about this add-on, see <a href="cce_10_0132.html">CCE Node Problem Detector</a>.</p>
 </div></div>
 </td>
 </tr>
 <tr id="cce_10_0012__cce_10_0363_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><ul id="cce_10_0012__cce_10_0363_ul13347201216402"><li id="cce_10_0012__cce_10_0363_li103472126407"><strong id="cce_10_0012__cce_10_0363_b14356162274112">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol1570817562482"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol179781326143914"><b>Data Disk</b></span>. <strong id="cce_10_0012__cce_10_0363_b5708195624814">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
-</li><li id="cce_10_0012__cce_10_0363_li18830161664015">If <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol19561032184918"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><ul id="cce_10_0012__cce_10_0363_ul13347201216402"><li id="cce_10_0012__cce_10_0363_li103472126407">At least one default data disk must be added if <strong id="cce_10_0012__cce_10_0363_b2563101631720">System Component Storage</strong> is set to <strong id="cce_10_0012__cce_10_0363_b2563191614178">Data Disk</strong> for the container runtime and kubelet. This data disk cannot be deleted or uninstalled. If it is deleted or uninstalled, the node will be unavailable.<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32,768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
+</li><li id="cce_10_0012__cce_10_0363_li18830161664015">If <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol19561032184918"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones. You can set the data disk size to a value ranging from 10 GiB to 32,768 GiB. The default value is 100 GiB.</li></ul>
 <div class="note" id="cce_10_0012__cce_10_0363_note95411755120"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__cce_10_0363_ul1388875765811"><li id="cce_10_0012__cce_10_0363_li9888165712586">If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.</li><li id="cce_10_0012__cce_10_0363_li7888757125811">Local disks may break down and do not ensure data reliability. Store your service data in EVS disks, which are more reliable than local disks.</li></ul>
 </div></div>
 <p id="cce_10_0012__cce_10_0363_p20408122884010"><strong id="cce_10_0012__cce_10_0363_b168590318488">Advanced Settings</strong></p>
-<div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><p id="cce_10_0012__cce_10_0363_p3752312011">Expand the area and configure the following parameters:</p></div>
-<div class="dropdowncontext"><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">Space Allocation of a Data Disk</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>
+<div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><p id="cce_10_0012__cce_10_0363_p3752312011">For the default data disk used by the container runtime and kubelet, expand advanced settings and configure the following parameters:</p></div>
+<div class="dropdowncontext"><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">Space Allocation of a Data Disk</a>.</li><li id="cce_10_0012__cce_10_0363_li1721650566"><strong id="cce_10_0012__cce_10_0363_b14167265318">Write Mode</strong>: You can select <a href="#cce_10_0012__cce_10_0363_li1152213439519">Linear</a> or <a href="#cce_10_0012__cce_10_0363_li1852244310516">Striped</a> for the default data disk.</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">Enable (key name)</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">Enable (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>
 </div></div><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. 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>
-<p id="cce_10_0012__cce_10_0363_p1077134819548"><a href="cce_10_0391.html">PVs</a> and <a href="cce_10_0726.html">EVs</a> support the following write modes:</p>
-<ul id="cce_10_0012__cce_10_0363_ul1752212438513"><li id="cce_10_0012__cce_10_0363_li1152213439519"><strong id="cce_10_0012__cce_10_0363_b198983618468">Linear</strong>: A linear logical volume integrates one or more physical volumes. Data is written to the next physical volume when the previous one is used up.</li><li id="cce_10_0012__cce_10_0363_li1852244310516"><strong id="cce_10_0012__cce_10_0363_b177696864712">Striped</strong>: A striped logical volume stripes data into blocks of the same size and stores them in multiple physical volumes in sequence. This allows data to be concurrently read and written. A storage pool consisting of striped volumes cannot be scaled-out. This option can be selected only when there are multiple volumes.</li></ul>
-<div class="note" id="cce_10_0012__cce_10_0363_note18645194919433"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__cce_10_0363_ul76451449144314"><li id="cce_10_0012__cce_10_0363_li3645049194318">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_li1645649184315">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>
+<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.</p>
+<p id="cce_10_0012__cce_10_0363_p839618351931">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"><a href="cce_10_0391.html">Use as PV</a>: 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"><a href="cce_10_0726.html">Use as ephemeral volume</a>: applicable when there is a high performance requirement on emptyDir.<div class="note" id="cce_10_0012__cce_10_0363_note153779122023"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__cce_10_0363_ul14378181210212"><li id="cce_10_0012__cce_10_0363_li15378201211219">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_li33781312025">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>
-</td>
+</li></ul>
+<div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><p id="cce_10_0012__cce_10_0363_p1077134819548">If the data disk is not mounted by default, the following write modes are supported:</p></div>
+<div class="dropdowncontext"><ul id="cce_10_0012__cce_10_0363_ul1752212438513"><li id="cce_10_0012__cce_10_0363_li1152213439519"><a name="cce_10_0012__cce_10_0363_li1152213439519"></a><a name="cce_10_0363_li1152213439519"></a><strong id="cce_10_0012__cce_10_0363_b198983618468">Linear</strong>: A linear logical volume integrates one or more physical volumes. Data is written to the next physical volume when the previous one is used up.</li><li id="cce_10_0012__cce_10_0363_li1852244310516"><a name="cce_10_0012__cce_10_0363_li1852244310516"></a><a name="cce_10_0363_li1852244310516"></a><strong id="cce_10_0012__cce_10_0363_b177696864712">Striped</strong>: A striped logical volume stripes data into blocks of the same size and stores them in multiple physical volumes in sequence. This allows data to be concurrently read and written. A storage pool consisting of striped volumes cannot be scaled-out. This option is available only if there are at least two data disks.</li></ul>
+</div></div></td>
 </tr>
 </tbody>
 </table>

docs/cce/umn/cce_10_0014.html

@@ -26,7 +26,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0924.html">Changing a Custom EIP for a LoadBalancer Service</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="cce_10_0685.html">Setting the Pod Ready Status Through the ELB Health Check</a></strong><br>
+<li class="ulchildlink"><strong><a href="cce_10_0685.html">Setting the Pod Readiness Status Through an ELB Health Check</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0084.html">Enabling ICMP Security Group Rules</a></strong><br>
 </li>

docs/cce/umn/cce_10_0018.html

@@ -4,7 +4,7 @@
 <div id="body1522667123001"><p id="cce_10_0018__p78381781804">CCE works with AOM 1.0 to collect workload logs. When a node is created, ICAgent (a DaemonSet named <strong id="cce_10_0018__b13829819578">icagent</strong> in the <strong id="cce_10_0018__b697274313582">kube-system</strong> namespace of a cluster) is installed by default. ICAgent collects workload logs and reports them to AOM 1.0. You can view workload logs on the CCE or AOM 1.0 console.</p>
 <div class="section" id="cce_10_0018__section17884754413"><h4 class="sectiontitle">Constraints</h4><p id="cce_10_0018__p23831558355">ICAgent only collects text log files in .log, .trace, and .out formats.</p>
 </div>
-<div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, choose <strong id="cce_10_0018__b15344161695011">Logging</strong> in <strong id="cce_10_0018__b1381882085012">Container Information</strong>.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000002467679305.png"></span> to add a log policy.</span><p><p id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary depending on workloads.</p>
+<div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, choose <strong id="cce_10_0018__b15344161695011">Logging</strong> in <strong id="cce_10_0018__b1381882085012">Container Information</strong>.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000002516079543.png"></span> to add a log policy.</span><p><p id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary depending on workloads.</p>
 </p></li><li id="cce_10_0018__li1479392315150"><span>Set <strong id="cce_10_0018__b5461630195419">Volume Type</strong> to <span class="uicontrol" id="cce_10_0018__uicontrol105212302547"><b>hostPath</b></span> or <span class="uicontrol" id="cce_10_0018__uicontrol1752103095410"><b>emptyDir</b></span>.</span><p>
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0018__table115901715550" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters for configuring a log policy</caption><thead align="left"><tr id="cce_10_0018__row45851074554"><th align="left" class="cellrowborder" valign="top" width="22.12%" id="mcps1.3.3.2.3.2.1.2.3.1.1"><p id="cce_10_0018__p115843785517">Parameter</p>
 </th>
@@ -97,7 +97,7 @@ spec:
           name: vol-log
       imagePullSecrets:
         - name: default-secret</pre>
-<p id="cce_10_0018__p878213715533">The following shows how to use a hostPath volume. Compared with emptyDir, the type of <strong id="cce_10_0018__b116061846152315">volumes</strong> is changed to <strong id="cce_10_0018__b19606134616237">hostPath</strong>, and the path on the host needs to be configured for this hostPath volume. In the following example, <span class="uicontrol" id="cce_10_0018__uicontrol046012383406"><b>/tmp/log</b></span> on the host is mounted to <span class="uicontrol" id="cce_10_0018__uicontrol1546533819400"><b>/var/log/nginx</b></span>. In this way, the ICAgent can collect logs in <strong id="cce_10_0018__b1246512382409">/var/log/nginx</strong>, without deleting the logs from <strong id="cce_10_0018__b64661838144012">/tmp/log</strong>.</p>
+<p id="cce_10_0018__p878213715533">The following shows how to use a hostPath volume. Compared with emptyDir, the type of <strong id="cce_10_0018__b116061846152315">volumes</strong> is changed to <strong id="cce_10_0018__b19606134616237">hostPath</strong>, and the path on the host needs to be configured for this hostPath volume. In the following example, <span class="uicontrol" id="cce_10_0018__uicontrol046012383406"><b>/tmp/log</b></span> on the host is mounted to <span class="uicontrol" id="cce_10_0018__uicontrol1546533819400"><b>/var/log/nginx</b></span>. In this way, the ICAgent can collect logs in <strong id="cce_10_0018__b1246512382409">/var/log/nginx</strong>, and the logs are still stored in <strong id="cce_10_0018__b64661838144012">/tmp/log</strong>.</p>
 <pre class="screen" id="cce_10_0018__screen1347245314534">apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -154,8 +154,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__keyword39514290">Pod</span>.</p>
-<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b1265292060">None</strong>: No extended path is configured.</li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b833957999">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b938033014">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b899085775">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__keyword463048936">Pod</span>.</p>
+<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b1673084912">None</strong>: No extended path is configured.</li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b96424558">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b1468169494">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b2057286321">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>

docs/cce/umn/cce_10_0020.html

@@ -14,6 +14,8 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0359.html">DNS</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="cce_10_0679.html">Cluster Network Settings</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="cce_10_0399.html">Configuring Intra-VPC Access</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0400.html">Accessing the Internet from a Container</a></strong><br>

docs/cce/umn/cce_10_0025.html

@@ -2,7 +2,7 @@
 
 <h1 class="topictitle1">CCE Operations Supported by CTS</h1>
 <div id="body1525226397666"><p id="cce_10_0025__p128516588310"><span class="keyword" id="cce_10_0025__keyword8727184318148">Cloud Trace Service</span> (<span class="keyword" id="cce_10_0025__keyword3727043181411">CTS</span>) records operations on cloud service resources, allowing you to query, audit, and backtrack the resource operation requests initiated from the CCE console or open APIs as well as responses to the requests.</p>
-<div class="note" id="cce_10_0025__note5938163561716"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0025__p149803512186">To collect the query events (Get and List) listed in the table below, enable read-only event reporting of CCE in CTS. Because query operations occur far more frequently than addition, deletion, or modification operations, enabling this function may generate a large volume of events. Assess the potential impact before enabling it. </p>
+<div class="note" id="cce_10_0025__note5938163561716"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0025__p149803512186">To collect the query events (Get and List) listed in the table below, enable read-only event reporting of CCE in CTS. Because query operations occur far more frequently than addition, deletion, or modification operations, enabling this function may generate a large number of events. Assess the potential impacts before enabling it.</p>
 </div></div>
 
 <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.3.3.2.4.1.1"><p id="cce_10_0025__p5122153665915">Operation</p>

docs/cce/umn/cce_10_0026.html

@@ -5,7 +5,7 @@
 </div>
 <div class="section" id="cce_10_0026__en-us_topic_0179639644_section036851413573"><h4 class="sectiontitle">What Is a Trace?</h4><p id="cce_10_0026__en-us_topic_0179639644_p7344192412579">A trace is an operation log for a cloud service resource, tracked and stored by CTS. Traces record operations such as adding, modifying, or deleting cloud service resources. You can view them to identify who performed operations and when for detailed tracking.</p>
 </div>
-<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><h4 class="sectiontitle">Viewing Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol143115612115"><li id="cce_10_0026__en-us_topic_0179639644_li1629194722218"><span>Log in to the management console, click <span><img id="cce_10_0026__en-us_topic_0179639644_image1229124714224" src="en-us_image_0000002359774578.png"></span> in the upper left corner, and choose <strong id="cce_10_0026__en-us_topic_0179639644_b0101171161313">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b17101511131310">Cloud Trace Service</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1443115692119"><span>In the navigation pane, choose <strong id="cce_10_0026__en-us_topic_0179639644_b5352121921314">Trace List</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1468123811239"><span>In the upper right corner of the page, set a desired query time range: <strong id="cce_10_0026__en-us_topic_0179639644_b18885164252718">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b3885114232715">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b1688574213277">Last 1 week</strong>. You can also click <strong id="cce_10_0026__en-us_topic_0179639644_b288519425275">Customize</strong> to specify a custom time range within the last seven days.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li243155612119"><span>Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>.</span><p><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_section19271975203"><h4 class="sectiontitle">Viewing Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol143115612115"><li id="cce_10_0026__en-us_topic_0179639644_li1629194722218"><span>Log in to the management console, click <span><img id="cce_10_0026__en-us_topic_0179639644_image1229124714224" src="en-us_image_0000002359774578.png"></span> in the upper left corner, and choose <strong id="cce_10_0026__en-us_topic_0179639644_b0101171161313">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b17101511131310">Cloud Trace Service</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1443115692119"><span>In the navigation pane, choose <strong id="cce_10_0026__en-us_topic_0179639644_b5352121921314">Trace List</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1468123811239"><span>In the upper right corner of the page, set a desired query time range: <strong id="cce_10_0026__en-us_topic_0179639644_b192893416490">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b122899464911">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b19289147490">Last 1 week</strong>. You can also click <strong id="cce_10_0026__en-us_topic_0179639644_b328913414912">Customize</strong> to specify a custom time range within the last seven days.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li243155612119"><span>Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>.</span><p><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="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0026__en-us_topic_0179639644_table147746583014" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Trace filtering parameters</caption><thead align="left"><tr id="cce_10_0026__en-us_topic_0179639644_row1877510573019"><th align="left" class="cellrowborder" valign="top" width="18.95%" id="mcps1.3.3.2.4.2.2.2.3.1.1"><p id="cce_10_0026__en-us_topic_0179639644_p1877512593016">Parameter</p>
 </th>
@@ -27,14 +27,14 @@
 <tr id="cce_10_0026__en-us_topic_0179639644_row531111429400"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p167757553018">Resource type</p>
 </td>
 <td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p1677513515307">Select the type of the resource involved in a trace from the drop-down list.</p>
-<p id="cce_10_0026__en-us_topic_0179639644_p1077535173016">For details about the resource types of each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i62441747131712">Cloud Trace Service User Guide</em>.</p>
+<p id="cce_10_0026__en-us_topic_0179639644_p1077535173016">For details about the resource types of each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i1090794613497">Cloud Trace Service User Guide</em>.</p>
 </td>
 </tr>
 <tr id="cce_10_0026__en-us_topic_0179639644_row17951953163817"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p17951145393815">Search By</p>
 </td>
 <td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p1866016362423">Select one of the following options:</p>
 <ul id="cce_10_0026__en-us_topic_0179639644_ul8324201518432"><li id="cce_10_0026__en-us_topic_0179639644_li1332441519434"><strong id="cce_10_0026__en-us_topic_0179639644_b17755195192214">Resource ID</strong>: ID of the cloud resource involved in a trace.<p id="cce_10_0026__en-us_topic_0179639644_p927319140446">Leave this field empty if the resource has no resource ID or if resource creation failed.</p>
-</li><li id="cce_10_0026__en-us_topic_0179639644_li19324111594319"><strong id="cce_10_0026__en-us_topic_0179639644_b20740051162314">Trace name</strong>: name of a trace.<p id="cce_10_0026__en-us_topic_0179639644_p162131756164314">For details about the operations that can be audited for each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i1219145055114">Cloud Trace Service User Guide</em>.</p>
+</li><li id="cce_10_0026__en-us_topic_0179639644_li19324111594319"><strong id="cce_10_0026__en-us_topic_0179639644_b20740051162314">Trace name</strong>: name of a trace.<p id="cce_10_0026__en-us_topic_0179639644_p162131756164314">For details about the operations that can be audited for each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i185782113507">Cloud Trace Service User Guide</em>.</p>
 </li><li id="cce_10_0026__en-us_topic_0179639644_li53251315144311"><strong id="cce_10_0026__en-us_topic_0179639644_b113836152512">Resource name</strong>: name of the cloud resource involved in a trace.<p id="cce_10_0026__en-us_topic_0179639644_p546964974419">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.</p>
 </li></ul>
 </td>
@@ -59,7 +59,7 @@
 </p></li><li id="cce_10_0026__en-us_topic_0179639644_li15432145622119"><span>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.</span><p><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_image1767234653119" src="en-us_image_0000001942942816.png"></span></p>
 <p id="cce_10_0026__en-us_topic_0179639644_p145491156142711"></p>
-</p></li><li id="cce_10_0026__en-us_topic_0179639644_li143245616217"><span>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.</span><p><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>
+</p></li><li id="cce_10_0026__en-us_topic_0179639644_li143245616217"><span>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.</span><p><p id="cce_10_0026__en-us_topic_0179639644_p1695161714447"><span><img id="cce_10_0026__en-us_topic_0179639644_image1990505483515" src="en-us_image_0000001758618249.png"></span></p>
 </p></li></ol>
 </div>
 <div class="section" id="cce_10_0026__en-us_topic_0179639644_section18501734161612"><h4 class="sectiontitle">Helpful Links</h4><ul id="cce_10_0026__en-us_topic_0179639644_ul19442019172"><li id="cce_10_0026__en-us_topic_0179639644_li547715311275">For details about the key fields in the trace structure, see <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/trace_structure.html#cts-03-0010" target="_blank" rel="noopener noreferrer">Trace Structure</a> and <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/example_traces.html" target="_blank" rel="noopener noreferrer">Example Traces</a>.</li></ul>

docs/cce/umn/cce_10_0031.html

@@ -12,7 +12,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0403.html">Changing a Cluster Scale</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="cce_10_0426.html">Changing the Default Security Group of a Node</a></strong><br>
+<li class="ulchildlink"><strong><a href="cce_10_0426.html">Changing the Default Node Security Group</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0212.html">Deleting a Cluster</a></strong><br>
 </li>

docs/cce/umn/cce_10_0034.html

@@ -10,16 +10,16 @@
 </div>
 <div class="section" id="cce_10_0034__section971014351338"><a name="cce_10_0034__section971014351338"></a><a name="section971014351338"></a><h4 class="sectiontitle">How the Add-on Works</h4><p id="cce_10_0034__p107541912344">An Nginx ingress consists of the ingress object, ingress controller, and Nginx. The ingress controller assembles ingresses into the Nginx configuration file (<strong id="cce_10_0034__b639012320451">nginx.conf</strong>) and reloads Nginx to make the configuration changes apply. When it detects that the pod in a Service changes, it dynamically changes the upstream server group configuration of Nginx. In this case, the Nginx process does not need to be reloaded. <a href="#cce_10_0034__fig204075132570">Figure 1</a> shows how this add-on works.</p>
 <ul id="cce_10_0034__ul12335125217342"><li id="cce_10_0034__li1533555233414">An ingress is a group of access rules that forward requests to specified Services based on domain names or URLs. Ingresses are stored in the object storage service etcd and are added, deleted, modified, and queried through APIs.</li><li id="cce_10_0034__li733615283411">The ingress controller monitors the changes of resource objects such as ingresses, Services, endpoints, secrets (mainly TLS certificates and keys), nodes, and ConfigMaps in real time and automatically performs operations on Nginx.</li><li id="cce_10_0034__li1633685273420">Nginx implements load balancing and access control at the application layer.</li></ul>
-<div class="fignone" id="cce_10_0034__fig204075132570"><a name="cce_10_0034__fig204075132570"></a><a name="fig204075132570"></a><span class="figcap"><b>Figure 1 </b>Working principles of NGINX Ingress Controller</span><br><span><img id="cce_10_0034__image1913206115716" src="en-us_image_0000002467718661.png"></span></div>
+<div class="fignone" id="cce_10_0034__fig204075132570"><a name="cce_10_0034__fig204075132570"></a><a name="fig204075132570"></a><span class="figcap"><b>Figure 1 </b>Working principles of NGINX Ingress Controller</span><br><span><img id="cce_10_0034__image1913206115716" src="en-us_image_0000002484119084.png"></span></div>
 </div>
 <div class="section" id="cce_10_0034__section3200193614201"><h4 class="sectiontitle">Precautions</h4><ul id="cce_10_0034__ul12529925421"><li id="cce_10_0034__li15529525324">For clusters earlier than v1.23, <strong id="cce_10_0034__b345165161317">kubernetes.io/ingress.class: "nginx"</strong> must be added to the annotation of the ingress created through the API. </li><li id="cce_10_0034__li11913127567">A dedicated load balancer must be of the network type (TCP/UDP) and support private networks (with a private IP address).</li><li id="cce_10_0034__li827072151315">If the node where NGINX Ingress Controller runs and containers on this node cannot access Nginx ingress, you need to configure anti-affinity for the workload pods and Nginx Ingress Controller. For details, see <a href="#cce_10_0034__section15456140194414">Configuring Anti-Affinity Between a Workload and Nginx Ingress Controller</a>.</li><li id="cce_10_0034__li837116398581">During the NGINX Ingress Controller pod upgrade, 10s are reserved for deleting the NGINX Ingress Controller at the ELB backend.</li><li id="cce_10_0034__li1215612416384">The timeout duration for the graceful exit of the NGINX Ingress Controller is 300s. If the timeout duration is longer than 300s during the upgrade of the NGINX Ingress Controller, persistent connections will be disconnected, and connectivity will be interrupted for a short period of time.</li></ul>
 </div>
-<div class="section" id="cce_10_0034__en-us_topic_0226102211_section92541494210"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0034__en-us_topic_0226102211_p996134411315">Before installing this add-on, you have one available cluster and there is a node running properly. If no cluster is available, create one according to <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</p>
+<div class="section" id="cce_10_0034__en-us_topic_0226102211_section92541494210"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0034__en-us_topic_0226102211_p996134411315">Before installing this add-on, you have one available cluster with a node running properly. If no cluster is available, create one according to <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</p>
 </div>
 <div class="section" id="cce_10_0034__section1152424015224"><a name="cce_10_0034__section1152424015224"></a><a name="section1152424015224"></a><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0034__ol595195015265"><li id="cce_10_0034__li330462393220"><span>Log in to the <span id="cce_10_0034__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0034__li13183153352515"><span>In the navigation pane, choose <strong id="cce_10_0034__b1673720498920"><span id="cce_10_0034__text1737849091">Add-ons</span></strong>. Locate <strong id="cce_10_0034__b1273719496911">NGINX Ingress Controller</strong> on the right and click <span class="uicontrol" id="cce_10_0034__uicontrol1273834913913"><b>Install</b></span>.</span></li><li id="cce_10_0034__li6185135511235"><span>On the <strong id="cce_10_0034__b168313930105924">Install Add-on</strong> page, configure the specifications as needed.</span><p><p id="cce_10_0034__p12804745248">You can adjust the number of add-on pods and resource quotas as required. High availability is not possible with a single pod. If an error occurs on the node where the add-on instance runs, the add-on will fail.</p>
-</p></li><li id="cce_10_0034__li584045813266"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0034__ul741422082911"><li id="cce_10_0034__li0953175016455"><a name="cce_10_0034__li0953175016455"></a><a name="li0953175016455"></a><strong id="cce_10_0034__b247210618418">Ingress Class</strong>: Enter a controller name. The name of each controller in the same cluster must be unique and cannot be set to <strong id="cce_10_0034__b10472106174115">cce</strong> (which is the unique identifier of the LoadBalancer ingress controller.) When creating an ingress, you can specify the controller name to declare which controller should manage this ingress.</li><li id="cce_10_0034__li43911954164512"><strong id="cce_10_0034__b87211241203016">Add-on Namespace</strong>: Select a namespace for the ingress controller.</li><li id="cce_10_0034__li194268504296"><strong id="cce_10_0034__b7357351122419">Load Balancer</strong>: Select a shared or dedicated load balancer. If no load balancer is available, create one. The load balancer has at least two listeners, and ports 80 and 443 are not occupied by listeners.</li><li id="cce_10_0034__li19869530141118"><strong id="cce_10_0034__b266512513184">Admission Check</strong>: Admission control is performed on Ingresses to ensure that the controller can generate valid configurations. Admission verification is performed on the configuration of Nginx Ingresses. If the verification fails, the request will be intercepted. For details about admission verification, see <a href="https://kubernetes.github.io/ingress-nginx/e2e-tests/#admission-admission-controller" target="_blank" rel="noopener noreferrer">Access Control</a>.<div class="note" id="cce_10_0034__note13941342101413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0034__ul13288250171411"><li id="cce_10_0034__li1228817507146">Admission check slows down the responses to Ingress requests.</li><li id="cce_10_0034__li172581224167">Only add-ons of version 2.4.1 or later support admission verification.</li></ul>
+</p></li><li id="cce_10_0034__li584045813266"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0034__ul741422082911"><li id="cce_10_0034__li0953175016455"><a name="cce_10_0034__li0953175016455"></a><a name="li0953175016455"></a><strong id="cce_10_0034__b247210618418">Ingress Class</strong>: Enter a controller name. The name of each controller in the same cluster must be unique and cannot be set to <strong id="cce_10_0034__b10472106174115">cce</strong> (which is the unique identifier of the LoadBalancer ingress controller). When creating an ingress, you can specify the controller name to declare which controller should manage this ingress.</li><li id="cce_10_0034__li43911954164512"><strong id="cce_10_0034__b87211241203016">Add-on Namespace</strong>: Select a namespace for the ingress controller.</li><li id="cce_10_0034__li194268504296"><strong id="cce_10_0034__b7357351122419">Load Balancer</strong>: Select a shared or dedicated load balancer. If no load balancer is available, create one. The load balancer has at least two listeners, and ports 80 and 443 are not occupied by listeners.</li><li id="cce_10_0034__li19869530141118"><strong id="cce_10_0034__b266512513184">Admission Check</strong>: Admission control is performed on Ingresses to ensure that the controller can generate valid configurations. Admission verification is performed on the configuration of Nginx Ingresses. If the verification fails, the request will be intercepted. For details about admission verification, see <a href="https://kubernetes.github.io/ingress-nginx/e2e-tests/#admission-admission-controller" target="_blank" rel="noopener noreferrer">Access Control</a>.<div class="note" id="cce_10_0034__note13941342101413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0034__ul13288250171411"><li id="cce_10_0034__li1228817507146">Admission check slows down the responses to Ingress requests.</li><li id="cce_10_0034__li172581224167">Only add-ons of version 2.4.1 or later support admission verification.</li></ul>
 </div></div>
-</li><li id="cce_10_0034__li66142206315"><strong id="cce_10_0034__b6241732145011">Nginx Parameters</strong>: You can configure the <strong id="cce_10_0034__b1463512386289">nginx.conf</strong> file, which will affect all managed ingresses. You can select <strong id="cce_10_0034__b174124435613">GUI</strong> or <strong id="cce_10_0034__b2410447568">YAML</strong>. <strong id="cce_10_0034__b194254415560">GUI</strong> is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.<p id="cce_10_0034__p1512810221947">To configure custom parameters supported by the Kubernetes community, choose <strong id="cce_10_0034__b184431518173115">YAML</strong> and find the related parameters in <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/" target="_blank" rel="noopener noreferrer">ConfigMaps</a>. For example, you can use the <strong id="cce_10_0034__b19750151011317">keep-alive-requests</strong> parameter to describe how to set the maximum number of requests for keeping active connections to 100.</p>
+</li><li id="cce_10_0034__li66142206315"><strong id="cce_10_0034__b6241732145011">Nginx Parameters</strong>: You can configure the <strong id="cce_10_0034__b1463512386289">nginx.conf</strong> file, which will affect all managed ingresses. You can select <strong id="cce_10_0034__b65271532199">GUI</strong> or <strong id="cce_10_0034__b18527193220918">YAML</strong>. <strong id="cce_10_0034__b2052715324915">GUI</strong> is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.<p id="cce_10_0034__p1512810221947">To configure custom parameters supported by the Kubernetes community, choose <strong id="cce_10_0034__b14281938796">YAML</strong> and find the related parameters in <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/" target="_blank" rel="noopener noreferrer">ConfigMaps</a>. For example, you can use the <strong id="cce_10_0034__b19750151011317">keep-alive-requests</strong> parameter to describe how to set the maximum number of requests for keeping active connections to 100.</p>
 <pre class="screen" id="cce_10_0034__screen6950408718">{
     "keep-alive-requests": "100"
 }</pre>
@@ -224,7 +224,7 @@ spec:
         app: nginx
     spec:
       containers:
-      - image: nginx:aplpine
+      - image: nginx:alpine
         imagePullPolicy: IfNotPresent
         name: nginx
       imagePullSecrets:

docs/cce/umn/cce_10_0047.html

@@ -159,7 +159,7 @@
 </tr>
 <tr id="cce_10_0047__row7534151220182"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.6.2.1.1.3.1.1 "><p id="cce_10_0047__p55339125183">Network Configuration</p>
 </td>
-<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.6.2.1.1.3.1.2 "><ul id="cce_10_0047__ul853411127187"><li id="cce_10_0047__li1153361211183">Pod ingress/egress bandwidth limit: You can set ingress and egress bandwidth limits for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0047__li135331712101812">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will be created using the container subnet and security group in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0047__li1253314122180">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0047__li11534712161812">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack network interfaces. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack Network Interfaces</a>.</li></ul>
+<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.3.2.6.2.1.1.3.1.2 "><ul id="cce_10_0047__ul853411127187"><li id="cce_10_0047__li1153361211183">Pod ingress/egress bandwidth limit: You can set ingress and egress bandwidth limits for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0047__li135331712101812">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will use the subnet and security group defined in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0047__li1253314122180">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0047__li11534712161812">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack network interfaces. For details, see <a href="cce_10_0604.html">Configuring a Shared Bandwidth for Dual-Stack Pods in a CCE Turbo Cluster</a>.</li></ul>
 </td>
 </tr>
 </tbody>

docs/cce/umn/cce_10_0048.html

@@ -3,11 +3,11 @@
 <h1 class="topictitle1">Creating a StatefulSet</h1>
 <div id="body1505966783091"><p id="cce_10_0048__p925511972817">A <a href="https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" target="_blank" rel="noopener noreferrer">StatefulSet</a> is an application that needs to retain data or state while running. StatefulSets are ideal for stateful applications, such as databases, cache services, and message queues. Unlike Deployments, StatefulSets have the following features:</p>
 <ul id="cce_10_0048__ul1978142634812"><li id="cce_10_0048__li878102619488"><strong id="cce_10_0048__b199251216104616">Fixed identifier</strong>: Each pod in a StatefulSet has a fixed identifier, which is associated with the pod name. The identifier is typically in the format of <span class="parmvalue" id="cce_10_0048__parmvalue7724184604418"><b>&lt;StatefulSet name&gt;-&lt;Ordinal&gt;</b></span>. For example, in a StatefulSet named <strong id="cce_10_0048__b1275919517402">web</strong>, the pods would have the names like <strong id="cce_10_0048__b8728122144110">web-0</strong> and <strong id="cce_10_0048__b7668142564119">web-1</strong>. This naming rule enables each pod to maintain its identity and persistent data even after restart or migration.</li><li id="cce_10_0048__li207852614817"><strong id="cce_10_0048__b790716920477">Ordered deployment and scaling</strong>: Pods in a StatefulSet are created, scaled, or deleted sequentially. For example, pods with higher ordinals are prioritized for scale-out and removed first during scale-in, which is critical to stateful applications that need to be started or stopped in sequence and ideal for scenarios like primary-secondary replication of databases.</li><li id="cce_10_0048__li738123204817"><strong id="cce_10_0048__b123058436480">Persistent storage</strong>: To ensure data persistence, you can assign stable persistent storage volumes to each StatefulSet pod by using <strong id="cce_10_0048__b790713501797">VolumeClaimTemplate</strong>. If a pod is scheduled to other nodes, its original data volume remains intact via the PVC, preventing data loss.</li></ul>
-<div class="section" id="cce_10_0048__section6329175411713"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0048__ul3611113041018"><li id="cce_10_0048__li28151714171212">When you delete or scale a StatefulSet, the system does not delete the storage volumes associated with the StatefulSet to ensure data security.</li><li id="cce_10_0048__li9611230141012">When you delete a StatefulSet, reduce the number of replicas to <strong id="cce_10_0048__b20407050121312">0</strong> before deleting the StatefulSet so that pods in the StatefulSet can be stopped in order.</li><li id="cce_10_0048__li611418311218">When you create a StatefulSet, a headless Service is required for pod access. For details, see <a href="cce_10_0398.html">Headless Service</a>.</li><li id="cce_10_0048__li093214329312">When a node is unavailable, pods become <strong id="cce_10_0048__b69930313149">Unready</strong>. In this case, manually delete the pods of the StatefulSet so that the pods can be migrated to a normal node.</li></ul>
+<div class="section" id="cce_10_0048__section6329175411713"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0048__ul3611113041018"><li id="cce_10_0048__li28151714171212">When you delete or scale a StatefulSet, the system does not delete the storage volumes associated with the StatefulSet to ensure data security.</li><li id="cce_10_0048__li9611230141012">When you delete a StatefulSet, reduce the number of replicas to <strong id="cce_10_0048__b20407050121312">0</strong> before deleting the StatefulSet so that pods in the StatefulSet can be stopped in order.</li><li id="cce_10_0048__li611418311218">When you create a StatefulSet, a headless Service is required for pod access. For details, see <a href="cce_10_0398.html">Headless Service</a>.</li><li id="cce_10_0048__li093214329312">When a node is unavailable, pods become <strong id="cce_10_0048__b69930313149">Unready</strong>. In this case, manually delete the pods of the StatefulSet so that the pods can be migrated to a normal node.</li></ul>
 </div>
 <div class="section" id="cce_10_0048__section1734962819219"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0048__ul1685719423426"><li id="cce_10_0048__cce_10_0047_li596019263145">A cluster is available. For details about how to create a cluster, see <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_10_0048__cce_10_0047_li1132215015415">There are some available nodes in the cluster. If no node is available, create one by referring to <a href="cce_10_0363.html">Creating a Node</a>.</li></ul>
 </div>
-<div class="section" id="cce_10_0048__section16385130102112"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0048__ol2012902601117"><li id="cce_10_0048__li9293104917265"><span>Log in to the <span id="cce_10_0048__cce_10_0047_ph1519791153812">CCE console</span>.</span></li><li id="cce_10_0048__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0048__b94442390613">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0048__b1844413910614">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0048__li67891737151520"><span>Configure <strong id="cce_10_0048__b168123018401">basic information</strong> about the workload.</span><p>
+<div class="section" id="cce_10_0048__section16385130102112"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0048__ol2012902601117"><li id="cce_10_0048__li9293104917265"><span>Log in to the <span id="cce_10_0048__cce_10_0047_ph1519791153812">CCE console</span>.</span></li><li id="cce_10_0048__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0048__b94442390613">Workloads</strong> in the navigation pane, and click <strong id="cce_10_0048__b1844413910614">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0048__li67891737151520"><span>Configure <strong id="cce_10_0048__b168123018401">basic information</strong> about the workload.</span><p>
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0048__table18732191924816" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0048__row147328197481"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.5.2.3.2.1.1.3.1.1"><p id="cce_10_0048__p11733619164811">Parameter</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.5.2.3.2.1.1.3.1.2"><p id="cce_10_0048__p13733201964812">Description</p>
@@ -170,7 +170,7 @@
 </tr>
 <tr id="cce_10_0048__row7534151220182"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.5.2.7.2.1.1.3.1.1 "><p id="cce_10_0048__p55339125183">Network Configuration</p>
 </td>
-<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.5.2.7.2.1.1.3.1.2 "><ul id="cce_10_0048__ul1582631234511"><li id="cce_10_0048__li11826612114513">Pod ingress/egress bandwidth limit: You can set ingress and egress bandwidth limits for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0048__li58262123457">Whether to enable the static IP address: available only for clusters that support this function. After this function is enabled, you can set the interval for reclaiming expired pod IP addresses. For details, see <a href="cce_10_0603.html">Configuring a Static IP Address for a Pod</a>.</li><li id="cce_10_0048__li2082621214510">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will be created using the container subnet and security group in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0048__li582619127452">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0048__li1826151234517">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack network interfaces. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack Network Interfaces</a>.</li></ul>
+<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.5.2.7.2.1.1.3.1.2 "><ul id="cce_10_0048__ul1582631234511"><li id="cce_10_0048__li11826612114513">Pod ingress/egress bandwidth limit: You can set ingress and egress bandwidth limits for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0048__li58262123457">Whether to enable the static IP address: available only for clusters that support this function. After this function is enabled, you can set the interval for reclaiming expired pod IP addresses. For details, see <a href="cce_10_0603.html">Configuring a Static IP Address for a Pod in a CCE Turbo Cluster</a>.</li><li id="cce_10_0048__li2082621214510">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will use the subnet and security group defined in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0048__li582619127452">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0048__li1826151234517">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack network interfaces. For details, see <a href="cce_10_0604.html">Configuring a Shared Bandwidth for Dual-Stack Pods in a CCE Turbo Cluster</a>.</li></ul>
 </td>
 </tr>
 </tbody>

docs/cce/umn/cce_10_0054.html

@@ -83,7 +83,7 @@
 <td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p1864418479569">This operation cannot be undone.</p>
 </td>
 </tr>
-<tr id="cce_10_0054__row273482911598"><td class="cellrowborder" rowspan="15" valign="top" width="14.42%" headers="mcps1.3.2.2.2.5.1.1 "><p id="cce_10_0054__p13120620202119">Worker node</p>
+<tr id="cce_10_0054__row273482911598"><td class="cellrowborder" rowspan="16" valign="top" width="14.42%" headers="mcps1.3.2.2.2.5.1.1 "><p id="cce_10_0054__p13120620202119">Worker node</p>
 </td>
 <td class="cellrowborder" valign="top" width="23.72%" headers="mcps1.3.2.2.2.5.1.2 "><p id="cce_10_0054__p4512165465912">Modifying the security group of worker nodes in a cluster</p>
 <div class="note" id="cce_10_0054__note733110531049"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0054__p153411953747">Naming rule of a worker node's security group: <em id="cce_10_0054__i143944160222">Cluster name</em>-<strong id="cce_10_0054__b1339915165227">cce-node</strong>-<em id="cce_10_0054__i18400171662214">{Random ID}</em></p>
@@ -110,6 +110,13 @@
 <td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p14512175415592">This operation cannot be undone.</p>
 </td>
 </tr>
+<tr id="cce_10_0054__row1342344942611"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.1 "><p id="cce_10_0054__p442424915264">Deleting the elastic network interface used by the node</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.2 "><p id="cce_10_0054__p1442464913266">The container network on the node is unavailable.</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p10424134982619">This operation cannot be undone.</p>
+</td>
+</tr>
 <tr id="cce_10_0054__row127351729155916"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.1 "><p id="cce_10_0054__p95135548591">Reinstalling the OS</p>
 </td>
 <td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.2 "><p id="cce_10_0054__p185132543597">Node components are deleted, and the node becomes unavailable.</p>
@@ -123,7 +130,7 @@
 <div class="note" id="cce_10_0054__note1791614419108"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0054__p17926741111013">Node running depends on the system kernel version. Do not use the <strong id="cce_10_0054__b513114494419">yum update</strong> command to update or reinstall the kernel of a node unless necessary. (Reinstalling the operating system kernel using the original image or other images is a risky operation.)</p>
 </div></div>
 </td>
-<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p10947153121219">For details, see <a href="cce_10_0003.html">Resetting a Node</a>.</p>
+<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p10947153121219">Reset the node. For details, see <a href="cce_10_0003.html">Resetting a Node</a>.</p>
 </td>
 </tr>
 <tr id="cce_10_0054__row473542920590"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.1 "><p id="cce_10_0054__p3513054165919">Changing the IP address of a node</p>
@@ -137,7 +144,7 @@
 </td>
 <td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.2 "><p id="cce_10_0054__p125135541599">The node may become unavailable, and components may be insecure if security-related configurations are modified.</p>
 </td>
-<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p851395416595">Restore the parameter settings to the recommended values. For details, see <a href="cce_10_0652.html">Modifying Node Pool Configurations</a>.</p>
+<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.3 "><p id="cce_10_0054__p851395416595">Restore the parameter settings to the recommended values. For details, see <a href="cce_10_0652.html">Managing Node Pool Configurations</a>.</p>
 </td>
 </tr>
 <tr id="cce_10_0054__row9442141061414"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.5.1.1 "><p id="cce_10_0054__p5513115415911">Modifying OS configuration</p>
@@ -295,7 +302,7 @@
 </div>
 </div>
 <div class="section" id="cce_10_0054__section1128213033113"><h4 class="sectiontitle">Load Balancing</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0054__table5358155303116" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Load balancing (operations on the ELB console)</caption><thead align="left"><tr id="cce_10_0054__row5358155363115"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.5.2.2.4.1.1"><p id="cce_10_0054__p7358105312312">Operation</p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0054__table5358155303116" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Load balancing</caption><thead align="left"><tr id="cce_10_0054__row5358155363115"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.5.2.2.4.1.1"><p id="cce_10_0054__p7358105312312">Operation</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.5.2.2.4.1.2"><p id="cce_10_0054__p10358153113116">Impact</p>
 </th>
@@ -347,9 +354,9 @@
 </tr>
 <tr id="cce_10_0054__row7358353163114"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0054__p13142103103818">Modifying the basic configurations such as the name, access control, timeout, or description of a listener added by CCE</p>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0054__p1078191016329">After master nodes are restarted due to reasons such as a cluster upgrade, all your modifications will be reset by CCE if the listener is deleted.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0054__p1078191016329">After master nodes are restarted due to reasons such as a cluster upgrade, all your modifications will be reset by CCE.</p>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0054__p5130319377">Do not modify the basic configurations of the listener created by CCE. Restore the configurations if they have been modified.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0054__p5130319377">Do not modify the permissions. Restore the permissions if they have been modified.</p>
 </td>
 </tr>
 <tr id="cce_10_0054__row735925323112"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0054__p349604319388">Modifying the backend server group of a listener added by CCE, including adding or deleting backend servers to or from the server group</p>
@@ -371,14 +378,14 @@
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.2 "><ul id="cce_10_0054__ul114412211467"><li id="cce_10_0054__li101446294619">Accessing the target Service or ingress will fail.</li><li id="cce_10_0054__li71441421464">After master nodes are restarted due to reasons such as a cluster upgrade, all your modifications will be reset by CCE if the forwarding rules are added using an ingress.</li></ul>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0054__p729721213310">Do not modify the forwarding policy of such a listener. Restore the configurations if they have been modified.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0054__p729721213310">Do not modify the permissions. Restore the permissions if they have been modified.</p>
 </td>
 </tr>
-<tr id="cce_10_0054__row15812153403"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0054__p101421931163814">Changing the certificate for a load balancer managed by CCE</p>
+<tr id="cce_10_0054__row15812153403"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0054__p1636993511434">Replacing the certificate of the listener created by CCE on the ELB console or modifying the server certificate created by CCE using a TLS key on the <strong id="cce_10_0054__b1634518183194">Certificates</strong> page of ELB</p>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0054__p478313106320">After master nodes are restarted due to reasons such as a cluster upgrade, all servers in the backend server group will be reset by CCE.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0054__p478313106320">In scenarios where a master node needs to be restarted, such as during a cluster upgrade, the modification will be reset by CCE. As a result, the Service or ingress may become inaccessible.</p>
 </td>
-<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0054__p111421438153818">Use the YAML file of the ingress to automatically manage certificates.</p>
+<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0054__p739943924515">Use the CCE console or YAML to update the certificate associated with the Service or ingress, or update the TLS key resources associated with the Service or ingress.</p>
 </td>
 </tr>
 </tbody>
@@ -421,7 +428,7 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_10_0054__row91492471212"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.7.2.2.4.1.1 "><p id="cce_10_0054__p28241823172215">Configuring a larger number of collection shards in Cloud Native Cluster Monitoring than the recommended value (one collection shards per 50 nodes)</p>
+<tbody><tr id="cce_10_0054__row91492471212"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.7.2.2.4.1.1 "><p id="cce_10_0054__p28241823172215">Configuring a larger number of collection shards in Cloud Native Cluster Monitoring than the recommended value (one collection shard per 50 nodes)</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.7.2.2.4.1.2 "><p id="cce_10_0054__p10149144762117">Excessive shards may overload the master node's memory, affecting system stability.</p>
 </td>