revert #1578 UCS API initial update 20250523 version

revert UCS API initial update 20250523 version

Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>

.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/asm/umn/asm_01_0020.html

@@ -7,9 +7,9 @@
 <div class="section" id="asm_01_0020__en-us_topic_0000001542706401_section1486314595204"><h4 class="sectiontitle">Constraints</h4><ul id="asm_01_0020__en-us_topic_0000001542706401_ul186475910202"><li id="asm_01_0020__en-us_topic_0000001542706401_li1786417596203">ASM depends on the domain name resolution of CoreDNS. Before creating a service mesh for a cluster, ensure that the cluster has required resources and CoreDNS is running normally.</li><li id="asm_01_0020__li133817361244">The components of Istio 1.13 and 1.15 cannot run on nodes running CentOS or EulerOS 2.5. When creating a service mesh, do not specify these types of nodes as master nodes.</li></ul>
 </div>
 <div class="section" id="asm_01_0020__en-us_topic_0000001542706401_section201371027102715"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0020__en-us_topic_0000001542706401_ol1158918434276"><li id="asm_01_0020__en-us_topic_0000001542706401_li184614499427"><span>Log in to the ASM console.</span></li><li id="asm_01_0020__en-us_topic_0000001542706401_li125894431271"><span>Click <strong id="asm_01_0020__b205391310114513">Create Mesh</strong> in the upper right corner.</span></li><li id="asm_01_0020__en-us_topic_0000001542706401_li135891543162714"><span>Configure the following parameters.</span><p><ul id="asm_01_0020__en-us_topic_0000001542706401_ul75901043202711"><li id="asm_01_0020__en-us_topic_0000001542706401_li2092711501216"><strong id="asm_01_0020__en-us_topic_0000001542706401_b1094850142211">Mesh Edition</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p4479132261213">Only service meshes of the Basic edition are supported for commercial use.</p>
-</li><li id="asm_01_0020__en-us_topic_0000001542706401_li35901243162718"><strong id="asm_01_0020__b1101751604">Mesh Name</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590743152711">Enter a service mesh name, which consists of 4 to 64 characters. It must start with a lowercase letter and cannot end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.</p>
+</li><li id="asm_01_0020__en-us_topic_0000001542706401_li35901243162718"><strong id="asm_01_0020__b22496209">Mesh Name</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590743152711">Enter a service mesh name, which consists of 4 to 64 characters. It must start with a lowercase letter and cannot end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.</p>
 <p id="asm_01_0020__en-us_topic_0000001542706401_p11590144316275">Each name in the same account must be unique. After a service mesh is created, the name cannot be modified.</p>
-</li><li id="asm_01_0020__en-us_topic_0000001542706401_li3590184362716"><strong id="asm_01_0020__b1115042375">Istio Version</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590144310274">Select the Istio version supported by the service mesh.</p>
+</li><li id="asm_01_0020__en-us_topic_0000001542706401_li3590184362716"><strong id="asm_01_0020__b1611790005">Istio Version</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590144310274">Select the Istio version supported by the service mesh.</p>
 </li><li id="asm_01_0020__li20991123625914"><strong id="asm_01_0020__b54661518132116">Enable IPv6</strong><p id="asm_01_0020__p04381549215">Conditions for enabling IPv4/IPv6 dual stack for a service mesh</p>
 
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_01_0020__table11439754142117" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_01_0020__row1743955417212"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.4.2.3.2.1.4.3.1.6.1.1"><p id="asm_01_0020__p1643985417218">Service Mesh Edition</p>
@@ -42,19 +42,19 @@
 <div class="note" id="asm_01_0020__note18440654152111"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0020__ul1744075432120"><li id="asm_01_0020__li1744055413210"><strong id="asm_01_0020__b11396256101815">Enable IPv6</strong> is only available in Basic service meshes based on Istio 1.18 or later.</li><li id="asm_01_0020__li194404548216">IPv4/IPv6 dual stack cannot be enabled for a service mesh whose Istio version is upgraded to 1.18 or later.</li></ul>
 <ul id="asm_01_0020__ul144085482119"><li id="asm_01_0020__li1344010549212">IPv4/IPv6 dual stack cannot be disabled once it is enabled for a service mesh. IPv4/IPv6 dual stack cannot be enabled for an existing service mesh.</li></ul>
 </div></div>
-</li><li id="asm_01_0020__en-us_topic_0000001542706401_li4590154315271"><strong id="asm_01_0020__b1657068806">Cluster</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p4590184313278">Select the cluster from the cluster list or enter the cluster name in the upper right corner of the list to search for the cluster. You can only select the clusters whose versions are supported by the current service mesh version.</p>
-</li><li id="asm_01_0020__en-us_topic_0000001542706401_li159044311277"><strong id="asm_01_0020__b871656394">Mesh Control Plane Node</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p125902437272">The control plane components of a Basic service mesh are installed in your cluster. You need to select a node for installing the control plane. If HA is required, you can select two or more nodes from different AZs.</p>
+</li><li id="asm_01_0020__en-us_topic_0000001542706401_li4590154315271"><strong id="asm_01_0020__b1825392822">Cluster</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p4590184313278">Select the cluster from the cluster list or enter the cluster name in the upper right corner of the list to search for the cluster. You can only select the clusters whose versions are supported by the current service mesh version.</p>
+</li><li id="asm_01_0020__en-us_topic_0000001542706401_li159044311277"><strong id="asm_01_0020__b553295356">Mesh Control Plane Node</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p125902437272">The control plane components of a Basic service mesh are installed in your cluster. You need to select a node for installing the control plane. If HA is required, you can select two or more nodes from different AZs.</p>
 <p id="asm_01_0020__en-us_topic_0000001542706401_p1959024392713">A selected node will be labeled with <strong id="asm_01_0020__b12113195612363">istio:master</strong>, and the components will be scheduled to that node.</p>
 </li><li id="asm_01_0020__li17225629125"><strong id="asm_01_0020__b182161818152520">Observability Configuration</strong><ul id="asm_01_0020__ul162251921123"><li id="asm_01_0020__li1522512214127"><strong id="asm_01_0020__b1443315218391">Tracing</strong><p id="asm_01_0020__p015131035712"><strong id="asm_01_0020__b1314122314192">Enable Call Chain</strong>: If this option is enabled, you can use distributed tracing to track requests in the service mesh.</p>
 <p id="asm_01_0020__p3225124129">- <strong id="asm_01_0020__b1649171110292">Sampling Rate</strong>: The number of requests generated by the tracing service/The total number of requests</p>
 <p id="asm_01_0020__p722519210123">- <strong id="asm_01_0020__b13853258294">Version</strong>: tracing service. If you select <strong id="asm_01_0020__b1028517591813">Third-party Jaeger/Zipkin service</strong>, you need to set <strong id="asm_01_0020__b613018597425">Service Address</strong> and <strong id="asm_01_0020__b665636154317">Service Port</strong>, which indicate the address and port number used by the third-party tracing service to receive requests.</p>
-<div class="note" id="asm_01_0020__note122518211219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0020__ul1522613251216"><li id="asm_01_0020__li112261223127">Only Istio 1.15 or later support the third-party tracing service.</li><li id="asm_01_0020__li142761222131512">If you want to use the third-party Jaeger or Zipkin service, install it first. Then, obtain the service address.</li><li id="asm_01_0020__li1622612111211">The default service ports of Jaeger and Zipkin are both 9411. If you create a custom service port during Jaeger or Zipkin installation, replace <strong id="asm_01_0020__b1161449123214">Service Port</strong> with the actual value.</li></ul>
+<div class="note" id="asm_01_0020__note122518211219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0020__ul1522613251216"><li id="asm_01_0020__li112261223127">Only Istio 1.15 and later versions support third-party tracing services.</li><li id="asm_01_0020__li142761222131512">If you want to use the third-party Jaeger or Zipkin service, install it first. Then, obtain the service address.</li><li id="asm_01_0020__li1622612111211">The default service ports of Jaeger and Zipkin are both 9411. If you create a custom service port during Jaeger or Zipkin installation, replace <strong id="asm_01_0020__b1161449123214">Service Port</strong> with the actual value.</li></ul>
 </div></div>
 </li></ul>
 </li></ul>
-</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li185901043112713"><span>(Optional) Specify advanced settings.</span><p><ul id="asm_01_0020__en-us_topic_0000001542706401_ul195914431277"><li id="asm_01_0020__en-us_topic_0000001542706401_li105911243172720"><strong id="asm_01_0020__b1108310788">Namespace Injection Settings</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p0591154316270">Select a namespace and label it with <strong id="asm_01_0020__b0190101221818">istio-injection=enabled</strong>. After being restarted, all pods in the namespace will be automatically injected with istio-proxy sidecars.</p>
+</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li185901043112713"><span>(Optional) Specify advanced settings.</span><p><ul id="asm_01_0020__en-us_topic_0000001542706401_ul195914431277"><li id="asm_01_0020__en-us_topic_0000001542706401_li105911243172720"><strong id="asm_01_0020__b337428543">Namespace Injection Settings</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p0591154316270">Select a namespace and label it with <strong id="asm_01_0020__b0190101221818">istio-injection=enabled</strong>. After being restarted, all pods in the namespace will be automatically injected with istio-proxy sidecars.</p>
 <p id="asm_01_0020__en-us_topic_0000001542706401_p1459184332714">If you do not configure namespace injection, you can inject a sidecar on the <strong id="asm_01_0020__b1960806132112">Sidecar Management</strong> tab (<strong id="asm_01_0020__b86087612111">Mesh Configuration</strong> &gt; <strong id="asm_01_0020__b196087611215">Sidecar Management</strong>) after the service mesh is created. For details, see <a href="asm_01_0041.html#asm_01_0041__section65931513505">Injecting a Sidecar</a>.</p>
-</li><li id="asm_01_0020__en-us_topic_0000001542706401_li1059184310276"><strong id="asm_01_0020__b109080228">Restart Existing Services</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p12591144362715"><span><img id="asm_01_0020__image879324619490" src="en-us_image_0000001920032153.png"></span>: The pods of existing services in the namespace will be restarted, which will temporarily interrupt your services. The istio-proxy sidecars can be automatically injected to the pods of existing services only after the pods are restarted.</p>
+</li><li id="asm_01_0020__en-us_topic_0000001542706401_li1059184310276"><strong id="asm_01_0020__b1505440256">Restart Existing Services</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p12591144362715"><span><img id="asm_01_0020__image879324619490" src="en-us_image_0000001920032153.png"></span>: The pods of existing services in the namespace will be restarted, which will temporarily interrupt your services. The istio-proxy sidecars can be automatically injected to the pods of existing services only after the pods are restarted.</p>
 <p id="asm_01_0020__en-us_topic_0000001542706401_p195911343162718"><span><img id="asm_01_0020__en-us_topic_0000001542706401_image1736110311031" src="en-us_image_0000001494249996.png"></span>: The istio-proxy sidecars cannot be automatically injected into the pods of existing services. You need to manually restart the pods on the CCE console to inject the sidecars.</p>
 </li><li id="asm_01_0020__li103761117176"><strong id="asm_01_0020__b161488533415">Traffic Interception Settings</strong><div class="note" id="asm_01_0020__note9376117978"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0020__p2376181712720">By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in <strong id="asm_01_0020__b134331479345">Traffic Interception Settings</strong>.</p>
 </div></div>
@@ -67,9 +67,9 @@
 <p id="asm_01_0020__p11377181717712"><strong id="asm_01_0020__b20653518442">Outbound IP Ranges</strong>: IP address ranges separated by commas (,) in CIDR format. You can use this field to specify the IP ranges that will be included or excluded for outbound traffic redirection.</p>
 <ul id="asm_01_0020__ul1337716172078"><li id="asm_01_0020__li1377417579"><strong id="asm_01_0020__b39502030153411">Include only specified IP ranges</strong> means that the traffic from specified IP ranges will be redirected to the sidecar.</li></ul>
 <ul id="asm_01_0020__ul14377181711717"><li id="asm_01_0020__li3377171710719"><strong id="asm_01_0020__b393303213347">Exclude only specified IP ranges</strong> means that the traffic from IP ranges except the specified IP ranges will be redirected to the sidecar.</li></ul>
-</li><li id="asm_01_0020__li1611138125316"><strong id="asm_01_0020__b308289121">Resource Tags</strong><p id="asm_01_0020__p1711128135317">Enter the tag key and tag value. A maximum of 20 tags can be added.</p>
+</li><li id="asm_01_0020__li1611138125316"><strong id="asm_01_0020__b896573998">Resource Tags</strong><p id="asm_01_0020__p1711128135317">Enter the tag key and tag value. A maximum of 20 tags can be added.</p>
 </li></ul>
-</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li859154318271"><span>Review the service mesh configuration in <strong id="asm_01_0020__b298934016">Configuration List</strong> on the right of the page and click <strong id="asm_01_0020__b1869262857">Submit</strong>.</span><p><p id="asm_01_0020__en-us_topic_0000001542706401_p13591174382714">It takes about 1 to 3 minutes to create a service mesh. If the service mesh status changes from <strong id="asm_01_0020__b1089376003">Installing</strong> to <strong id="asm_01_0020__b341929893">Running</strong>, the service mesh is successfully created.</p>
+</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li859154318271"><span>Review the service mesh configuration in <strong id="asm_01_0020__b1410335113">Configuration List</strong> on the right of the page and click <strong id="asm_01_0020__b250962436">Submit</strong>.</span><p><p id="asm_01_0020__en-us_topic_0000001542706401_p13591174382714">It takes about 1 to 3 minutes to create a service mesh. If the service mesh status changes from <strong id="asm_01_0020__b1250689906">Installing</strong> to <strong id="asm_01_0020__b1089094307">Running</strong>, the service mesh is successfully created.</p>
 <div class="note" id="asm_01_0020__en-us_topic_0000001542706401_note14591184342712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0020__en-us_topic_0000001542706401_p1459119432275">When the service mesh is enabled, the following operations are performed:</p>
 <ul id="asm_01_0020__en-us_topic_0000001542706401_ul859134311276"><li id="asm_01_0020__en-us_topic_0000001542706401_li195911043152719">Helm orchestrates the application into a Release as the resource of the service mesh control plane.</li></ul>
 </div></div>

docs/asm/umn/asm_01_0041.html

@@ -5,12 +5,15 @@
 <div class="section" id="asm_01_0041__section65931513505"><a name="asm_01_0041__section65931513505"></a><a name="section65931513505"></a><h4 class="sectiontitle">Injecting a Sidecar</h4><p id="asm_01_0041__p1820212632111">You can view the namespace and cluster that the injected sidecar belongs to. If no sidecar has been injected or you need to inject sidecars for more namespaces, perform the following operations:</p>
 <ol id="asm_01_0041__ol13641175216560"><li id="asm_01_0041__li683575385614"><span>Log in to the ASM console and click the name of the target service mesh to go to its details page.</span></li><li id="asm_01_0041__li987742619292"><span>In the navigation pane, choose <strong id="asm_01_0041__b23024965310246">Mesh Configuration</strong>. Then, click the <strong id="asm_01_0041__b79698741510246">Sidecar Management</strong> tab.</span></li><li id="asm_01_0041__li122863200343"><span>Click <strong id="asm_01_0041__b212025475310246">Sidecar Management</strong>, select a namespace, determine whether enable <strong id="asm_01_0041__b34328513417">Restart Existing Services</strong>, and click <strong id="asm_01_0041__b163426572510246">OK</strong>.</span><p><p id="asm_01_0041__p5867153384619">Parameter description:</p>
 <ul id="asm_01_0041__ul1213414267113"><li id="asm_01_0041__li151346264113"><strong id="asm_01_0041__b162639501293">Namespace</strong>: Select one or more namespaces. The system adds labels for namespaces based on Istio versions.<ul id="asm_01_0041__ul715833017173"><li id="asm_01_0041__li115810307178"><strong id="asm_01_0041__b93355351461">istio-injection=enabled</strong> can be used in Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions.</li></ul>
-<ul id="asm_01_0041__ul196772518187"><li id="asm_01_0041__li6677853189"><strong id="asm_01_0041__b5658241104719">istio.io/rev=&lt;revision&gt;</strong> can be used in Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions.</li></ul>
+<ul id="asm_01_0041__ul196772518187"><li id="asm_01_0041__li6677853189"><strong id="asm_01_0041__b5658241104719">istio.io/rev=&lt;revision&gt;</strong> can be used in Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, all Istio 1.18 versions, and all Istio 1.28 versions.</li></ul>
 </li><li id="asm_01_0041__li1283731219"><strong id="asm_01_0041__b176898850910246">Restart Existing Services</strong><p id="asm_01_0041__p16974516217"><span><img id="asm_01_0041__image1251935012150" src="en-us_image_0000001930216052.png"></span>: Enabling <strong id="asm_01_0041__b178031814163717">Restart Existing Services</strong> will restart the pods of existing services and temporarily interrupt your services. New pods will have istio-proxy sidecars automatically injected.</p>
 <ul id="asm_01_0041__ul1893924912361"><li id="asm_01_0041__li149404492367">If you select a new namespace, an automatic injection label is added. After all pods running the Deployment in that namespace are restarted, the istio-proxy sidecars will be automatically injected into new pods.</li></ul>
 <ul id="asm_01_0041__ul330205410366"><li id="asm_01_0041__li5302135413618">If you deselect a namespace, the automatic injection label is deleted. After all pods running the Deployment in that namespace are restarted, new pods do not have istio-proxy sidecars.</li></ul>
 <ul id="asm_01_0041__ul157408585364"><li id="asm_01_0041__li074055833619">If there are pods that are not injected with sidecars in selected namespaces, all pods running the Deployment will be restarted to inject sidecars. If all pods have sidecars injected, the pods will not be restarted.</li></ul>
-<p id="asm_01_0041__p45731657222"><span><img id="asm_01_0041__image1736110311031" src="en-us_image_0000001256463368.png"></span>: When you do not enable <strong id="asm_01_0041__b198411563510">Restart Existing Services</strong>, the istio-proxy sidecars cannot be automatically injected into the pods of existing services. In this case, you need to manually restart the pods on the CCE console to inject the sidecars. This parameter affects only existing services. If the namespaces are labeled with <strong id="asm_01_0041__b1545117533412">istio-injection=enabled</strong>, sidecars will be automatically injected into new pods.</p>
+<p id="asm_01_0041__p45731657222"><span><img id="asm_01_0041__image1736110311031" src="en-us_image_0000001256463368.png"></span>: The istio-proxy sidecars cannot be automatically injected into the pods of existing services. You need to manually restart the pods on the CCE console to inject the sidecars. This parameter affects only existing services. If the namespaces are labeled with <strong id="asm_01_0041__b1545117533412">istio-injection=enabled</strong> or <strong id="asm_01_0041__b95971230195613">istio.io/rev=&lt;revision&gt;</strong>, sidecars will be automatically injected into new pods.</p>
+<div class="caution" id="asm_01_0041__note1035861813226"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_01_0041__p191121442193617">This module does not provide the function of restarting services in a specific namespace. If a namespace is not selected, the automatic injection label will be removed from the namespace. After the workload in the namespace is restarted, the istio-proxy sidecar will not be automatically injected.</p>
+<p id="asm_01_0041__p735815185225">To inject a sidecar into a workload in a specified namespace, ensure that the namespace is selected and enabled. Then, go to the <strong id="asm_01_0041__b106411057172819">Workloads</strong> page of the CCE cluster console, select the workload, and choose <strong id="asm_01_0041__b173501542913">More</strong> &gt; <strong id="asm_01_0041__b156784815297">Redeploy</strong>. After the workload is restarted, the istio-proxy sidecar is automatically injected.</p>
+</div></div>
 </li><li id="asm_01_0041__li975935132613"><strong id="asm_01_0041__b4935192843517">Traffic Interception Settings</strong><div class="note" id="asm_01_0041__note130182311537"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0041__p5301112325320">By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in <strong id="asm_01_0041__b15949143017359">Traffic Interception Settings</strong>.</p>
 </div></div>
 <p id="asm_01_0041__p10174123175619"><strong id="asm_01_0041__b97421432123511">Inbound Ports</strong>: Inbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for inbound traffic redirection.</p>
@@ -23,7 +26,8 @@
 <ul id="asm_01_0041__ul13301528313"><li id="asm_01_0041__li5311221939"><strong id="asm_01_0041__b922854213514">Include only specified IP ranges</strong> means that the traffic from specified IP ranges will be redirected to the sidecar.</li></ul>
 <ul id="asm_01_0041__ul112121251130"><li id="asm_01_0041__li42121455318"><strong id="asm_01_0041__b19623164303511">Exclude only specified IP ranges</strong> means that the traffic from IP ranges except the specified IP ranges will be redirected to the sidecar.</li></ul>
 </li></ul>
-<div class="note" id="asm_01_0041__note1279618584133"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0041__ul97451116162713"><li id="asm_01_0041__li1974521615271">If the system displays a message indicating that modification of namespace injection is not enabled in the following clusters, you need to run the <strong id="asm_01_0041__b11447123395415">kubectl</strong> command to enable namespace injection. For details, see <a href="asm_faq_0036.html">How Do I Enable Namespace Injection for a Cluster?</a>.</li><li id="asm_01_0041__li12746181642719">After sidecar injection is enabled for a namespace of a cluster, sidecars are automatically injected for pods of all workloads in the namespace. If you do not want to inject sidecars for some workloads, see <a href="asm_faq_0037.html">How Do I Disable Sidecar Injection for Workloads?</a>.</li></ul>
+<div class="note" id="asm_01_0041__note1279618584133"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0041__ul3174175111130"><li id="asm_01_0041__li151741951141317">For details about why sidecar injection failed, see .</li></ul>
+<ul id="asm_01_0041__ul97451116162713"><li id="asm_01_0041__li1974521615271">If ASM displays a message indicating that modification of namespace injection is not enabled in the following clusters, you need to run the <strong id="asm_01_0041__b11447123395415">kubectl</strong> command to enable namespace injection. For details, see <a href="asm_faq_0036.html">How Do I Enable Namespace Injection for a Cluster?</a></li><li id="asm_01_0041__li12746181642719">After sidecar injection is enabled for a namespace of a cluster, sidecars are automatically injected for pods of all workloads in the namespace. If you do not want to inject sidecars for some workloads, see <a href="asm_faq_0037.html">How Do I Disable Sidecar Injection for Workloads?</a></li></ul>
 </div></div>
 </p></li></ol>
 </div>

docs/asm/umn/asm_01_0124.html

@@ -1,7 +1,7 @@
 <a name="asm_01_0124"></a><a name="asm_01_0124"></a>
 
 <h1 class="topictitle1">Features in v1.18</h1>
-<div id="body0000001737146797"><ul id="asm_01_0124__ul1742120185319"><li id="asm_01_0124__li1842160195316">Istio 1.18 is supported.</li><li id="asm_01_0124__li1036314425311">CCE Turbo clusters v1.25, v1.27, v1.28, v1.29, and v1.30, as well as v1.31 are supported.</li><li id="asm_01_0124__li6393101715319">CCE clusters v1.25, v1.27, v1.28, v1.29, and v1.30, as well as v1.31 are supported.</li><li id="asm_01_0124__li1910522175320">Kubernetes Gateway API is supported.</li></ul>
+<div id="body0000001737146797"><ul id="asm_01_0124__ul1742120185319"><li id="asm_01_0124__li1842160195316">Istio 1.18 is supported.</li><li id="asm_01_0124__li1036314425311">CCE Turbo clusters v1.25, v1.27, v1.28, v1.29, v1.30, and v1.31, as well as v1.32 and v1.33 are supported.</li><li id="asm_01_0124__li6393101715319">CCE clusters v1.25, v1.27, v1.28, v1.29, v1.30, and v1.31 , as well as v1.32 and v1.33 are supported.</li><li id="asm_01_0124__li1910522175320">Kubernetes Gateway API is supported.</li></ul>
 <p id="asm_01_0124__p58433415527">For details, visit <a href="https://istio.io/latest/news/releases/1.18.x/" target="_blank" rel="noopener noreferrer">https://istio.io/latest/news/releases/1.18.x/</a>.</p>
 </div>
 <div>

docs/asm/umn/asm_01_0141.html

@@ -0,0 +1,17 @@
+<a name="asm_01_0141"></a><a name="asm_01_0141"></a>
+
+<h1 class="topictitle1">Using IAM to Grant Access to ASM</h1>
+<div id="body0000002494975758"></div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="asm_01_0145.html">Using IAM Roles or Policies to Grant Access to ASM</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="asm_01_0146.html">Using IAM Identity Policies to Grant Access to ASM</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001627845328.html">User Guide</a></div>
+</div>
+</div>
+

docs/asm/umn/asm_01_0145.html

@@ -0,0 +1,66 @@
+<a name="asm_01_0145"></a><a name="asm_01_0145"></a>
+
+<h1 class="topictitle1">Using IAM Roles or Policies to Grant Access to ASM</h1>
+<div id="body0000002526896091"><p id="asm_01_0145__en-us_topic_0000001489537442_p198079372297">System-defined permissions in  provided by <a href="https://docs.otc.t-systems.com/en-us/usermanual/iam/iam_01_0026.html" target="_blank" rel="noopener noreferrer">Identity and Access Management (IAM)</a> let you control access to ASM. With IAM, you can:</p>
+<ul id="asm_01_0145__en-us_topic_0000001489537442_ul1848820457453"><li id="asm_01_0145__en-us_topic_0000001489537442_li348974516454">Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing ASM resources.</li><li id="asm_01_0145__en-us_topic_0000001489537442_li11681126173515">Grant users only the permissions required to perform a given task based on their job responsibilities.</li><li id="asm_01_0145__en-us_topic_0000001489537442_li12185165313915">Entrust an account or a cloud service to perform efficient O&amp;M on your ASM resources.</li></ul>
+<p id="asm_01_0145__en-us_topic_0000001489537442_p14662743155318">If your account meets your permissions requirements, you can skip this section.</p>
+<p id="asm_01_0145__en-us_topic_0000001489537442_p158501603165"><a href="#asm_01_0145__en-us_topic_0000001489537442_fig1351611812271">Figure 1</a> shows the process flow of role/policy-based authorization.</p>
+<div class="section" id="asm_01_0145__en-us_topic_0000001489537442_section17723185741610"><h4 class="sectiontitle">Prerequisites</h4><p id="asm_01_0145__en-us_topic_0000001489537442_p17286682272">Before granting permissions to user groups, learn about system-defined permissions in  for ASM. To grant permissions for other services, learn about all <a href="https://docs.otc.t-systems.com/permissions/index.html" target="_blank" rel="noopener noreferrer">permissions</a> supported by IAM.</p>
+</div>
+<div class="section" id="asm_01_0145__en-us_topic_0000001489537442_section1189416161520"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="asm_01_0145__en-us_topic_0000001489537442_fig1351611812271"><a name="asm_01_0145__en-us_topic_0000001489537442_fig1351611812271"></a><a name="en-us_topic_0000001489537442_fig1351611812271"></a><span class="figcap"><b>Figure 1 </b>Process of granting ASM permissions using role/policy-based authorization</span><br><span><img id="asm_01_0145__en-us_topic_0000001489537442_image35161382273" src="en-us_image_0000002526896489.png"></span></div>
+<ol id="asm_01_0145__en-us_topic_0000001489537442_ol10176191312813"><li id="asm_01_0145__en-us_topic_0000001489537442_li10176121316284"><a name="asm_01_0145__en-us_topic_0000001489537442_li10176121316284"></a><a name="en-us_topic_0000001489537442_li10176121316284"></a>On the IAM console, <a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html" target="_blank" rel="noopener noreferrer">create a user group and assign permissions to it</a>.<p id="asm_01_0145__en-us_topic_0000001489537442_p41762137286">Create a user group on the IAM console, and assign the <strong id="asm_01_0145__b18180133023513">ASM ReadOnlyAccess</strong> permissions to the group.</p>
+</li><li id="asm_01_0145__en-us_topic_0000001489537442_li181761413162818"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0031.html" target="_blank" rel="noopener noreferrer">Create an IAM user and add it to the user group</a>.<p id="asm_01_0145__en-us_topic_0000001489537442_p16177613182816">On the IAM console, create a user and add it to the user group created in <a href="#asm_01_0145__en-us_topic_0000001489537442_li10176121316284">1</a>.</p>
+</li><li id="asm_01_0145__en-us_topic_0000001489537442_li1177513202816"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html" target="_blank" rel="noopener noreferrer">Log in as the IAM user</a> and verify permissions.<p id="asm_01_0145__en-us_topic_0000001489537442_p1317741312289">In the authorized region, perform the following operations:</p>
+<ul id="asm_01_0145__en-us_topic_0000001489537442_ul1692751312242"><li id="asm_01_0145__en-us_topic_0000001489537442_li205729227246">Choose <strong id="asm_01_0145__b1623482611425">Service List</strong> &gt; <strong id="asm_01_0145__b11306103015437">Application Service Mesh</strong>. Click <strong id="asm_01_0145__b2155175674318">Buy Mesh</strong> on the ASM console. If a message appears indicating that you have insufficient permissions to perform the operation, the <strong id="asm_01_0145__b7209151616449">ASM ReadOnlyAccess</strong> policy is in effect.</li><li id="asm_01_0145__en-us_topic_0000001489537442_li1857212212418">Choose another service from <strong id="asm_01_0145__b1545117611422">Service List</strong>. If a message appears indicating that you have insufficient permissions to access the service, the <strong id="asm_01_0145__b104520624218">ASM ReadOnlyAccess</strong> policy is in effect.</li></ul>
+</li></ol>
+</div>
+<div class="section" id="asm_01_0145__en-us_topic_0000001489537442_section7529733164812"><h4 class="sectiontitle">Example Custom Policies</h4><p id="asm_01_0145__p576211773818">You can create custom policies to supplement the system-defined policies of ASM. For details about actions supported in custom policies, see .</p>
+<p id="asm_01_0145__en-us_topic_0000001489537442_p1391019913815">To create a custom policy, choose either visual editor or JSON.</p>
+<ul id="asm_01_0145__en-us_topic_0000001489537442_ul1146431393818"><li id="asm_01_0145__en-us_topic_0000001489537442_li5764181518386">Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy grammar.</li><li id="asm_01_0145__en-us_topic_0000001489537442_li546410135389">JSON: Create a JSON policy or edit an existing one.</li></ul>
+<p id="asm_01_0145__p2477135725615">For details, see .</p>
+<p id="asm_01_0145__p10716518386">The following lists examples of common ASM custom policies.</p>
+<ul id="asm_01_0145__en-us_topic_0000001489537442_ul2504185715494"><li id="asm_01_0145__en-us_topic_0000001489537442_li5504357164912">Example 1: Grant permissions to create service meshes.<pre class="screen" id="asm_01_0145__en-us_topic_0000001489537442_screen48273211535">{
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "asm:mesh:create"
+            ]
+        }
+    ]
+}</pre>
+</li><li id="asm_01_0145__en-us_topic_0000001489537442_li3652938178">Example 2: Grant permissions to deny service mesh deletion.<p id="asm_01_0145__en-us_topic_0000001489537442_p1892813119464"><a name="asm_01_0145__en-us_topic_0000001489537442_li3652938178"></a><a name="en-us_topic_0000001489537442_li3652938178"></a>A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.</p>
+<pre class="screen" id="asm_01_0145__en-us_topic_0000001489537442_screen39281011144617">{
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Deny",
+            "Action": [
+                "asm:mesh:createGateway"
+            ]
+        }
+    ]
+}</pre>
+</li><li id="asm_01_0145__en-us_topic_0000001489537442_li8475316125413">Example 3: Create a custom policy containing multiple actions.<p id="asm_01_0145__en-us_topic_0000001489537442_p466319313484"><a name="asm_01_0145__en-us_topic_0000001489537442_li8475316125413"></a><a name="en-us_topic_0000001489537442_li8475316125413"></a>A custom policy can contain the actions of one or multiple services that are of the same type (global or project-level). Example policy containing actions of multiple services:</p>
+<pre class="screen" id="asm_01_0145__screen125841914164916">{
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "cce:cluster:create"
+                "asm:mesh:create"
+            ]
+        }
+    ]
+}</pre>
+</li></ul>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0141.html">Using IAM to Grant Access to ASM</a></div>
+</div>
+</div>
+

docs/asm/umn/asm_01_0146.html

@@ -0,0 +1,70 @@
+<a name="asm_01_0146"></a><a name="asm_01_0146"></a>
+
+<h1 class="topictitle1">Using IAM Identity Policies to Grant Access to ASM</h1>
+<div id="body0000002494976322"><p id="asm_01_0146__en-us_topic_0000001543558165_p198079372297">System-defined permissions in  provided by <a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0026.html" target="_blank" rel="noopener noreferrer">Identity and Access Management (IAM)</a> let you control access to ASM. With IAM, you can:</p>
+<ul id="asm_01_0146__en-us_topic_0000001543558165_ul1848820457453"><li id="asm_01_0146__en-us_topic_0000001543558165_li348974516454">Create IAM users or user groups for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing ASM resources.</li><li id="asm_01_0146__en-us_topic_0000001543558165_li11681126173515">Grant users only the permissions required to perform a given task based on their job responsibilities.</li><li id="asm_01_0146__en-us_topic_0000001543558165_li12185165313915">Entrust an account or a cloud service to perform efficient O&amp;M on your ASM resources.</li></ul>
+<p id="asm_01_0146__en-us_topic_0000001543558165_p14662743155318">If your account meets your permissions requirements, you can skip this section.</p>
+<p id="asm_01_0146__en-us_topic_0000001543558165_p158501603165"><a href="#asm_01_0146__en-us_topic_0000001543558165_fig1351611812271">Figure 1</a> shows the process flow of identity policy-based authorization.</p>
+<div class="section" id="asm_01_0146__en-us_topic_0000001543558165_section17723185741610"><h4 class="sectiontitle">Prerequisites</h4><p id="asm_01_0146__en-us_topic_0000001543558165_p17286682272">Before granting permissions, learn about system-defined permissions in . To grant permissions for other services, learn about all <a href="https://docs.otc.t-systems.com/permissions/index.html" target="_blank" rel="noopener noreferrer">permissions</a> supported by IAM.</p>
+</div>
+<div class="section" id="asm_01_0146__en-us_topic_0000001543558165_section1189416161520"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="asm_01_0146__en-us_topic_0000001543558165_fig1351611812271"><a name="asm_01_0146__en-us_topic_0000001543558165_fig1351611812271"></a><a name="en-us_topic_0000001543558165_fig1351611812271"></a><span class="figcap"><b>Figure 1 </b>Process of granting ASM permissions using identity policy-based authorization</span><br><span><img id="asm_01_0146__en-us_topic_0000001543558165_image35161382273" src="en-us_image_0000002526896571.png"></span></div>
+<ol id="asm_01_0146__en-us_topic_0000001543558165_ol10176191312813"><li id="asm_01_0146__en-us_topic_0000001543558165_li10176121316284">On the IAM console, .<p id="asm_01_0146__en-us_topic_0000001543558165_p41762137286"><a name="asm_01_0146__en-us_topic_0000001543558165_li10176121316284"></a><a name="en-us_topic_0000001543558165_li10176121316284"></a>Create a user or user group on the IAM console.</p>
+</li><li id="asm_01_0146__en-us_topic_0000001543558165_li16925112804614"> (<strong id="asm_01_0146__b15261138162215">ASMReadOnlyPolicy</strong> as an example) to the user or user group.</li><li id="asm_01_0146__en-us_topic_0000001543558165_li1177513202816"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html" target="_blank" rel="noopener noreferrer">Log in as the IAM user</a> and verify permissions.<p id="asm_01_0146__en-us_topic_0000001543558165_p1317741312289">In the authorized region, perform the following operations:</p>
+<ul id="asm_01_0146__en-us_topic_0000001543558165_ul1692751312242"><li id="asm_01_0146__en-us_topic_0000001543558165_li205729227246">Choose <strong id="asm_01_0146__b160142117265">Service List</strong> &gt; <strong id="asm_01_0146__b760112213264">Application Service Mesh</strong>. Click <strong id="asm_01_0146__b1660272114269">Buy Mesh</strong> on the ASM console. If a message appears indicating that you have insufficient permissions to perform the operation, <strong id="asm_01_0146__b160262182618">ASMReadOnlyPolicy</strong> is in effect.</li><li id="asm_01_0146__en-us_topic_0000001543558165_li1857212212418">Choose another service from <strong id="asm_01_0146__b113084327264">Service List</strong>. If a message appears indicating that you have insufficient permissions to access the service, <strong id="asm_01_0146__b030863242611">ASMReadOnlyPolicy</strong> is in effect.</li></ul>
+</li></ol>
+</div>
+<div class="section" id="asm_01_0146__en-us_topic_0000001543558165_section7529733164812"><h4 class="sectiontitle">Example Custom Identity Policies</h4><p id="asm_01_0146__p19154121744816">You can create custom identity policies to supplement the system-defined identity policies of ASM. For details about actions supported in custom identity policies, see .</p>
+<p id="asm_01_0146__en-us_topic_0000001543558165_p1391019913815">To create a custom identity policy, choose either visual editor or JSON.</p>
+<ul id="asm_01_0146__en-us_topic_0000001543558165_ul1146431393818"><li id="asm_01_0146__en-us_topic_0000001543558165_li5764181518386">Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy grammar.</li><li id="asm_01_0146__en-us_topic_0000001543558165_li546410135389">JSON: Create a JSON policy or edit an existing one.</li></ul>
+<p id="asm_01_0146__p160623765212">For details, see .</p>
+<p id="asm_01_0146__p17139055195519">When creating a custom identity policy, use the Resource element to specify the resources the identity policy applies to and use the Condition element (service-specific condition keys) to control when the identity policy is in effect. For details about the supported resource types and condition keys, see .</p>
+<p id="asm_01_0146__p310122114562">The following provides examples of custom ASM identity policies.</p>
+<ul id="asm_01_0146__en-us_topic_0000001543558165_ul2504185715494"><li id="asm_01_0146__en-us_topic_0000001543558165_li5504357164912">Example 1: Grant permissions to create service meshes.<pre class="screen" id="asm_01_0146__en-us_topic_0000001543558165_screen25351137165916">{
+    "Version": "5.0",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "asm:mesh:create",
+                "asm:mesh:createGateway"
+            ]
+        }
+    ]
+}</pre>
+</li><li id="asm_01_0146__en-us_topic_0000001543558165_li8475316125413">Example 2: Create a custom identity policy containing multiple actions.<p id="asm_01_0146__en-us_topic_0000001543558165_p164313514480"><a name="asm_01_0146__en-us_topic_0000001543558165_li8475316125413"></a><a name="en-us_topic_0000001543558165_li8475316125413"></a></p>
+<p id="asm_01_0146__en-us_topic_0000001543558165_p466319313484">A custom identity policy can contain the actions of one or more services. Example identity policy containing multiple actions:</p>
+<pre class="screen" id="asm_01_0146__en-us_topic_0000001543558165_screen46646311485">{
+    "Version": "5.0",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "asm:mesh:create",
+                "asm:mesh:createGateway"
+            ]
+        },
+        {
+            "Effect": "Allow",
+            "Action": [
+                "evs:volumes:create",
+                "evs:volumes:list"
+            ]
+        },
+        {
+            "Effect": "Allow",
+            "Action": [
+                "ecs:cloudServers:createServers",
+                "ecs:cloudServers:listServersDetails"
+            ]
+        }
+    ]
+}</pre>
+</li></ul>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0141.html">Using IAM to Grant Access to ASM</a></div>
+</div>
+</div>
+

docs/asm/umn/asm_pd_0001.html

@@ -4,8 +4,6 @@
 <div id="body39451090"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="asm_productdesc_0017.html">Infographic for ASM</a></strong><br>
-</li>
 <li class="ulchildlink"><strong><a href="asm_productdesc_0001.html">Introduction</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="asm_productdesc_0002.html">Advantages</a></strong><br>
@@ -14,6 +12,8 @@
 </li>
 <li class="ulchildlink"><strong><a href="asm_productdesc_0004.html">Notes and Constraints</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="asm_productdesc_0019.html">Permissions</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="asm_productdesc_0005.html">Basic Concepts</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="asm_productdesc_0006.html">Recommended Node Specifications</a></strong><br>

docs/asm/umn/asm_productdesc_0004.html

@@ -16,7 +16,7 @@
 </tr>
 <tr id="asm_productdesc_0004__row2060314173555"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.1 "><p id="asm_productdesc_0004__p760391712553">1.18</p>
 </td>
-<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.2 "><p id="asm_productdesc_0004__p14822277556">v1.25, v1.27, v1.28, v1.29, v1.30, or v1.31</p>
+<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.2 "><p id="asm_productdesc_0004__p14822277556">v1.25, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32, or v1.33</p>
 </td>
 </tr>
 </tbody>

docs/asm/umn/asm_productdesc_0017.html

@@ -1,12 +0,0 @@
-<a name="asm_productdesc_0017"></a><a name="asm_productdesc_0017"></a>
-
-<h1 class="topictitle1">Infographic for ASM</h1>
-<div id="body0000001209484931"><p id="asm_productdesc_0017__p1289416386116"></p>
-<p id="asm_productdesc_0017__p837613199456"><span><img id="asm_productdesc_0017__image73201388158" src="en-us_image_0000002043652974.png"></span></p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_pd_0001.html">Service Overview</a></div>
-</div>
-</div>
-

docs/asm/umn/asm_qs_0002.html

@@ -1,6 +1,6 @@
 <a name="asm_qs_0002"></a><a name="asm_qs_0002"></a>
 
-<h1 class="topictitle1">Enabling Istio for a Cluster </h1>
+<h1 class="topictitle1">Enabling Istio for a Cluster</h1>
 <div id="body0000001168400759"></div>
 <div>
 <ul class="ullinks">

docs/asm/umn/en-us_topic_0000001627845328.html

@@ -10,6 +10,8 @@
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="asm_01_0016.html">Application Service Mesh</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="asm_01_0141.html">Using IAM to Grant Access to ASM</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="asm_01_0017.html">Creating a Service Mesh</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="asm_01_0023.html">Mesh Management</a></strong><br>

docs/cce/api-ref/AddNode.html

@@ -730,15 +730,26 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="AddNode__row19231117141516"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.1 "><p id="AddNode__p833114714155">dockerBaseSize</p>
+<tbody><tr id="AddNode__row19231117141516"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.1 "><p id="AddNode__p579610541215">containerBaseSize</p>
 </td>
-<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.2 "><p id="AddNode__p173311275154">No</p>
+<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.2 "><p id="AddNode__p1779611581220">No</p>
 </td>
-<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.3 "><p id="AddNode__p4331167171519">Integer</p>
+<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.3 "><p id="AddNode__p19796145161216">Integer</p>
 </td>
-<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.18.2.5.1.4 "><p id="AddNode__p153311479153">Available disk space of a single container on a node, in GB.</p>
-<p id="AddNode__p123318717150">If this parameter is left blank or is set to <strong id="AddNode__b10331776156">0</strong>, the default value is used. In Device Mapper mode, the default value is <strong id="AddNode__b53310781520">10</strong>. In OverlayFS mode, the available space of a single container is not limited by default, and the <strong id="AddNode__b4331137161520">dockerBaseSize</strong> setting takes effect only on EulerOS nodes in the cluster of the new version.</p>
-<p id="AddNode__p1233215716152">When Device Mapper is used, you are advised to set <strong id="AddNode__b93321781510">dockerBaseSize</strong> to a value less than or equal to 80 GB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device.</p>
+<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.18.2.5.1.4 "><p id="AddNode__p3796185141215"><strong id="AddNode__b107966513126">Definition</strong></p>
+<p id="AddNode__p4796185121211">Available disk space of a single container on a node (unit: G).</p>
+<div class="note" id="AddNode__note187967518129"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="AddNode__ul10796105141216"><li id="AddNode__li19796115111215"><p id="AddNode__p77961581212"><a name="AddNode__li19796115111215"></a><a name="li19796115111215"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li><li id="AddNode__li37962571214"><p id="AddNode__p1579618531212"><a name="AddNode__li37962571214"></a><a name="li37962571214"></a>If this parameter is not specified or is set to <strong id="AddNode__b107965531213">0</strong>, the default value is used. In OverlayFS mode, no fixed limit is imposed on the available space of a single container. In Device Mapper mode, the default value is <strong id="AddNode__b979614531210">10</strong>, and the <strong id="AddNode__b18796550121">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.</p>
+</li><li id="AddNode__li4796255123"><p id="AddNode__p87964516126"><a name="AddNode__li4796255123"></a><a name="li4796255123"></a>For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</p>
+</li><li id="AddNode__li20796251121"><p id="AddNode__p279610581219"><a name="AddNode__li20796251121"></a><a name="li20796251121"></a>When Device Mapper is used, it is recommended that <strong id="AddNode__b1479619513123">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to time-consuming initialization. If there are special requirements for the container disk space, you can mount external or local storage. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being discarded.</p>
+</li></ul>
+<p id="AddNode__p17684155181218">This parameter cannot be updated when a node pool is being updated.</p>
+</div></div>
+<p id="AddNode__p1579675181214"><strong id="AddNode__b107966531214">Constraints</strong></p>
+<p id="AddNode__p1379611510125"><strong id="AddNode__b117969518129">Range</strong></p>
+<p id="AddNode__p137968541217">N/A</p>
+<p id="AddNode__p1379615501217"><strong id="AddNode__b77968515126">Default Value</strong></p>
+<p id="AddNode__p12796358125">N/A</p>
 </td>
 </tr>
 <tr id="AddNode__row7231107111514"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.1 "><p id="AddNode__p203321791517">runtime</p>

docs/cce/api-ref/ResetNode.html

@@ -728,15 +728,26 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="ResetNode__row533425216511"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.1 "><p id="ResetNode__p958665216511">dockerBaseSize</p>
+<tbody><tr id="ResetNode__row533425216511"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.1 "><p id="ResetNode__p6209862129">containerBaseSize</p>
 </td>
-<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.2 "><p id="ResetNode__p458618521257">No</p>
+<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.2 "><p id="ResetNode__p132091617122">No</p>
 </td>
-<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.3 "><p id="ResetNode__p1358613521057">Integer</p>
+<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.3 "><p id="ResetNode__p192101760121">Integer</p>
 </td>
-<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.18.2.5.1.4 "><p id="ResetNode__p758635211512">Available disk space of a single container on a node, in GB.</p>
-<p id="ResetNode__p13586175220512">If this parameter is left blank or is set to <strong id="ResetNode__b19586125217511">0</strong>, the default value is used. In Device Mapper mode, the default value is <strong id="ResetNode__b25861252356">10</strong>. In OverlayFS mode, the available space of a single container is not limited by default, and the <strong id="ResetNode__b145861052155">dockerBaseSize</strong> setting takes effect only on EulerOS nodes in the cluster of the new version.</p>
-<p id="ResetNode__p45861752156">When Device Mapper is used, you are advised to set <strong id="ResetNode__b135863528518">dockerBaseSize</strong> to a value less than or equal to 80 GB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device.</p>
+<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.18.2.5.1.4 "><p id="ResetNode__p72100611126"><strong id="ResetNode__b1821026111220">Definition</strong></p>
+<p id="ResetNode__p11210156181213">Available disk space of a single container on a node (unit: G).</p>
+<div class="note" id="ResetNode__note52108651211"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="ResetNode__ul921010619128"><li id="ResetNode__li13210463125"><p id="ResetNode__p1521066191218"><a name="ResetNode__li13210463125"></a><a name="li13210463125"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li><li id="ResetNode__li1221012621219"><p id="ResetNode__p1321056171214"><a name="ResetNode__li1221012621219"></a><a name="li1221012621219"></a>If this parameter is not specified or is set to <strong id="ResetNode__b22101261122">0</strong>, the default value is used. In OverlayFS mode, no fixed limit is imposed on the available space of a single container. In Device Mapper mode, the default value is <strong id="ResetNode__b62100691218">10</strong>, and the <strong id="ResetNode__b1821011671218">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.</p>
+</li><li id="ResetNode__li121017631219"><p id="ResetNode__p9210369124"><a name="ResetNode__li121017631219"></a><a name="li121017631219"></a>For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</p>
+</li><li id="ResetNode__li122106620125"><p id="ResetNode__p11210196141210"><a name="ResetNode__li122106620125"></a><a name="li122106620125"></a>When Device Mapper is used, it is recommended that <strong id="ResetNode__b1021026171219">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to time-consuming initialization. If there are special requirements for the container disk space, you can mount external or local storage. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being discarded.</p>
+</li></ul>
+<p id="ResetNode__p1575919518120">This parameter cannot be updated when a node pool is being updated.</p>
+</div></div>
+<p id="ResetNode__p0210156171219"><strong id="ResetNode__b42105620126">Constraints</strong></p>
+<p id="ResetNode__p10210967120"><strong id="ResetNode__b42101161129">Range</strong></p>
+<p id="ResetNode__p721015671217">N/A</p>
+<p id="ResetNode__p42106613121"><strong id="ResetNode__b321011614122">Default Value</strong></p>
+<p id="ResetNode__p421066121213">N/A</p>
 </td>
 </tr>
 <tr id="ResetNode__row123341752757"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.18.2.5.1.1 "><p id="ResetNode__p358619521654">runtime</p>

docs/cce/api-ref/cce_02_0083.html

@@ -28,6 +28,8 @@
 </li>
 <li class="ulchildlink"><strong><a href="node_storage_example.html">Attaching Disks to a Node</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="cce_10_0341.html">Space Allocation of a Data Disk</a></strong><br>
+</li>
 </ul>
 </div>
 

docs/cce/api-ref/cce_02_0092.html

@@ -58,6 +58,8 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_02_0357.html">Deleting a Node Pool</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="cce_02_0358.html">Synchronizing Node Pool Configurations to Existing Nodes</a></strong><br>
+</li>
 </ul>
 
 <div class="familylinks">

docs/cce/api-ref/cce_02_0103.html

@@ -20,6 +20,8 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_02_0366.html">Add-on Instance Parameters</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="job_lifecycle_management.html">Job Management</a></strong><br>
+</li>
 </ul>
 </div>
 

docs/cce/api-ref/cce_02_0238.html

@@ -154,16 +154,40 @@
 </td>
 <td class="cellrowborder" valign="top" width="20.93%" headers="mcps1.3.4.5.2.4.1.2 "><p id="cce_02_0238__p252511174227">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="55.81%" headers="mcps1.3.4.5.2.4.1.3 "><p id="cce_02_0238__p0929195015409">Cluster's baseline Kubernetes version. The latest version is recommended.</p>
+<td class="cellrowborder" valign="top" width="55.81%" headers="mcps1.3.4.5.2.4.1.3 "><p id="cce_02_0238__p7573017202218"><strong id="cce_02_0238__b457318173220">Details</strong>:</p>
+<p id="cce_02_0238__p20573111752219">Cluster version, which mirrors the baseline version of the Kubernetes community. The latest commercial version is recommended.</p>
+<p id="cce_02_0238__p12573101792220">You can create clusters of the latest three versions on the CCE console. To learn which cluster versions are available, log in to the CCE console, create a cluster, and check the supported cluster versions.</p>
+<p id="cce_02_0238__p857391712229">You can call APIs to create clusters of other versions. However, these cluster versions will be gradually terminated. For details about the support policy, see the CCE announcement.</p>
+<p id="cce_02_0238__p057318174226"><strong id="cce_02_0238__b115731217112217">Constraints</strong>:</p>
+<p id="cce_02_0238__p1757311713227">The value must be in the format of <strong id="cce_02_0238__b157391712222">vX.Y[.Z[-rN]]</strong>, for example, <strong id="cce_02_0238__b657371732218">v1.30</strong>, <strong id="cce_02_0238__b115739175225">v1.30.0</strong>, or <strong id="cce_02_0238__b165731217172211">v1.30.0-r0</strong>. Specifying either of these values will create a cluster of version 1.30.</p>
+<ul id="cce_02_0238__ul17573717182212"><li id="cce_02_0238__li205731317192216"><p id="cce_02_0238__p15573151792214"><a name="cce_02_0238__li205731317192216"></a><a name="li205731317192216"></a><strong id="cce_02_0238__b957391712229">X</strong>: major version in the Kubernetes community</p>
+</li><li id="cce_02_0238__li1357331702214"><p id="cce_02_0238__p12573181715227"><a name="cce_02_0238__li1357331702214"></a><a name="li1357331702214"></a><strong id="cce_02_0238__b11573121718224">Y</strong>: minor version in the Kubernetes community</p>
+</li><li id="cce_02_0238__li11573181792213"><p id="cce_02_0238__p157331782211"><a name="cce_02_0238__li11573181792213"></a><a name="li11573181792213"></a><strong id="cce_02_0238__b175731117102216">Z</strong>: patch version in the Kubernetes community</p>
+</li><li id="cce_02_0238__li1757341717221"><p id="cce_02_0238__p1957371717225"><a name="cce_02_0238__li1757341717221"></a><a name="li1757341717221"></a><strong id="cce_02_0238__b857371772218">N</strong>: CCE patch version.</p>
+</li></ul>
+<p id="cce_02_0238__p13573101732213"><strong id="cce_02_0238__b4573517122217">Options</strong>:</p>
+<p id="cce_02_0238__p10573181713224">N/A</p>
+<p id="cce_02_0238__p557301752218"><strong id="cce_02_0238__b1257319178223">Default value</strong>:</p>
+<ul id="cce_02_0238__ul357312171221"><li id="cce_02_0238__li15573101702210"><p id="cce_02_0238__p657313172224"><a name="cce_02_0238__li15573101702210"></a><a name="li15573101702210"></a>If this parameter is left empty, a cluster of the latest version is created by default.</p>
+</li><li id="cce_02_0238__li957312171223"><p id="cce_02_0238__p165731717122215"><a name="cce_02_0238__li957312171223"></a><a name="li957312171223"></a>If a baseline cluster version is specified but the R version is not specified, a cluster of the latest R version will be created by default. It is a good practice not to specify the R version.</p>
+</li></ul>
 </td>
 </tr>
 <tr id="cce_02_0238__row1126035716393"><td class="cellrowborder" valign="top" width="23.26%" headers="mcps1.3.4.5.2.4.1.1 "><p id="cce_02_0238__p1884144893515">platformVersion</p>
 </td>
 <td class="cellrowborder" valign="top" width="20.93%" headers="mcps1.3.4.5.2.4.1.2 "><p id="cce_02_0238__p284124873520">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="55.81%" headers="mcps1.3.4.5.2.4.1.3 "><p id="cce_02_0238__p38411148113510">Version of the CCE cluster platform, which is for viewing only and cannot be specified during cluster creation. The latest platform version corresponding to the cluster version is automatically selected during cluster creation.</p>
-<div class="p" id="cce_02_0238__p10350184112363">Value format: <strong id="cce_02_0238__b9950204813384">cce.X.Y</strong><ul id="cce_02_0238__ul24765594314"><li id="cce_02_0238__li14761859431"><strong id="cce_02_0238__b146921148154814">X</strong> indicates the quarterly or regularly feature version number, starting from 1.</li><li id="cce_02_0238__li84766513437"><strong id="cce_02_0238__b8450650184815">Y</strong> indicates the patch version of the cluster, starting from 0 (feature version). Other values indicate later patch versions after the feature version is released.</li></ul>
-</div>
+<td class="cellrowborder" valign="top" width="55.81%" headers="mcps1.3.4.5.2.4.1.3 "><p id="cce_02_0238__p857316175224"><strong id="cce_02_0238__b125737175223">Details</strong>:</p>
+<p id="cce_02_0238__p1057361782211">CCE cluster platform version, which is an internal version under the cluster version (<strong id="cce_02_0238__b175731517122218">version</strong>). Platform versions are used to trace iterations in a major cluster version. They are unique within a major cluster version and recounted when the major cluster version changes.</p>
+<p id="cce_02_0238__p1657311170220"><strong id="cce_02_0238__b20573141712222">Constraints</strong>:</p>
+<p id="cce_02_0238__p165735172225">This parameter cannot be customized, and when you create a cluster, the latest corresponding platform version is selected automatically.</p>
+<p id="cce_02_0238__p18573131718224"><strong id="cce_02_0238__b1257310170222">Options</strong>:</p>
+<p id="cce_02_0238__p18573131752216">The format of <strong id="cce_02_0238__b257411702211">platformVersion</strong> is <strong id="cce_02_0238__b20574517132216">cce.X.Y</strong>.</p>
+<ul id="cce_02_0238__ul357414179228"><li id="cce_02_0238__li1257416178223"><p id="cce_02_0238__p5574101713228"><a name="cce_02_0238__li1257416178223"></a><a name="li1257416178223"></a><strong id="cce_02_0238__b11574617102212">X</strong>: internal feature version, which indicates changes in features, patches, or OS support in the cluster version. The value starts from <strong id="cce_02_0238__b19574217192218">1</strong> and increases monotonically.</p>
+</li><li id="cce_02_0238__li6574131714225"><p id="cce_02_0238__p10574131752217"><a name="cce_02_0238__li6574131714225"></a><a name="li6574131714225"></a><strong id="cce_02_0238__b3574101710227">Y</strong>: patch version of an internal feature version. It is used only for software package update after the feature version is released. No other modification is involved. The value starts from <strong id="cce_02_0238__b15574817182211">0</strong> and increases monotonically.</p>
+</li></ul>
+<p id="cce_02_0238__p357413172228"><strong id="cce_02_0238__b1957431714221">Default value</strong>:</p>
+<p id="cce_02_0238__p1157413170228">N/A</p>
 </td>
 </tr>
 <tr id="cce_02_0238__row533805884917"><td class="cellrowborder" valign="top" width="23.26%" headers="mcps1.3.4.5.2.4.1.1 "><p id="cce_02_0238__p1633905884915">az</p>

docs/cce/api-ref/cce_02_0242.html

@@ -525,13 +525,27 @@
 <td class="cellrowborder" valign="top" width="49.01960784313725%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0242__p3419323992">Specifies the IAM agency name.</p>
 </td>
 </tr>
-<tr id="cce_02_0242__row16874635181011"><td class="cellrowborder" valign="top" width="20.15686274509804%" headers="mcps1.3.3.10.2.5.1.1 "><p id="cce_02_0242__p1917197105716">dockerBaseSize</p>
+<tr id="cce_02_0242__row16874635181011"><td class="cellrowborder" valign="top" width="20.15686274509804%" headers="mcps1.3.3.10.2.5.1.1 "><p id="cce_02_0242__p728111882717">containerBaseSize</p>
 </td>
-<td class="cellrowborder" valign="top" width="15.931372549019606%" headers="mcps1.3.3.10.2.5.1.2 "><p id="cce_02_0242__p389518122571">No</p>
+<td class="cellrowborder" valign="top" width="15.931372549019606%" headers="mcps1.3.3.10.2.5.1.2 "><p id="cce_02_0242__p1728141852718">No</p>
 </td>
-<td class="cellrowborder" valign="top" width="14.892156862745098%" headers="mcps1.3.3.10.2.5.1.3 "><p id="cce_02_0242__p15176712576">Integer</p>
+<td class="cellrowborder" valign="top" width="14.892156862745098%" headers="mcps1.3.3.10.2.5.1.3 "><p id="cce_02_0242__p6284187278">Integer</p>
 </td>
-<td class="cellrowborder" valign="top" width="49.01960784313725%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0242__p18174765710">Available disk space of a single Docker container on the node using the device mapper.</p>
+<td class="cellrowborder" valign="top" width="49.01960784313725%" headers="mcps1.3.3.10.2.5.1.4 "><p id="cce_02_0242__p72891816277"><strong id="cce_02_0242__b828171852718">Details</strong>:</p>
+<p id="cce_02_0242__p132831819278">Available disk space of a single container on a node (unit: G).</p>
+<p id="cce_02_0242__p928171892719">For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
+<p id="cce_02_0242__p13281818102713"><strong id="cce_02_0242__b9289182279">Constraints</strong>:</p>
+<p id="cce_02_0242__p20282181278">When Device Mapper is used, it is recommended that <strong id="cce_02_0242__b142816187278">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.</p>
+<ul id="cce_02_0242__ul1828141819278"><li id="cce_02_0242__li728918152714"><p id="cce_02_0242__p182801811274"><a name="cce_02_0242__li728918152714"></a><a name="li728918152714"></a>The <strong id="cce_02_0242__b152891818273">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).</p>
+</li><li id="cce_02_0242__li128181819279"><p id="cce_02_0242__p1728121862710"><a name="cce_02_0242__li128181819279"></a><a name="li128181819279"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li></ul>
+<p id="cce_02_0242__p5281189279"><strong id="cce_02_0242__b102831802714">Options</strong>:</p>
+<p id="cce_02_0242__p1929101819277">10 to 500</p>
+<p id="cce_02_0242__p112911822716"><strong id="cce_02_0242__b429131832714">Default value</strong>:</p>
+<p id="cce_02_0242__p1929418182716">If the value is not specified or is set to 0, the default value is used.</p>
+<ul id="cce_02_0242__ul1929141842717"><li id="cce_02_0242__li142917187279"><p id="cce_02_0242__p122941819279"><a name="cce_02_0242__li142917187279"></a><a name="li142917187279"></a>The default value is <strong id="cce_02_0242__b1029101816271">10</strong> in Device Mapper mode.</p>
+</li><li id="cce_02_0242__li1429151852715"><p id="cce_02_0242__p82981862715"><a name="cce_02_0242__li1429151852715"></a><a name="li1429151852715"></a>In OverlayFS mode, the available space of a single container is not limited by default.</p>
+</li></ul>
 </td>
 </tr>
 <tr id="cce_02_0242__row9333104293318"><td class="cellrowborder" valign="top" width="20.15686274509804%" headers="mcps1.3.3.10.2.5.1.1 "><p id="cce_02_0242__p203338425338">alpha.cce/preInstall</p>
@@ -1736,11 +1750,26 @@
 <td class="cellrowborder" valign="top" width="56.00000000000001%" headers="mcps1.3.4.9.2.4.1.3 "><p id="cce_02_0242__p720391621210">Maximum number of pods on the node.</p>
 </td>
 </tr>
-<tr id="cce_02_0242__row144531347131912"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.9.2.4.1.1 "><p id="cce_02_0242__p67621357536">dockerBaseSize</p>
+<tr id="cce_02_0242__row144531347131912"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.9.2.4.1.1 "><p id="cce_02_0242__p1601456182610">containerBaseSize</p>
 </td>
-<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.9.2.4.1.2 "><p id="cce_02_0242__p1976214115310">Integer</p>
+<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.9.2.4.1.2 "><p id="cce_02_0242__p170756172615">No</p>
 </td>
-<td class="cellrowborder" valign="top" width="56.00000000000001%" headers="mcps1.3.4.9.2.4.1.3 "><p id="cce_02_0242__p197620112533">Available disk space of a single Docker container on the node using the device mapper.</p>
+<td class="cellrowborder" valign="top" width="56.00000000000001%" headers="mcps1.3.4.9.2.4.1.3 "><p id="cce_02_0242__p00165642612">Integer</p>
+<p id="cce_02_0242__p10185622612"><strong id="cce_02_0242__b1065620261">Details</strong>:</p>
+<p id="cce_02_0242__p11065662614">Available disk space of a single container on a node (unit: G).</p>
+<p id="cce_02_0242__p60105617261">For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
+<p id="cce_02_0242__p00205642610"><strong id="cce_02_0242__b50856182614">Constraints</strong>:</p>
+<p id="cce_02_0242__p100145618262">When Device Mapper is used, it is recommended that <strong id="cce_02_0242__b9055662616">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.</p>
+<ul id="cce_02_0242__ul170165614266"><li id="cce_02_0242__li190105617261"><p id="cce_02_0242__p140556152615"><a name="cce_02_0242__li190105617261"></a><a name="li190105617261"></a>The <strong id="cce_02_0242__b1201656142620">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).</p>
+</li><li id="cce_02_0242__li13075620266"><p id="cce_02_0242__p107567262"><a name="cce_02_0242__li13075620266"></a><a name="li13075620266"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li></ul>
+<p id="cce_02_0242__p150856162616"><strong id="cce_02_0242__b1095652618">Options</strong>:</p>
+<p id="cce_02_0242__p601856152618">10 to 500</p>
+<p id="cce_02_0242__p16085615261"><strong id="cce_02_0242__b18085620265">Default value</strong>:</p>
+<p id="cce_02_0242__p1007567265">If the value is not specified or is set to 0, the default value is used.</p>
+<ul id="cce_02_0242__ul90115617262"><li id="cce_02_0242__li8055622616"><p id="cce_02_0242__p6055620265"><a name="cce_02_0242__li8055622616"></a><a name="li8055622616"></a>The default value is <strong id="cce_02_0242__b200175619265">10</strong> in Device Mapper mode.</p>
+</li><li id="cce_02_0242__li1001556122613"><p id="cce_02_0242__p1806568269"><a name="cce_02_0242__li1001556122613"></a><a name="li1001556122613"></a>In OverlayFS mode, the available space of a single container is not limited by default.</p>
+</li></ul>
 </td>
 </tr>
 <tr id="cce_02_0242__row28414286321"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.9.2.4.1.1 "><p id="cce_02_0242__p18552819328">agency_name</p>

docs/cce/api-ref/cce_02_0243.html

@@ -505,11 +505,26 @@
 <td class="cellrowborder" valign="top" width="56.00000000000001%" headers="mcps1.3.4.11.2.4.1.3 "><p id="cce_02_0243__p720391621210">Maximum number of pods on the node.</p>
 </td>
 </tr>
-<tr id="cce_02_0243__row144531347131912"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.11.2.4.1.1 "><p id="cce_02_0243__p67621357536">dockerBaseSize</p>
+<tr id="cce_02_0243__row144531347131912"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.11.2.4.1.1 "><p id="cce_02_0243__p728111882717">containerBaseSize</p>
 </td>
-<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.2.4.1.2 "><p id="cce_02_0243__p1976214115310">Integer</p>
+<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.2.4.1.2 "><p id="cce_02_0243__p1728141852718">No</p>
 </td>
-<td class="cellrowborder" valign="top" width="56.00000000000001%" headers="mcps1.3.4.11.2.4.1.3 "><p id="cce_02_0243__p197620112533">Available disk space of a single Docker container on the node using the device mapper.</p>
+<td class="cellrowborder" valign="top" width="56.00000000000001%" headers="mcps1.3.4.11.2.4.1.3 "><p id="cce_02_0243__p6284187278">Integer</p>
+<p id="cce_02_0243__p72891816277"><strong id="cce_02_0243__b828171852718">Details</strong>:</p>
+<p id="cce_02_0243__p132831819278">Available disk space of a single container on a node (unit: G).</p>
+<p id="cce_02_0243__p928171892719">For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
+<p id="cce_02_0243__p13281818102713"><strong id="cce_02_0243__b9289182279">Constraints</strong>:</p>
+<p id="cce_02_0243__p20282181278">When Device Mapper is used, it is recommended that <strong id="cce_02_0243__b142816187278">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.</p>
+<ul id="cce_02_0243__ul1828141819278"><li id="cce_02_0243__li728918152714"><p id="cce_02_0243__p182801811274"><a name="cce_02_0243__li728918152714"></a><a name="li728918152714"></a>The <strong id="cce_02_0243__b152891818273">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).</p>
+</li><li id="cce_02_0243__li128181819279"><p id="cce_02_0243__p1728121862710"><a name="cce_02_0243__li128181819279"></a><a name="li128181819279"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li></ul>
+<p id="cce_02_0243__p5281189279"><strong id="cce_02_0243__b102831802714">Options</strong>:</p>
+<p id="cce_02_0243__p1929101819277">10 to 500</p>
+<p id="cce_02_0243__p112911822716"><strong id="cce_02_0243__b429131832714">Default value</strong>:</p>
+<p id="cce_02_0243__p1929418182716">If the value is not specified or is set to 0, the default value is used.</p>
+<ul id="cce_02_0243__ul1929141842717"><li id="cce_02_0243__li142917187279"><p id="cce_02_0243__p122941819279"><a name="cce_02_0243__li142917187279"></a><a name="li142917187279"></a>The default value is <strong id="cce_02_0243__b1029101816271">10</strong> in Device Mapper mode.</p>
+</li><li id="cce_02_0243__li1429151852715"><p id="cce_02_0243__p82981862715"><a name="cce_02_0243__li1429151852715"></a><a name="li1429151852715"></a>In OverlayFS mode, the available space of a single container is not limited by default.</p>
+</li></ul>
 </td>
 </tr>
 <tr id="cce_02_0243__row926375016583"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.4.11.2.4.1.1 "><p id="cce_02_0243__p11263165015811">periodType</p>

docs/cce/api-ref/cce_02_0269.html

@@ -444,7 +444,17 @@
 <ul id="cce_02_0269__ul1018212328240"><li id="cce_02_0269__li4182232152415"><strong id="cce_02_0269__b4182173210246">DockerLVMConfigOverride</strong>: Docker data disk configuration item. (This parameter has been discarded. Use the storage field instead.) The following is an example default configuration:<pre class="screen" id="cce_02_0269__screen2182173272419">"DockerLVMConfigOverride":"dockerThinpool=vgpaas/90%VG;kubernetesLV=vgpaas/10%VG;diskType=evs;lvType=linear"</pre>
 <p id="cce_02_0269__p191831232172413">The configuration contains the following fields:</p>
 <ul id="cce_02_0269__ul618333232416"><li id="cce_02_0269__li218373212412"><strong id="cce_02_0269__b1318343232413">userLV</strong>: size of the user space, for example, <strong id="cce_02_0269__b101831532172410">vgpaas/20%VG</strong>.</li><li id="cce_02_0269__li12183193211248"><strong id="cce_02_0269__b51831432202420">userPath</strong>: mount path of the user space, for example, <strong id="cce_02_0269__b11183132192412">/home/wqt-test</strong>.</li><li id="cce_02_0269__li11183113212418"><strong id="cce_02_0269__b1018383212245">diskType</strong>: disk type. Currently, only <strong id="cce_02_0269__b11183203232410">evs</strong>, <strong id="cce_02_0269__b1218383210242">hdd</strong>, and <strong id="cce_02_0269__b1418383222414">ssd</strong> are supported.</li><li id="cce_02_0269__li1518353211246"><strong id="cce_02_0269__b51831328243">lvType</strong>: type of a logic volume. Currently, the value can be <strong id="cce_02_0269__b19183132152415">linear</strong> or <strong id="cce_02_0269__b5183173211248">striped</strong>.</li><li id="cce_02_0269__li121831321249"><strong id="cce_02_0269__b8183163272419">dockerThinpool</strong>: Docker space size, for example, <strong id="cce_02_0269__b1318373214245">vgpaas/60%VG</strong>.</li><li id="cce_02_0269__li3183632142412"><strong id="cce_02_0269__b1318319326248">kubernetesLV</strong>: kubelet space size, for example, <strong id="cce_02_0269__b1183103211241">vgpaas/20%VG</strong>.</li></ul>
-</li><li id="cce_02_0269__li673211271463"><strong id="cce_02_0269__b418319329245">dockerBaseSize</strong>: available disk space of a single Docker container on a node in Device Mapper mode. This field is not supported in OverlayFS mode (nodes that use Ubuntu 18.04 in CCE Turbo clusters and nodes that use Ubuntu 18.04 in CCE clusters).</li><li id="cce_02_0269__li4748142710464"><strong id="cce_02_0269__b117471027184620">init-node-password</strong>: initial node password</li><li id="cce_02_0269__li374822784616"><strong id="cce_02_0269__b1974832784616">offloadNode</strong>: whether the node is a CCE Turbo cluster node. This parameter is not supported when you add a node to a node pool.</li><li id="cce_02_0269__li20748192715461"><strong id="cce_02_0269__b177481827144610">publicKey</strong>: node public key. Used when creating a key pair.</li><li id="cce_02_0269__li157481227114618"><strong id="cce_02_0269__b4748427174620">alpha.cce/preInstall</strong>: pre-installation script.</li></ul>
+</li><li id="cce_02_0269__li673211271463"><strong id="cce_02_0269__b198891320103411">containerBaseSize</strong>: Available disk space of a single container on a node (unit: G). For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.<ul id="cce_02_0269__ul189315643712"><li id="cce_02_0269__li9931256123716"><strong id="cce_02_0269__b1650616501140">Constraints</strong>:<p id="cce_02_0269__p1350611501241">When Device Mapper is used, it is recommended that <strong id="cce_02_0269__b125060501748">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.</p>
+<ul id="cce_02_0269__ul650615501417"><li id="cce_02_0269__li1650612501040"><p id="cce_02_0269__p1350614501446"><a name="cce_02_0269__li1650612501040"></a><a name="li1650612501040"></a>The <strong id="cce_02_0269__b05061750944">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).</p>
+</li><li id="cce_02_0269__li1850635014418"><p id="cce_02_0269__p2050616501442"><a name="cce_02_0269__li1850635014418"></a><a name="li1850635014418"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li></ul>
+</li><li id="cce_02_0269__li1592164416387"><strong id="cce_02_0269__b175061501846">Options</strong>:<p id="cce_02_0269__p85061650549">10 to 500</p>
+</li><li id="cce_02_0269__li18725854193810"><strong id="cce_02_0269__b2506250241">Default value</strong>:<p id="cce_02_0269__p25061550343">If the value is not specified or is set to 0, the default value is used.</p>
+<ul id="cce_02_0269__ul125061850347"><li id="cce_02_0269__li1650665018415"><p id="cce_02_0269__p11506195013412"><a name="cce_02_0269__li1650665018415"></a><a name="li1650665018415"></a>The default value is <strong id="cce_02_0269__b1250620506412">10</strong> in Device Mapper mode.</p>
+</li><li id="cce_02_0269__li12506550545"><p id="cce_02_0269__p4506175020415"><a name="cce_02_0269__li12506550545"></a><a name="li12506550545"></a>In OverlayFS mode, the available space of a single container is not limited by default.</p>
+</li></ul>
+</li></ul>
+</li><li id="cce_02_0269__li4748142710464"><strong id="cce_02_0269__b117471027184620">init-node-password</strong>: initial node password</li><li id="cce_02_0269__li374822784616"><strong id="cce_02_0269__b1974832784616">offloadNode</strong>: whether the node is a CCE Turbo cluster node. This parameter is not supported when you add a node to a node pool.</li><li id="cce_02_0269__li20748192715461"><strong id="cce_02_0269__b177481827144610">publicKey</strong>: node public key. Used when creating a key pair.</li><li id="cce_02_0269__li157481227114618"><strong id="cce_02_0269__b4748427174620">alpha.cce/preInstall</strong>: pre-installation script.</li></ul>
 <div class="note" id="cce_02_0269__note19184163262410"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_02_0269__p31842032162416">The input value must be Base64-encoded. (Command: <strong id="cce_02_0269__b181841732132418">echo -n <em id="cce_02_0269__i2070315592917">Content to be encoded</em> | base64</strong>)</p>
 </div></div>
 <ul id="cce_02_0269__ul418403218247"><li id="cce_02_0269__li9184163218243"><strong id="cce_02_0269__b3184732192414">alpha.cce/postInstall</strong>: post-installation script</li></ul>

docs/cce/api-ref/cce_02_0273.html

@@ -8,12 +8,49 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_02_0273__row164291129171211"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p94305298122"><span id="cce_02_0273__ph8224839151219">2025-10-28</span></p>
+<tbody><tr id="cce_02_0273__row19701173581314"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p12197345161310">2026-03-25</p>
 </td>
-<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p114301129101211"><span id="cce_02_0273__ph192921859151210">Add:</span></p>
-<p id="cce_02_0273__p133191961312">Added the <strong id="cce_02_0273__b179071485168">alpha.cce/postInstall</strong> parameter in <a href="cce_02_0356.html">Updating a Specified Node Pool</a>.</p>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p16701133501314"><span id="cce_02_0273__ph844125216138">Update:</span></p>
+<ul id="cce_02_0273__ul457513123141"><li id="cce_02_0273__li10575012171419">Updated <a href="cce_02_0236.html#cce_02_0236__table1873418287490">Creating a Cluster</a>.</li></ul>
+</td>
+</tr>
+<tr id="cce_02_0273__row71861848111012"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p375512419407">2026-03-11</p>
+</td>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p772953318402">Update:</p>
+<p id="cce_02_0273__p7953154018401">Updated the <strong id="cce_02_0273__b1075864441514">version </strong>and <strong id="cce_02_0273__b6670155712283">platformVersion </strong>parameter description in <a href="cce_02_0236.html#cce_02_0236__table1873418287490">Creating a Cluster</a>.</p>
+</td>
+</tr>
+<tr id="cce_02_0273__row1532514274613"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p13251042194613">2026-03-03</p>
+</td>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p18683122112478">Add:</p>
+<p id="cce_02_0273__p3206142711472">Added the <strong id="cce_02_0273__b472019529478">deletionProtection</strong><strong id="cce_02_0273__b127203529470"> </strong>parameter in <a href="cce_02_0236.html#cce_02_0236__table1873418287490">Creating a Cluster</a>.</p>
+</td>
+</tr>
+<tr id="cce_02_0273__row49801816133713"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p14980516203713">2025-12-30</p>
+</td>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p9854163373718">Add:</p>
+<ul id="cce_02_0273__ul15346173063516"><li id="cce_02_0273__li183462302352">Added <a href="cce_02_0358.html">Synchronizing Node Pool Configurations to Existing Nodes</a>.</li></ul>
+<ul id="cce_02_0273__ul734693033511"><li id="cce_02_0273__li2346193016357">Added <a href="BatchCreateAddonPrecheck.html">Creating Add-on Check Tasks in Batches</a> and <a href="ListAddonPrecheckTasks.html">Obtaining the Add-on Check Task Results</a>.</li><li id="cce_02_0273__li4202154012366">Added <a href="job_lifecycle_management.html">Job Management</a>.</li><li id="cce_02_0273__li69412057121113">Added the <strong id="cce_02_0273__b14410380139">support-overload</strong> and <strong id="cce_02_0273__b5395111313131">dataplane-v2</strong> parameter description in <a href="cce_02_0236.html#cce_02_0236__table1873418287490">Creating a Cluster</a>.</li></ul>
+</td>
+</tr>
+<tr id="cce_02_0273__row12582114032717"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p175822407279">2025-11-25</p>
+</td>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p1582164012279">Add:</p>
+<p id="cce_02_0273__p1573514082813">Added the <strong id="cce_02_0273__b97209195284">userTags</strong> parameter in <a href="cce_02_0356.html">Updating a Specified Node Pool</a>.</p>
+</td>
+</tr>
+<tr id="cce_02_0273__row68081447162412"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p19808154710245">2025-11-06</p>
+</td>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p4808144792419">Update:</p>
+<ul id="cce_02_0273__ul11715109310"><li id="cce_02_0273__li3731020314">Updated the parameter <strong id="cce_02_0273__b8242530133014">dockerBaseSize</strong> to <strong id="cce_02_0273__b07283518302">containerBaseSize</strong> in <a href="cce_02_0242.html">Creating a Node</a> , <a href="cce_02_0243.html">Reading a Specified Node</a> , <a href="AddNode.html">Accepting a Node</a> , <a href="ResetNode.html">Resetting a Node</a> , <a href="cce_02_0269.html">Listing All Node Pools in a Specified Cluster</a> , <a href="cce_02_0357.html">Deleting a Node Pool</a>.</li></ul>
+</td>
+</tr>
+<tr id="cce_02_0273__row164291129171211"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p94305298122">2025-10-28</p>
+</td>
+<td class="cellrowborder" valign="top" width="82.02000000000001%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_02_0273__p114301129101211">Add:</p>
+<ul id="cce_02_0273__ul765913473115"><li id="cce_02_0273__li366024203119">Added the <strong id="cce_02_0273__b179071485168">alpha.cce/postInstall</strong> parameter in <a href="cce_02_0356.html">Updating a Specified Node Pool</a>.</li></ul>
 <p id="cce_02_0273__p14731931122411">Delete:</p>
-<p id="cce_02_0273__p1697195017298">Removed the <strong id="cce_02_0273__b16304144142617">cluster_id</strong> from the URI in <a href="cce_02_0324.html">Deleting an Add-on Instance</a> , <a href="cce_02_0325.html">Reading an Add-on Instance</a> , <a href="cce_02_0326.html">Listing Add-on Instances</a>.</p>
+<ul id="cce_02_0273__ul1048918712313"><li id="cce_02_0273__li154891674311">Removed the <strong id="cce_02_0273__b16304144142617">cluster_id</strong> from the URI in <a href="cce_02_0324.html">Deleting an Add-on Instance</a> , <a href="cce_02_0325.html">Reading an Add-on Instance</a> , <a href="cce_02_0326.html">Listing Add-on Instances</a>.</li></ul>
 </td>
 </tr>
 <tr id="cce_02_0273__row39101651122310"><td class="cellrowborder" valign="top" width="17.98%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_02_0273__p5910551162311">2025-09-12</p>

docs/cce/api-ref/cce_02_0320.html

@@ -16,6 +16,10 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_02_0326.html">Listing Add-on Instances</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="BatchCreateAddonPrecheck.html">Creating Add-on Check Tasks in Batches</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="ListAddonPrecheckTasks.html">Obtaining the Add-on Check Task Results</a></strong><br>
+</li>
 </ul>
 
 <div class="familylinks">

docs/cce/api-ref/cce_02_0357.html

@@ -384,7 +384,17 @@
 <ul id="cce_02_0357__ul1018212328240"><li id="cce_02_0357__li4182232152415"><strong id="cce_02_0357__b4182173210246">DockerLVMConfigOverride</strong>: Docker data disk configuration item. (This parameter has been discarded. Use the storage field instead.) The following is an example default configuration:<pre class="screen" id="cce_02_0357__screen2182173272419">"DockerLVMConfigOverride":"dockerThinpool=vgpaas/90%VG;kubernetesLV=vgpaas/10%VG;diskType=evs;lvType=linear"</pre>
 <p id="cce_02_0357__p191831232172413">The configuration contains the following fields:</p>
 <ul id="cce_02_0357__ul618333232416"><li id="cce_02_0357__li218373212412"><strong id="cce_02_0357__b1318343232413">userLV</strong>: size of the user space, for example, <strong id="cce_02_0357__b101831532172410">vgpaas/20%VG</strong>.</li><li id="cce_02_0357__li12183193211248"><strong id="cce_02_0357__b51831432202420">userPath</strong>: mount path of the user space, for example, <strong id="cce_02_0357__b11183132192412">/home/wqt-test</strong>.</li><li id="cce_02_0357__li11183113212418"><strong id="cce_02_0357__b1018383212245">diskType</strong>: disk type. Currently, only <strong id="cce_02_0357__b11183203232410">evs</strong>, <strong id="cce_02_0357__b1218383210242">hdd</strong>, and <strong id="cce_02_0357__b1418383222414">ssd</strong> are supported.</li><li id="cce_02_0357__li1518353211246"><strong id="cce_02_0357__b51831328243">lvType</strong>: type of a logic volume. Currently, the value can be <strong id="cce_02_0357__b19183132152415">linear</strong> or <strong id="cce_02_0357__b5183173211248">striped</strong>.</li><li id="cce_02_0357__li121831321249"><strong id="cce_02_0357__b8183163272419">dockerThinpool</strong>: Docker space size, for example, <strong id="cce_02_0357__b1318373214245">vgpaas/60%VG</strong>.</li><li id="cce_02_0357__li3183632142412"><strong id="cce_02_0357__b1318319326248">kubernetesLV</strong>: kubelet space size, for example, <strong id="cce_02_0357__b1183103211241">vgpaas/20%VG</strong>.</li></ul>
-</li><li id="cce_02_0357__li673211271463"><strong id="cce_02_0357__b418319329245">dockerBaseSize</strong>: available disk space of a single Docker container on a node in Device Mapper mode. This field is not supported in OverlayFS mode (nodes that use Ubuntu 18.04 in CCE Turbo clusters and nodes that use Ubuntu 18.04 in CCE clusters).</li><li id="cce_02_0357__li4748142710464"><strong id="cce_02_0357__b117471027184620">init-node-password</strong>: initial node password</li><li id="cce_02_0357__li374822784616"><strong id="cce_02_0357__b1974832784616">offloadNode</strong>: whether the node is a CCE Turbo cluster node.</li><li id="cce_02_0357__li20748192715461"><strong id="cce_02_0357__b177481827144610">publicKey</strong>: node public key. Used when creating a key pair.</li><li id="cce_02_0357__li157481227114618"><strong id="cce_02_0357__b4748427174620">alpha.cce/preInstall</strong>: pre-installation script.</li></ul>
+</li><li id="cce_02_0357__li191611937174113"><strong id="cce_02_0357__b198891320103411">containerBaseSize</strong>: Available disk space of a single container on a node (unit: G). For details about how to allocate the space for the container runtime, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.<ul id="cce_02_0357__ul189315643712"><li id="cce_02_0357__li9931256123716"><strong id="cce_02_0357__b1650616501140">Constraints</strong>:<p id="cce_02_0357__p1350611501241">When Device Mapper is used, it is recommended that <strong id="cce_02_0357__b125060501748">containerBaseSize</strong> be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.</p>
+<ul id="cce_02_0357__ul650615501417"><li id="cce_02_0357__li1650612501040"><p id="cce_02_0357__p1350614501446"><a name="cce_02_0357__li1650612501040"></a><a name="li1650612501040"></a>The <strong id="cce_02_0357__b05061750944">containerBaseSize</strong> setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).</p>
+</li><li id="cce_02_0357__li1850635014418"><p id="cce_02_0357__p2050616501442"><a name="cce_02_0357__li1850635014418"></a><a name="li1850635014418"></a>This parameter cannot be updated when a node pool is being updated.</p>
+</li></ul>
+</li><li id="cce_02_0357__li1592164416387"><strong id="cce_02_0357__b175061501846">Options</strong>:<p id="cce_02_0357__p85061650549">10 to 500</p>
+</li><li id="cce_02_0357__li18725854193810"><strong id="cce_02_0357__b2506250241">Default value</strong>:<p id="cce_02_0357__p25061550343">If the value is not specified or is set to 0, the default value is used.</p>
+<ul id="cce_02_0357__ul125061850347"><li id="cce_02_0357__li1650665018415"><p id="cce_02_0357__p11506195013412"><a name="cce_02_0357__li1650665018415"></a><a name="li1650665018415"></a>The default value is <strong id="cce_02_0357__b1250620506412">10</strong> in Device Mapper mode.</p>
+</li><li id="cce_02_0357__li12506550545"><p id="cce_02_0357__p4506175020415"><a name="cce_02_0357__li12506550545"></a><a name="li12506550545"></a>In OverlayFS mode, the available space of a single container is not limited by default.</p>
+</li></ul>
+</li></ul>
+</li><li id="cce_02_0357__li4748142710464"><strong id="cce_02_0357__b117471027184620">init-node-password</strong>: initial node password</li><li id="cce_02_0357__li374822784616"><strong id="cce_02_0357__b1974832784616">offloadNode</strong>: whether the node is a CCE Turbo cluster node.</li><li id="cce_02_0357__li20748192715461"><strong id="cce_02_0357__b177481827144610">publicKey</strong>: node public key. Used when creating a key pair.</li><li id="cce_02_0357__li157481227114618"><strong id="cce_02_0357__b4748427174620">alpha.cce/preInstall</strong>: pre-installation script.</li></ul>
 <div class="note" id="cce_02_0357__note19184163262410"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_02_0357__p31842032162416">The input value must be Base64-encoded. (Command: <strong id="cce_02_0357__b181841732132418">echo -n <em id="cce_02_0357__i2070315592917">Content to be encoded</em> | base64</strong>)</p>
 </div></div>
 <ul id="cce_02_0357__ul418403218247"><li id="cce_02_0357__li9184163218243"><strong id="cce_02_0357__b3184732192414">alpha.cce/postInstall</strong>: post-installation script</li></ul>

docs/cce/api-ref/job_lifecycle_management.html

@@ -0,0 +1,20 @@
+<a name="job_lifecycle_management"></a><a name="job_lifecycle_management"></a>
+
+<h1 class="topictitle1">Job Management</h1>
+<div id="body32001227"><p>    </p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="ListJobs.html">Obtaining the Job List</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="GetOneJob.html">Obtaining Job Details</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="DeleteJob.html">Deleting a Job</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_02_0103.html">APIs</a></div>
+</div>
+</div>
+

docs/cce/api-ref/node_storage_example.html

@@ -15,7 +15,7 @@ storageDevice=/dev/vdb
 vgcreate ${vgName} ${storageDevice}</pre>
 </div>
 </li><li id="node_storage_example__en-us_topic_0000001207069618_li23058191031">EVS disks match the disks created in <strong id="node_storage_example__en-us_topic_0000001207069618_b121287102717">dataVolumes</strong> based on the settings of <strong id="node_storage_example__en-us_topic_0000001207069618_b131291350152416">matchLabels</strong>.</li></ol>
-</li><li id="node_storage_example__en-us_topic_0000001207069618_li117111634433">Policies have priorities to match <strong id="node_storage_example__en-us_topic_0000001207069618_b1925417132278">matchLabels</strong>. The <strong id="node_storage_example__en-us_topic_0000001207069618_b204408516511">matchLabels</strong> policy nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b41561438317">storageSelectors</strong> has a higher priority and the disk nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b1491422012711">dataVolumes</strong> will be preferentially matches. As <strong id="node_storage_example__en-us_topic_0000001207069618_b13629123310290">matchLabels</strong> uses loose matching, you are advised to place the <strong id="node_storage_example__en-us_topic_0000001207069618_b1092135719611">matchLabels</strong> policy with a small matching range on the top. For example:<div class="p" id="node_storage_example__en-us_topic_0000001207069618_p177629163419"><span><img id="node_storage_example__en-us_topic_0000001207069618_image5240152411538" src="en-us_image_0000001207617538.png" title="Click to enlarge" class="imgResize"></span><ol type="a" id="node_storage_example__en-us_topic_0000001207069618_ol1754716742"><li id="node_storage_example__en-us_topic_0000001207069618_li9541116248">In step 1, the first disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b113884264325">dataVolumes</strong> is matched by the EVS disk whose size is 100 GiB and storage class is SAS. In step 2, the second disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b1674773313449">dataVolumes</strong> is matched by the EVS disk whose size is 100 GiB because the first disk has been selected.</li><li id="node_storage_example__en-us_topic_0000001207069618_li25415160410">In step 3, two disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b1191053713331">dataVolumes</strong> can be matched because <strong id="node_storage_example__en-us_topic_0000001207069618_b153181629153315">volumeType</strong> or <strong id="node_storage_example__en-us_topic_0000001207069618_b119099318338">count</strong> is not specified in <strong id="node_storage_example__en-us_topic_0000001207069618_b75458247126">matchLabels</strong>. In this case, no disk is available for matching in step 4.</li></ol>
+</li><li id="node_storage_example__en-us_topic_0000001207069618_li117111634433">Policies have priorities to match <strong id="node_storage_example__en-us_topic_0000001207069618_b1925417132278">matchLabels</strong>. The <strong id="node_storage_example__en-us_topic_0000001207069618_b204408516511">matchLabels</strong> policy nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b41561438317">storageSelectors</strong> has a higher priority and the disk nearest to <strong id="node_storage_example__en-us_topic_0000001207069618_b1491422012711">dataVolumes</strong> will be preferentially matches. As <strong id="node_storage_example__en-us_topic_0000001207069618_b13629123310290">matchLabels</strong> uses loose matching, you are advised to place the <strong id="node_storage_example__en-us_topic_0000001207069618_b1092135719611">matchLabels</strong> policy with a small matching range on the top. For example:<div class="p" id="node_storage_example__en-us_topic_0000001207069618_p177629163419"><span><img id="node_storage_example__en-us_topic_0000001207069618_image5240152411538" src="en-us_image_0000001207617538.png" title="Click to enlarge" class="imgResize"></span><ol type="a" id="node_storage_example__en-us_topic_0000001207069618_ol1754716742"><li id="node_storage_example__en-us_topic_0000001207069618_li9541116248">In step 1, the first disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b113884264325">dataVolumes</strong> is matched by the EVS disk whose size is 100 GiB and storage class is SAS. In step 2, the second disk in <strong id="node_storage_example__en-us_topic_0000001207069618_b1674773313449">dataVolumes</strong> is matched by the EVS disk whose size is 100 GiB because the first disk has been selected.</li><li id="node_storage_example__en-us_topic_0000001207069618_li25415160410">In step 3, two disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b958618181359">dataVolumes</strong> can be matched because <strong id="node_storage_example__en-us_topic_0000001207069618_b4587141815517">volumeType</strong> or <strong id="node_storage_example__en-us_topic_0000001207069618_b8587018057">count</strong> is not specified. In this case, no disk is available for matching in step 4.</li></ol>
 </div>
 </li><li id="node_storage_example__en-us_topic_0000001207069618_li78286464319"><strong id="node_storage_example__en-us_topic_0000001207069618_b181371053114510">storageGroups</strong> associates with <strong id="node_storage_example__en-us_topic_0000001207069618_b16743185584513">storageSelectors</strong> based on <strong id="node_storage_example__en-us_topic_0000001207069618_b7844135573316">selectorName</strong>. Finally, two 100 GiB disks are selected. The CCE backend groups the two PVs into a volume group (VG) and divides the VG into two logical volumes (LVs) in the ratio of 9:1. 10% of Kubernetes LVs are partitioned in striped mode. 90% runtime LVs are partitioned in linear mode by default because runtimeConfig is not configured.</li></ol>
 </div>
@@ -218,7 +218,7 @@ vgcreate ${vgName} ${storageDevice}</pre>
 </div>
 <div class="section" id="node_storage_example__en-us_topic_0000001207069618_section163256264156"><h4 class="sectiontitle">Creating Striped LVs to Improve Disk Performance</h4><p id="node_storage_example__en-us_topic_0000001207069618_p12858184310159">Currently, the striped LV function is supported only by calling an API. The following is an example:</p>
 <p id="node_storage_example__en-us_topic_0000001207069618_p911834651514"><span><img id="node_storage_example__en-us_topic_0000001207069618_image1389812341168" src="en-us_image_0000001252020583.png" title="Click to enlarge" class="imgResize"></span></p>
-<ol id="node_storage_example__en-us_topic_0000001207069618_ol7789413121719"><li id="node_storage_example__en-us_topic_0000001207069618_li17891013121712"><strong id="node_storage_example__en-us_topic_0000001207069618_b154262614309">storageSelectors</strong> matches all EVS disks in <strong id="node_storage_example__en-us_topic_0000001207069618_b15422634143016">dataVolumes</strong> because <strong id="node_storage_example__en-us_topic_0000001207069618_b10454154613011">matchLabels</strong> is not contained in <strong id="node_storage_example__en-us_topic_0000001207069618_b33031551153018">storageSelectors</strong>.</li><li id="node_storage_example__en-us_topic_0000001207069618_li12789131310171">Create a VG named <strong id="node_storage_example__en-us_topic_0000001207069618_b89501408324">vgpaas</strong> using LVM.</li><li id="node_storage_example__en-us_topic_0000001207069618_li3789161317176">Strip 90% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b1914129113217">vgpaas</strong> space into runtime LVs.</li><li id="node_storage_example__en-us_topic_0000001207069618_li157893136179">Strip 10% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b14091386321">vgpaas</strong> space into Kubernetes LVs.</li></ol>
+<ol id="node_storage_example__en-us_topic_0000001207069618_ol7789413121719"><li id="node_storage_example__en-us_topic_0000001207069618_li17891013121712">If <strong id="node_storage_example__en-us_topic_0000001207069618_b1864610411482">matchLabels</strong> in <strong id="node_storage_example__en-us_topic_0000001207069618_b14163134418819">storageSelectors</strong> is empty, all EVS disks will be selected.</li><li id="node_storage_example__en-us_topic_0000001207069618_li12789131310171">Create a VG named <strong id="node_storage_example__en-us_topic_0000001207069618_b89501408324">vgpaas</strong> using LVM.</li><li id="node_storage_example__en-us_topic_0000001207069618_li3789161317176">Strip 90% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b1914129113217">vgpaas</strong> space into runtime LVs.</li><li id="node_storage_example__en-us_topic_0000001207069618_li157893136179">Strip 10% of the <strong id="node_storage_example__en-us_topic_0000001207069618_b14091386321">vgpaas</strong> space into Kubernetes LVs.</li></ol>
 <div class="note" id="node_storage_example__en-us_topic_0000001207069618_note1598564031718"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="node_storage_example__en-us_topic_0000001207069618_ul77543234504"><li id="node_storage_example__en-us_topic_0000001207069618_li7790024155011">Two or more data disks are required for striping.</li><li id="node_storage_example__en-us_topic_0000001207069618_li18754102315014">When creating a striped LV, ensure that the types and sizes of the PVs added to the VG are the same. Otherwise, the creation will fail.</li><li id="node_storage_example__en-us_topic_0000001207069618_li32967561071">When creating a striped LV, use the striping configuration for both the runtime LV and Kubernetes LV. Otherwise, the creation will fail.</li></ul>
 </div></div>
 <p id="node_storage_example__en-us_topic_0000001207069618_p1529343517181">Log in to the node and run the following command to view the striping result:</p>