fix pull

Add HCDC workflow
Reviewed-by: Tino Schreiber <tino.schreiber@t-systems.com> Co-authored-by: Sebastian Gode <sebastian.gode@telekom.de> Co-committed-by: Sebastian Gode <sebastian.gode@telekom.de>
2025-09-25 12:44:23 +00:00 · 2025-09-25 12:35:26 +00:00 · 2025-09-22 13:37:59 +00:00 · 2025-09-19 11:31:53 +00:00 · 2025-09-19 10:05:18 +00:00 · 2025-09-19 10:00:40 +00:00
8309 changed files with 419710 additions and 172570 deletions
--- a/.gitea/workflows/run-hcdc.yaml
+++ b/.gitea/workflows/run-hcdc.yaml
@ -0,0 +1,96 @@
+name: Run HCDC
+
+on:
+  pull_request:
+    types: [opened, reopened, synchronize, edited]
+
+jobs:
+  run-hcdc:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout PR head (same repo)
+        if: ${{ gitea.event.pull_request.head.repo.full_name == gitea.repository }}
+        uses: https://github.com/actions/checkout@v4
+        with:
+          repository: ${{ gitea.repository }}
+          ref: ${{ gitea.event.pull_request.head.ref }}
+          fetch-depth: 0
+          persist-credentials: false
+          token: ${{ gitea.token }}
+
+      - name: Checkout PR head (fork via PR ref)
+        if: ${{ gitea.event.pull_request.head.repo.full_name != gitea.repository }}
+        uses: https://github.com/actions/checkout@v4
+        with:
+          repository: ${{ gitea.repository }}
+          ref: refs/pull/${{ gitea.event.pull_request.number }}/head
+          fetch-depth: 0
+          persist-credentials: false
+          token: ${{ gitea.token }}
+
+      - name: Checkout base
+        uses: https://github.com/actions/checkout@v4
+        with:
+          repository: ${{ gitea.repository }}
+          ref: ${{ gitea.event.pull_request.base.ref }}
+          path: base
+          fetch-depth: 0
+          persist-credentials: false
+          token: ${{ gitea.token }}
+
+
+      - name: Get OTC token
+        id: otc
+        uses: https://github.com/opentelekomcloud-infra/github-actions/.github/actions/get-otc-token@v1
+        with:
+            os_username: ${{ secrets.OTC_HCDC_USERNAME }}
+            os_password: ${{ secrets.OTC_HCDC_PASSWORD }}
+            os_domain_name: ${{ secrets.OTC_HCDC_DOMAIN_NAME }}
+            os_project_id: ${{ secrets.OTC_HCDC_PROJECT_ID }}
+
+      - name: Run HCDC
+        id: hcdc
+        uses: https://github.com/opentelekomcloud-infra/github-actions/.github/actions/run-hcdc@v1
+        with:
+          auth_token: ${{ steps.otc.outputs.auth_token }}
+          pr_branch: ${{ gitea.event.pull_request.head.ref }}
+          base_branch: ${{ gitea.event.pull_request.base.ref }}
+          python-version: "3.12"
+    
+      - name: Comment in case there's an error
+        if: ${{ failure() && steps.hcdc.outcome == 'failure' }}
+        env:
+          GITEA_URL: ${{ gitea.server_url }}
+          REPO: ${{ gitea.repository }}
+          PR_NUMBER: ${{ gitea.event.pull_request.number }}
+          TOKEN: ${{ gitea.token }}
+        run: |
+          set -euo pipefail
+
+          MSG="HCDC check detected possible illegal characters. Please check logs and review the affected images/text."
+
+          if [ -f hcdc.json ]; then
+            BODY="$(jq -r --arg msg "$MSG" '
+              def list_paths(obj):
+                (obj.files // []) 
+                | map(select((.detected // false) == true) | .file) 
+                | unique;
+              def section(title; arr):
+                title + ":\n" + (if (arr|length)>0 then (arr | map("- " + .) | join("\n")) else "- (none)" end);
+              $msg + "\n\n"
+              + section("Images"; (try list_paths(.images) catch []))
+              + "\n\n"
+              + section("Text";   (try list_paths(.text)   catch []))
+              | {body: .}
+              | @json
+            ' hcdc.json)"
+          else
+            BODY="$(jq -n --arg msg "$MSG" '{body: $msg}')"
+          fi
+
+          curl -sS --fail-with-body -X POST \
+            -H "Authorization: token ${TOKEN}" \
+            -H "Content-Type: application/json" \
+            "${GITEA_URL}/api/v1/repos/${REPO}/issues/${PR_NUMBER}/comments" \
+            -d "${BODY}"
--- a/docs/asm/api-ref/ALL_META.TXT.json
+++ b/docs/asm/api-ref/ALL_META.TXT.json
@ -49,8 +49,8 @@
 		"search_title":"",
 		"metedata":[
 			{
-				"prodname":"asm",
-				"documenttype":"api"
+				"documenttype":"api",
+				"prodname":"asm"
 			}
 		],
 		"title":"Service Mesh APIs",
@ -61,14 +61,14 @@
 		"node_id":"asm_api_0101.xml",
 		"product_code":"asm",
 		"code":"4",
-		"des":"This API is used to create a service mesh.POST /v1/meshesStatus code: 201Status code: 400Status code: 409Status code: 500Creating a service meshStatus code: 201The servic",
+		"des":"This API is used to create a service mesh.POST /v1/{project_id}/meshesStatus code: 201Status code: 400Status code: 409Status code: 500Creating a service meshStatus code: ",
 		"doc_type":"api",
 		"kw":"Creating a Service Mesh,Service Mesh APIs,API Reference",
 		"search_title":"",
 		"metedata":[
 			{
-				"prodname":"asm",
-				"documenttype":"api"
+				"documenttype":"api",
+				"prodname":"asm"
 			}
 		],
 		"title":"Creating a Service Mesh",
@ -79,14 +79,14 @@
 		"node_id":"asm_api_0102.xml",
 		"product_code":"asm",
 		"code":"5",
-		"des":"This API is used to delete a service mesh.DELETE /v1/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus code: 200The service mesh ",
+		"des":"This API is used to delete a service mesh.DELETE /v1/{project_id}/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus code: 200The ",
 		"doc_type":"api",
 		"kw":"Deleting a Service Mesh,Service Mesh APIs,API Reference",
 		"search_title":"",
 		"metedata":[
 			{
-				"prodname":"asm",
-				"documenttype":"api"
+				"documenttype":"api",
+				"prodname":"asm"
 			}
 		],
 		"title":"Deleting a Service Mesh",
@ -97,14 +97,14 @@
 		"node_id":"asm_api_0103.xml",
 		"product_code":"asm",
 		"code":"6",
-		"des":"This API is used to obtain details about a service mesh.GET /v1/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus code: 200The de",
+		"des":"This API is used to obtain details about a service mesh.GET /v1/{project_id}/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus co",
 		"doc_type":"api",
 		"kw":"Querying a Service Mesh,Service Mesh APIs,API Reference",
 		"search_title":"",
 		"metedata":[
 			{
-				"prodname":"asm",
-				"documenttype":"api"
+				"documenttype":"api",
+				"prodname":"asm"
 			}
 		],
 		"title":"Querying a Service Mesh",
@ -115,14 +115,14 @@
 		"node_id":"asm_api_0104.xml",
 		"product_code":"asm",
 		"code":"7",
-		"des":"This API is used to obtain details about all service meshes.GET /v1/meshesStatus code: 200Status code: 400Status code: 500NoneStatus code: 200The details about all servic",
+		"des":"This API is used to obtain details about all service meshes.GET /v1/{project_id}/meshesStatus code: 200Status code: 400Status code: 500NoneStatus code: 200The details abo",
 		"doc_type":"api",
 		"kw":"Querying the Service Mesh List,Service Mesh APIs,API Reference",
 		"search_title":"",
 		"metedata":[
 			{
-				"prodname":"asm",
-				"documenttype":"api"
+				"documenttype":"api",
+				"prodname":"asm"
 			}
 		],
 		"title":"Querying the Service Mesh List",
--- a/docs/asm/api-ref/CLASS.TXT.json
+++ b/docs/asm/api-ref/CLASS.TXT.json
@ -27,7 +27,7 @@
 		"code":"3"
 	},
 	{
-		"desc":"This API is used to create a service mesh.POST /v1/meshesStatus code: 201Status code: 400Status code: 409Status code: 500Creating a service meshStatus code: 201The servic",
+		"desc":"This API is used to create a service mesh.POST /v1/{project_id}/meshesStatus code: 201Status code: 400Status code: 409Status code: 500Creating a service meshStatus code: ",
 		"product_code":"asm",
 		"title":"Creating a Service Mesh",
 		"uri":"asm_api_0101.html",
@ -36,7 +36,7 @@
 		"code":"4"
 	},
 	{
-		"desc":"This API is used to delete a service mesh.DELETE /v1/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus code: 200The service mesh ",
+		"desc":"This API is used to delete a service mesh.DELETE /v1/{project_id}/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus code: 200The ",
 		"product_code":"asm",
 		"title":"Deleting a Service Mesh",
 		"uri":"asm_api_0102.html",
@ -45,7 +45,7 @@
 		"code":"5"
 	},
 	{
-		"desc":"This API is used to obtain details about a service mesh.GET /v1/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus code: 200The de",
+		"desc":"This API is used to obtain details about a service mesh.GET /v1/{project_id}/meshes/{mesh_id}Status code: 200Status code: 400Status code: 404Status code: 500NoneStatus co",
 		"product_code":"asm",
 		"title":"Querying a Service Mesh",
 		"uri":"asm_api_0103.html",
@ -54,7 +54,7 @@
 		"code":"6"
 	},
 	{
-		"desc":"This API is used to obtain details about all service meshes.GET /v1/meshesStatus code: 200Status code: 400Status code: 500NoneStatus code: 200The details about all servic",
+		"desc":"This API is used to obtain details about all service meshes.GET /v1/{project_id}/meshesStatus code: 200Status code: 400Status code: 500NoneStatus code: 200The details abo",
 		"product_code":"asm",
 		"title":"Querying the Service Mesh List",
 		"uri":"asm_api_0104.html",
--- a/docs/asm/api-ref/asm_api_0021.html
+++ b/docs/asm/api-ref/asm_api_0021.html
@ -8,7 +8,19 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="asm_api_0021__row158031552498"><td class="cellrowborder" valign="top" width="24.310000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="asm_api_0021__p4804952394">2025-03-07</p>
+<tbody><tr id="asm_api_0021__row14384430051"><td class="cellrowborder" valign="top" width="24.310000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="asm_api_0021__p28621736552">2025-06-24</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.69%" headers="mcps1.3.1.1.3.1.2 "><p id="asm_api_0021__p13862153612515">API updates:</p>
+<ul id="asm_api_0021__ul1486214362056"><li id="asm_api_0021__li18862123610519">Deleted <strong id="asm_api_0021__b26497598814">metrics</strong> and <strong id="asm_api_0021__b1978455584">accessLogging</strong> from all APIs.</li><li id="asm_api_0021__li6862336354">Deleted <strong id="asm_api_0021__b17461163815913">metrics</strong> and <strong id="asm_api_0021__b1950510424912">accessLogging</strong> from all example responses.</li></ul>
+</td>
+</tr>
+<tr id="asm_api_0021__row11299185321914"><td class="cellrowborder" valign="top" width="24.310000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="asm_api_0021__p16299195310194">2025-05-06</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.69%" headers="mcps1.3.1.1.3.1.2 "><p id="asm_api_0021__p1038213368222">API updates:</p>
+<ul id="asm_api_0021__ul1738314361228"><li id="asm_api_0021__li83831036112210">Modified API URIs.</li><li id="asm_api_0021__li47221519142314">Modified request and response parameters.</li><li id="asm_api_0021__li338311364220">Modified request and response examples.</li></ul>
+</td>
+</tr>
+<tr id="asm_api_0021__row158031552498"><td class="cellrowborder" valign="top" width="24.310000000000002%" headers="mcps1.3.1.1.3.1.1 "><p id="asm_api_0021__p4804952394">2025-03-07</p>
 </td>
 <td class="cellrowborder" valign="top" width="75.69%" headers="mcps1.3.1.1.3.1.2 "><p id="asm_api_0021__p16804252798">Deleted duplicate links in <a href="asm_api_0012.html">API</a>.</p>
 </td>
--- a/docs/asm/api-ref/asm_api_0101.html
+++ b/docs/asm/api-ref/asm_api_0101.html
--- a/docs/asm/api-ref/asm_api_0102.html
+++ b/docs/asm/api-ref/asm_api_0102.html
--- a/docs/asm/api-ref/asm_api_0103.html
+++ b/docs/asm/api-ref/asm_api_0103.html
--- a/docs/asm/api-ref/asm_api_0104.html
+++ b/docs/asm/api-ref/asm_api_0104.html
--- a/docs/asm/umn/ALL_META.TXT.json
+++ b/docs/asm/umn/ALL_META.TXT.json
--- a/docs/asm/umn/CLASS.TXT.json
+++ b/docs/asm/umn/CLASS.TXT.json
--- a/docs/asm/umn/asm_01_0020.html
+++ b/docs/asm/umn/asm_01_0020.html
@ -4,12 +4,12 @@
 <div id="body8662426"><p id="asm_01_0020__en-us_topic_0000001542706401_p7705103811473">ASM allows you to create a Basic service mesh for commercial use.</p>
 <div class="section" id="asm_01_0020__en-us_topic_0000001542706401_section033812246196"><h4 class="sectiontitle">Prerequisites</h4><p id="asm_01_0020__en-us_topic_0000001542706401_p43381724171910">A CCE cluster is available.</p>
 </div>
-<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">Istio components v1.13 and v1.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 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 Create Mesh 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__b147201102">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">Service mesh names under the same account must be unique and cannot be modified after creation.</p>
-</li><li id="asm_01_0020__en-us_topic_0000001542706401_li3590184362716"><strong id="asm_01_0020__b1937452824">Istio Version</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p19590144310274">Select the Istio version supported by the service mesh.</p>
+<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>
+<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__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>
@ -30,32 +30,32 @@
 </td>
 <td class="cellrowborder" valign="top" width="15.260000000000002%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.3 "><p id="asm_01_0020__p94391954112116">CCE Turbo clusters</p>
 </td>
-<td class="cellrowborder" valign="top" width="20.4%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.4 "><p id="asm_01_0020__p843985414211">Cloud native network 2.0</p>
+<td class="cellrowborder" valign="top" width="20.4%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.4 "><p id="asm_01_0020__p843985414211">Cloud Native Network 2.0</p>
 </td>
-<td class="cellrowborder" valign="top" width="37.05%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.5 "><p id="asm_01_0020__p17439135413211">To enable IPv6.</p>
+<td class="cellrowborder" valign="top" width="37.05%" headers="mcps1.3.4.2.3.2.1.4.3.1.6.1.5 "><p id="asm_01_0020__p17439135413211">IPv6 needs to be enabled for a cluster.</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
-<p id="asm_01_0020__p124428207334">For details, see <a href="asm_bestpractice_1009.html">How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled</a></p>
+<p id="asm_01_0020__p124428207334">For details, see <a href="asm_bestpractice_1009.html">How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled</a>.</p>
 <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__b2100410425">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 it. 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__b973752981">Mesh Control Plane Node</strong><p id="asm_01_0020__en-us_topic_0000001542706401_p125902437272">The control plane components of the Basic service mesh are installed in the user cluster. Therefore, 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__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>
 <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__li1233211216319"><strong id="asm_01_0020__b1115002839">Application Metrics</strong><p id="asm_01_0020__p93321821123112">If this option is enabled, you can specify service access metrics, application topologies, and service health and SLO definitions in the service mesh.</p>
-</li><li id="asm_01_0020__li1522512214127"><strong id="asm_01_0020__b1443315218391">Tracing</strong><p id="asm_01_0020__p3225124129">- <strong id="asm_01_0020__b1649171110292">Sampling Rate</strong>: Number of requests generated by the tracing service/Total number of requests</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 customize the service port during Jaeger or Zipkin installation, replace <strong id="asm_01_0020__b3675134710313">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 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></div>
 </li></ul>
 </li></ul>
-</p></li><li id="asm_01_0020__en-us_topic_0000001542706401_li185901043112713"><span>(Optional) Configure 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__b808612298">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__b1742517548222">istio-injection=enabled</strong>. After being restarted, all pods in the namespace will be automatically injected with an istio-proxy sidecar.</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__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 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__b963350775">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>: Pods of the existing services in the namespace will be restarted, which will temporarily interrupt your services. The <strong id="asm_01_0020__b658216428">istio-proxy</strong> sidecar is automatically injected into the pods of the existing services.</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 <strong id="asm_01_0020__b166037221819">istio-proxy</strong> sidecar cannot be automatically injected into the pods of the existing services. You need to manually restart the workloads on the CCE console to inject the sidecar.</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>
+<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>
 <p id="asm_01_0020__p93763174718"><strong id="asm_01_0020__b9810181314341">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>
@ -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__b1576740032">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__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></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__b151099494">Configuration List</strong> on the right of the page and click <strong id="asm_01_0020__b441494675">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__b567440244">Installing</strong> to <strong id="asm_01_0020__b17683781">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__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>
 <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>
--- a/docs/asm/umn/asm_01_0029.html
+++ b/docs/asm/umn/asm_01_0029.html
@ -6,9 +6,9 @@
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="asm_01_0031.html">Configuration Diagnosis</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_01_0060.html">Manual Fixing Items</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_01_0060.html">Fixing Items Manually</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_01_0065.html">Auto Fixing Items</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_01_0065.html">Fixing Items Automatically</a></strong><br>
 </li>
 </ul>

--- a/docs/asm/umn/asm_01_0036.html
+++ b/docs/asm/umn/asm_01_0036.html
@ -9,7 +9,7 @@
 </li></ul>
 </p></li><li id="asm_01_0036__li771712313588"><span>Configure basic information of the grayscale release task.</span><p><ul id="asm_01_0036__ul6468103391818"><li id="asm_01_0036__li182551458340"><strong id="asm_01_0036__b151365433183">Grayscale Release Form</strong><p id="asm_01_0036__p2064691819344">Select <strong id="asm_01_0036__b1497597343102415">Canary Release</strong> or <strong id="asm_01_0036__b2049366149102415">Blue-Green Deployment</strong> as required. For details about the differences between the two forms, see <a href="asm_01_0035.html">Grayscale Release Overview</a>.</p>
 </li><li id="asm_01_0036__li4938581353"><strong id="asm_01_0036__b743019103613">Task Name</strong><p id="asm_01_0036__p98958413619">Customize a grayscale release task name. Enter 4 to 63 characters, starting with a lowercase letter and ending with a letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</p>
-</li><li id="asm_01_0036__li36212449385"><strong id="asm_01_0036__b13288953173816">Namespace</strong><p id="asm_01_0036__p26361500386">Select the namespace to which the service belongs.</p>
+</li><li id="asm_01_0036__li36212449385"><strong id="asm_01_0036__b13288953173816">Namespace</strong><p id="asm_01_0036__p26361500386">Select the namespace that the service belongs to.</p>
 </li><li id="asm_01_0036__li10113185692215"><strong id="asm_01_0036__b083101432311">Service</strong><p id="asm_01_0036__p11370657182210">Select the service to be released from the drop-down list box. Services that are running grayscale tasks cannot be selected. They are automatically filtered out from the list.</p>
 </li><li id="asm_01_0036__li164901553114017"><strong id="asm_01_0036__b486725564018">Workload</strong><p id="asm_01_0036__p614765119400">Select the workload to which the service belongs.</p>
 </li><li id="asm_01_0036__li16245142511413"><strong id="asm_01_0036__b2245142520413">Version</strong><p id="asm_01_0036__p5245132584112">Current service version number, which cannot be changed.</p>
@ -24,14 +24,14 @@
 </p></li><li id="asm_01_0036__li5242204519710"><span>(For canary release only) Click <strong id="asm_01_0036__b2127315232102415">Configure Traffic Policy</strong> to configure a traffic policy.</span><p><p id="asm_01_0036__p58080153163125"><strong id="asm_01_0036__b371783390102415">Policy Type</strong>: The value can be <strong id="asm_01_0036__b1569755184102415">Based on traffic ratio</strong> or <strong id="asm_01_0036__b1443871107102415">Based on request content</strong>.</p>
 <ul id="asm_01_0036__ul61311494163314"><li id="asm_01_0036__li1265865519290"><strong id="asm_01_0036__b179291468309">Based on traffic ratio</strong><p id="asm_01_0036__p910935618296">A specified ratio of traffic will be directed to the grayscale version. For example, 75% of the traffic is directed to the original version, and 25% is directed to the grayscale version. In actual applications, you can gradually increase the traffic ratio of the grayscale version and deliver policies to monitor the performance of the grayscale version.</p>
 <div class="fignone" id="asm_01_0036__fig1550914468143"><span class="figcap"><b>Figure 1 </b>Based on traffic ratio</span><br><span><img class="eddx" id="asm_01_0036__image45091246201417" src="en-us_image_0000001210438852.png"></span></div>
-<p id="asm_01_0036__p184331616162415"><strong id="asm_01_0036__b361084949102415">Traffic</strong> <strong id="asm_01_0036__b1076523187102415">ratio</strong>: You can set the traffic ratio for the original version and grayscale version. The system distributes traffic to the two versions based on the specific traffic ratio.</p>
+<p id="asm_01_0036__p184331616162415">You can set the traffic ratio for the original version and grayscale version. The system distributes traffic to the two versions based on the specific traffic ratio.</p>
 </li></ul>
-<ul id="asm_01_0036__ul21864151442"><li id="asm_01_0036__li1318621514442"><strong id="asm_01_0036__b1184715194414">Based on request content</strong><p id="asm_01_0036__p10186515104411">The grayscale version can be accessed only when the traffic meets the rules based on the cookies, custom headers, queries, operating systems, and browsers. For example, only HTTP requests whose cookies meet <strong id="asm_01_0036__b1217005551102415">User=Internal</strong> can be forwarded to the grayscale version. Other requests are still received by the original version.</p>
+<ul id="asm_01_0036__ul21864151442"><li id="asm_01_0036__li1318621514442"><strong id="asm_01_0036__b1184715194414">Based on request content</strong><p id="asm_01_0036__p10186515104411">With such a policy, a grayscale version can be accessed only when the traffic meets the rules based on cookies, headers, queries, allowed operating systems, and allowed browsers. For example, only HTTP requests whose cookies meet <strong id="asm_01_0036__b1217005551102415">User=Internal</strong> can be forwarded to the grayscale version. Other requests are still received by the original version.</p>
 <div class="fignone" id="asm_01_0036__fig19101134141212"><span class="figcap"><b>Figure 2 </b>Based on request content</span><br><span><img class="eddx" id="asm_01_0036__image1610220411210" src="en-us_image_0000001210119300.png"></span></div>
 <ul id="asm_01_0036__ul146803318438"><li id="asm_01_0036__li1765991217433"><strong id="asm_01_0036__b0949204010510">Cookie</strong><p id="asm_01_0036__p14135174411452"><strong id="asm_01_0036__b351285221111">Regular expression</strong>: When the cookie of a request matches the configured regular expression, the request will be distributed to the grayscale version.</p>
-</li><li id="asm_01_0036__li63161151174315"><strong id="asm_01_0036__b99941448155113">Header</strong><ul id="asm_01_0036__ul17661191910713"><li id="asm_01_0036__li111518584416"><strong id="asm_01_0036__b08691434192116">Full match</strong>: Only the URL that fully matches the values you set can be accessed. For example, if <strong id="asm_01_0036__b1697833709102415">Key</strong> is set to <strong id="asm_01_0036__b2061631694102415">User</strong> and <strong id="asm_01_0036__b781961949102415">Value</strong> is set to <strong id="asm_01_0036__b38182976102415">Internal</strong>, only requests whose headers contain <strong id="asm_01_0036__b1880166255102415">User</strong> with the value <strong id="asm_01_0036__b438277587102415">Internal</strong> are responded by the service of the grayscale version.</li><li id="asm_01_0036__li1830122117716"><strong id="asm_01_0036__b1433176777102415">Regular expression</strong>: When the header of a request matches the configured regular expression, the request will be distributed to the grayscale version.<p id="asm_01_0036__p530216211679">You can customize the key and value for filtering. The value supports the full match and regular expression.</p>
+</li><li id="asm_01_0036__li63161151174315"><strong id="asm_01_0036__b99941448155113">Header</strong><ul id="asm_01_0036__ul17661191910713"><li id="asm_01_0036__li111518584416"><strong id="asm_01_0036__b08691434192116">Full match</strong>: Only the header that fully matches the values you set can be used for service access. For example, if <strong id="asm_01_0036__b1697833709102415">Key</strong> is set to <strong id="asm_01_0036__b2061631694102415">User</strong> and <strong id="asm_01_0036__b781961949102415">Value</strong> is set to <strong id="asm_01_0036__b38182976102415">Internal</strong>, only requests whose headers contain <strong id="asm_01_0036__b1880166255102415">User</strong> with the value <strong id="asm_01_0036__b438277587102415">Internal</strong> are responded by the grayscale version.</li><li id="asm_01_0036__li1830122117716"><strong id="asm_01_0036__b1433176777102415">Regular expression</strong>: When the header of a request matches the configured regular expression, the request will be distributed to the grayscale version.<p id="asm_01_0036__p530216211679">You can create custom key and value. The value supports the full match and regular expression.</p>
 </li></ul>
-</li><li id="asm_01_0036__li0455205112192"><strong id="asm_01_0036__b6293190135211">Query</strong><ul id="asm_01_0036__ul122705534206"><li id="asm_01_0036__li62701453112015"><strong id="asm_01_0036__b052280152213">Full match</strong>: Only the URL that fully matches the values you set can be accessed. For example, if <strong id="asm_01_0036__b1874948701102415">Key</strong> is set to <strong id="asm_01_0036__b1903766040102415">User</strong> and <strong id="asm_01_0036__b1996971534102415">Value</strong> is set to <strong id="asm_01_0036__b2112203613102415">Internal</strong>, only requests whose queries contain <strong id="asm_01_0036__b433224998102415">User</strong> with the value <strong id="asm_01_0036__b566472174102415">Internal</strong> are responded by the service of the grayscale version.</li><li id="asm_01_0036__li127075311208"><strong id="asm_01_0036__b1062257843102415">Regular expression</strong>: When the query of a request matches the configured regular expression, the request will be distributed to the grayscale version.<p id="asm_01_0036__p112701053182010">You can customize the key and value for filtering. The value supports the full match and regular expression.</p>
+</li><li id="asm_01_0036__li0455205112192"><strong id="asm_01_0036__b6293190135211">Query</strong><ul id="asm_01_0036__ul122705534206"><li id="asm_01_0036__li62701453112015"><strong id="asm_01_0036__b052280152213">Full match</strong>: Only the query that fully matches the values you set can be used for service access. For example, if <strong id="asm_01_0036__b1874948701102415">Key</strong> is set to <strong id="asm_01_0036__b1903766040102415">User</strong> and <strong id="asm_01_0036__b1996971534102415">Value</strong> is set to <strong id="asm_01_0036__b2112203613102415">Internal</strong>, only requests whose queries contain <strong id="asm_01_0036__b433224998102415">User</strong> with the value <strong id="asm_01_0036__b566472174102415">Internal</strong> are responded by the grayscale version.</li><li id="asm_01_0036__li127075311208"><strong id="asm_01_0036__b1062257843102415">Regular expression</strong>: When the query of a request matches the configured regular expression, the request will be distributed to the grayscale version.<p id="asm_01_0036__p112701053182010">You can customize the key and value for filtering. The value supports the full match and regular expression.</p>
 </li></ul>
 </li><li id="asm_01_0036__li15787154419"><strong id="asm_01_0036__b649621384102415">Allowed OS</strong>: Select OSs that can access the grayscale version, including iOS, Android, Windows, and macOS.</li><li id="asm_01_0036__li526131604411"><strong id="asm_01_0036__b2030726272102415">Allowed Browser</strong>: Select browsers that can access the grayscale version, including Chrome and Internet Explorer.</li><li id="asm_01_0036__li1630402520442"><strong id="asm_01_0036__b1968871174102415">Traffic management YAML</strong>: The rule YAML is automatically generated based on the configured parameters.</li></ul>
 </li></ul>
--- a/docs/asm/umn/asm_01_0037.html
+++ b/docs/asm/umn/asm_01_0037.html
@ -8,13 +8,13 @@
 <ol id="asm_01_0037__ol22602493585"><li id="asm_01_0037__li172608490583"><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_0037__li1685515685910"><span>In the navigation pane, choose <strong id="asm_01_0037__b1198257152102457">Grayscale Release</strong>. Then click the target canary release task.</span></li><li id="asm_01_0037__li119651731195914"><span>On the <span class="uicontrol" id="asm_01_0037__uicontrol15603542195919"><b>Configure Traffic Policy</b></span> page, set the traffic ratio of the grayscale version.</span><p><p id="asm_01_0037__p204971340517">If the traffic ratio of the grayscale version is set to <strong id="asm_01_0037__b1049686697102457">x</strong>, the traffic ratio of the original version is automatically adjusted to <strong id="asm_01_0037__b1249862318102457">100-x</strong>.</p>
 </p></li><li id="asm_01_0037__li1654913119011"><span>Click <strong id="asm_01_0037__b2088803477102457">Deliver Policy</strong>.</span></li></ol>
 <p id="asm_01_0037__p229215343582"><strong id="asm_01_0037__b2085653513584">Modifying a grayscale policy that is based on request content</strong></p>
-<p id="asm_01_0037__p78315545421">With such a policy, a grayscale version can be accessed only when the traffic meets the rules based on Cookies, Headers, Queries, Allowed Operating Systems, and Allowed Browsers. In real-world use cases, rules may be modified for multiple times to fully verify the performance of the grayscale version.</p>
-<ol id="asm_01_0037__ol63435402427"><li id="asm_01_0037__li83431840114212"><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_0037__li1343134014429"><span>In the navigation pane on the left, choose <strong id="asm_01_0037__b808078738102457">Grayscale Release</strong> and click the target canary release task.</span></li><li id="asm_01_0037__li43433409426"><span>On the <span class="uicontrol" id="asm_01_0037__uicontrol221028061102457"><b>Configure Traffic Policy</b></span> page, reconfigure <strong id="asm_01_0037__b158529202102457">Cookie</strong>, <strong id="asm_01_0037__b1274928578102457">Header</strong>, <strong id="asm_01_0037__b1679842724102457">Query</strong>, <strong id="asm_01_0037__b227798411102457">Allowed OS</strong>, and <strong id="asm_01_0037__b323640813102457">Allowed Browser</strong>.</span></li><li id="asm_01_0037__li134315402422"><span>Click <strong id="asm_01_0037__b1247868421102457">Deliver Policy</strong>.</span></li></ol>
+<p id="asm_01_0037__p78315545421">With such a policy, a grayscale version can be accessed only when the traffic meets the rules based on cookies, headers, queries, allowed operating systems, and allowed browsers. In real-world use cases, rules may be modified for multiple times to fully verify the performance of the grayscale version.</p>
+<ol id="asm_01_0037__ol63435402427"><li id="asm_01_0037__li83431840114212"><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_0037__li1343134014429"><span>In the navigation pane, choose <strong id="asm_01_0037__b1329515052517">Grayscale Release</strong>. Then click the target canary release task.</span></li><li id="asm_01_0037__li43433409426"><span>On the <span class="uicontrol" id="asm_01_0037__uicontrol221028061102457"><b>Configure Traffic Policy</b></span> page, reconfigure <strong id="asm_01_0037__b158529202102457">Cookie</strong>, <strong id="asm_01_0037__b1274928578102457">Header</strong>, <strong id="asm_01_0037__b1679842724102457">Query</strong>, <strong id="asm_01_0037__b227798411102457">Allowed OS</strong>, and <strong id="asm_01_0037__b323640813102457">Allowed Browser</strong>.</span></li><li id="asm_01_0037__li134315402422"><span>Click <strong id="asm_01_0037__b1247868421102457">Deliver Policy</strong>.</span></li></ol>
 </div>
 <div class="section" id="asm_01_0037__section1198719955819"><h4 class="sectiontitle">Switching the Grayscale Policy Type</h4><p id="asm_01_0037__p1938319221655">You can change the type of a grayscale policy from <span class="uicontrol" id="asm_01_0037__uicontrol196956419398"><b>based on request content</b></span> to <span class="uicontrol" id="asm_01_0037__uicontrol8517310113911"><b>based on traffic ratio</b></span> and vice versa. After this operation is complete, all configured rules become invalid and all traffic is redistributed based on the new policy.</p>
 <div class="notice" id="asm_01_0037__note084791961611"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="asm_01_0037__p071154481611">Grayscale policies can be changed only for running tasks. After a grayscale version is released (that is, the new version completely takes over the traffic and the old version has been brought offline), its grayscale policy cannot be reconfigured.</p>
 </div></div>
-<ol id="asm_01_0037__ol1210818591352"><li id="asm_01_0037__li52621017101914"><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_0037__li46935210529"><span>In the navigation pane on the left, choose <strong id="asm_01_0037__b245738102102457">Grayscale Release</strong> and click the target canary release task.</span></li><li id="asm_01_0037__li196067405229"><span>On the <span class="uicontrol" id="asm_01_0037__uicontrol85896715214"><b>Configure Traffic Policy</b></span> page, change the policy type.</span></li><li id="asm_01_0037__li188191539102411"><span>Click <strong id="asm_01_0037__b1743078927102457">Deliver Policy</strong>.</span></li></ol>
+<ol id="asm_01_0037__ol1210818591352"><li id="asm_01_0037__li52621017101914"><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_0037__li46935210529"><span>In the navigation pane, choose <strong id="asm_01_0037__b6894111472512">Grayscale Release</strong>. Then click the target canary release task.</span></li><li id="asm_01_0037__li196067405229"><span>On the <span class="uicontrol" id="asm_01_0037__uicontrol85896715214"><b>Configure Traffic Policy</b></span> page, change the policy type.</span></li><li id="asm_01_0037__li188191539102411"><span>Click <strong id="asm_01_0037__b1743078927102457">Deliver Policy</strong>.</span></li></ol>
 </div>
 <div class="section" id="asm_01_0037__section124701017142211"><h4 class="sectiontitle">Taking Over All Traffic</h4><p id="asm_01_0037__p772618508120">After you click <span class="uicontrol" id="asm_01_0037__uicontrol6726125018123"><b>Take Over All Traffic</b></span>, the original version or grayscale version takes over all traffic.</p>
 <ol id="asm_01_0037__ol11726175016122"><li id="asm_01_0037__li590412592365"><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_0037__li167261550131217"><span>In the navigation pane on the left, choose <strong id="asm_01_0037__b2072504440102457">Grayscale Release</strong> and click the target grayscale release task.</span></li><li id="asm_01_0037__li11726450171215"><span>On the <strong id="asm_01_0037__b675106888102457">Monitor and Manage Traffic</strong> page, click <strong id="asm_01_0037__b2027459733102457">Take Over All Traffic</strong> next to the target version.</span></li><li id="asm_01_0037__li107261550141217"><span>In the displayed dialog box, click <strong id="asm_01_0037__b313926256102457">OK</strong>.</span></li></ol>
--- a/docs/asm/umn/asm_01_0041.html
+++ b/docs/asm/umn/asm_01_0041.html
@ -6,11 +6,11 @@
 <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>
-</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 associated pods and temporarily interrupt your services. New pods will have istio-proxy sidecars automatically injected.</p>
+</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__image1297291313419" 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 associated pods. You need to manually restart the workload on the CCE console to inject 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>: 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>
 </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>
@ -19,7 +19,7 @@
 <p id="asm_01_0041__p1492182965613"><strong id="asm_01_0041__b1262643613359">Outbound Ports</strong>: Outbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for outbound traffic redirection.</p>
 <ul id="asm_01_0041__ul887675114113"><li id="asm_01_0041__li208771351116"><strong id="asm_01_0041__b20581938193512">Include only specified ports</strong> means that the traffic from services in a service mesh over specified ports will be redirected to the sidecar.</li></ul>
 <ul id="asm_01_0041__ul91091571217"><li id="asm_01_0041__li9109125715112"><strong id="asm_01_0041__b8850163916356">Exclude only specified ports</strong> means that the traffic from services in a service mesh over the ports except the specified ports will be redirected to the sidecar.</li></ul>
-<p id="asm_01_0041__p14346164816561"><strong id="asm_01_0041__b13849134010355">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 excluded from redirection to the sidecar.</p>
+<p id="asm_01_0041__p14346164816561"><strong id="asm_01_0041__b1117210221271">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_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>
--- a/docs/asm/umn/asm_01_0049.html
+++ b/docs/asm/umn/asm_01_0049.html
@ -116,7 +116,7 @@
 </tbody>
 </table>
 </div>
-<div class="section" id="asm_01_0049__section17947144510113"><h4 class="sectiontitle">Constraints</h4><p id="asm_01_0049__p15725165911311">Traffic management cannot be performed for the service whose configuration diagnosis fails. For details about rectifying faults, see <a href="asm_01_0060.html">Manual Fixing Items</a> or <a href="asm_01_0065.html">Auto Fixing Items</a>.</p>
+<div class="section" id="asm_01_0049__section17947144510113"><h4 class="sectiontitle">Constraints</h4><p id="asm_01_0049__p15725165911311">Traffic management cannot be performed for the service whose configuration diagnosis fails. For details about rectifying faults, see <a href="asm_01_0060.html">Fixing Items Manually</a> or <a href="asm_01_0065.html">Fixing Items Automatically</a>.</p>
 </div>
 </div>
 <div>
--- a/docs/asm/umn/asm_01_0050.html
+++ b/docs/asm/umn/asm_01_0050.html
--- a/docs/asm/umn/asm_01_0056.html
+++ b/docs/asm/umn/asm_01_0056.html
@ -6,7 +6,7 @@
 <p id="asm_01_0056__p113671654155016">When creating a load balancer, you need to ensure that it belongs to the same VPC as the cluster.</p>
 </div>
 <div class="section" id="asm_01_0056__section15169750114920"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0056__ol4817103154612"><li id="asm_01_0056__li1433614120526"><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_0056__li218910061117"><span>In the navigation pane on the left, choose <strong id="asm_01_0056__b766458229102515">Gateway Management</strong> and click <strong id="asm_01_0056__b966014901102515">Add Gateway</strong>.</span></li><li id="asm_01_0056__li65921447162912"><span>Configure the following parameters.</span><p><ul id="asm_01_0056__ul1359211474297"><li id="asm_01_0056__li139001750192815"><strong id="asm_01_0056__b3657180102915">Gateway Name</strong><p id="asm_01_0056__p15441558132814">Enter a gateway name. Enter 4 to 59 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.</p>
-</li><li id="asm_01_0056__li205096299321"><strong id="asm_01_0056__b1576717357329">Cluster</strong><p id="asm_01_0056__p1719143716324">Select the cluster to which the gateway belongs.</p>
+</li><li id="asm_01_0056__li205096299321"><strong id="asm_01_0056__b1576717357329">Cluster</strong><p id="asm_01_0056__p1719143716324">Select the cluster that the gateway belongs to.</p>
 </li><li id="asm_01_0056__li1627847173510"><strong id="asm_01_0056__b72023510139">Load Balancer</strong><ul id="asm_01_0056__ul198721433124110"><li id="asm_01_0056__li1373914385357">Gateways use shared and dedicated load balancers of ELB for the access over both public and private IPv4 networks.</li></ul>
 </li><li id="asm_01_0056__li137621212344"><strong id="asm_01_0056__b196012994813">Access Entry</strong><p id="asm_01_0056__p103982038193113">Gateways configure a listener for the load balancer, which listens to requests from the load balancer and distributes traffic.</p>
 <ul id="asm_01_0056__ul1776173623113"><li id="asm_01_0056__li196722183918"><strong id="asm_01_0056__b1876120366312">External Protocol</strong><p id="asm_01_0056__p12761163618313">Select one to match the protocol type of your service. <strong id="asm_01_0056__b1196471084102515">HTTP</strong>, <strong id="asm_01_0056__b727748035102515">gRPC</strong>, <strong id="asm_01_0056__b2109712016102515">TCP</strong>, <strong id="asm_01_0056__b807938525102515">TLS</strong>, and <strong id="asm_01_0056__b1914909991102515">HTTPS</strong> are supported.</p>
@ -17,17 +17,17 @@
 </li><li id="asm_01_0056__li185755272428"><strong id="asm_01_0056__b33038550462">Earliest TLS Version Supported/Latest TLS Version Supported</strong><p id="asm_01_0056__p16437125165612">When configuring a TLS protocol with TLS termination enabled or an HTTPS protocol, you can select the earliest and latest TLS versions.</p>
 </li></ul>
 </li></ul>
-</p></li><li id="asm_01_0056__li35552319193"><span>(Optional) Configure routing parameters.</span><p><p id="asm_01_0056__p350315261000">When the access address of a request matches the forwarding policy (which consists of a domain name and URL. If the domain name is left empty, the ELB IP address is used by default), the request is forwarded to the corresponding target Service for processing. Click <span><img id="asm_01_0056__image3642183711263" src="en-us_image_0000001209954130.png"></span>. The <strong id="asm_01_0056__b28836919618">Add Route</strong> dialog box is displayed.</p>
+</p></li><li id="asm_01_0056__li35552319193"><span>(Optional) Configure the route parameters.</span><p><p id="asm_01_0056__p350315261000">When the access address of a request matches the forwarding rule (which consists of a domain name and URL. If the domain name is left empty, the IP address of the load balancer is used by default), the request is forwarded to the corresponding target service for processing. Click <span><img id="asm_01_0056__image3642183711263" src="en-us_image_0000001209954130.png"></span>. The <strong id="asm_01_0056__b28836919618">Add Route</strong> dialog box is displayed.</p>
 <ul id="asm_01_0056__ul43052021171916"><li id="asm_01_0056__li103041421111912"><strong id="asm_01_0056__b20304152120193">Domain Name</strong><p id="asm_01_0056__p1330482114196">Enter the external domain name of the service. If this parameter is left blank, the IP address of the load balancer is used by default. If you enable TLS termination, enter a domain name configured in the certificate for SNI domain name verification.</p>
-</li><li id="asm_01_0056__li1230512118195"><strong id="asm_01_0056__b3304192131916">URL Matching Rule</strong><ul id="asm_01_0056__ul43041021141915"><li id="asm_01_0056__li193041021111910"><strong id="asm_01_0056__b1640956582102515">Prefix</strong>: A URL can be accessed if its prefix is the same as that you configure. For example, <strong id="asm_01_0056__b1627472063102515">/healthz/v1</strong> and <strong id="asm_01_0056__b2009910935102515">/healthz/v2</strong>.</li><li id="asm_01_0056__li2304821181912"><strong id="asm_01_0056__b167861112172215">Exact</strong>: Only the URL that fully matches the values you set can be accessed. For example, if the URL is set to <strong id="asm_01_0056__b1296786758102515">/healthz</strong>, only <strong id="asm_01_0056__b1008928963102515">/healthz</strong> can be accessed.</li></ul>
-</li><li id="asm_01_0056__li1305192141912"><strong id="asm_01_0056__b193051421101911">URL</strong><p id="asm_01_0056__p123051212194">Mapping URL supported by the service, for example, <strong id="asm_01_0056__b286376356102515">/example</strong>.</p>
-</li><li id="asm_01_0056__li133056214197"><strong id="asm_01_0056__b130522112199">Namespace</strong><p id="asm_01_0056__p18305421111919">Select the namespace to which the gateway belongs.</p>
+</li><li id="asm_01_0056__li1230512118195"><strong id="asm_01_0056__b3304192131916">URL Matching Rule</strong><ul id="asm_01_0056__ul43041021141915"><li id="asm_01_0056__li193041021111910"><strong id="asm_01_0056__b92221320125617">Prefix match</strong>: A URL can be accessed if its prefix is the same as the URL you set. For example, if the URL is set to <strong id="asm_01_0056__b173121244439">/healthz</strong>, <strong id="asm_01_0056__b19312162494311">/healthz/v1</strong> and <strong id="asm_01_0056__b19313112424315">/healthz/v2</strong> can be accessed.</li><li id="asm_01_0056__li2304821181912"><strong id="asm_01_0056__b167861112172215">Full match</strong>: Only the URL that fully matches the URL you set can be accessed. For example, if the URL is set to <strong id="asm_01_0056__b1296786758102515">/healthz</strong>, only <strong id="asm_01_0056__b1008928963102515">/healthz</strong> can be accessed.</li></ul>
+</li><li id="asm_01_0056__li1305192141912"><strong id="asm_01_0056__b193051421101911">URL</strong><p id="asm_01_0056__p123051212194">Mapping URL supported by the service, for example, <strong id="asm_01_0056__b188131036134117">/example</strong>.</p>
+</li><li id="asm_01_0056__li133056214197"><strong id="asm_01_0056__b130522112199">Namespace</strong><p id="asm_01_0056__p18305421111919">Select the namespace that the gateway belongs to.</p>
 </li><li id="asm_01_0056__li33051621171912"><strong id="asm_01_0056__b11305121111916">Target Service</strong><p id="asm_01_0056__p134063347264">Service of the gateway. Select a value from the drop-down list box. The target service is filtered based on the corresponding gateway protocol. For details about the filtering rules, see <a href="asm_faq_0035.html">Why Cannot I Select the Corresponding Service When Adding a Route?</a></p>
-<p id="asm_01_0056__p18216183513118">The service which configuration diagnosis fails cannot be selected. You need to fix the issues first. For details, see <a href="asm_01_0060.html">Manual Fixing Items</a> or <a href="asm_01_0065.html">Auto Fixing Items</a>.</p>
+<p id="asm_01_0056__p18216183513118">The service which configuration diagnosis fails cannot be selected. You need to fix the issues first. For details, see <a href="asm_01_0060.html">Fixing Items Manually</a> or <a href="asm_01_0065.html">Fixing Items Automatically</a>.</p>
 </li><li id="asm_01_0056__li10305621141916"><strong id="asm_01_0056__b5305121111910">Access Port</strong><p id="asm_01_0056__p9305182112191">Only ports that match external protocols are displayed.</p>
 </li><li id="asm_01_0056__li8016197318"><strong id="asm_01_0056__b1986112519313">Rewrite</strong><p id="asm_01_0056__p42700201559">(This parameter is configurable when the external protocol is HTTP.)</p>
-<p id="asm_01_0056__p149531923439">Rewrite the HTTP URI and host/authority header before forwarding. Disabled by default. To enable it, configure the following parameters:</p>
-<ul id="asm_01_0056__ul147951020181917"><li id="asm_01_0056__li279572091910">URI: This value is used to rewrite the URI or prefix.</li><li id="asm_01_0056__li3390152618199">Host/Authority Header: This value is used to rewrite the HTTP host/authority header.</li></ul>
+<p id="asm_01_0056__p149531923439">Rewrite the HTTP URI and host/authority header before forwarding. This option is disabled by default. To enable it, configure the following parameters:</p>
+<ul id="asm_01_0056__ul147951020181917"><li id="asm_01_0056__li279572091910"><strong id="asm_01_0056__b37865916147">URI</strong>: used to rewrite the URI or prefix. If the original path is matched by prefix, the value provided in this field replaces the corresponding matched prefix.</li><li id="asm_01_0056__li3390152618199"><strong id="asm_01_0056__b1867783431514">Host/Authority Header</strong>: used to rewrite the HTTP host/authority header.</li></ul>
 </li></ul>
 </p></li><li id="asm_01_0056__li19910958562"><span>Click <span class="uicontrol" id="asm_01_0056__uicontrol169158519564"><b>OK</b></span>.</span><p><p id="asm_01_0056__p688514211217">You can obtain the external network access address of the service in the <strong id="asm_01_0056__b840925467102515">Service Management</strong> page.</p>
 </p></li></ol>
--- a/docs/asm/umn/asm_01_0057.html
+++ b/docs/asm/umn/asm_01_0057.html
@ -3,18 +3,18 @@
 <h1 class="topictitle1">Adding a Route</h1>
 <div id="body0000001121400726"><div class="section" id="asm_01_0057__section195155335313"><h4 class="sectiontitle">Scenarios</h4><p id="asm_01_0057__p931218541531">You can add multiple routes and configure multiple forwarding policies for a created gateway.</p>
 </div>
-<div class="section" id="asm_01_0057__section8243022955"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0057__ol4817103154612"><li id="asm_01_0057__li218910061117"><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_0057__li4563349450"><span>In the navigation pane on the left, choose <strong id="asm_01_0057__b1723779989102359">Gateway Management</strong>, select the target gateway, click <span class="uicontrol" id="asm_01_0057__uicontrol1443280921102359"><b>Add Route</b></span> in the <strong id="asm_01_0057__b1193311901102359">Operation</strong> column, and configure the following parameters:</span><p><ul id="asm_01_0057__ul43052021171916"><li id="asm_01_0057__li103041421111912"><strong id="asm_01_0057__b20304152120193">Domain Name</strong><p id="asm_01_0057__p1330482114196">Enter the external domain name of the service. If this parameter is left blank, the IP address of the load balancer is used by default. If you enable TLS termination, enter a domain name configured in the certificate for SNI domain name verification.</p>
-</li><li id="asm_01_0057__li1230512118195"><strong id="asm_01_0057__b3304192131916">URL Matching Rule</strong><ul id="asm_01_0057__ul43041021141915"><li id="asm_01_0057__li193041021111910"><strong id="asm_01_0057__b962008790102359">Prefix</strong>: A URL can be accessed if its prefix is the same as that you configure. For example, <strong id="asm_01_0057__b518106701102359">/healthz/v1</strong> and <strong id="asm_01_0057__b1301388330102359">/healthz/v2</strong>.</li><li id="asm_01_0057__li2304821181912"><strong id="asm_01_0057__b1070295332113">Exact</strong>: Only the URL that fully matches the values you set can be accessed. For example, if the URL is set to <strong id="asm_01_0057__b1560656592102359">/healthz</strong>, only <strong id="asm_01_0057__b592325887102359">/healthz</strong> can be accessed.</li></ul>
-</li><li id="asm_01_0057__li1305192141912"><strong id="asm_01_0057__b193051421101911">URL</strong><p id="asm_01_0057__p123051212194">Mapping URL supported by the service, for example, <strong id="asm_01_0057__b1278776861102359">/example</strong>.</p>
+<div class="section" id="asm_01_0057__section8243022955"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0057__ol4817103154612"><li id="asm_01_0057__li218910061117"><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_0057__li4563349450"><span>In the navigation pane, choose <strong id="asm_01_0057__b1723779989102359">Gateway Management</strong>. On the displayed page, locate the target gateway and click <span class="uicontrol" id="asm_01_0057__uicontrol1443280921102359"><b>Add Route</b></span> in the <strong id="asm_01_0057__b1193311901102359">Operation</strong> column. In the displayed dialog box, configure the following parameters:</span><p><ul id="asm_01_0057__ul43052021171916"><li id="asm_01_0057__li103041421111912"><strong id="asm_01_0057__b20304152120193">Domain Name</strong><p id="asm_01_0057__p1330482114196">Enter the external domain name of the service. If this parameter is left blank, the IP address of the load balancer is used by default. If you enable TLS termination, enter a domain name configured in the certificate for SNI domain name verification.</p>
+</li><li id="asm_01_0057__li1230512118195"><strong id="asm_01_0057__b3304192131916">URL Matching Rule</strong><ul id="asm_01_0057__ul43041021141915"><li id="asm_01_0057__li193041021111910"><strong id="asm_01_0057__b1911861163410">Prefix match</strong>: A URL can be accessed if its prefix is the same as the URL you set. For example, if the URL is set to <strong id="asm_01_0057__b19458121723417">/healthz</strong>, <strong id="asm_01_0057__b144584176344">/healthz/v1</strong> and <strong id="asm_01_0057__b8458151720345">/healthz/v2</strong> can be accessed.</li><li id="asm_01_0057__li2304821181912"><strong id="asm_01_0057__b14157322133415">Full match</strong>: Only the URL that fully matches the URL you set can be accessed. For example, if the URL is set to <strong id="asm_01_0057__b1582612399341">/healthz</strong>, only <strong id="asm_01_0057__b2826339163411">/healthz</strong> can be accessed.</li></ul>
+</li><li id="asm_01_0057__li1305192141912"><strong id="asm_01_0057__b193051421101911">URL</strong><p id="asm_01_0057__p123051212194">Mapped URL that can access the target service, for example, <strong id="asm_01_0057__b19589191713243">/example</strong>.</p>
 <div class="note" id="asm_01_0057__note1841442516472"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0057__p19415112514478">The URLs of the same gateway must be unique.</p>
 </div></div>
-</li><li id="asm_01_0057__li133056214197"><strong id="asm_01_0057__b130522112199">Namespace</strong><p id="asm_01_0057__p18305421111919">Select the namespace to which the gateway belongs.</p>
+</li><li id="asm_01_0057__li133056214197"><strong id="asm_01_0057__b130522112199">Namespace</strong><p id="asm_01_0057__p18305421111919">Select the namespace that the gateway belongs to.</p>
 </li><li id="asm_01_0057__li33051621171912"><strong id="asm_01_0057__b11305121111916">Target Service</strong><p id="asm_01_0057__p134063347264">Service of the gateway. Select a value from the drop-down list box. The target service is filtered based on the corresponding gateway protocol. For details about the filtering rules, see <a href="asm_faq_0035.html">Why Cannot I Select the Corresponding Service When Adding a Route?</a>.</p>
-<p id="asm_01_0057__p18216183513118">The service which configuration diagnosis fails cannot be selected. You need to fix the issues first. For details, see <a href="asm_01_0060.html">Manual Fixing Items</a> or <a href="asm_01_0065.html">Auto Fixing Items</a>.</p>
+<p id="asm_01_0057__p18216183513118">The service which configuration diagnosis fails cannot be selected. You need to fix the issues first. For details, see <a href="asm_01_0060.html">Fixing Items Manually</a> or <a href="asm_01_0065.html">Fixing Items Automatically</a>.</p>
 </li><li id="asm_01_0057__li10305621141916"><strong id="asm_01_0057__b5305121111910">Access Port</strong><p id="asm_01_0057__p9305182112191">Only ports that match external protocols are displayed.</p>
 </li><li id="asm_01_0057__li8016197318"><strong id="asm_01_0057__b1986112519313">Rewrite</strong><p id="asm_01_0057__p42700201559">(This parameter is configurable when the external protocol is HTTP.)</p>
-<p id="asm_01_0057__p149531923439">Rewrite the HTTP URI and host/authority header before forwarding. Disabled by default. To enable it, configure the following parameters:</p>
-<ul id="asm_01_0057__ul147951020181917"><li id="asm_01_0057__li279572091910">URI: This value is used to rewrite the URI or prefix.</li><li id="asm_01_0057__li3390152618199">Host/Authority Header: This value is used to rewrite the HTTP host/authority header.</li></ul>
+<p id="asm_01_0057__p149531923439">Rewrite the HTTP URI and host/authority header before forwarding. This option is disabled by default. To enable it, configure the following parameters:</p>
+<ul id="asm_01_0057__ul147951020181917"><li id="asm_01_0057__li279572091910"><strong id="asm_01_0057__b7909141711237">URI</strong>: used to rewrite the URI or prefix. If the original path is matched by prefix, the value provided in this field replaces the corresponding matched prefix.</li><li id="asm_01_0057__li3390152618199"><strong id="asm_01_0057__b15841624102313">Host/Authority Header</strong>: used to rewrite the HTTP host/authority header.</li></ul>
 </li></ul>
 </p></li><li id="asm_01_0057__li1666416119713"><span>Click <span class="uicontrol" id="asm_01_0057__uicontrol8784608473"><b>OK</b></span>.</span></li></ol>
 </div>
--- a/docs/asm/umn/asm_01_0060.html
+++ b/docs/asm/umn/asm_01_0060.html
@ -1,6 +1,6 @@
 <a name="asm_01_0060"></a><a name="asm_01_0060"></a>

-<h1 class="topictitle1">Manual Fixing Items</h1>
+<h1 class="topictitle1">Fixing Items Manually</h1>
 <div id="body0000001175771819"></div>
 <div>
 <ul class="ullinks">
--- a/docs/asm/umn/asm_01_0061.html
+++ b/docs/asm/umn/asm_01_0061.html
@ -25,7 +25,7 @@
 </div>
 <div>
 <div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0060.html">Manual Fixing Items</a></div>
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0060.html">Fixing Items Manually</a></div>
 </div>
 </div>

--- a/docs/asm/umn/asm_01_0062.html
+++ b/docs/asm/umn/asm_01_0062.html
@ -25,7 +25,7 @@
 </div>
 <div>
 <div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0060.html">Manual Fixing Items</a></div>
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0060.html">Fixing Items Manually</a></div>
 </div>
 </div>

--- a/docs/asm/umn/asm_01_0063.html
+++ b/docs/asm/umn/asm_01_0063.html
@ -3,13 +3,13 @@
 <h1 class="topictitle1">All Pods Have Sidecars Injected</h1>
 <div id="body0000001175772865"><div class="section" id="asm_01_0063__section146041745338"><h4 class="sectiontitle">Description</h4><p id="asm_01_0063__p1487717583317">An <strong id="asm_01_0063__b8850152035217">istio-proxy</strong> container must exist in all pods of a Service. Otherwise, this item is abnormal.</p>
 </div>
-<div class="section" id="asm_01_0063__section1457519694110"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0063__ol11865432551"><li id="asm_01_0063__li12186243175513"><span>Log in to the ASM console and click the name of the service mesh that the Service is added to. Choose <strong id="asm_01_0063__b761794971520">Mesh Configuration</strong> in the navigation pane, click the <strong id="asm_01_0063__b861824921513">Sidecar Management</strong> tab, and check whether a sidecar is injected into the namespace that the Service belongs to.</span><p><ul id="asm_01_0063__ul1680513160015"><li id="asm_01_0063__li1680515161008">If the sidecar is not injected into the namespace, go to <a href="#asm_01_0063__li1665121115612">2</a>.</li><li id="asm_01_0063__li198192408015">If the sidecar has been injected into the namespace, go to <a href="#asm_01_0063__li127525055610">3</a>.<p id="asm_01_0063__p1515351917258">Check method:</p>
+<div class="section" id="asm_01_0063__section1457519694110"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0063__ol11865432551"><li id="asm_01_0063__li12186243175513"><span>Log in to the ASM console and click the name of the service mesh that the Service is added to. In the navigation pane, choose <strong id="asm_01_0063__b913273845519">Mesh Configuration</strong>. On the displayed page, click the <strong id="asm_01_0063__b11321438195516">Sidecar Management</strong> tab. Then, check whether a sidecar is injected into the namespace that the Service belongs to.</span><p><ul id="asm_01_0063__ul1680513160015"><li id="asm_01_0063__li1680515161008">If the sidecar is not injected into the namespace, go to <a href="#asm_01_0063__li1665121115612">2</a>.</li><li id="asm_01_0063__li198192408015">If the sidecar has been injected into the namespace, go to <a href="#asm_01_0063__li127525055610">3</a>.<p id="asm_01_0063__p1515351917258">Check method:</p>
 <p id="asm_01_0063__p42381524122517">On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose <strong id="asm_01_0063__b11801397414">Namespaces</strong>. On the displayed page, locate your namespace and click <strong id="asm_01_0063__b9613112883416">Edit YAML</strong> in the <strong id="asm_01_0063__b15711152403411">Operation</strong> column. If there is the <strong id="asm_01_0063__b175091651103918">istio.io/rev=&lt;revision&gt;</strong> or <strong id="asm_01_0063__b20795258123916">istio-injection=enabled</strong> label, the sidecar has been injected.</p>
 <div class="note" id="asm_01_0063__note87391512153111"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="asm_01_0063__ul12328442183114"><li id="asm_01_0063__li832864243112">There must the <strong id="asm_01_0063__b128477083514">istio-injection=enabled</strong> label for Istio 1.13.9-r3 and earlier versions, as well as Istio 1.15.5-r2 and earlier versions. Note that the version numbers are combined by hyphens (-).</li><li id="asm_01_0063__li89671844113111">There must be the <strong id="asm_01_0063__b198671148379">istio.io/rev=&lt;revision&gt;</strong> label for Istio later than 1.13.9-r3, Istio later than 1.15.5-r2, and all Istio 1.18 versions. Note that the version numbers are combined by hyphens (-).<p id="asm_01_0063__p1336942717254"><span><img id="asm_01_0063__image4821824135818" src="en-us_image_0000002086005592.png"></span></p>
 </li></ul>
 </div></div>
 </li></ul>
-</p></li><li id="asm_01_0063__li1665121115612"><a name="asm_01_0063__li1665121115612"></a><a name="li1665121115612"></a><span>Inject a sidecar into a workload or inject sidecars into the pods of all workloads in the namespace. For details, see <a href="asm_01_0041.html#asm_01_0041__section65931513505">Injecting a Sidecar</a>.</span><p><p id="asm_01_0063__p126911222119">Injection methods:</p>
+</p></li><li id="asm_01_0063__li1665121115612"><a name="asm_01_0063__li1665121115612"></a><a name="li1665121115612"></a><span>Inject a sidecar into a workload or inject sidecars into the pods of all workloads in the namespace.</span><p><p id="asm_01_0063__p126911222119">Injection methods:</p>
 <ul id="asm_01_0063__ul142566176620"><li id="asm_01_0063__li1717131013105">To inject sidecars into the pods of all workloads in the namespace, run the following command to add a label to the namespace (the label varies depending on the Istio version):<pre class="screen" id="asm_01_0063__screen1281611095517"><strong id="asm_01_0063__b1181951015558">kubectl label ns</strong> &lt;namespace&gt; istio-injection=enabled</pre>
 <p id="asm_01_0063__p19362226185219">Or</p>
 <pre class="screen" id="asm_01_0063__screen1788741815554"><strong id="asm_01_0063__b128882181554">kubectl label ns</strong> &lt;namespace&gt; istio.io/rev=&lt;revision&gt;</pre>
@ -18,22 +18,24 @@
 </div>
 </div></div>
 </li></ul>
-<ul id="asm_01_0063__ul77018142713"><li id="asm_01_0063__li168449341119">Injecting a sidecar into a workload<div class="p" id="asm_01_0063__p10496970111"><a name="asm_01_0063__li168449341119"></a><a name="li168449341119"></a>On the CCE console, locate the target workload, choose <strong id="asm_01_0063__b4452123114113">More</strong> &gt; <strong id="asm_01_0063__b109016381012">Edit YAML</strong> in the <strong id="asm_01_0063__b157254481818">Operation</strong> column, and manually add the <strong id="asm_01_0063__b04982581119">annotations</strong> field.<pre class="screen" id="asm_01_0063__screen575018269110">      annotations:
-        sidecar.istio.io/inject: 'true'</pre>
-</div>
-<p id="asm_01_0063__p1794791520305"><span><img id="asm_01_0063__image115521522121112" src="en-us_image_0000001394586873.png"></span></p>
+<ul id="asm_01_0063__ul77018142713"><li id="asm_01_0063__li168449341119">Injecting a sidecar into a workload<p id="asm_01_0063__p10496970111"><a name="asm_01_0063__li168449341119"></a><a name="li168449341119"></a>On the CCE console, locate the target workload, choose <strong id="asm_01_0063__b4452123114113">More</strong> &gt; <strong id="asm_01_0063__b109016381012">Edit YAML</strong> in the <strong id="asm_01_0063__b157254481818">Operation</strong> column, and manually add the <strong id="asm_01_0063__b250343594810">annotations</strong> or <strong id="asm_01_0063__b672144111486">labels</strong> field based on your Istio version.</p>
+<ul id="asm_01_0063__ul1915643412531"><li id="asm_01_0063__li169663217532">For 1.13.9-r3 and later versions, 1.15.5-r2 and later versions, and all 1.18 versions, the configuration is follows:<pre class="screen" id="asm_01_0063__screen83914201599">      labels:
+        istio.io/rev=&lt;revision&gt;</pre>
+</li><li id="asm_01_0063__li12491642185318">For 1.13.9-r3 and earlier versions as well as 1.15.5-r2 and earlier versions, the configuration is follows:<pre class="screen" id="asm_01_0063__screen10491442125313">      annotations:
+        istio-injection: enabled</pre>
+</li></ul>
 </li></ul>
 <p id="asm_01_0063__p18904104210315">For more details about sidecar injection, see <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/" target="_blank" rel="noopener noreferrer">Installing the Sidecar</a>.</p>
 </p></li><li id="asm_01_0063__li127525055610"><a name="asm_01_0063__li127525055610"></a><a name="li127525055610"></a><span>If namespace injection is enabled for the cluster but no sidecar is injected into the pod, you need to manually restart the pod on the CCE console as follows:</span><p><p id="asm_01_0063__p6931112013420">On the CCE console, choose <strong id="asm_01_0063__b51514267743241">More</strong> &gt; <strong id="asm_01_0063__b185900250343241">Redeploy</strong> in the <strong id="asm_01_0063__b143167820043241">Operation</strong> column of the target workload.</p>
 </p></li><li id="asm_01_0063__li10713191914412"><span>Check whether the host network mode is configured for the workload as follows:</span><p><p id="asm_01_0063__p31276451075">On the CCE console, choose <strong id="asm_01_0063__b1371751914718">More</strong> &gt; <strong id="asm_01_0063__b15717191914719">Edit YAML</strong> in the <strong id="asm_01_0063__b07176192714">Operation</strong> column of the target workload, and check whether <strong id="asm_01_0063__b1178116582714">spec.template.spec.hostNetwork: true</strong> is configured. If yes, check whether this field can be deleted or set to <strong id="asm_01_0063__b1692120472143">false</strong>. Otherwise, sidecars cannot be injected.</p>
 <p id="asm_01_0063__p196591218181315"><span><img id="asm_01_0063__image1665921861311" src="en-us_image_0000001344069664.png"></span></p>
-</p></li><li id="asm_01_0063__li127567207111"><span>Check whether the number of pods exceeds the service mesh scale.</span><p><p id="asm_01_0063__p1075619201610">If the number exceeds , the excess pods cannot be injected with sidecars.</p>
+</p></li><li id="asm_01_0063__li127567207111"><span>Check whether the number of pods exceeds the service mesh scale.</span><p><p id="asm_01_0063__p1075619201610">If the number exceeds, the excess pods cannot be injected with sidecars.</p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0060.html">Manual Fixing Items</a></div>
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0060.html">Fixing Items Manually</a></div>
 </div>
 </div>

--- a/docs/asm/umn/asm_01_0065.html
+++ b/docs/asm/umn/asm_01_0065.html
@ -1,6 +1,6 @@
 <a name="asm_01_0065"></a><a name="asm_01_0065"></a>

-<h1 class="topictitle1">Auto Fixing Items</h1>
+<h1 class="topictitle1">Fixing Items Automatically</h1>
 <div id="body0000001175891735"></div>
 <div>
 <ul class="ullinks">
@ -8,7 +8,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="asm_01_0067.html">The Service Selector Cannot Contain version Labels</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_01_0069.html">The Service Is Configured with a Default-version Route and The Route Configuration Is Correct</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_01_0069.html">The Service Is Configured with a Default-Version Route and the Route Configuration Is Correct</a></strong><br>
 </li>
 </ul>

--- a/docs/asm/umn/asm_01_0066.html
+++ b/docs/asm/umn/asm_01_0066.html
@ -6,13 +6,13 @@
 <p id="asm_01_0066__p0468101021218"><strong id="asm_01_0066__b1009304413102627">&lt;protocol&gt;</strong> can be <strong id="asm_01_0066__b2134182545102627">http</strong>, <strong id="asm_01_0066__b426502840102627">tcp</strong>, or <strong id="asm_01_0066__b1310352250102627">grpc</strong>. Istio provides routing capabilities based on protocols defined on ports. For example, <strong id="asm_01_0066__b413874376102627">name: http-service0</strong> and <strong id="asm_01_0066__b1009174383102627">name: tcp</strong> are valid port names, while <strong id="asm_01_0066__b1702190975102627">name: httpforecast</strong> is not.</p>
 <p id="asm_01_0066__p122601816122117">If the Service port name is invalid, this item is abnormal.</p>
 </div>
-<div class="section" id="asm_01_0066__section727870104217"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0066__ol1727810104213"><li id="asm_01_0066__li102781407429"><span>Log in to the CCE console and click the cluster name to go to the cluster console.</span></li><li id="asm_01_0066__li52781302422"><span>In the navigation pane, choose <strong id="asm_01_0066__b236423932019">Services &amp; Ingresses</strong>. Click the <strong id="asm_01_0066__b474713414458">Service</strong> tab, search for the Service by cluster name and namespace, and click <strong id="asm_01_0066__b862745419249">Edit YAML</strong>. Then, view the Service protocol and add a protocol type before the Service name.</span><p><p id="asm_01_0066__p142784012424"><span><img id="asm_01_0066__image112786012424" src="en-us_image_0000001254992703.png"></span></p>
+<div class="section" id="asm_01_0066__section727870104217"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0066__ol1727810104213"><li id="asm_01_0066__li102781407429"><span>Log in to the CCE console and click the cluster name to go to the cluster console.</span></li><li id="asm_01_0066__li52781302422"><span>In the navigation pane, choose <strong id="asm_01_0066__b236423932019">Services &amp; Ingresses</strong>. On the <strong id="asm_01_0066__b474713414458">Service</strong> tab, search for the Service by cluster name and namespace, and click <strong id="asm_01_0066__b862745419249">Edit YAML</strong>. Then, view and modify the Service protocol and add the protocol type before the Service name.</span><p><p id="asm_01_0066__p142784012424"><span><img id="asm_01_0066__image112786012424" src="en-us_image_0000001254992703.png"></span></p>
 </p></li><li id="asm_01_0066__li9278600425"><span>Click <strong id="asm_01_0066__b1508075284102627">OK</strong>.</span></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0065.html">Auto Fixing Items</a></div>
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0065.html">Fixing Items Automatically</a></div>
 </div>
 </div>

--- a/docs/asm/umn/asm_01_0067.html
+++ b/docs/asm/umn/asm_01_0067.html
@ -3,13 +3,13 @@
 <h1 class="topictitle1">The Service Selector Cannot Contain version Labels</h1>
 <div id="body0000001175892785"><div class="section" id="asm_01_0067__section53791230142415"><h4 class="sectiontitle">Description</h4><p id="asm_01_0067__p18675632152410">The <strong id="asm_01_0067__b9712182727">spec.selector</strong> of a Service cannot be labeled with <strong id="asm_01_0067__b127131229217">version</strong>. Otherwise, this item is abnormal.</p>
 </div>
-<div class="section" id="asm_01_0067__section1746811221448"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0067__ol2046892274413"><li id="asm_01_0067__li194682224444"><span>Log in to the CCE console and click the cluster name to go to the cluster console.</span></li><li id="asm_01_0067__li134681722134416"><span>In the navigation pane, choose <strong id="asm_01_0067__b1982141613293">Services &amp; Ingresses</strong>. Click the <strong id="asm_01_0067__b13800823104714">Service</strong> tab, search for the Service by cluster name and namespace, click <strong id="asm_01_0067__b1641517485317">Edit YAML</strong>. Then, view <strong id="asm_01_0067__b12282102411321">spec.selector</strong> and delete the <strong id="asm_01_0067__b27141245113215">version</strong> label.</span><p><p id="asm_01_0067__p74682223442"><span><img id="asm_01_0067__image11468192210442" src="en-us_image_0000001254992865.png"></span></p>
+<div class="section" id="asm_01_0067__section1746811221448"><h4 class="sectiontitle">Rectification Guide</h4><ol id="asm_01_0067__ol2046892274413"><li id="asm_01_0067__li194682224444"><span>Log in to the CCE console and click the cluster name to go to the cluster console.</span></li><li id="asm_01_0067__li134681722134416"><span>In the navigation pane, choose <strong id="asm_01_0067__b1982141613293">Services &amp; Ingresses</strong>. On the <strong id="asm_01_0067__b13800823104714">Service</strong> tab, search for the Service by cluster name and namespace, click <strong id="asm_01_0067__b1641517485317">Edit YAML</strong>. Then, view <strong id="asm_01_0067__b12282102411321">spec.selector</strong> and delete the <strong id="asm_01_0067__b27141245113215">version</strong> label.</span><p><p id="asm_01_0067__p74682223442"><span><img id="asm_01_0067__image11468192210442" src="en-us_image_0000001254992865.png"></span></p>
 </p></li></ol>
 </div>
 </div>
 <div>
 <div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0065.html">Auto Fixing Items</a></div>
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0065.html">Fixing Items Automatically</a></div>
 </div>
 </div>

--- a/docs/asm/umn/asm_01_0069.html
+++ b/docs/asm/umn/asm_01_0069.html
@ -1,6 +1,6 @@
 <a name="asm_01_0069"></a><a name="asm_01_0069"></a>

-<h1 class="topictitle1">The Service Is Configured with a Default-version Route and The Route Configuration Is Correct</h1>
+<h1 class="topictitle1">The Service Is Configured with a Default-Version Route and the Route Configuration Is Correct</h1>
 <div id="body0000001129693296"><div class="section" id="asm_01_0069__section338613811422"><h4 class="sectiontitle">Description</h4><p id="asm_01_0069__p73411754171">Istio defines service traffic routing rules in <strong id="asm_01_0069__b327293546102357">VirtualService</strong> and <strong id="asm_01_0069__b1336703240102357">DestinationRule</strong>. Therefore, you need to configure <strong id="asm_01_0069__b1307529050102357">VirtualService</strong> and <strong id="asm_01_0069__b531862740102357">DestinationRule</strong> for each service. The following rules must be met:</p>
 <ul id="asm_01_0069__ul14631191075912"><li id="asm_01_0069__li26691915135918">All ports of a Service must be configured in <strong id="asm_01_0069__b840689012102357">VirtualService</strong>.</li><li id="asm_01_0069__li56311510165920">The protocol type in <strong id="asm_01_0069__b303546881102357">VirtualService</strong> must be the same as that of the ports of a Service.</li><li id="asm_01_0069__li332613014131">The default service version must be configured in <strong id="asm_01_0069__b946334923102357">VirtualService</strong> and <strong id="asm_01_0069__b252832806102357">DestinationRule</strong>.</li></ul>
 <div class="note" id="asm_01_0069__note8326150111318"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0069__p77811347151319">If the check result changes, the port number or port name of a Service may be changed.</p>
@ -14,7 +14,7 @@
 </div>
 <div>
 <div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0065.html">Auto Fixing Items</a></div>
+<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_01_0065.html">Fixing Items Automatically</a></div>
 </div>
 </div>

--- a/docs/asm/umn/asm_01_0095.html
+++ b/docs/asm/umn/asm_01_0095.html
@ -1,7 +1,7 @@
 <a name="asm_01_0095"></a><a name="asm_01_0095"></a>

 <h1 class="topictitle1">Features in v1.15</h1>
-<div id="body0000001509781437"><ul id="asm_01_0095__ul9461425169"><li id="asm_01_0095__li114615221619">Istio 1.15.7 is supported.</li><li id="asm_01_0095__li572016471613">CCE Turbo clusters v1.21, v1.23, v1.25, and v1.27 are supported.</li><li id="asm_01_0095__li24721410161617">CCE clusters v1.21, v1.23, v1.25, and v1.27 are supported.</li><li id="asm_01_0095__li9405152166">Security vulnerabilities such as CVE-2023-44487, CVE-2023-39325 and CVE-2023-27487 are fixed.</li></ul>
+<div id="body0000001509781437"><ul id="asm_01_0095__ul9461425169"><li id="asm_01_0095__li114615221619">Istio 1.15.7 is supported.</li><li id="asm_01_0095__li572016471613">CCE Turbo clusters v1.21, v1.23, v1.25, and v1.27 are supported.</li><li id="asm_01_0095__li24721410161617">CCE clusters v1.21, v1.23, v1.25, and v1.27 are supported.</li><li id="asm_01_0095__li9405152166">Security vulnerabilities, such as CVE-2023-44487, CVE-2023-39325 and CVE-2023-27487, are fixed.</li></ul>
 <p id="asm_01_0095__p124581357171516">For details, visit <a href="https://istio.io/latest/news/releases/1.15.x/announcing-1.15.7/" target="_blank" rel="noopener noreferrer">https://istio.io/latest/news/releases/1.15.x/announcing-1.15.7/</a>.</p>
 </div>
 <div>
--- a/docs/asm/umn/asm_01_0124.html
+++ b/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 are supported.</li><li id="asm_01_0124__li6393101715319">CCE clusters v1.25, v1.27, v1.28, v1.29, and v1.30 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, 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>
 <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>
--- a/docs/asm/umn/asm_01_0133.html
+++ b/docs/asm/umn/asm_01_0133.html
@ -2,14 +2,12 @@

 <h1 class="topictitle1">Service Mesh Events</h1>
 <div id="body0000001698194042"><div class="section" id="asm_01_0133__en-us_topic_0000001245220449_section4882153517306"><h4 class="sectiontitle">Scenarios</h4><p id="asm_01_0133__en-us_topic_0000001245220449_p6387194691713">ASM supports the event center, which allows you to query details about important operations such as service mesh creation and deletion and gateway creation and deletion.</p>
-<div class="note" id="asm_01_0133__note198721932184717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0133__p10331731132415">You can view events in a Basic service mesh (based on Istio 1.15 or later).</p>
+<div class="note" id="asm_01_0133__note198721932184717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_01_0133__p10331731132415">You can view events in a Basic service mesh of 1.15 or later.</p>
 </div></div>
 </div>
 <div class="section" id="asm_01_0133__section655465134710"><h4 class="sectiontitle">Procedure</h4><ol id="asm_01_0133__en-us_topic_0000001245220449_ol3932132211530"><li id="asm_01_0133__en-us_topic_0000001245220449_li3932122212534"><span>Log in to the ASM console and search for the Basic service mesh by edition.</span></li><li id="asm_01_0133__en-us_topic_0000001245220449_li10538191319558"><span>Click <span><img id="asm_01_0133__image689423910493" src="en-us_image_0000001698197390.png"></span> in the upper right corner. In the window that slides out from the right, view service mesh events.</span><p><p id="asm_01_0133__p1728984312421"></p>
 </p></li></ol>
-<p id="asm_01_0133__p539616711425"></p>
 </div>
-<p id="asm_01_0133__p8060118"></p>
 </div>
 <div>
 <div class="familylinks">
--- a/docs/asm/umn/asm_bestpractice_1009.html
+++ b/docs/asm/umn/asm_bestpractice_1009.html
@ -4,7 +4,7 @@
 <div id="body0000001735119876"><p id="asm_bestpractice_1009__p1629514211458">You can create a CCE cluster with IPv4/IPv6 dual stack enabled and enable IPv4/IPv6 dual stack for the service mesh that the cluster is added to. IPv4/IPv6 dual stack allows services in the service mesh to use both IPv4 and IPv6 addresses for service-to-service interactions. After an IPv4/IPv6 dual-stack gateway is added for the service mesh, you can provide services for users using an IPv6 client. This section describes how you can create a service mesh with IPv4/IPv6 dual stack, so that services in the service mesh can communicate with each other using IPv6 addresses.</p>
 <div class="section" id="asm_bestpractice_1009__section241033319520"><h4 class="sectiontitle">Application Scenarios</h4><ul id="asm_bestpractice_1009__ul1891110468467"><li id="asm_bestpractice_1009__li1191184617465">If an IPv6 address is required for service access and traffic management, you can enable IPv4/IPv6 dual stack.</li><li id="asm_bestpractice_1009__li162511452164617">If you provide services for users who use IPv6 clients, you can create a gateway for a service mesh with IPv4/IPv6 dual stack enabled.</li></ul>
 </div>
-<div class="section" id="asm_bestpractice_1009__section10909135625310"><h4 class="sectiontitle">Constraints</h4><ul id="asm_bestpractice_1009__ul89074563534"><li id="asm_bestpractice_1009__li490735665310">Conditions for enabling IPv4/IPv6 dual stack for a service mesh</li></ul>
+<div class="section" id="asm_bestpractice_1009__section10909135625310"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="asm_bestpractice_1009__ul89074563534"><li id="asm_bestpractice_1009__li490735665310">Conditions for enabling IPv4/IPv6 dual stack for a service mesh</li></ul>

 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="asm_bestpractice_1009__table990895610539" frame="border" border="1" rules="all"><thead align="left"><tr id="asm_bestpractice_1009__row179081156175318"><th align="left" class="cellrowborder" valign="top" width="12.379999999999999%" id="mcps1.3.3.3.1.6.1.1"><p id="asm_bestpractice_1009__p89071156165312">Service Mesh Edition</p>
 </th>
@ -68,7 +68,7 @@
 <p id="asm_bestpractice_1009__p266122616264"></p>
 <p id="asm_bestpractice_1009__p943184717542"></p>
 <p id="asm_bestpractice_1009__p1029714339528">Configure other parameters based on site requirements.</p>
-</p></li><li id="asm_bestpractice_1009__li1229773335218"><span id="asm_bestpractice_1009__p4163181041415">Click the service mesh name to access the details page.</span><p><p id="asm_bestpractice_1009__li1229773335218p0">On the <strong id="asm_bestpractice_1009__b070135181319">Mesh Configuration</strong> &gt; <strong id="asm_bestpractice_1009__b18828199101318">Basic Information</strong> tab, you can see that IPv4/IPv6 dual stack has been enabled.</p>
+</p></li><li id="asm_bestpractice_1009__li1229773335218"><span id="asm_bestpractice_1009__p4163181041415">Click the service mesh name to access the details page.</span><p><p id="asm_bestpractice_1009__li1229773335218p0">On the <strong id="asm_bestpractice_1009__b1390431534617">Basic Information</strong> tab (<strong id="asm_bestpractice_1009__b070135181319">Mesh Configuration</strong> &gt; <strong id="asm_bestpractice_1009__b18828199101318">Basic Information</strong>), you can see that IPv4/IPv6 dual stack has been enabled.</p>
 <p id="asm_bestpractice_1009__p4297103325211"></p>
 </p></li></ol>
 </div>
--- a/docs/asm/umn/asm_bestpractice_3002.html
+++ b/docs/asm/umn/asm_bestpractice_3002.html
@ -1,9 +1,9 @@
 <a name="asm_bestpractice_3002"></a><a name="asm_bestpractice_3002"></a>

 <h1 class="topictitle1">Introduction</h1>
-<div id="body1568601267887"><p id="asm_bestpractice_3002__p637810612810">Dubbo is a special protocol which needs the following supports:</p>
-<ul id="asm_bestpractice_3002__ul419611400289"><li id="asm_bestpractice_3002__li19196840112810">Envoy on the service mesh data plane supports the parsing and traffic management of the Dubbo protocol.</li><li id="asm_bestpractice_3002__li5893131682919">The mesh control plane supports the configuration of Dubbo governance rules to manage services such as grayscale release, load balancing, and access authorization.</li></ul>
-<p id="asm_bestpractice_3002__p163331137142817">In addition, the service discovery model of Dubbo is different from that of Kubernetes and Spring Cloud. Therefore, additional processing is required.</p>
+<div id="body1568601267887"><p id="asm_bestpractice_3002__p637810612810">Dubbo is a special protocol. The following functions must be provided:</p>
+<ul id="asm_bestpractice_3002__ul419611400289"><li id="asm_bestpractice_3002__li19196840112810">Envoy on the service mesh data plane parses protocols and manages traffic of Dubbo.</li><li id="asm_bestpractice_3002__li5893131682919">The service mesh control plane supports Dubbo governance rules and service management such as grayscale release, load balancing, and access authorization.</li></ul>
+<p id="asm_bestpractice_3002__p163331137142817">In addition, the service discovery model of Dubbo is different from that of Kubernetes or Spring Cloud. Additional processing is required.</p>
 </div>
 <div>
 <div class="familylinks">
--- a/docs/asm/umn/asm_faq_0001.html
+++ b/docs/asm/umn/asm_faq_0001.html
@ -8,7 +8,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="asm_faq_0004.html">Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_faq_0005.html">Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_faq_0005.html">Why Cannot I Access the Page of the Deployed Demo Application?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="asm_faq_0035.html">Why Cannot I Select the Corresponding Service When Adding a Route?</a></strong><br>
 </li>
--- a/docs/asm/umn/asm_faq_0005.html
+++ b/docs/asm/umn/asm_faq_0005.html
@ -1,7 +1,7 @@
 <a name="asm_faq_0005"></a><a name="asm_faq_0005"></a>

-<h1 class="topictitle1">Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?</h1>
-<div id="body1546055873319"><div class="section" id="asm_faq_0005__section48145132817"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0005__p224713620288">The page of the demo application cannot be accessed after the application is successfully deployed.</p>
+<h1 class="topictitle1">Why Cannot I Access the Page of the Deployed Demo Application?</h1>
+<div id="body1546055873319"><div class="section" id="asm_faq_0005__section48145132817"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0005__p224713620288">The page of the deployed demo application cannot be accessed.</p>
 </div>
 <div class="section" id="asm_faq_0005__section957651892820"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0005__p721722012812">The load balancer configured for the application does not listen to the port.</p>
 </div>
--- a/docs/asm/umn/asm_faq_0006.html
+++ b/docs/asm/umn/asm_faq_0006.html
@ -4,7 +4,7 @@
 <div id="body1554353306515"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="asm_faq_0007.html">Why Can't I Change the Image Used for the Grayscale Version When Performing Grayscale Release?</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_faq_0007.html">Why Can't I Change the Image Used for the Grayscale Version When Performing a Grayscale Release?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="asm_faq_0008.html">Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?</a></strong><br>
 </li>
--- a/docs/asm/umn/asm_faq_0007.html
+++ b/docs/asm/umn/asm_faq_0007.html
@ -1,11 +1,11 @@
 <a name="asm_faq_0007"></a><a name="asm_faq_0007"></a>

-<h1 class="topictitle1">Why Can't I Change the Image Used for the Grayscale Version When Performing Grayscale Release?</h1>
-<div id="body1545635500617"><div class="section" id="asm_faq_0007__section14328175311487"><h4 class="sectiontitle">Description</h4><p id="asm_faq_0007__p6673854124817">When I perform grayscale release, the image used for the grayscale version cannot be changed.</p>
+<h1 class="topictitle1">Why Can't I Change the Image Used for the Grayscale Version When Performing a Grayscale Release?</h1>
+<div id="body1545635500617"><div class="section" id="asm_faq_0007__section14328175311487"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0007__p6673854124817">When I perform a grayscale release, the image used for the grayscale version cannot be changed.</p>
 </div>
-<div class="section" id="asm_faq_0007__section1950487184920"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0007__p77060834914">When performing grayscale release on a service, you create a new version of the same service. Therefore, the image used by the service cannot be changed. Only image tags can be changed.</p>
+<div class="section" id="asm_faq_0007__section1950487184920"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0007__p77060834914">When performing the grayscale release on a service, you can only change the tags of the image used by the service.</p>
 </div>
-<div class="section" id="asm_faq_0007__section647261714912"><h4 class="sectiontitle">Solution</h4><p id="asm_faq_0007__p135701818174918">Pack the required image into a different tag of the same image and push it to the image repository. Then, select the newly pushed image tag when you perform grayscale release on the service.</p>
+<div class="section" id="asm_faq_0007__section647261714912"><h4 class="sectiontitle">Solution</h4><p id="asm_faq_0007__p135701818174918">Pack the required image into a different tag of the same image and push it to the image repository. Then, select the newly pushed image tag when you perform a grayscale release on the service.</p>
 </div>
 </div>
 <div>
--- a/docs/asm/umn/asm_faq_0019.html
+++ b/docs/asm/umn/asm_faq_0019.html
@ -12,7 +12,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="asm_faq_0037.html">How Do I Disable Sidecar Injection for Workloads?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_faq_0039.html">What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_faq_0039.html">What Can I Do If a Pod Cannot Be Started Due to Unready Sidecar?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="asm_faq_0044.html">How Do I Handle a Canary Upgrade Failure?</a></strong><br>
 </li>
--- a/docs/asm/umn/asm_faq_0029.html
+++ b/docs/asm/umn/asm_faq_0029.html
@ -4,9 +4,9 @@
 <div id="body1600074666720"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="asm_faq_0030.html">Why Does a Service Mesh Remain in the Installing State for a Long Time After I Enable It for a Cluster?</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_faq_0030.html">Why Does an Enabled Service Mesh Remain in the Installing State for a Long Time?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_faq_0031.html">Why Does a Service Mesh Remain in the Unready State for a Long Time After I Uninstall It?</a></strong><br>
+<li class="ulchildlink"><strong><a href="asm_faq_0031.html">Why Does an Uninstalled Service Mesh Remain in the Unready State for a Long Time?</a></strong><br>
 </li>
 </ul>

--- a/docs/asm/umn/asm_faq_0030.html
+++ b/docs/asm/umn/asm_faq_0030.html
@ -1,7 +1,7 @@
 <a name="asm_faq_0030"></a><a name="asm_faq_0030"></a>

-<h1 class="topictitle1">Why Does a Service Mesh Remain in the Installing State for a Long Time After I Enable It for a Cluster?</h1>
-<div id="body1600074666721"><div class="section" id="asm_faq_0030__section1494171613215"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0030__p8837417429">After I create a service mesh (that is, create a Dedicated service mesh) for a CCE cluster, it remains in the installing state for a long time and a message is displayed indicating that the user security group rules are successfully enabled.</p>
+<h1 class="topictitle1">Why Does an Enabled Service Mesh Remain in the Installing State for a Long Time?</h1>
+<div id="body1600074666721"><div class="section" id="asm_faq_0030__section1494171613215"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0030__p8837417429">After I enable a service mesh (create a service mesh) for a CCE cluster, it remains in the installing state for a long time and a message is displayed indicating that the Istio-based service mesh is being enabled and the security group rules are successfully enabled.</p>
 </div>
 <div class="section" id="asm_faq_0030__section19812813158"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="asm_faq_0030__p29431791152">Log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0030__b847051616431">Namespaces</strong>. Then, check whether the <strong id="asm_faq_0030__b718482082520">istio-system</strong> namespace exists.</p>
 </div>
--- a/docs/asm/umn/asm_faq_0031.html
+++ b/docs/asm/umn/asm_faq_0031.html
@ -1,6 +1,6 @@
 <a name="asm_faq_0031"></a><a name="asm_faq_0031"></a>

-<h1 class="topictitle1">Why Does a Service Mesh Remain in the Unready State for a Long Time After I Uninstall It?</h1>
+<h1 class="topictitle1">Why Does an Uninstalled Service Mesh Remain in the Unready State for a Long Time?</h1>
 <div id="body1600074666721"><div class="section" id="asm_faq_0031__section2060853210484"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0031__p797293315489">On the ASM console, after I uninstall a service mesh, it remains in the unready state for a long time.</p>
 </div>
 <div class="section" id="asm_faq_0031__section62421653135217"><h4 class="sectiontitle">Fault Diagnosis</h4><ol id="asm_faq_0031__ol114041584333"><li id="asm_faq_0031__li15404165815336"><span>Log in to the CCE console. Click the cluster name to go to the cluster console. In the navigation pane, choose <strong id="asm_faq_0031__b1819515325711">App Templates</strong>.</span></li><li id="asm_faq_0031__li16806182703412"><span>Click <strong id="asm_faq_0031__b591845810489">Releases</strong> and select the target cluster from the drop-down list. Check the releases and the latest events about uninstallation failure.</span><p><p id="asm_faq_0031__p12911043121320">The <strong id="asm_faq_0031__b1343111283520">Status</strong> of <strong id="asm_faq_0031__b9432182819526">istio-master</strong> is <strong id="asm_faq_0031__b114331328145216">Uninstallation Failed</strong>, and the following message is displayed.</p>
--- a/docs/asm/umn/asm_faq_0036.html
+++ b/docs/asm/umn/asm_faq_0036.html
@ -19,6 +19,13 @@
        <strong id="asm_faq_0036__b1321171816284">autoInject: enabled</strong>
      remotePilotAddress: *.*.*.*
      tag: 1.8.6-r1-20220512225026</pre>
+<div class="caution" id="asm_faq_0036__note64454489259"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0036__asm_faq_0042_p1942555041213">Perform the following operations only in Istio 1.18.7-r4 or later.</p>
+<p id="asm_faq_0036__asm_faq_0042_p12491217172313">After running the <strong id="asm_faq_0036__asm_faq_0042_b1167713144507">kubectl edit iop</strong> command to edit the parameter to be modified, change the value of <strong id="asm_faq_0036__asm_faq_0042_b856252085018">install.istio.io/ignoreReconcile</strong> to <strong id="asm_faq_0036__asm_faq_0042_b94161923105014">false</strong>, save the modification, and exit.</p>
+<p id="asm_faq_0036__asm_faq_0042_p1149117176234"><span><img id="asm_faq_0036__asm_faq_0042_image124911717192310" src="en-us_image_0000002241895141.png"></span></p>
+<p id="asm_faq_0036__asm_faq_0042_p9491121722317">Run the <strong id="asm_faq_0036__asm_faq_0042_b472114279502">kubectl get iop -n istio-system</strong> command to check the IOP status. Wait until the value of <strong id="asm_faq_0036__asm_faq_0042_b538783419506">STATUS</strong> changes to <strong id="asm_faq_0036__asm_faq_0042_b1852693715505">HEALTHY</strong>.</p>
+<p id="asm_faq_0036__asm_faq_0042_p11491121712231"><span><img id="asm_faq_0036__asm_faq_0042_image14491111762316" src="en-us_image_0000002242015001.png"></span></p>
+<p id="asm_faq_0036__asm_faq_0042_p1849131762315">Change the value of <strong id="asm_faq_0036__asm_faq_0042_b9531143444915">install.istio.io/ignoreReconcile</strong> to <strong id="asm_faq_0036__asm_faq_0042_b1862817376491">true</strong>.</p>
+</div></div>
 </p></li><li id="asm_faq_0036__li797012579155"><a name="asm_faq_0036__li797012579155"></a><a name="li797012579155"></a><span>Run the <strong id="asm_faq_0036__b1190414902214">kubectl edit cm -nistio-system istio-sidecar-injector</strong> command to modify the <strong id="asm_faq_0036__b4911109202215">istio-sidecar-injector</strong> configuration item.</span><p><pre class="screen" id="asm_faq_0036__screen1219885482913">data:
  config: |-
    <strong id="asm_faq_0036__b18198165413294">policy: enabled</strong></pre>
--- a/docs/asm/umn/asm_faq_0037.html
+++ b/docs/asm/umn/asm_faq_0037.html
@ -10,7 +10,7 @@
 <ul id="asm_faq_0037__ul131144284459"><li id="asm_faq_0037__li161141928154518">For service meshes 1.13 or later:<p id="asm_faq_0037__p165276064812"><a name="asm_faq_0037__li161141928154518"></a><a name="li161141928154518"></a>Locate the <strong id="asm_faq_0037__b542419398134">spec.template.metadata.label</strong> field and add <strong id="asm_faq_0037__b942443915138">sidecar.istio.io/inject: 'false'</strong>.</p>
 <pre class="screen" id="asm_faq_0037__screen1852740154813">      label:
        sidecar.istio.io/inject: 'false'</pre>
-<p id="asm_faq_0037__p194274115277"><span><img id="asm_faq_0037__image13417142112712" src="en-us_image_0000001997321585.png"></span></p>
+<p id="asm_faq_0037__p194274115277"><span><img id="asm_faq_0037__image12978182218568" src="en-us_image_0000002373720729.png"></span></p>
 </li></ul>
 <p id="asm_faq_0037__p1535858144817">For more details about sidecar injection, see <a href="https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#controlling-the-injection-policy" target="_blank" rel="noopener noreferrer">Automatic Sidecar Injection</a>.</p>
 </p></li></ol>
--- a/docs/asm/umn/asm_faq_0039.html
+++ b/docs/asm/umn/asm_faq_0039.html
@ -1,7 +1,7 @@
 <a name="asm_faq_0039"></a><a name="asm_faq_0039"></a>

-<h1 class="topictitle1">What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar</h1>
-<div id="body0000001416537088"><div class="section" id="asm_faq_0039__section13605431272"><h4 class="sectiontitle">Description</h4><p id="asm_faq_0039__p158541327718">Pods of services managed by a mesh may fail to be started and keep restarting. When the service container communicates with external systems, the traffic passes through the <strong id="asm_faq_0039__b8829174674415">istio-proxy</strong> container. However, the service container is started earlier than the <strong id="asm_faq_0039__b17795457184413">istio-proxy</strong> container. As a result, the communication with external systems fails and the pod keeps restarting.</p>
+<h1 class="topictitle1">What Can I Do If a Pod Cannot Be Started Due to Unready Sidecar?</h1>
+<div id="body0000001416537088"><div class="section" id="asm_faq_0039__section13605431272"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0039__p158541327718">Pods of services managed by a mesh may fail to be started and keep restarting. When the service container communicates with external systems, the traffic passes through the <strong id="asm_faq_0039__b8829174674415">istio-proxy</strong> container. However, the service container is started earlier than the <strong id="asm_faq_0039__b17795457184413">istio-proxy</strong> container. As a result, the communication with external systems fails and the pod keeps restarting.</p>
 </div>
 <div class="section" id="asm_faq_0039__section533210301494"><h4 class="sectiontitle">Solution</h4><p id="asm_faq_0039__p15691639496">In Istio 1.7 and later versions, the community adds a switch named <strong id="asm_faq_0039__b16318164516466">HoldApplicationUntilProxyStarts</strong> to the <strong id="asm_faq_0039__b1327174911466">istio-injector</strong> injection logic. After the switch is enabled, the proxy is injected to the first container and the <strong id="asm_faq_0039__b152221254154711">istio-proxy</strong> container is started earlier than the service container.</p>
 <p id="asm_faq_0039__p155691339496">The switch can be configured globally or locally. The following describes two ways to enable the switch.</p>
@ -10,7 +10,14 @@
 <ul id="asm_faq_0039__ul5973203951113"><li id="asm_faq_0039__li159731839111118"><strong id="asm_faq_0039__b298917211546">Global Configuration</strong><ol id="asm_faq_0039__ol02451524181213"><li id="asm_faq_0039__li1424518249128">Run the following command to edit the IOP CR resource:<p id="asm_faq_0039__p156121036111211"><a name="asm_faq_0039__li1424518249128"></a><a name="li1424518249128"></a><strong id="asm_faq_0039__b9682046151219">kubectl edit iop private-data-plane -n istio-system</strong></p>
 <p id="asm_faq_0039__p104637523125">Add the following command to the <strong id="asm_faq_0039__b6511135545416">spec.values.global.proxy</strong> field:</p>
 <pre class="screen" id="asm_faq_0039__screen1683321021316">holdApplicationUntilProxyStarts: true</pre>
-<p id="asm_faq_0039__p2908162419169"><span><img id="asm_faq_0039__image890813245162" src="en-us_image_0000001416062808.png"></span></p>
+<p id="asm_faq_0039__p2908162419169"><span><img id="asm_faq_0039__image1725932412558" src="en-us_image_0000002339842264.png"></span></p>
+<div class="caution" id="asm_faq_0039__note64454489259"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0039__asm_faq_0042_p1942555041213">Perform the following operations only in Istio 1.18.7-r4 or later.</p>
+<p id="asm_faq_0039__asm_faq_0042_p12491217172313">After running the <strong id="asm_faq_0039__asm_faq_0042_b1167713144507">kubectl edit iop</strong> command to edit the parameter to be modified, change the value of <strong id="asm_faq_0039__asm_faq_0042_b856252085018">install.istio.io/ignoreReconcile</strong> to <strong id="asm_faq_0039__asm_faq_0042_b94161923105014">false</strong>, save the modification, and exit.</p>
+<p id="asm_faq_0039__asm_faq_0042_p1149117176234"><span><img id="asm_faq_0039__asm_faq_0042_image124911717192310" src="en-us_image_0000002241895141.png"></span></p>
+<p id="asm_faq_0039__asm_faq_0042_p9491121722317">Run the <strong id="asm_faq_0039__asm_faq_0042_b472114279502">kubectl get iop -n istio-system</strong> command to check the IOP status. Wait until the value of <strong id="asm_faq_0039__asm_faq_0042_b538783419506">STATUS</strong> changes to <strong id="asm_faq_0039__asm_faq_0042_b1852693715505">HEALTHY</strong>.</p>
+<p id="asm_faq_0039__asm_faq_0042_p11491121712231"><span><img id="asm_faq_0039__asm_faq_0042_image14491111762316" src="en-us_image_0000002242015001.png"></span></p>
+<p id="asm_faq_0039__asm_faq_0042_p1849131762315">Change the value of <strong id="asm_faq_0039__asm_faq_0042_b9531143444915">install.istio.io/ignoreReconcile</strong> to <strong id="asm_faq_0039__asm_faq_0042_b1862817376491">true</strong>.</p>
+</div></div>
 </li><li id="asm_faq_0039__li1787413350127">Run the following command to check whether the latest logs contain no error information:<p id="asm_faq_0039__p1775013126175"><a name="asm_faq_0039__li1787413350127"></a><a name="li1787413350127"></a><strong id="asm_faq_0039__b104261821141713">kubectl logs -n istio-operator $(kubectl get po -n istio-operator | awk '{print $1}' | grep -v NAME)</strong></p>
 </li><li id="asm_faq_0039__li4552151120177">Run the following command to check whether the IOP CR is normal:<p id="asm_faq_0039__p1017024613173"><a name="asm_faq_0039__li4552151120177"></a><a name="li4552151120177"></a><strong id="asm_faq_0039__b135219543174">kubectl get iop -n istio-system</strong></p>
 <p id="asm_faq_0039__p9464165217213"><span><img id="asm_faq_0039__image246465215219" src="en-us_image_0000001416224808.png"></span></p>
@ -19,7 +26,7 @@
 </li><li id="asm_faq_0039__li20809847233">Run the following command to check whether the pod is restarted:<p id="asm_faq_0039__p16470512414"><a name="asm_faq_0039__li20809847233"></a><a name="li20809847233"></a><strong id="asm_faq_0039__b352081622414">kubectl get pod -n </strong><em id="asm_faq_0039__i155216169249">default</em><strong id="asm_faq_0039__b18299141962414"> | grep </strong><em id="asm_faq_0039__i146291419192416">nginx</em></p>
 <p id="asm_faq_0039__p3198122913259"><span><img id="asm_faq_0039__image16198122972515" src="en-us_image_0000001416065480.png"></span></p>
 </li><li id="asm_faq_0039__li2870334101211">Run the following command to check whether <strong id="asm_faq_0039__b333314121549">postStart lifecycle</strong> is added to the pod and whether the <strong id="asm_faq_0039__b240151815410">istio-proxy</strong> container is placed in the first position:<p id="asm_faq_0039__p995575614257"><strong id="asm_faq_0039__b18832511162612">kubectl edit pod</strong> <em id="asm_faq_0039__i14521101417265">nginx-7bc96f87b9-l4dbl</em></p>
-<p id="asm_faq_0039__p4118254366"><span><img id="asm_faq_0039__image2112258362" src="en-us_image_0000001466625829.png"></span></p>
+<p id="asm_faq_0039__p4118254366"><span><img id="asm_faq_0039__image14974741016" src="en-us_image_0000002373730569.png"></span></p>
 </li></ol>
 </li><li id="asm_faq_0039__li1997393981112"><strong id="asm_faq_0039__b1377545711361">Local Configuration</strong><p id="asm_faq_0039__p1526744420116">For Istio 1.8 or later versions, you can label the pods for which this function needs to be enabled with <strong id="asm_faq_0039__b164702414819">proxy.istio.io/config</strong> and set <strong id="asm_faq_0039__b1243311357816">holdApplicationUntilProxyStarts</strong> to true.</p>
 <p id="asm_faq_0039__p142873506374">The following uses the <strong id="asm_faq_0039__b1213192371010">nginx</strong> service in the <strong id="asm_faq_0039__b5903112815103">default</strong> namespace as an example. The operations for other services are similar.</p>
--- a/docs/asm/umn/asm_faq_0044.html
+++ b/docs/asm/umn/asm_faq_0044.html
@ -16,12 +16,12 @@
 </tr>
 <tr id="asm_faq_0044__row136381425135812"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p1963882595815">1.15</p>
 </td>
-<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p11638192517583">1.21, 1.23, 1.25, and 1.27</p>
+<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p11638192517583">1.21, 1.23, 1.25, 1.27, and 1.28</p>
 </td>
 </tr>
 <tr id="asm_faq_0044__row13514175315319"><td class="cellrowborder" valign="top" width="49.919999999999995%"><p id="asm_faq_0044__p16527951103114">1.18</p>
 </td>
-<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p195271851173113">1.25, 1.27, 1.28, 1.29, and 1.30</p>
+<td class="cellrowborder" valign="top" width="50.080000000000005%"><p id="asm_faq_0044__p195271851173113">1.25, 1.27, and 1.28, as well as 1.29, 1.30, and 1.31</p>
 </td>
 </tr>
 </tbody>
--- a/docs/asm/umn/asm_faq_0049.html
+++ b/docs/asm/umn/asm_faq_0049.html
@ -73,12 +73,12 @@ spec:
 <p id="asm_faq_0049__p1829426115320"></p>
 <div class="caution" id="asm_faq_0049__note531232182212"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0049__p13363282212">If you do not need to access the Zipkin UI, set <strong id="asm_faq_0049__b169334233214">Access Type</strong> to <strong id="asm_faq_0049__b4971887338">ClusterIP</strong>.</p>
 </div></div>
-</p></li><li id="asm_faq_0049__li13729338114412"><span>Buy a service mesh and interconnect it with Zipkin.</span><p><p id="asm_faq_0049__p178544214419">Log in to the ASM console and click . In <strong id="asm_faq_0049__b25262914373">Cluster Configuration</strong>, select the cluster in <a href="#asm_faq_0049__li098232175213">1</a>. In <strong id="asm_faq_0049__b119744819378">Observability Configuration</strong>, enable tracing. Then, select <strong id="asm_faq_0049__b3741155114113">Third-party Jaeger/Zipkin service</strong> for <strong id="asm_faq_0049__b129028384435">Version</strong>, set <strong id="asm_faq_0049__b6563615174517">Service Address</strong> and <strong id="asm_faq_0049__b15594118184511">Access Port</strong>, and configure other parameters as required.</p>
+</p></li><li id="asm_faq_0049__li13729338114412"><span>create a service mesh and connect it to Zipkin.</span><p><p id="asm_faq_0049__p178544214419">Log in to the ASM console and click <strong id="asm_faq_0049__b127089816391">Create Mesh</strong>. In <strong id="asm_faq_0049__b25262914373">Cluster Configuration</strong>, select the cluster in <a href="#asm_faq_0049__li098232175213">1</a>. In <strong id="asm_faq_0049__b119744819378">Observability Configuration</strong>, enable tracing. Then, select <strong id="asm_faq_0049__b3741155114113">Third-party Jaeger/Zipkin service</strong> for <strong id="asm_faq_0049__b129028384435">Version</strong>, set <strong id="asm_faq_0049__b6563615174517">Service Address</strong> and <strong id="asm_faq_0049__b15594118184511">Access Port</strong>, and configure other parameters as required.</p>
 <p id="asm_faq_0049__p138755284596"></p>
-<div class="caution" id="asm_faq_0049__note1954184272911"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0049__p5541194213296">The value of <strong id="asm_faq_0049__b328316538457">Service Address</strong> is <em id="asm_faq_0049__i145201645134915">{Service name}</em><strong id="asm_faq_0049__b14606164913498">.</strong><em id="asm_faq_0049__i18501105534915">{Namespace}</em><strong id="asm_faq_0049__b1735704504">.svc.cluster.local</strong>. Replace <em id="asm_faq_0049__i1140244855114">{Service name}</em> and <em id="asm_faq_0049__i566095955112">{Namespace}</em> with those specified in <a href="#asm_faq_0049__li139077291524">2</a>.</p>
-<p id="asm_faq_0049__p9502451103216">The value of <strong id="asm_faq_0049__b866100145419">Access Port</strong> is that specified in <a href="#asm_faq_0049__li139077291524">2</a>.</p>
+<div class="caution" id="asm_faq_0049__note1954184272911"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="asm_faq_0049__p5541194213296"><strong id="asm_faq_0049__b328316538457">Service Address</strong> is in the format of <em id="asm_faq_0049__i145201645134915">{Service name}</em><strong id="asm_faq_0049__b14606164913498">.</strong><em id="asm_faq_0049__i18501105534915">{Namespace}</em><strong id="asm_faq_0049__b1735704504">.svc.cluster.local</strong>. Replace <em id="asm_faq_0049__i1140244855114">{Service name}</em> and <em id="asm_faq_0049__i566095955112">{Namespace}</em> with those specified in <a href="#asm_faq_0049__li139077291524">2</a>.</p>
+<p id="asm_faq_0049__p9502451103216"><strong id="asm_faq_0049__b866100145419">Access Port</strong> is that specified in <a href="#asm_faq_0049__li139077291524">2</a>.</p>
 </div></div>
-</p></li><li id="asm_faq_0049__li359554412532"><span>. After the deployment is complete, the services shown in the following figure are displayed on the <strong id="asm_faq_0049__b12741242574">Service Management</strong> page.</span><p><p id="asm_faq_0049__p1912126104113"></p>
+</p></li><li id="asm_faq_0049__li359554412532"><span>After the deployment is complete, the <strong id="asm_faq_0049__b151017395910">details</strong>, <strong id="asm_faq_0049__b14904959595">productpage</strong>, <strong id="asm_faq_0049__b10464178105910">ratings</strong>, and <strong id="asm_faq_0049__b9904811115912">reviews</strong> services are displayed on the <strong id="asm_faq_0049__b12741242574">Service Management</strong> page.</span><p><p id="asm_faq_0049__p1912126104113"></p>
 </p></li><li id="asm_faq_0049__li11168185540"><span>Access the productpage details page to trigger tracing.</span><p><p id="asm_faq_0049__p994155384316">Go to the service mesh details page. In the navigation pane, choose <strong id="asm_faq_0049__b1794819291214">Service Management</strong>. On the displayed page, click the external address <strong id="asm_faq_0049__b8391193317134">http://</strong><em id="asm_faq_0049__i19361530171312">{IP address}</em><strong id="asm_faq_0049__b3838132317585">:</strong><em id="asm_faq_0049__i1939011246589">{Port number}</em><strong id="asm_faq_0049__b1083813236584">/productpage</strong> of the <strong id="asm_faq_0049__b7804940162011">productpage</strong> service.</p>
 </p></li><li id="asm_faq_0049__li97966665113"><span>View the traces on the Zipkin UI at <strong id="asm_faq_0049__b1818212220317">http://</strong><em id="asm_faq_0049__i744022917316">{Public IP address of the load balancer configured for <strong id="asm_faq_0049__b5406145520">zipkin</strong>}</em><strong id="asm_faq_0049__b123921011345">:</strong><em id="asm_faq_0049__i36251828659">{Access port of <strong id="asm_faq_0049__b178134321512">zipkin</strong>}</em><strong id="asm_faq_0049__b156189392519">/zipkin/</strong>.</span><p><p id="asm_faq_0049__p17254111175110"></p>
 <div class="note" id="asm_faq_0049__note18532611511"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="asm_faq_0049__p1637017116550">You can obtain the IP address and port for logging in to the Zipkin client as follows:</p>
--- a/docs/asm/umn/asm_his_0001.html
+++ b/docs/asm/umn/asm_his_0001.html
@ -8,14 +8,24 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="asm_his_0001__row12221715111214"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p831582041212">2024-12-02</p>
+<tbody><tr id="asm_his_0001__row76689151355"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p14659112111512">2025-07-01</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><p id="asm_his_0001__p1477102715123">Added clusters v1.29 and v1.30.</p>
+<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><p id="asm_his_0001__p106594214518">Added the tracing information.</p>
+</td>
+</tr>
+<tr id="asm_his_0001__row124041616122215"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p114501718162213">2025-05-06</p>
+</td>
+<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><p id="asm_his_0001__p14501118122219">Supported clusters v1.31.</p>
+</td>
+</tr>
+<tr id="asm_his_0001__row12221715111214"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p831582041212">2024-12-02</p>
+</td>
+<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><p id="asm_his_0001__p1477102715123">Supported clusters v1.29 and v1.30.</p>
 </td>
 </tr>
 <tr id="asm_his_0001__row12332131943315"><td class="cellrowborder" valign="top" width="20.5%" headers="mcps1.3.1.2.3.1.1 "><p id="asm_his_0001__p633271918332">2024-10-12</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><ul id="asm_his_0001__ul124871631153718"><li id="asm_his_0001__li114871531183711">The following are modifications based on review comments:<p id="asm_his_0001__p16968945178"><a name="asm_his_0001__li114871531183711"></a><a name="li114871531183711"></a>- Added the "Upgrades" chapter.</p>
+<td class="cellrowborder" valign="top" width="79.5%" headers="mcps1.3.1.2.3.1.2 "><ul id="asm_his_0001__ul124871631153718"><li id="asm_his_0001__li114871531183711">Modified the following based on review comments:<p id="asm_his_0001__p16968945178"><a name="asm_his_0001__li114871531183711"></a><a name="li114871531183711"></a>- Added the "Upgrades" chapter.</p>
 <p id="asm_his_0001__p13718237816">- Updated the infographic of ASM.</p>
 <p id="asm_his_0001__p1411131911920">- Optimized other problems.</p>
 <p id="asm_his_0001__p153701734080">- Added the change history.</p>
--- a/docs/asm/umn/asm_pd_0001.html
+++ b/docs/asm/umn/asm_pd_0001.html
@ -12,7 +12,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="asm_productdesc_0003.html">Application Scenarios</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="asm_productdesc_0004.html">Constraints</a></strong><br>
+<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_0005.html">Basic Concepts</a></strong><br>
 </li>
--- a/docs/asm/umn/asm_productdesc_0001.html
+++ b/docs/asm/umn/asm_productdesc_0001.html
@ -15,18 +15,18 @@
 <ul id="asm_productdesc_0001__ul331217277488"><li id="asm_productdesc_0001__li5312112714812">Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic.</li><li id="asm_productdesc_0001__li5312427154818">Fine-grained control of traffic behavior with rich routing rules, retries, and fault injection.</li><li id="asm_productdesc_0001__li17312122754812">Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress.</li><li id="asm_productdesc_0001__li1931202774818">Secure service-to-service communication in a cluster with strong identity-based authentication and authorization.</li></ul>
 <p id="asm_productdesc_0001__p113125276482">Istio aims to achieve scalability and meet various deployment requirements.</p>
 </div>
-<div class="section" id="asm_productdesc_0001__section84803125459"><h4 class="sectiontitle">Features</h4><p id="asm_productdesc_0001__p1538453712538"><strong id="asm_productdesc_0001__b16680194810536">Grayscale release</strong></p>
+<div class="section" id="asm_productdesc_0001__section84803125459"><h4 class="sectiontitle">Features</h4><p id="asm_productdesc_0001__p1538453712538"><strong id="asm_productdesc_0001__b16680194810536">Grayscale Release</strong></p>
 <ul id="asm_productdesc_0001__ul1382mcpsimp"><li id="asm_productdesc_0001__li1383mcpsimp">Grayscale policies based on request content: You can set criteria based on request content, such as header and cookie. Only requests meeting the criteria will be distributed to the grayscale version.</li><li id="asm_productdesc_0001__li1384mcpsimp">Grayscale policies based on traffic ratio: You can set specific ratio for the traffic to be distributed to the grayscale version.</li><li id="asm_productdesc_0001__li1385mcpsimp">Canary release: Guidance will be provided to help you perform canary release on a service, including rolling out a grayscale version, observing the running and traffic of the grayscale version, configuring grayscale release policies, and diverging the traffic.</li><li id="asm_productdesc_0001__li1386mcpsimp">Blue-green deployment: Guidance will be provided to help you perform blue-green deployment on a service, including rolling out a grayscale version, observing the running of the grayscale version, observing the traffic, and switching the traffic.</li></ul>
-<p id="asm_productdesc_0001__p12232986161"><strong id="asm_productdesc_0001__b1816271112546">Traffic management</strong></p>
+<p id="asm_productdesc_0001__p12232986161"><strong id="asm_productdesc_0001__b1816271112546">Traffic Management</strong></p>
 <ul id="asm_productdesc_0001__ul1391mcpsimp"><li id="asm_productdesc_0001__li1392mcpsimp">Layer-7 connection pool management: You can set the maximum number of HTTP requests, maximum number of retry times, maximum number of pending requests, maximum number of requests for each connection, and maximum connection idle period.</li><li id="asm_productdesc_0001__li1393mcpsimp">Layer-4 connection pool management: You can set the maximum TCP connections, connection timeout duration, maximum non-responses, minimum idle period, and health check interval.</li><li id="asm_productdesc_0001__li1395mcpsimp">Outlier detection: You can configure outlier detection rules, such as the number of consecutive errors allowed before a pod is evicted, check period, base ejection time, and maximum percentage of ejected pods.</li><li id="asm_productdesc_0001__li1396mcpsimp">Retry: You can configure the number of HTTP retry times, retry timeout duration, and retry condition.</li><li id="asm_productdesc_0001__li2071375751612">Timeout: You can configure the HTTP request timeout duration.</li><li id="asm_productdesc_0001__li1402mcpsimp">Load balancing: You can configure multiple load balancing policies, such as random, round robin, least connections, and consistent hashing.</li><li id="asm_productdesc_0001__li41827375170">HTTP header: You can flexibly add, edit, and remove HTTP headers, including the operations on the HTTP headers before the request is forwarded to the destination service and before the response is returned to the client.</li><li id="asm_productdesc_0001__li1404mcpsimp">Fault injection: You can configure delay and abort faults.</li></ul>
 <p id="asm_productdesc_0001__p1968313817166"><strong id="asm_productdesc_0001__b1457422418579">Security</strong></p>
-<ul id="asm_productdesc_0001__ul1407mcpsimp"><li id="asm_productdesc_0001__li1408mcpsimp">Peer authentication: Peer authentication defines how traffic reaches the current service pod through the tunnel (or not through the tunnel). Currently, three authentication policies are supported: <strong id="asm_productdesc_0001__b14561517122820">UNSET</strong>, <strong id="asm_productdesc_0001__b11735162015283">PERMISSIVE</strong>, and <strong id="asm_productdesc_0001__b812922432812">STRICT</strong>.</li><li id="asm_productdesc_0001__li1409mcpsimp">Access authorization: Access authorization controls the access to services in the mesh and determines whether a request can be sent to the current service.</li></ul>
+<ul id="asm_productdesc_0001__ul1407mcpsimp"><li id="asm_productdesc_0001__li1408mcpsimp">Peer authentication: Peer authentication defines how traffic reaches the current service pod through the tunnel (or not through the tunnel). Currently, three authentication policies are supported: <strong id="asm_productdesc_0001__b14561517122820">UNSET</strong>, <strong id="asm_productdesc_0001__b11735162015283">PERMISSIVE</strong>, and <strong id="asm_productdesc_0001__b812922432812">STRICT</strong>.</li><li id="asm_productdesc_0001__li1409mcpsimp">Access authorization: Access authorization controls the access to services in a service mesh and determines whether a request can be sent to the current service.</li></ul>
 <p id="asm_productdesc_0001__p21191917164"><strong id="asm_productdesc_0001__b080315428576">Observability</strong></p>
-<ul id="asm_productdesc_0001__ul1412mcpsimp"><li id="asm_productdesc_0001__li1413mcpsimp">Application access topology: An application access topology shows the dependencies between services.</li><li id="asm_productdesc_0001__li1414mcpsimp">Service running monitoring: Service access information, including service information, different versions of the service, QPS, and latency can be monitored.</li><li id="asm_productdesc_0001__li1415mcpsimp">Access logs: Service access logs can be collected and searched.</li></ul>
-<p id="asm_productdesc_0001__p156019665817"><strong id="asm_productdesc_0001__b558618285198">Framework of the mesh data plane</strong></p>
+<ul id="asm_productdesc_0001__ul1412mcpsimp"><li id="asm_productdesc_0001__li1414mcpsimp">Service running monitoring: Service access information, including service information, different versions of the service, QPS, and latency can be monitored.</li><li id="asm_productdesc_0001__li1416mcpsimp">Tracing: Non-intrusive tracing points. You can use the tracing data to demarcate and locate faults.</li></ul>
+<p id="asm_productdesc_0001__p156019665817"><strong id="asm_productdesc_0001__b558618285198">Data Plane Framework</strong></p>
 <ul id="asm_productdesc_0001__ul1427mcpsimp"><li id="asm_productdesc_0001__li1428mcpsimp">Spring Cloud: supports unified management of services developed using Spring Cloud SDK.</li><li id="asm_productdesc_0001__li1429mcpsimp">Dubbo: supports unified management of services developed using Dubbo SDK.</li></ul>
-<p id="asm_productdesc_0001__p1116812975816"><strong id="asm_productdesc_0001__b695910292201">Compatibility and extension</strong></p>
-<ul id="asm_productdesc_0001__ul1432mcpsimp"><li id="asm_productdesc_0001__li1433mcpsimp">Community compatibility: ASM APIs are fully compatible with the Istio community.</li><li id="asm_productdesc_0001__li1434mcpsimp">Support for community add-ons: Tracing, Prometheus, Kiali, and Grafana are supported.</li></ul>
+<p id="asm_productdesc_0001__p1116812975816"><strong id="asm_productdesc_0001__b695910292201">Compatibility and Extension</strong></p>
+<ul id="asm_productdesc_0001__ul1432mcpsimp"><li id="asm_productdesc_0001__li1433mcpsimp">Community compatibility: ASM APIs are fully compatible with Istio.</li><li id="asm_productdesc_0001__li1434mcpsimp">Support for community add-ons: Tracing, Prometheus, Kiali, and Grafana are supported.</li></ul>
 </div>
 </div>
 <div>
--- a/docs/asm/umn/asm_productdesc_0002.html
+++ b/docs/asm/umn/asm_productdesc_0002.html
@ -1,16 +1,16 @@
 <a name="asm_productdesc_0002"></a><a name="asm_productdesc_0002"></a>

 <h1 class="topictitle1">Advantages</h1>
-<div id="body1554084199870"><div class="section" id="asm_productdesc_0002__section7497174582015"><h4 class="sectiontitle">Ease of Use</h4><p id="asm_productdesc_0002__p16530111831214">The out-of-the-box usability allows you to use a service mesh without code rewrite or manual installation.</p>
+<div id="body1554084199870"><div class="section" id="asm_productdesc_0002__section7497174582015"><h4 class="sectiontitle">Ease of Use</h4><p id="asm_productdesc_0002__p16530111831214">The out-of-the-box features allow you to use a service mesh without code rewrite or manual installation.</p>
 </div>
-<div class="section" id="asm_productdesc_0002__section73741324105216"><h4 class="sectiontitle">Built-in Canary Release and Blue-Green Deployment</h4><ul id="asm_productdesc_0002__ul223414400516"><li id="asm_productdesc_0002__li112341540115118">Deployment of the grayscale version and traffic switchover with a few clicks</li><li id="asm_productdesc_0002__li1623474015511">Configurable grayscale policy that can be set based on traffic ratio and request content (cookies, OSs, and browsers)</li><li id="asm_productdesc_0002__li5234184011518">One-stop health, performance, and traffic monitoring, achieving quantified, intelligent, and visualized grayscale release</li></ul>
+<div class="section" id="asm_productdesc_0002__section73741324105216"><h4 class="sectiontitle">Built-in Canary Release and Blue-Green Deployment</h4><ul id="asm_productdesc_0002__ul223414400516"><li id="asm_productdesc_0002__li112341540115118">Deployment of the grayscale version and traffic switchover with a few clicks</li><li id="asm_productdesc_0002__li1623474015511">Configurable grayscale policy that can be set based on traffic ratio and request content (cookies, OSs, and browsers)</li><li id="asm_productdesc_0002__li5234184011518">One-stop health and performance monitoring as well as traffic monitoring, achieving quantified, intelligent, and visualized grayscale release</li></ul>
 </div>
 <div class="section" id="asm_productdesc_0002__section020164014510"><h4 class="sectiontitle">Policy-based Intelligent Routing and Flexible Traffic Management</h4><p id="asm_productdesc_0002__p13235184015517">Load balancing, service routing, fault injection, and outlier detection policies can be intuitively configured. Microservice traffic management can be real-time, visualized, intelligent, and automated, requiring no modifications on your applications.</p>
 <ul id="asm_productdesc_0002__ul5236134012518"><li id="asm_productdesc_0002__li223674025117">Routing rules can be set based on weight and content to implement flexible grayscale release of applications.</li><li id="asm_productdesc_0002__li17236164017519">Load balancing achieves high availability for service processing.</li><li id="asm_productdesc_0002__li13236340125116">Outlier detection ensures stable and reliable links between services.</li><li id="asm_productdesc_0002__li1523694018511">Network persistent connection management saves resources and improves network throughput.</li><li id="asm_productdesc_0002__li8236124055118">Service security certification, authentication, and audit lay a solid foundation for service security assurance.</li></ul>
 </div>
 <div class="section" id="asm_productdesc_0002__section1388710257216"><h4 class="sectiontitle">Enhanced Performance and Reliability</h4><p id="asm_productdesc_0002__p198968411827">The performance and reliability of the control plane and data plane are enhanced based on the community version.</p>
 </div>
-<div class="section" id="asm_productdesc_0002__section0577195720219"><h4 class="sectiontitle">Multi-infrastructure</h4><p id="asm_productdesc_0002__p6562101010316">An O&amp;M-free hosting control plane is provided. Unified service governance, grayscale release, security, and service running monitoring capabilities are supported. Unified service discovery and management of multiple infrastructure resources such as containers and VMs are provided.</p>
+<div class="section" id="asm_productdesc_0002__section0577195720219"><h4 class="sectiontitle">Multi-Infrastructure Management</h4><p id="asm_productdesc_0002__p6562101010316">An O&amp;M-free hosting control plane is provided. Unified service governance, grayscale release, security, and service running monitoring capabilities are supported. Unified service discovery and management of multiple infrastructure resources such as containers and VMs are provided.</p>
 </div>
 <div class="section" id="asm_productdesc_0002__section73734418314"><h4 class="sectiontitle">Protocol Extension</h4><p id="asm_productdesc_0002__p163871455537">The HTTP, gRPC, TCP, TLS, and Dubbo protocols are supported.</p>
 </div>
--- a/docs/asm/umn/asm_productdesc_0004.html
+++ b/docs/asm/umn/asm_productdesc_0004.html
@ -1,6 +1,6 @@
 <a name="asm_productdesc_0004"></a><a name="asm_productdesc_0004"></a>

-<h1 class="topictitle1">Constraints</h1>
+<h1 class="topictitle1">Notes and Constraints</h1>
 <div id="body1554084199870"><div class="section" id="asm_productdesc_0004__section5851930151419"><h4 class="sectiontitle">Constraints on Clusters</h4><p id="asm_productdesc_0004__p82752046165218">Before creating a service mesh, ensure that you have an available cluster. Cluster versions and mesh versions must meet the adaptation rules listed in <a href="#asm_productdesc_0004__table1495413335343">Table 1</a>.</p>

 <div class="tablenoborder"><a name="asm_productdesc_0004__table1495413335343"></a><a name="table1495413335343"></a><table cellpadding="4" cellspacing="0" summary="" id="asm_productdesc_0004__table1495413335343" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Adaptation rules between ASM and cluster versions</caption><thead align="left"><tr id="asm_productdesc_0004__row17955233113416"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.1.3.2.3.1.1"><p id="asm_productdesc_0004__p89551933153417">ASM Version</p>
@ -11,18 +11,18 @@
 </thead>
 <tbody><tr id="asm_productdesc_0004__row523184395810"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.1 "><p id="asm_productdesc_0004__p223164375818">1.15</p>
 </td>
-<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.2 "><p id="asm_productdesc_0004__p32394310583">v1.21, v1.23, v1.25, or v1.27</p>
+<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.3.2.3.1.2 "><p id="asm_productdesc_0004__p32394310583">v1.21, v1.23, v1.25, v1.27, or v1.28</p>
 </td>
 </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, or v1.30</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, or v1.31</p>
 </td>
 </tr>
 </tbody>
 </table>
 </div>
-<p id="asm_productdesc_0004__p697265013512">Containers on the node running Ubuntu 22.04 in a CCE Turbo cluster cannot be added to a service mesh earlier than v1.18.</p>
+<p id="asm_productdesc_0004__p697265013512">Containers on the node running Ubuntu 22.04 in a CCE Turbo cluster cannot be added to a service mesh earlier than 1.18.</p>
 </div>
 <div class="section" id="asm_productdesc_0004__section16988202112217"><h4 class="sectiontitle">Constraints on Service Meshes</h4><p id="asm_productdesc_0004__p3409102719214">When you use service meshes for service governance, a Deployment can only match with one service to avoid abnormal grayscale release, gateway access, or other functions.</p>
 </div>
--- a/Show More
+++ b/Show More