diff --git a/docs/cce/umn/ALL_META.TXT.json b/docs/cce/umn/ALL_META.TXT.json
index 2270b6fdc..a55f31336 100644
--- a/docs/cce/umn/ALL_META.TXT.json
+++ b/docs/cce/umn/ALL_META.TXT.json
@@ -277,11 +277,29 @@
 		"title":"Security Vulnerability Responses",
 		"githuburl":""
 	},
+	{
+		"uri":"CVE-2025-23266.html",
+		"node_id":"cve-2025-23266.xml",
+		"product_code":"cce",
+		"code":"16",
+		"des":"NVIDIA Container Toolkit is an open-source tool package from NVIDIA. It allows you to use NVIDIA GPUs to speed up computing in a containerized environment. The toolkit in",
+		"doc_type":"usermanual2",
+		"kw":"Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025",
+		"search_title":"",
+		"metedata":[
+			{
+				"prodname":"cce",
+				"documenttype":"usermanual"
+			}
+		],
+		"title":"Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267)",
+		"githuburl":""
+	},
 	{
 		"uri":"cce_bulletin_0011.html",
 		"node_id":"cce_bulletin_0011.xml",
 		"product_code":"cce",
-		"code":"16",
+		"code":"17",
 		"des":"High-risk vulnerabilities:CCE fixes vulnerabilities as soon as possible after the Kubernetes community detects them and releases fixing solutions. The fixing policies are",
 		"doc_type":"usermanual2",
 		"kw":"Vulnerability Fixing Policies,Security Vulnerability Responses,User Guide",
@@ -300,7 +318,7 @@
 		"uri":"CVE-2021-4034.html",
 		"node_id":"cve-2021-4034.xml",
 		"product_code":"cce",
-		"code":"17",
+		"code":"18",
 		"des":"Recently, a security research team disclosed a privilege escalation vulnerability (CVE-2021-4034, also dubbed PwnKit) in PolKit's pkexec. Unprivileged users can gain full",
 		"doc_type":"usermanual2",
 		"kw":"Linux Polkit Privilege Escalation Vulnerability (CVE-2021-4034),Security Vulnerability Responses,Use",
@@ -320,7 +338,7 @@
 		"uri":"cce_bulletin_0206.html",
 		"node_id":"cce_bulletin_0206.xml",
 		"product_code":"cce",
-		"code":"18",
+		"code":"19",
 		"des":"The Linux Kernel SACK vulnerabilities have been fixed. This section describes the solution to these vulnerabilities.On June 18, 2019, Red Hat released a security notice, ",
 		"doc_type":"usermanual2",
 		"kw":"Notice on Fixing Linux Kernel SACK Vulnerabilities,Security Vulnerability Responses,User Guide",
@@ -340,7 +358,7 @@
 		"uri":"cce_qs_0000.html",
 		"node_id":"cce_qs_0000.xml",
 		"product_code":"cce",
-		"code":"19",
+		"code":"20",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Getting Started",
@@ -360,7 +378,7 @@
 		"uri":"cce_qs_0001.html",
 		"node_id":"cce_qs_0001.xml",
 		"product_code":"cce",
-		"code":"20",
+		"code":"21",
 		"des":"This section describes how to use Cloud Container Engine (CCE) and provides frequently asked questions (FAQs) to help you quickly get started with CCE.Complete the follow",
 		"doc_type":"usermanual2",
 		"kw":"Introduction,Getting Started,User Guide",
@@ -378,7 +396,7 @@
 		"uri":"cce_qs_0006.html",
 		"node_id":"cce_qs_0006.xml",
 		"product_code":"cce",
-		"code":"21",
+		"code":"22",
 		"des":"Before using CCE, make the following preparations:Creating an IAM userObtaining Resource Permissions(Optional) Creating a VPC(Optional) Creating a Key PairIf you want to ",
 		"doc_type":"usermanual2",
 		"kw":"VPC,Preparations,Getting Started,User Guide",
@@ -396,7 +414,7 @@
 		"uri":"cce_qs_0008.html",
 		"node_id":"cce_qs_0008.xml",
 		"product_code":"cce",
-		"code":"22",
+		"code":"23",
 		"des":"This section describes how to quickly create a CCE cluster. In this example, the default or simple configurations are in use.If you have no clusters, click Create Cluster",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Kubernetes Cluster,Getting Started,User Guide",
@@ -414,7 +432,7 @@
 		"uri":"cce_qs_0003.html",
 		"node_id":"cce_qs_0003.xml",
 		"product_code":"cce",
-		"code":"23",
+		"code":"24",
 		"des":"You can use images to quickly create a single-pod workload that can be accessed from public networks. This section describes how to use CCE to quickly deploy an Nginx app",
 		"doc_type":"usermanual2",
 		"kw":"Deploying a Deployment (Nginx),Getting Started,User Guide",
@@ -432,7 +450,7 @@
 		"uri":"cce_qs_0007.html",
 		"node_id":"cce_qs_0007.xml",
 		"product_code":"cce",
-		"code":"24",
+		"code":"25",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Deploying WordPress and MySQL That Depend on Each Other",
@@ -450,7 +468,7 @@
 		"uri":"cce_qs_0009.html",
 		"node_id":"cce_qs_0009.xml",
 		"product_code":"cce",
-		"code":"25",
+		"code":"26",
 		"des":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Deploying WordPress and MySQL That Depend on Each Other,User Guide",
@@ -468,7 +486,7 @@
 		"uri":"cce_qs_0004.html",
 		"node_id":"cce_qs_0004.xml",
 		"product_code":"cce",
-		"code":"26",
+		"code":"27",
 		"des":"WordPress must be used together with MySQL. WordPress runs the content management program while MySQL serves as a database to store data.You have created a CCE cluster th",
 		"doc_type":"usermanual2",
 		"kw":"Step 1: Deploying MySQL,Deploying WordPress and MySQL That Depend on Each Other,User Guide",
@@ -486,7 +504,7 @@
 		"uri":"cce_qs_0005.html",
 		"node_id":"cce_qs_0005.xml",
 		"product_code":"cce",
-		"code":"27",
+		"code":"28",
 		"des":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser",
 		"doc_type":"usermanual2",
 		"kw":"Step 2: Deploying WordPress,Deploying WordPress and MySQL That Depend on Each Other,User Guide",
@@ -504,7 +522,7 @@
 		"uri":"cce_10_0054.html",
 		"node_id":"cce_10_0054.xml",
 		"product_code":"cce",
-		"code":"28",
+		"code":"29",
 		"des":"During service deployment or running, you may trigger high-risk operations at different levels, causing service faults or interruption. To help you better estimate and av",
 		"doc_type":"usermanual2",
 		"kw":"network-attachment-definitions,High-Risk Operations,User Guide",
@@ -522,7 +540,7 @@
 		"uri":"cce_10_0091.html",
 		"node_id":"cce_10_0091.xml",
 		"product_code":"cce",
-		"code":"29",
+		"code":"30",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Clusters",
@@ -540,7 +558,7 @@
 		"uri":"cce_10_0430.html",
 		"node_id":"cce_10_0430.xml",
 		"product_code":"cce",
-		"code":"30",
+		"code":"31",
 		"des":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the entire lifecycle of containerized applications and delivers scalable,",
 		"doc_type":"usermanual2",
 		"kw":"Number of Master Nodes in a Cluster,Cluster Overview,Clusters,User Guide",
@@ -558,7 +576,7 @@
 		"uri":"cce_10_0002.html",
 		"node_id":"cce_10_0002.xml",
 		"product_code":"cce",
-		"code":"31",
+		"code":"32",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Cluster Version Release Notes",
@@ -576,7 +594,7 @@
 		"uri":"cce_10_0068.html",
 		"node_id":"cce_10_0068.xml",
 		"product_code":"cce",
-		"code":"32",
+		"code":"33",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes Version Release Notes",
@@ -594,8 +612,8 @@
 		"uri":"cce_bulletin_0099.html",
 		"node_id":"cce_bulletin_0099.xml",
 		"product_code":"cce",
-		"code":"33",
-		"des":"CCE allows you to create Kubernetes clusters 1.31. This section describes the changes made in Kubernetes 1.31.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
+		"code":"34",
+		"des":"CCE allows you to create Kubernetes 1.31 clusters. This section describes the changes made in Kubernetes 1.31.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.31 Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
@@ -612,8 +630,8 @@
 		"uri":"cce_bulletin_0095.html",
 		"node_id":"cce_bulletin_0095.xml",
 		"product_code":"cce",
-		"code":"34",
-		"des":"CCE allows you to create Kubernetes clusters 1.30. This section describes the changes made in Kubernetes 1.30.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
+		"code":"35",
+		"des":"CCE allows you to create Kubernetes 1.30 clusters. This section describes the changes made in Kubernetes 1.30.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.30 Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
@@ -630,8 +648,8 @@
 		"uri":"cce_bulletin_0089.html",
 		"node_id":"cce_bulletin_0089.xml",
 		"product_code":"cce",
-		"code":"35",
-		"des":"CCE allows you to create Kubernetes clusters 1.29. This section describes the changes made in Kubernetes 1.29.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
+		"code":"36",
+		"des":"CCE allows you to create Kubernetes 1.29 clusters. This section describes the changes made in Kubernetes 1.29.New and Enhanced FeaturesAPI Changes and RemovalsIncompatibl",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.29 Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
@@ -648,8 +666,8 @@
 		"uri":"cce_bulletin_0068.html",
 		"node_id":"cce_bulletin_0068.xml",
 		"product_code":"cce",
-		"code":"36",
-		"des":"CCE allows you to create Kubernetes clusters 1.28. This section describes the changes made in Kubernetes 1.28.Important NotesNew and Enhanced FeaturesAPI Changes and Remo",
+		"code":"37",
+		"des":"CCE allows you to create Kubernetes 1.28 clusters. This section describes the changes made in Kubernetes 1.28.Important NotesNew and Enhanced FeaturesAPI Changes and Remo",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.28 Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
@@ -666,8 +684,8 @@
 		"uri":"cce_bulletin_0059.html",
 		"node_id":"cce_bulletin_0059.xml",
 		"product_code":"cce",
-		"code":"37",
-		"des":"CCE allows you to create Kubernetes clusters 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations and R",
+		"code":"38",
+		"des":"CCE allows you to create Kubernetes 1.27 clusters. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations and R",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.27 Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
@@ -684,10 +702,10 @@
 		"uri":"cce_bulletin_0058.html",
 		"node_id":"cce_bulletin_0058.xml",
 		"product_code":"cce",
-		"code":"38",
+		"code":"39",
 		"des":"This section describes the changes made in Kubernetes 1.25 compared with Kubernetes 1.23.New FeaturesDeprecations and RemovalsEnhanced Kubernetes 1.25 on CCEReferencesKub",
 		"doc_type":"usermanual2",
-		"kw":"Kubernetes 1.25 Release Notes,Kubernetes Version Release Notes,User Guide",
+		"kw":"Kubernetes 1.25 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
 		"metedata":[
 			{
@@ -695,17 +713,17 @@
 				"documenttype":"usermanual"
 			}
 		],
-		"title":"Kubernetes 1.25 Release Notes",
+		"title":"Kubernetes 1.25 (EOM) Release Notes",
 		"githuburl":""
 	},
 	{
 		"uri":"cce_bulletin_0027.html",
 		"node_id":"cce_bulletin_0027.xml",
 		"product_code":"cce",
-		"code":"39",
+		"code":"40",
 		"des":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes v1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, an",
 		"doc_type":"usermanual2",
-		"kw":"Kubernetes 1.23 Release Notes,Kubernetes Version Release Notes,User Guide",
+		"kw":"Kubernetes 1.23 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
 		"search_title":"",
 		"metedata":[
 			{
@@ -713,14 +731,14 @@
 				"documenttype":"usermanual"
 			}
 		],
-		"title":"Kubernetes 1.23 Release Notes",
+		"title":"Kubernetes 1.23 (EOM) Release Notes",
 		"githuburl":""
 	},
 	{
 		"uri":"cce_bulletin_0026.html",
 		"node_id":"cce_bulletin_0026.xml",
 		"product_code":"cce",
-		"code":"40",
+		"code":"41",
 		"des":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes v1.21 Release NotesCronJob is now in the stable state, and the version number changes to batch/v1.The",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.21 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
@@ -738,7 +756,7 @@
 		"uri":"cce_whsnew_0010.html",
 		"node_id":"cce_whsnew_0010.xml",
 		"product_code":"cce",
-		"code":"41",
+		"code":"42",
 		"des":"This section describes the updates in CCE Kubernetes 1.19.Kubernetes v1.19 Release NotesvSphere in-tree volumes can be migrated to vSphere CSI drivers. The in-tree vSpher",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.19 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
@@ -756,7 +774,7 @@
 		"uri":"cce_whsnew_0007.html",
 		"node_id":"cce_whsnew_0007.xml",
 		"product_code":"cce",
-		"code":"42",
+		"code":"43",
 		"des":"This section describes the updates in CCE Kubernetes 1.17.All resources in the apps/v1beta1 and apps/v1beta2 API versions are no longer served. Migrate to use the apps/v1",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes 1.17 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
@@ -774,7 +792,7 @@
 		"uri":"cce_10_0405.html",
 		"node_id":"cce_10_0405.xml",
 		"product_code":"cce",
-		"code":"43",
+		"code":"44",
 		"des":"In CCE clusters of v1.25, containerd is the default runtime for nodes, except for nodes running EulerOS 2.5. In addition, clusters of v1.25 or later no longer support Eul",
 		"doc_type":"usermanual2",
 		"kw":"Patch Version Release Notes,Cluster Version Release Notes,User Guide",
@@ -792,7 +810,7 @@
 		"uri":"cce_10_0298.html",
 		"node_id":"cce_10_0298.xml",
 		"product_code":"cce",
-		"code":"44",
+		"code":"45",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Cluster",
@@ -810,7 +828,7 @@
 		"uri":"cce_10_0342.html",
 		"node_id":"cce_10_0342.xml",
 		"product_code":"cce",
-		"code":"45",
+		"code":"46",
 		"des":"CCE provides different types of clusters for you to select. The following table lists the differences between them.",
 		"doc_type":"usermanual2",
 		"kw":"Comparison Between Cluster Types,Creating a Cluster,User Guide",
@@ -828,7 +846,7 @@
 		"uri":"cce_10_0028.html",
 		"node_id":"cce_10_0028.xml",
 		"product_code":"cce",
-		"code":"46",
+		"code":"47",
 		"des":"On the CCE console, you can easily create Kubernetes clusters. After a cluster is created, the master node is hosted by CCE. You only need to create worker nodes. In this",
 		"doc_type":"usermanual2",
 		"kw":"Creating a CCE Standard/Turbo Cluster,Creating a Cluster,User Guide",
@@ -846,7 +864,7 @@
 		"uri":"cce_10_0349.html",
 		"node_id":"cce_10_0349.xml",
 		"product_code":"cce",
-		"code":"47",
+		"code":"48",
 		"des":"kube-proxy is a key component of a Kubernetes cluster. It is used for load balancing and forwarding data between a Service and its backend pods.CCE supports the iptables ",
 		"doc_type":"usermanual2",
 		"kw":"kube-proxy,iptables,IP Virtual Server (IPVS),forwarding modes,Comparing iptables and IPVS,Creating a",
@@ -864,7 +882,7 @@
 		"uri":"cce_10_0140.html",
 		"node_id":"cce_10_0140.xml",
 		"product_code":"cce",
-		"code":"48",
+		"code":"49",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Connecting to a Cluster",
@@ -882,7 +900,7 @@
 		"uri":"cce_10_0107.html",
 		"node_id":"cce_10_0107.xml",
 		"product_code":"cce",
-		"code":"49",
+		"code":"50",
 		"des":"kubectl is a command-line tool provided by Kubernetes, enabling you to manage cluster resources, view cluster status, deploy applications, and debug issues through the CL",
 		"doc_type":"usermanual2",
 		"kw":"Intranet access,Internet access,kubectl,intranet access,Internet access,Two-Way Authentication for D",
@@ -900,7 +918,7 @@
 		"uri":"cce_10_0175.html",
 		"node_id":"cce_10_0175.xml",
 		"product_code":"cce",
-		"code":"50",
+		"code":"51",
 		"des":"X.509 certificates are essential for verifying identities and encrypting communication within CCE clusters. These certificates enable authorized clients to access target ",
 		"doc_type":"usermanual2",
 		"kw":"X.509 certificate,Accessing a Cluster Using an X.509 Certificate,Connecting to a Cluster,User Guide",
@@ -918,7 +936,7 @@
 		"uri":"cce_10_0367.html",
 		"node_id":"cce_10_0367.xml",
 		"product_code":"cce",
-		"code":"51",
+		"code":"52",
 		"des":"Subject Alternative Name (SAN) enables certificates to be associated with multiple values, including IP addresses and domain names. A SAN is usually used by the client to",
 		"doc_type":"usermanual2",
 		"kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Gu",
@@ -936,7 +954,7 @@
 		"uri":"cce_10_0864.html",
 		"node_id":"cce_10_0864.xml",
 		"product_code":"cce",
-		"code":"52",
+		"code":"53",
 		"des":"You can bind an EIP to an API server of a Kubernetes cluster so that the API server can access the Internet.Binding an EIP to an API server for Internet access can pose a",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Cluster's API Server for Internet Access,Connecting to a Cluster,User Guide",
@@ -954,7 +972,7 @@
 		"uri":"cce_10_0744.html",
 		"node_id":"cce_10_0744.xml",
 		"product_code":"cce",
-		"code":"53",
+		"code":"54",
 		"des":"In multi-tenant scenarios, CCE generates a unique credential (such as a kubeconfig file or an X.509 certificate) for each user to access their designated cluster. These c",
 		"doc_type":"usermanual2",
 		"kw":"Revoking a Cluster Access Credential,Connecting to a Cluster,User Guide",
@@ -972,7 +990,7 @@
 		"uri":"cce_10_0031.html",
 		"node_id":"cce_10_0031.xml",
 		"product_code":"cce",
-		"code":"54",
+		"code":"55",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Managing a Cluster",
@@ -990,7 +1008,7 @@
 		"uri":"cce_10_0213.html",
 		"node_id":"cce_10_0213.xml",
 		"product_code":"cce",
-		"code":"55",
+		"code":"56",
 		"des":"Cluster configuration parameters are underlying rules that define node behavior, resource allocation, communication rules, and scaling policies in a distributed system. T",
 		"doc_type":"usermanual2",
 		"kw":"Cluster configuration parameters,cluster configuration parameters,Cluster configuration parameters,C",
@@ -1008,7 +1026,7 @@
 		"uri":"cce_10_0602.html",
 		"node_id":"cce_10_0602.xml",
 		"product_code":"cce",
-		"code":"56",
+		"code":"57",
 		"des":"Cluster overload occurs when system load such as request volume or resource usage exceeds the system's processing capacity, leading to degraded performance or system fail",
 		"doc_type":"usermanual2",
 		"kw":"Enabling Overload Control for a Cluster,Managing a Cluster,User Guide",
@@ -1026,7 +1044,7 @@
 		"uri":"cce_10_0403.html",
 		"node_id":"cce_10_0403.xml",
 		"product_code":"cce",
-		"code":"57",
+		"code":"58",
 		"des":"A cluster scale specifies the maximum number of nodes a cluster can manage. If the current cluster scale cannot meet your requirements, you can scale it out.A cluster tha",
 		"doc_type":"usermanual2",
 		"kw":"scale it out,Changing a Cluster Scale,Managing a Cluster,User Guide",
@@ -1044,7 +1062,7 @@
 		"uri":"cce_10_0426.html",
 		"node_id":"cce_10_0426.xml",
 		"product_code":"cce",
-		"code":"58",
+		"code":"59",
 		"des":"When creating a cluster, you can customize a node security group to centrally manage network security policies. For a created cluster, you can change its default node sec",
 		"doc_type":"usermanual2",
 		"kw":"Changing the Default Security Group of a Node,Managing a Cluster,User Guide",
@@ -1062,7 +1080,7 @@
 		"uri":"cce_10_0212.html",
 		"node_id":"cce_10_0212.xml",
 		"product_code":"cce",
-		"code":"59",
+		"code":"60",
 		"des":"Deleting a cluster will delete the workloads and Services in the cluster, and the deleted data cannot be recovered. Before performing this operation, ensure that related ",
 		"doc_type":"usermanual2",
 		"kw":"Deleting a Cluster,Managing a Cluster,User Guide",
@@ -1080,7 +1098,7 @@
 		"uri":"cce_10_0927.html",
 		"node_id":"cce_10_0927.xml",
 		"product_code":"cce",
-		"code":"60",
+		"code":"61",
 		"des":"Unexpected deletion of clusters can occur in practice, especially when multiple users share an account and accidentally delete clusters that do not belong to them. To pre",
 		"doc_type":"usermanual2",
 		"kw":"Preventing Cluster Deletion,Managing a Cluster,User Guide",
@@ -1098,7 +1116,7 @@
 		"uri":"cce_10_0214.html",
 		"node_id":"cce_10_0214.xml",
 		"product_code":"cce",
-		"code":"61",
+		"code":"62",
 		"des":"If a cluster is not needed temporarily, hibernate it to reduce costs.After a cluster is hibernated, resources such as workloads cannot be created or managed in the cluste",
 		"doc_type":"usermanual2",
 		"kw":"Hibernating or Waking Up a Cluster,Managing a Cluster,User Guide",
@@ -1116,7 +1134,7 @@
 		"uri":"cce_10_0215.html",
 		"node_id":"cce_10_0215.xml",
 		"product_code":"cce",
-		"code":"62",
+		"code":"63",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Upgrading a Cluster",
@@ -1134,7 +1152,7 @@
 		"uri":"cce_10_0197.html",
 		"node_id":"cce_10_0197.xml",
 		"product_code":"cce",
-		"code":"63",
+		"code":"64",
 		"des":"CCE strictly complies with community consistency authentication. It releases three Kubernetes versions each year and offers a maintenance period of at least 24 months aft",
 		"doc_type":"usermanual2",
 		"kw":"cluster upgrade process,Node Priority,In-place upgrade,Cluster Upgrade Overview,Upgrading a Cluster,",
@@ -1152,7 +1170,7 @@
 		"uri":"cce_10_0302.html",
 		"node_id":"cce_10_0302.xml",
 		"product_code":"cce",
-		"code":"64",
+		"code":"65",
 		"des":"Before the upgrade, you can check whether your cluster can be upgraded and which versions are available on the CCE console. For details, see Cluster Upgrade Overview.Befo",
 		"doc_type":"usermanual2",
 		"kw":"Deprecated APIs,Before You Start,Upgrading a Cluster,User Guide",
@@ -1170,7 +1188,7 @@
 		"uri":"cce_10_0560.html",
 		"node_id":"cce_10_0560.xml",
 		"product_code":"cce",
-		"code":"65",
+		"code":"66",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Performing Post-Upgrade Verification",
@@ -1188,7 +1206,7 @@
 		"uri":"cce_10_0568.html",
 		"node_id":"cce_10_0568.xml",
 		"product_code":"cce",
-		"code":"66",
+		"code":"67",
 		"des":"After a cluster is upgraded, check whether the cluster is in the Running state.CCE automatically checks your cluster status. Go to the cluster list page and confirm the c",
 		"doc_type":"usermanual2",
 		"kw":"Cluster Status Check,Performing Post-Upgrade Verification,User Guide",
@@ -1206,7 +1224,7 @@
 		"uri":"cce_10_0569.html",
 		"node_id":"cce_10_0569.xml",
 		"product_code":"cce",
-		"code":"67",
+		"code":"68",
 		"des":"After a cluster is upgraded, check whether nodes in the cluster are in the Running state.CCE automatically checks your node statuses. Go to the node list page and confirm",
 		"doc_type":"usermanual2",
 		"kw":"Node Status Check,Performing Post-Upgrade Verification,User Guide",
@@ -1224,7 +1242,7 @@
 		"uri":"cce_10_0567.html",
 		"node_id":"cce_10_0567.xml",
 		"product_code":"cce",
-		"code":"68",
+		"code":"69",
 		"des":"After a cluster is upgraded, check whether there are any nodes that skip the upgrade in the cluster. These nodes may affect the proper running of the cluster.CCE automati",
 		"doc_type":"usermanual2",
 		"kw":"Node Skipping Check,Performing Post-Upgrade Verification,User Guide",
@@ -1242,7 +1260,7 @@
 		"uri":"cce_10_0561.html",
 		"node_id":"cce_10_0561.xml",
 		"product_code":"cce",
-		"code":"69",
+		"code":"70",
 		"des":"After a cluster is upgraded, check whether its services are running properly.Different services have different verification mode. Select a suitable one and verify the ser",
 		"doc_type":"usermanual2",
 		"kw":"Service Check,Performing Post-Upgrade Verification,User Guide",
@@ -1260,7 +1278,7 @@
 		"uri":"cce_10_0565.html",
 		"node_id":"cce_10_0565.xml",
 		"product_code":"cce",
-		"code":"70",
+		"code":"71",
 		"des":"Check whether nodes can be created in the cluster.If nodes cannot be created in your cluster after the cluster is upgraded, contact technical support.",
 		"doc_type":"usermanual2",
 		"kw":"New Node Check,Performing Post-Upgrade Verification,User Guide",
@@ -1278,7 +1296,7 @@
 		"uri":"cce_10_0566.html",
 		"node_id":"cce_10_0566.xml",
 		"product_code":"cce",
-		"code":"71",
+		"code":"72",
 		"des":"Check whether pods can be created on the existing nodes after the cluster is upgraded.Check whether pods can be created on new nodes after the cluster is upgraded.After c",
 		"doc_type":"usermanual2",
 		"kw":"New Pod Check,Performing Post-Upgrade Verification,User Guide",
@@ -1296,7 +1314,7 @@
 		"uri":"cce_10_0210.html",
 		"node_id":"cce_10_0210.xml",
 		"product_code":"cce",
-		"code":"72",
+		"code":"73",
 		"des":"This section describes how to migrate services from a cluster of an earlier version to a cluster of a later version in CCE.This operation is applicable when a cross-versi",
 		"doc_type":"usermanual2",
 		"kw":"Migrating Services Across Clusters of Different Versions,Upgrading a Cluster,User Guide",
@@ -1314,7 +1332,7 @@
 		"uri":"cce_10_0550.html",
 		"node_id":"cce_10_0550.xml",
 		"product_code":"cce",
-		"code":"73",
+		"code":"74",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Troubleshooting for Pre-upgrade Check Exceptions",
@@ -1332,7 +1350,7 @@
 		"uri":"cce_10_0549.html",
 		"node_id":"cce_10_0549.xml",
 		"product_code":"cce",
-		"code":"74",
+		"code":"75",
 		"des":"The system automatically checks a cluster before its upgrade. If the cluster does not meet the pre-upgrade check conditions, the upgrade cannot continue. To avoid risks, ",
 		"doc_type":"usermanual2",
 		"kw":"Pre-upgrade Check,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1350,7 +1368,7 @@
 		"uri":"cce_10_0431.html",
 		"node_id":"cce_10_0431.xml",
 		"product_code":"cce",
-		"code":"75",
+		"code":"76",
 		"des":"Check the following items:Check whether the node is available.Check whether the node OS supports the upgrade.Check whether the node is marked with unexpected node pool la",
 		"doc_type":"usermanual2",
 		"kw":"Node Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1368,7 +1386,7 @@
 		"uri":"cce_10_0432.html",
 		"node_id":"cce_10_0432.xml",
 		"product_code":"cce",
-		"code":"76",
+		"code":"77",
 		"des":"Check whether the target cluster is under upgrade management.CCE may temporarily restrict the cluster upgrade due to the following reasons:The cluster is identified as th",
 		"doc_type":"usermanual2",
 		"kw":"Upgrade Management,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1386,7 +1404,7 @@
 		"uri":"cce_10_0433.html",
 		"node_id":"cce_10_0433.xml",
 		"product_code":"cce",
-		"code":"77",
+		"code":"78",
 		"des":"Check the following items:Check whether the add-on status is normal.Check whether the add-on supports the target version.Scenario 1: The add-on malfunctions.Log in to the",
 		"doc_type":"usermanual2",
 		"kw":"Add-ons,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1404,7 +1422,7 @@
 		"uri":"cce_10_0434.html",
 		"node_id":"cce_10_0434.xml",
 		"product_code":"cce",
-		"code":"78",
+		"code":"79",
 		"des":"Check whether the current HelmRelease record contains discarded Kubernetes APIs that are not supported by the target cluster version. If yes, the Helm chart may be unavai",
 		"doc_type":"usermanual2",
 		"kw":"Helm Charts,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1422,7 +1440,7 @@
 		"uri":"cce_10_0435.html",
 		"node_id":"cce_10_0435.xml",
 		"product_code":"cce",
-		"code":"79",
+		"code":"80",
 		"des":"Check whether your master nodes can be accessed using SSH.There is a low probability that the SSH connectivity check fails due to network fluctuations. Perform the pre-up",
 		"doc_type":"usermanual2",
 		"kw":"SSH Connectivity of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1440,7 +1458,7 @@
 		"uri":"cce_10_0436.html",
 		"node_id":"cce_10_0436.xml",
 		"product_code":"cce",
-		"code":"80",
+		"code":"81",
 		"des":"Check the node pool status.Check whether the node pool OS or container runtime is supported after the upgrade.Scenario: The node pool malfunctions.Log in to the CCE conso",
 		"doc_type":"usermanual2",
 		"kw":"Node Pools,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1458,7 +1476,7 @@
 		"uri":"cce_10_0437.html",
 		"node_id":"cce_10_0437.xml",
 		"product_code":"cce",
-		"code":"81",
+		"code":"82",
 		"des":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group rule with the source IP address set to the master ",
 		"doc_type":"usermanual2",
 		"kw":"Security Groups,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1476,7 +1494,7 @@
 		"uri":"cce_10_0439.html",
 		"node_id":"cce_10_0439.xml",
 		"product_code":"cce",
-		"code":"82",
+		"code":"83",
 		"des":"Check whether nodes need to be migrated.This issue is caused by either an error in the node's package pull component or the absence of key system components on the node, ",
 		"doc_type":"usermanual2",
 		"kw":"Residual Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1494,7 +1512,7 @@
 		"uri":"cce_10_0440.html",
 		"node_id":"cce_10_0440.xml",
 		"product_code":"cce",
-		"code":"83",
+		"code":"84",
 		"des":"Check whether there are discarded resources in the clusters.Scenario 1: The Service in the clusters of v1.25 or later has discarded annotation tolerate-unready-endpoints.",
 		"doc_type":"usermanual2",
 		"kw":"Discarded Kubernetes Resources,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1512,7 +1530,7 @@
 		"uri":"cce_10_0441.html",
 		"node_id":"cce_10_0441.xml",
 		"product_code":"cce",
-		"code":"84",
+		"code":"85",
 		"des":"Read the version compatibility differences and ensure that they are not affected. The patch upgrade does not involve version compatibility differences.",
 		"doc_type":"usermanual2",
 		"kw":"Compatibility Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1530,7 +1548,7 @@
 		"uri":"cce_10_0442.html",
 		"node_id":"cce_10_0442.xml",
 		"product_code":"cce",
-		"code":"85",
+		"code":"86",
 		"des":"Check whether cce-agent on the current node is of the latest version.Scenario 1: The error message \"you cce-agent no update, please restart it\" is displayed.This issue oc",
 		"doc_type":"usermanual2",
 		"kw":"CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1548,7 +1566,7 @@
 		"uri":"cce_10_0443.html",
 		"node_id":"cce_10_0443.xml",
 		"product_code":"cce",
-		"code":"86",
+		"code":"87",
 		"des":"Check whether the node's CPU usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods to",
 		"doc_type":"usermanual2",
 		"kw":"Node CPU Usage,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1566,7 +1584,7 @@
 		"uri":"cce_10_0444.html",
 		"node_id":"cce_10_0444.xml",
 		"product_code":"cce",
-		"code":"87",
+		"code":"88",
 		"des":"Check the following items:Check whether the key CRD packageversions.version.cce.io of the cluster is deleted.Check whether the cluster key CRD network-attachment-definiti",
 		"doc_type":"usermanual2",
 		"kw":"CRDs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1584,7 +1602,7 @@
 		"uri":"cce_10_0445.html",
 		"node_id":"cce_10_0445.xml",
 		"product_code":"cce",
-		"code":"88",
+		"code":"89",
 		"des":"Check the following items:Check whether the key data disks on the node meet the upgrade requirements.Check whether the /tmp directory has 500 MB available space.During th",
 		"doc_type":"usermanual2",
 		"kw":"Node Disks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1602,7 +1620,7 @@
 		"uri":"cce_10_0446.html",
 		"node_id":"cce_10_0446.xml",
 		"product_code":"cce",
-		"code":"89",
+		"code":"90",
 		"des":"Check the following items:Check whether the DNS configuration of the current node can resolve the OBS address.Check whether the current node can access the OBS address of",
 		"doc_type":"usermanual2",
 		"kw":"Node DNS,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1620,7 +1638,7 @@
 		"uri":"cce_10_0447.html",
 		"node_id":"cce_10_0447.xml",
 		"product_code":"cce",
-		"code":"90",
+		"code":"91",
 		"des":"Check whether the owner and owner group of the files in the /var/paas directory used by the CCE are both paas.Scenario 1: The error message \"xx file permission has been c",
 		"doc_type":"usermanual2",
 		"kw":"Node Key Directory File Permissions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1638,7 +1656,7 @@
 		"uri":"cce_10_0448.html",
 		"node_id":"cce_10_0448.xml",
 		"product_code":"cce",
-		"code":"91",
+		"code":"92",
 		"des":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node will be unavailable. Restore th",
 		"doc_type":"usermanual2",
 		"kw":"kubelet,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1656,7 +1674,7 @@
 		"uri":"cce_10_0449.html",
 		"node_id":"cce_10_0449.xml",
 		"product_code":"cce",
-		"code":"92",
+		"code":"93",
 		"des":"Check whether the node's memory usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods",
 		"doc_type":"usermanual2",
 		"kw":"Node Memory,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1674,7 +1692,7 @@
 		"uri":"cce_10_0450.html",
 		"node_id":"cce_10_0450.xml",
 		"product_code":"cce",
-		"code":"93",
+		"code":"94",
 		"des":"Check whether the clock synchronization server ntpd or chronyd of the node is running properly.Scenario 1: ntpd is running abnormally.Log in to the node and run the syste",
 		"doc_type":"usermanual2",
 		"kw":"Node Clock Synchronization Server,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1692,7 +1710,7 @@
 		"uri":"cce_10_0451.html",
 		"node_id":"cce_10_0451.xml",
 		"product_code":"cce",
-		"code":"94",
+		"code":"95",
 		"des":"Check whether the OS kernel version of the node is supported by CCE.Case 1: The node image is not a standard CCE image.CCE nodes run depending on the initial standard ker",
 		"doc_type":"usermanual2",
 		"kw":"Node OS,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1710,7 +1728,7 @@
 		"uri":"cce_10_0452.html",
 		"node_id":"cce_10_0452.xml",
 		"product_code":"cce",
-		"code":"95",
+		"code":"96",
 		"des":"Verify that the master nodes in your cluster have more than 2 CPU cores.The master nodes have only 2 CPU cores, which may lead to a cluster upgrade failure.Contact techni",
 		"doc_type":"usermanual2",
 		"kw":"Node CPU Cores,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1728,7 +1746,7 @@
 		"uri":"cce_10_0453.html",
 		"node_id":"cce_10_0453.xml",
 		"product_code":"cce",
-		"code":"96",
+		"code":"97",
 		"des":"Check whether the Python commands are available on a node.If the command output is not 0, the check fails.Reset the node or manually install Python before attempting the ",
 		"doc_type":"usermanual2",
 		"kw":"Node Python Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1746,7 +1764,7 @@
 		"uri":"cce_10_0455.html",
 		"node_id":"cce_10_0455.xml",
 		"product_code":"cce",
-		"code":"97",
+		"code":"98",
 		"des":"Check whether the nodes in the cluster are ready.Scenario 1: The nodes are in the unavailable status.Log in to the CCE console and click the cluster name to access the cl",
 		"doc_type":"usermanual2",
 		"kw":"Node Readiness,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1764,7 +1782,7 @@
 		"uri":"cce_10_0456.html",
 		"node_id":"cce_10_0456.xml",
 		"product_code":"cce",
-		"code":"98",
+		"code":"99",
 		"des":"Check whether journald of a node is normal.Log in to the node and run the systemctl is-active systemd-journald command to obtain the running status of journald. If the co",
 		"doc_type":"usermanual2",
 		"kw":"Node journald,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1782,7 +1800,7 @@
 		"uri":"cce_10_0457.html",
 		"node_id":"cce_10_0457.xml",
 		"product_code":"cce",
-		"code":"99",
+		"code":"100",
 		"des":"Check whether the containerd.sock file is on the node. This file affects the startup of container runtime in the Euler OS.Scenario: The Docker used by the node is the cus",
 		"doc_type":"usermanual2",
 		"kw":"containerd.sock,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1800,7 +1818,7 @@
 		"uri":"cce_10_0458.html",
 		"node_id":"cce_10_0458.xml",
 		"product_code":"cce",
-		"code":"100",
+		"code":"101",
 		"des":"This check item is not typical and implies that an internal error was found during the pre-upgrade check.Perform the pre-upgrade check again.If it fails again, submit a s",
 		"doc_type":"usermanual2",
 		"kw":"Internal Error,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1818,7 +1836,7 @@
 		"uri":"cce_10_0459.html",
 		"node_id":"cce_10_0459.xml",
 		"product_code":"cce",
-		"code":"101",
+		"code":"102",
 		"des":"Check whether there are inaccessible mount points on the node.Scenario: There are inaccessible mount points on the node.If NFS (such as obsfs or SFS) is used by the node ",
 		"doc_type":"usermanual2",
 		"kw":"Node Mount Points,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1836,7 +1854,7 @@
 		"uri":"cce_10_0460.html",
 		"node_id":"cce_10_0460.xml",
 		"product_code":"cce",
-		"code":"102",
+		"code":"103",
 		"des":"Check whether the taint needed for cluster upgrade exists on the node.Scenario 1: The node is skipped during the cluster upgrade.If the version of the node is different f",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes Node Taints,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1854,7 +1872,7 @@
 		"uri":"cce_10_0478.html",
 		"node_id":"cce_10_0478.xml",
 		"product_code":"cce",
-		"code":"103",
+		"code":"104",
 		"des":"Check whether there are any compatibility restrictions on the current Everest add-on.There are compatibility restrictions on the current Everest add-on and it cannot be u",
 		"doc_type":"usermanual2",
 		"kw":"Everest Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1872,7 +1890,7 @@
 		"uri":"cce_10_0479.html",
 		"node_id":"cce_10_0479.xml",
 		"product_code":"cce",
-		"code":"104",
+		"code":"105",
 		"des":"Check whether there are compatibility limitations between the current and target cce-controller-hpa add-on versions.There are compatibility limitations between the curren",
 		"doc_type":"usermanual2",
 		"kw":"cce-hpa-controller Limitations,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1890,7 +1908,7 @@
 		"uri":"cce_10_0480.html",
 		"node_id":"cce_10_0480.xml",
 		"product_code":"cce",
-		"code":"105",
+		"code":"106",
 		"des":"Check whether the current cluster version and the target version support enhanced CPU policy.Scenario: Only the current cluster version supports the enhanced CPU policy f",
 		"doc_type":"usermanual2",
 		"kw":"Enhanced CPU Policies,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1908,7 +1926,7 @@
 		"uri":"cce_10_0484.html",
 		"node_id":"cce_10_0484.xml",
 		"product_code":"cce",
-		"code":"106",
+		"code":"107",
 		"des":"Check whether the container runtime and network components on the worker nodes are healthy.Issue 1: CNI Agent is not active.If your cluster version is earlier than v1.17.",
 		"doc_type":"usermanual2",
 		"kw":"Health of Worker Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1926,7 +1944,7 @@
 		"uri":"cce_10_0485.html",
 		"node_id":"cce_10_0485.xml",
 		"product_code":"cce",
-		"code":"107",
+		"code":"108",
 		"des":"Check whether cluster components such as the Kubernetes component, container runtime component, and network component are running properly before the upgrade.Perform the ",
 		"doc_type":"usermanual2",
 		"kw":"Health of Master Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1944,7 +1962,7 @@
 		"uri":"cce_10_0486.html",
 		"node_id":"cce_10_0486.xml",
 		"product_code":"cce",
-		"code":"108",
+		"code":"109",
 		"des":"Check whether the resources of Kubernetes components, such as etcd and kube-controller-manager, exceed the upper limit.Solution 1: Reduce Kubernetes resources that are ne",
 		"doc_type":"usermanual2",
 		"kw":"Memory Resource Limit of Kubernetes Components,Troubleshooting for Pre-upgrade Check Exceptions,User",
@@ -1962,7 +1980,7 @@
 		"uri":"cce_10_0487.html",
 		"node_id":"cce_10_0487.xml",
 		"product_code":"cce",
-		"code":"109",
+		"code":"110",
 		"des":"The system scans the audit logs of the past day to check whether the user calls the deprecated APIs of the target Kubernetes version.Due to the limited time range of audi",
 		"doc_type":"usermanual2",
 		"kw":"Discarded Kubernetes APIs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1980,7 +1998,7 @@
 		"uri":"cce_10_0488.html",
 		"node_id":"cce_10_0488.xml",
 		"product_code":"cce",
-		"code":"110",
+		"code":"111",
 		"des":"If IPv6 is enabled for a CCE Turbo cluster, check whether the target cluster version supports IPv6.CCE Turbo clusters support IPv6 since v1.23. This feature is available ",
 		"doc_type":"usermanual2",
 		"kw":"IPv6 Support in CCE Turbo Clusters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -1998,7 +2016,7 @@
 		"uri":"cce_10_0489.html",
 		"node_id":"cce_10_0489.xml",
 		"product_code":"cce",
-		"code":"111",
+		"code":"112",
 		"des":"Check whether NetworkManager of a node is normal.Log in to the node and run the systemctl is-active NetworkManager command to obtain the running status of NetworkManager.",
 		"doc_type":"usermanual2",
 		"kw":"NetworkManager,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2016,7 +2034,7 @@
 		"uri":"cce_10_0490.html",
 		"node_id":"cce_10_0490.xml",
 		"product_code":"cce",
-		"code":"112",
+		"code":"113",
 		"des":"Check the ID file format.",
 		"doc_type":"usermanual2",
 		"kw":"Node ID File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2034,7 +2052,7 @@
 		"uri":"cce_10_0491.html",
 		"node_id":"cce_10_0491.xml",
 		"product_code":"cce",
-		"code":"113",
+		"code":"114",
 		"des":"When you upgrade a cluster to v1.19 or later, the system checks whether the following configuration files have been modified on the backend:/opt/cloud/cce/kubernetes/kube",
 		"doc_type":"usermanual2",
 		"kw":"Node Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2052,7 +2070,7 @@
 		"uri":"cce_10_0492.html",
 		"node_id":"cce_10_0492.xml",
 		"product_code":"cce",
-		"code":"114",
+		"code":"115",
 		"des":"Check whether the configuration files of key components exist on the node.The following table lists the files to be checked.Reset the node. For details, see Resetting a N",
 		"doc_type":"usermanual2",
 		"kw":"Node Configuration File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2070,7 +2088,7 @@
 		"uri":"cce_10_0493.html",
 		"node_id":"cce_10_0493.xml",
 		"product_code":"cce",
-		"code":"115",
+		"code":"116",
 		"des":"Check whether the current CoreDNS key configuration Corefile is different from the Helm release record. The difference may be overwritten during the add-on upgrade, affec",
 		"doc_type":"usermanual2",
 		"kw":"CoreDNS Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2088,7 +2106,7 @@
 		"uri":"cce_10_0494.html",
 		"node_id":"cce_10_0494.xml",
 		"product_code":"cce",
-		"code":"116",
+		"code":"117",
 		"des":"Check whether the sudo commands and sudo-related files of the node are working.Scenario 1: The sudo command fails to be executed.During the in-place cluster upgrade, the ",
 		"doc_type":"usermanual2",
 		"kw":"sudo,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2106,7 +2124,7 @@
 		"uri":"cce_10_0495.html",
 		"node_id":"cce_10_0495.xml",
 		"product_code":"cce",
-		"code":"117",
+		"code":"118",
 		"des":"Whether some key commands that the node upgrade depends on are workingScenario 1: Executing the package manager command failed.Executing the rpm or dpkg command failed. I",
 		"doc_type":"usermanual2",
 		"kw":"Key Node Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2124,7 +2142,7 @@
 		"uri":"cce_10_0496.html",
 		"node_id":"cce_10_0496.xml",
 		"product_code":"cce",
-		"code":"118",
+		"code":"119",
 		"des":"Check whether the docker/containerd.sock file is directly mounted to the pods on a node. During an upgrade, Docker or containerd restarts and the sock file on the host ch",
 		"doc_type":"usermanual2",
 		"kw":"Mounting of a Sock File on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2142,7 +2160,7 @@
 		"uri":"cce_10_0497.html",
 		"node_id":"cce_10_0497.xml",
 		"product_code":"cce",
-		"code":"119",
+		"code":"120",
 		"des":"Check whether the certificate used by an HTTPS load balancer has been modified on ELB.The certificate referenced by an HTTPS ingress created on CCE is modified on the ELB",
 		"doc_type":"usermanual2",
 		"kw":"HTTPS Load Balancer Certificate Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Gu",
@@ -2160,7 +2178,7 @@
 		"uri":"cce_10_0498.html",
 		"node_id":"cce_10_0498.xml",
 		"product_code":"cce",
-		"code":"120",
+		"code":"121",
 		"des":"Check whether the default mount directory and soft link on the node have been manually mounted or modified.Non-shared diskBy default, /var/lib/docker, containerd, or /mnt",
 		"doc_type":"usermanual2",
 		"kw":"Node Mounting,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2178,7 +2196,7 @@
 		"uri":"cce_10_0499.html",
 		"node_id":"cce_10_0499.xml",
 		"product_code":"cce",
-		"code":"121",
+		"code":"122",
 		"des":"Check whether user paas is allowed to log in to a node.Run the following command to check whether user paas is allowed to log in to a node:If the permissions assigned to ",
 		"doc_type":"usermanual2",
 		"kw":"Login Permissions of User paas on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2196,7 +2214,7 @@
 		"uri":"cce_10_0500.html",
 		"node_id":"cce_10_0500.xml",
 		"product_code":"cce",
-		"code":"122",
+		"code":"123",
 		"des":"Check whether the load balancer associated with a Service is allocated with a private IPv4 address.Solution 1: Delete the Service that is associated with a load balancer ",
 		"doc_type":"usermanual2",
 		"kw":"Private IPv4 Addresses of Load Balancers,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2214,7 +2232,7 @@
 		"uri":"cce_10_0501.html",
 		"node_id":"cce_10_0501.xml",
 		"product_code":"cce",
-		"code":"123",
+		"code":"124",
 		"des":"Check the historical upgrade records of the cluster and confirm that the current version of the cluster meets the requirements for upgrading to the target version.Upgradi",
 		"doc_type":"usermanual2",
 		"kw":"Historical Upgrade Records,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2232,7 +2250,7 @@
 		"uri":"cce_10_0502.html",
 		"node_id":"cce_10_0502.xml",
 		"product_code":"cce",
-		"code":"124",
+		"code":"125",
 		"des":"Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.The CIDR block of the management plane has been modifi",
 		"doc_type":"usermanual2",
 		"kw":"CIDR Block of the Cluster Management Plane,Troubleshooting for Pre-upgrade Check Exceptions,User Gui",
@@ -2250,7 +2268,7 @@
 		"uri":"cce_10_0503.html",
 		"node_id":"cce_10_0503.xml",
 		"product_code":"cce",
-		"code":"125",
+		"code":"126",
 		"des":"CCE AI Suite (NVIDIA GPU) is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The driver of CCE AI Suite (NVIDIA GP",
 		"doc_type":"usermanual2",
 		"kw":"CCE AI Suite (NVIDIA GPU),Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2268,7 +2286,7 @@
 		"uri":"cce_10_0504.html",
 		"node_id":"cce_10_0504.xml",
 		"product_code":"cce",
-		"code":"126",
+		"code":"127",
 		"des":"Check whether the default system parameter settings on your nodes are modified.If the MTU value of the bond0 network on your BMS node is not the default value 1500, this ",
 		"doc_type":"usermanual2",
 		"kw":"Nodes' System Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2286,7 +2304,7 @@
 		"uri":"cce_10_0505.html",
 		"node_id":"cce_10_0505.xml",
 		"product_code":"cce",
-		"code":"127",
+		"code":"128",
 		"des":"Check whether there are residual package version data in the current cluster.A message is displayed indicating that there are residual 10.12.1.109 CRD resources in your c",
 		"doc_type":"usermanual2",
 		"kw":"Residual Package Version Data,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2304,7 +2322,7 @@
 		"uri":"cce_10_0506.html",
 		"node_id":"cce_10_0506.xml",
 		"product_code":"cce",
-		"code":"128",
+		"code":"129",
 		"des":"Check whether the commands required for the upgrade are available on the node.The cluster upgrade failure is typically caused by the lack of key node commands that are re",
 		"doc_type":"usermanual2",
 		"kw":"Node Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2322,7 +2340,7 @@
 		"uri":"cce_10_0507.html",
 		"node_id":"cce_10_0507.xml",
 		"product_code":"cce",
-		"code":"129",
+		"code":"130",
 		"des":"Check whether swap has been enabled on CCE nodes.By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of disa",
 		"doc_type":"usermanual2",
 		"kw":"Node Swap,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2340,7 +2358,7 @@
 		"uri":"cce_10_0508.html",
 		"node_id":"cce_10_0508.xml",
 		"product_code":"cce",
-		"code":"130",
+		"code":"131",
 		"des":"Check item 1: Check whether there is an Nginx Ingress route whose ingress type is not specified (kubernetes.io/ingress.class: nginx is not added to annotations) in the cl",
 		"doc_type":"usermanual2",
 		"kw":"NGINX Ingress Controller,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2358,7 +2376,7 @@
 		"uri":"cce_10_0510.html",
 		"node_id":"cce_10_0510.xml",
 		"product_code":"cce",
-		"code":"131",
+		"code":"132",
 		"des":"Check whether the service pods running on a containerd node are restarted when containerd is upgraded.containerd on your node may need to be restarted. To minimize the im",
 		"doc_type":"usermanual2",
 		"kw":"containerd Pod Restart Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2376,7 +2394,7 @@
 		"uri":"cce_10_0511.html",
 		"node_id":"cce_10_0511.xml",
 		"product_code":"cce",
-		"code":"132",
+		"code":"133",
 		"des":"Check whether the configuration of CCE AI Suite (NVIDIA GPU) in a cluster has been intrusively modified. If so, upgrading the cluster may fail.",
 		"doc_type":"usermanual2",
 		"kw":"Key CCE AI Suite (NVIDIA GPU) Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2394,7 +2412,7 @@
 		"uri":"cce_10_0512.html",
 		"node_id":"cce_10_0512.xml",
 		"product_code":"cce",
-		"code":"133",
+		"code":"134",
 		"des":"Check whether GPU service pods are rebuilt in a cluster when kubelet is restarted during the upgrade of the cluster.Upgrade the cluster when the impact on services is con",
 		"doc_type":"usermanual2",
 		"kw":"GPU Pod Rebuild Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2412,7 +2430,7 @@
 		"uri":"cce_10_0513.html",
 		"node_id":"cce_10_0513.xml",
 		"product_code":"cce",
-		"code":"134",
+		"code":"135",
 		"des":"Check whether ELB listener access control has been configured using annotations for the Services in the current cluster.If so, check whether their configurations are corr",
 		"doc_type":"usermanual2",
 		"kw":"ELB Listener Access Control,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2430,7 +2448,7 @@
 		"uri":"cce_10_0514.html",
 		"node_id":"cce_10_0514.xml",
 		"product_code":"cce",
-		"code":"135",
+		"code":"136",
 		"des":"Check whether the flavor of the master nodes in the cluster is the same as the actual flavor of these nodes.This issue is typically caused by modifications made to the ma",
 		"doc_type":"usermanual2",
 		"kw":"Master Node Flavor,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2448,7 +2466,7 @@
 		"uri":"cce_10_0515.html",
 		"node_id":"cce_10_0515.xml",
 		"product_code":"cce",
-		"code":"136",
+		"code":"137",
 		"des":"Check whether the number of available IP addresses in the cluster subnet supports rolling upgrade.Rolling upgrade is not supported if there are not enough IP addresses in",
 		"doc_type":"usermanual2",
 		"kw":"Subnet Quota of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2466,7 +2484,7 @@
 		"uri":"cce_10_0516.html",
 		"node_id":"cce_10_0516.xml",
 		"product_code":"cce",
-		"code":"137",
+		"code":"138",
 		"des":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If your node's runtime is not ",
 		"doc_type":"usermanual2",
 		"kw":"Node Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2484,7 +2502,7 @@
 		"uri":"cce_10_0517.html",
 		"node_id":"cce_10_0517.xml",
 		"product_code":"cce",
-		"code":"138",
+		"code":"139",
 		"des":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If your node pool's runtime is",
 		"doc_type":"usermanual2",
 		"kw":"Node Pool Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2502,7 +2520,7 @@
 		"uri":"cce_10_0518.html",
 		"node_id":"cce_10_0518.xml",
 		"product_code":"cce",
-		"code":"139",
+		"code":"140",
 		"des":"Check the number of images on your node. If there are more than 1000 images, it takes a long time for Docker to start, affecting the standard Docker output and functions ",
 		"doc_type":"usermanual2",
 		"kw":"Number of Node Images,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2520,7 +2538,7 @@
 		"uri":"cce_10_0520.html",
 		"node_id":"cce_10_0520.xml",
 		"product_code":"cce",
-		"code":"140",
+		"code":"141",
 		"des":"Check whether the target version supports secret encryption. If it does not, clusters that have this feature enabled cannot be upgraded to the target version.Secret encry",
 		"doc_type":"usermanual2",
 		"kw":"Compatibility Check of Secret Encryption,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2538,7 +2556,7 @@
 		"uri":"cce_10_0521.html",
 		"node_id":"cce_10_0521.xml",
 		"product_code":"cce",
-		"code":"141",
+		"code":"142",
 		"des":"Make sure that CCE AI Suite (NVIDIA GPU) and Ubuntu nodes are compatible before using them in a cluster. If the Ubuntu kernel is 5.15.0-113-generic, the driver of the GPU",
 		"doc_type":"usermanual2",
 		"kw":"Compatibility Between the Ubuntu Kernel and GPU Driver,Troubleshooting for Pre-upgrade Check Excepti",
@@ -2556,7 +2574,7 @@
 		"uri":"cce_10_0522.html",
 		"node_id":"cce_10_0522.xml",
 		"product_code":"cce",
-		"code":"142",
+		"code":"143",
 		"des":"An unfinished drainage task is detected in the cluster, which may resume after the upgrade. If this happens, running pods will be evicted, which could impact your service",
 		"doc_type":"usermanual2",
 		"kw":"Drainage Tasks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2574,7 +2592,7 @@
 		"uri":"cce_10_0523.html",
 		"node_id":"cce_10_0523.xml",
 		"product_code":"cce",
-		"code":"143",
+		"code":"144",
 		"des":"Check the number of image layers on your node. If there are more than 5000 layers, it will take a long time for Docker or containerd to start, affecting the stdout of Doc",
 		"doc_type":"usermanual2",
 		"kw":"Image Layers on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2592,7 +2610,7 @@
 		"uri":"cce_10_0524.html",
 		"node_id":"cce_10_0524.xml",
 		"product_code":"cce",
-		"code":"144",
+		"code":"145",
 		"des":"Check whether your cluster is eligible for a rolling upgrade. The result shows that the rolling upgrade is not supported.Rolling upgrades cannot be performed if the tenan",
 		"doc_type":"usermanual2",
 		"kw":"Cluster Rolling Upgrade,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2610,7 +2628,7 @@
 		"uri":"cce_10_0525.html",
 		"node_id":"cce_10_0525.xml",
 		"product_code":"cce",
-		"code":"145",
+		"code":"146",
 		"des":"Check whether the number of certificates on your node is greater than 1000. During an upgrade, certificate files will be processed in batches. An excessive number of cert",
 		"doc_type":"usermanual2",
 		"kw":"Rotation Certificates,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2628,7 +2646,7 @@
 		"uri":"cce_10_0526.html",
 		"node_id":"cce_10_0526.xml",
 		"product_code":"cce",
-		"code":"146",
+		"code":"147",
 		"des":"Check whether any modifications have been made to the listener, forwarding policy, forwarding rule, backend cloud server group, backend cloud server, or certificate confi",
 		"doc_type":"usermanual2",
 		"kw":"Ingress and ELB Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guid",
@@ -2646,7 +2664,7 @@
 		"uri":"cce_10_0527.html",
 		"node_id":"cce_10_0527.xml",
 		"product_code":"cce",
-		"code":"147",
+		"code":"148",
 		"des":"Check the network policy settings on the master nodes in your cluster. If any manual modifications have been made, they will be reset during the upgrade.Check whether net",
 		"doc_type":"usermanual2",
 		"kw":"Network Policies of Cluster Network Components,Troubleshooting for Pre-upgrade Check Exceptions,User",
@@ -2664,7 +2682,7 @@
 		"uri":"cce_10_0528.html",
 		"node_id":"cce_10_0528.xml",
 		"product_code":"cce",
-		"code":"148",
+		"code":"149",
 		"des":"Check whether the nic-max-above-warm-target value configured for the network component of the current cluster exceeds the maximum value allowed.Determine the scope of imp",
 		"doc_type":"usermanual2",
 		"kw":"Cluster and Node Pool Configurations,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2682,7 +2700,7 @@
 		"uri":"cce_10_0529.html",
 		"node_id":"cce_10_0529.xml",
 		"product_code":"cce",
-		"code":"149",
+		"code":"150",
 		"des":"Check whether the time zone of the master nodes matches the cluster's time zone. If they are different, the master nodes will be updated to match the cluster's time zone ",
 		"doc_type":"usermanual2",
 		"kw":"Time Zone of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2700,7 +2718,7 @@
 		"uri":"cce_10_0530.html",
 		"node_id":"cce_10_0530.xml",
 		"product_code":"cce",
-		"code":"150",
+		"code":"151",
 		"des":"Check whether the SNATIPRanges value has changed after the upgrade. This check is available only for CCE Turbo clusters.In a CCE Turbo cluster, the CIDR blocks in SNATIPR",
 		"doc_type":"usermanual2",
 		"kw":"SNATIPRanges,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2718,7 +2736,7 @@
 		"uri":"cce_10_0531.html",
 		"node_id":"cce_10_0531.xml",
 		"product_code":"cce",
-		"code":"151",
+		"code":"152",
 		"des":"Manual modifications to add-on configuration parameters (typically ConfigMaps), instead of modifications through the CCE console or APIs, may be overwritten after an upgr",
 		"doc_type":"usermanual2",
 		"kw":"Add-on Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
@@ -2736,7 +2754,7 @@
 		"uri":"cce_10_0183.html",
 		"node_id":"cce_10_0183.xml",
 		"product_code":"cce",
-		"code":"152",
+		"code":"153",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Nodes",
@@ -2754,7 +2772,7 @@
 		"uri":"cce_10_0180.html",
 		"node_id":"cce_10_0180.xml",
 		"product_code":"cce",
-		"code":"153",
+		"code":"154",
 		"des":"A container cluster consists of a set of worker machines, called nodes, that run containerized applications. A node can be a virtual machine (VM) or a physical machine (P",
 		"doc_type":"usermanual2",
 		"kw":"paas,user group,Node Overview,Nodes,User Guide",
@@ -2772,7 +2790,7 @@
 		"uri":"cce_10_0462.html",
 		"node_id":"cce_10_0462.xml",
 		"product_code":"cce",
-		"code":"154",
+		"code":"155",
 		"des":"Container engines, one of the most important components of Kubernetes, manage the lifecycle of images and containers. The kubelet interacts with a container runtime throu",
 		"doc_type":"usermanual2",
 		"kw":"Container Engines,Nodes,User Guide",
@@ -2790,7 +2808,7 @@
 		"uri":"cce_10_0476.html",
 		"node_id":"cce_10_0476.xml",
 		"product_code":"cce",
-		"code":"155",
+		"code":"156",
 		"des":"This section describes the mappings between released cluster versions and OS versions.",
 		"doc_type":"usermanual2",
 		"kw":"Node OSs,Nodes,User Guide",
@@ -2808,7 +2826,7 @@
 		"uri":"cce_10_0363.html",
 		"node_id":"cce_10_0363.xml",
 		"product_code":"cce",
-		"code":"156",
+		"code":"157",
 		"des":"At least one cluster has been created.A key pair has been created for identity authentication upon remote node login.The DNS configuration of a subnet where a node is loc",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Node,Nodes,User Guide",
@@ -2826,7 +2844,7 @@
 		"uri":"cce_10_0198.html",
 		"node_id":"cce_10_0198.xml",
 		"product_code":"cce",
-		"code":"157",
+		"code":"158",
 		"des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.When accepting an ECS, you can reset the ECS OS to a standard ",
 		"doc_type":"usermanual2",
 		"kw":"Accepting Nodes for Management,Nodes,User Guide",
@@ -2844,7 +2862,7 @@
 		"uri":"cce_10_0185.html",
 		"node_id":"cce_10_0185.xml",
 		"product_code":"cce",
-		"code":"158",
+		"code":"159",
 		"des":"Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node.Before you log in to a node (an ECS) using SS",
 		"doc_type":"usermanual2",
 		"kw":"Logging In to a Node,Nodes,User Guide",
@@ -2862,7 +2880,7 @@
 		"uri":"cce_10_0672.html",
 		"node_id":"cce_10_0672.xml",
 		"product_code":"cce",
-		"code":"159",
+		"code":"160",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"node labels",
@@ -2880,7 +2898,7 @@
 		"uri":"cce_10_0004.html",
 		"node_id":"cce_10_0004.xml",
 		"product_code":"cce",
-		"code":"160",
+		"code":"161",
 		"des":"You can add different labels to nodes and define different attributes for labels. By using these node labels, you can quickly understand the characteristics of each node.",
 		"doc_type":"usermanual2",
 		"kw":"node labels,Inherent Label of a Node,Managing Node Labels,Management Nodes,User Guide",
@@ -2898,7 +2916,7 @@
 		"uri":"cce_10_0352.html",
 		"node_id":"cce_10_0352.xml",
 		"product_code":"cce",
-		"code":"161",
+		"code":"162",
 		"des":"Taints enable a node to repel specific pods to prevent these pods from being scheduled to the node.On the CCE console, you can also batch manage nodes' taints.Enter the k",
 		"doc_type":"usermanual2",
 		"kw":"NoSchedule,PreferNoSchedule,NoExecute,System Taints,Managing Node Taints,Management Nodes,User Guide",
@@ -2916,7 +2934,7 @@
 		"uri":"cce_10_0003.html",
 		"node_id":"cce_10_0003.xml",
 		"product_code":"cce",
-		"code":"162",
+		"code":"163",
 		"des":"You can reset a node to modify the node configuration, such as the node OS and login mode.Resetting a node will reinstall the node OS and the Kubernetes software on the n",
 		"doc_type":"usermanual2",
 		"kw":"reset a node,Resetting a Node,Management Nodes,User Guide",
@@ -2934,7 +2952,7 @@
 		"uri":"cce_10_0338.html",
 		"node_id":"cce_10_0338.xml",
 		"product_code":"cce",
-		"code":"163",
+		"code":"164",
 		"des":"Removing a node from a cluster will re-install the node OS and clear CCE components on the node.Removing a node will not delete the server corresponding to the node. You ",
 		"doc_type":"usermanual2",
 		"kw":"Removing a Node,Management Nodes,User Guide",
@@ -2952,7 +2970,7 @@
 		"uri":"cce_10_0184.html",
 		"node_id":"cce_10_0184.xml",
 		"product_code":"cce",
-		"code":"164",
+		"code":"165",
 		"des":"Each node in a cluster is a cloud server or physical machine. After a cluster node is created, you can change the cloud server name or specifications as required. Modifyi",
 		"doc_type":"usermanual2",
 		"kw":"synchronize the ECS,Synchronizing the Data of Cloud Servers,Management Nodes,User Guide",
@@ -2970,7 +2988,7 @@
 		"uri":"cce_10_0605.html",
 		"node_id":"cce_10_0605.xml",
 		"product_code":"cce",
-		"code":"165",
+		"code":"166",
 		"des":"After you enable nodal drainage on the console, CCE configures the node to be non-schedulable and securely evicts all pods that comply with Rules for Draining Nodes on th",
 		"doc_type":"usermanual2",
 		"kw":"nodal drainage,nodal drainage,Draining a Node,Management Nodes,User Guide",
@@ -2988,7 +3006,7 @@
 		"uri":"cce_10_0186.html",
 		"node_id":"cce_10_0186.xml",
 		"product_code":"cce",
-		"code":"166",
+		"code":"167",
 		"des":"If a node is no longer needed, delete it from the node list on the CCE console if the node is billed on a pay-per-use basis. Do not manually remove nodes using kubectl de",
 		"doc_type":"usermanual2",
 		"kw":"Deleting a Node,Management Nodes,User Guide",
@@ -3006,7 +3024,7 @@
 		"uri":"cce_10_0036.html",
 		"node_id":"cce_10_0036.xml",
 		"product_code":"cce",
-		"code":"167",
+		"code":"168",
 		"des":"When a node in the cluster is stopped, all services on that node will also be stopped, and the node will no longer be available for scheduling. Check if your services wil",
 		"doc_type":"usermanual2",
 		"kw":"Stopping a Node,Management Nodes,User Guide",
@@ -3024,7 +3042,7 @@
 		"uri":"cce_10_0276.html",
 		"node_id":"cce_10_0276.xml",
 		"product_code":"cce",
-		"code":"168",
+		"code":"169",
 		"des":"In a rolling upgrade, a new node is created, existing workloads are migrated to the new node, and then the old node is deleted. Figure 1 shows the migration process.The o",
 		"doc_type":"usermanual2",
 		"kw":"Performing Rolling Upgrade for Nodes,Management Nodes,User Guide",
@@ -3042,7 +3060,7 @@
 		"uri":"cce_10_0704.html",
 		"node_id":"cce_10_0704.xml",
 		"product_code":"cce",
-		"code":"169",
+		"code":"170",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Node O&M",
@@ -3060,7 +3078,7 @@
 		"uri":"cce_10_0178.html",
 		"node_id":"cce_10_0178.xml",
 		"product_code":"cce",
-		"code":"170",
+		"code":"171",
 		"des":"Some node resources are used to run mandatory Kubernetes system components and resources to make the node as part of your cluster. Therefore, the total number of node res",
 		"doc_type":"usermanual2",
 		"kw":"total number of node resources,Node Resource Reservation Policy,Node O&M,User Guide",
@@ -3078,7 +3096,7 @@
 		"uri":"cce_10_0341.html",
 		"node_id":"cce_10_0341.xml",
 		"product_code":"cce",
-		"code":"171",
+		"code":"172",
 		"des":"This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.In clusters of a version earlier than v1.23.18-r",
 		"doc_type":"usermanual2",
 		"kw":"Data Disk Space Allocation,Container engine and container image space,container engine and container",
@@ -3096,7 +3114,7 @@
 		"uri":"cce_10_0348.html",
 		"node_id":"cce_10_0348.xml",
 		"product_code":"cce",
-		"code":"172",
+		"code":"173",
 		"des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:When creating a cluster in the VPC network model, follow the  and specify",
 		"doc_type":"usermanual2",
 		"kw":"Maximum Number of Pods on a Node,alpha.cce/fixPoolMask,maximum number of pods,Maximum Number of Pods",
@@ -3114,7 +3132,7 @@
 		"uri":"cce_10_0883.html",
 		"node_id":"cce_10_0883.xml",
 		"product_code":"cce",
-		"code":"173",
+		"code":"174",
 		"des":"To maintain the stability of nodes, CCE stores Kubernetes and container runtime components on separate data disks. Kubernetes uses the /mnt/paas/kubernetes directory, and",
 		"doc_type":"usermanual2",
 		"kw":"Differences in kubelet and Runtime Component Configurations Between CCE and the Native Community,Nod",
@@ -3132,7 +3150,7 @@
 		"uri":"cce_10_0601.html",
 		"node_id":"cce_10_0601.xml",
 		"product_code":"cce",
-		"code":"174",
+		"code":"175",
 		"des":"As of Kubernetes v1.24, dockershim has been deprecated. To maintain compatibility and ensure continued support for future Kubernetes releases, switch your node's containe",
 		"doc_type":"usermanual2",
 		"kw":"Migrating Nodes from Docker to containerd,Node O&M,User Guide",
@@ -3150,7 +3168,7 @@
 		"uri":"cce_10_0659.html",
 		"node_id":"cce_10_0659.xml",
 		"product_code":"cce",
-		"code":"175",
+		"code":"176",
 		"des":"The node fault detection function depends on the NPD add-on. The add-on instances run on nodes and monitor nodes. This section describes how to enable node fault detectio",
 		"doc_type":"usermanual2",
 		"kw":"Node Fault Detection,Check Items,Configuring Node Fault Detection Policies,Node O&M,User Guide",
@@ -3168,7 +3186,7 @@
 		"uri":"cce_bestpractice_10020.html",
 		"node_id":"cce_bestpractice_10020.xml",
 		"product_code":"cce",
-		"code":"176",
+		"code":"177",
 		"des":"When creating a node, use the pre- or -installation commands to install tools or perform security hardening on the node. This section provides guidance for you to correct",
 		"doc_type":"usermanual2",
 		"kw":"Executing the Pre- or Post-installation Commands During Node Creation,Node O&M,User Guide",
@@ -3186,7 +3204,7 @@
 		"uri":"cce_10_0035.html",
 		"node_id":"cce_10_0035.xml",
 		"product_code":"cce",
-		"code":"177",
+		"code":"178",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Node Pools",
@@ -3204,7 +3222,7 @@
 		"uri":"cce_10_0081.html",
 		"node_id":"cce_10_0081.xml",
 		"product_code":"cce",
-		"code":"178",
+		"code":"179",
 		"des":"CCE introduces node pools to help you better manage nodes in Kubernetes clusters. A node pool contains one node or a group of nodes with identical configuration in a clus",
 		"doc_type":"usermanual2",
 		"kw":"DefaultPool,DefaultPool,Deploying a Workload in a Specified Node Pool,Node Pool Overview,Node Pools,",
@@ -3222,7 +3240,7 @@
 		"uri":"cce_10_0012.html",
 		"node_id":"cce_10_0012.xml",
 		"product_code":"cce",
-		"code":"179",
+		"code":"180",
 		"des":"This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.Basic SettingsNo",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Node Pool,Node Pools,User Guide",
@@ -3240,7 +3258,7 @@
 		"uri":"cce_10_0658.html",
 		"node_id":"cce_10_0658.xml",
 		"product_code":"cce",
-		"code":"180",
+		"code":"181",
 		"des":"You can specify a specification in a node pool for scaling.The default node pool does not support scaling. Use Creating a Node to add a node.Resize: Add or reduce nodes f",
 		"doc_type":"usermanual2",
 		"kw":"Scaling a Node Pool,Node Pools,User Guide",
@@ -3258,7 +3276,7 @@
 		"uri":"cce_10_0222.html",
 		"node_id":"cce_10_0222.xml",
 		"product_code":"cce",
-		"code":"181",
+		"code":"182",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Managing a Node Pool",
@@ -3276,7 +3294,7 @@
 		"uri":"cce_10_0653.html",
 		"node_id":"cce_10_0653.xml",
 		"product_code":"cce",
-		"code":"182",
+		"code":"183",
 		"des":"Changes to the container engine, OS, or pre-/post-installation script in a node pool take effect only on new nodes. To synchronize the modification onto existing nodes, m",
 		"doc_type":"usermanual2",
 		"kw":"base size,Updating a Node Pool,Managing a Node Pool,User Guide",
@@ -3294,7 +3312,7 @@
 		"uri":"cce_10_0727.html",
 		"node_id":"cce_10_0727.xml",
 		"product_code":"cce",
-		"code":"183",
+		"code":"184",
 		"des":"Auto Scaling (AS) enables elastic scaling of nodes in a node pool based on scaling policies. Without this function, you have to manually adjust the number of nodes in a n",
 		"doc_type":"usermanual2",
 		"kw":"Updating an AS Configuration,Managing a Node Pool,User Guide",
@@ -3312,7 +3330,7 @@
 		"uri":"cce_10_0652.html",
 		"node_id":"cce_10_0652.xml",
 		"product_code":"cce",
-		"code":"184",
+		"code":"185",
 		"des":"The default node pool does not support the management operations described in this section.CCE allows you to highly customize Kubernetes parameter settings on core compon",
 		"doc_type":"usermanual2",
 		"kw":"Modifying Node Pool Configurations,Managing a Node Pool,User Guide",
@@ -3330,7 +3348,7 @@
 		"uri":"cce_10_0886.html",
 		"node_id":"cce_10_0886.xml",
 		"product_code":"cce",
-		"code":"185",
+		"code":"186",
 		"des":"If you want to add a newly created ECS to a node pool in a cluster, or remove a node from a node pool and add it to the node pool again, accept the node.When an ECS is ac",
 		"doc_type":"usermanual2",
 		"kw":"Accepting Nodes in a Node Pool,Managing a Node Pool,User Guide",
@@ -3348,7 +3366,7 @@
 		"uri":"cce_10_0655.html",
 		"node_id":"cce_10_0655.xml",
 		"product_code":"cce",
-		"code":"186",
+		"code":"187",
 		"des":"You can copy the configuration of an existing node pool on the CCE console to create new node pools.",
 		"doc_type":"usermanual2",
 		"kw":"Copying a Node Pool,Managing a Node Pool,User Guide",
@@ -3366,7 +3384,7 @@
 		"uri":"cce_10_0654.html",
 		"node_id":"cce_10_0654.xml",
 		"product_code":"cce",
-		"code":"187",
+		"code":"188",
 		"des":"After the configuration of a node pool is updated, some configurations cannot be automatically synchronized for existing nodes. You can manually synchronize configuration",
 		"doc_type":"usermanual2",
 		"kw":"Synchronizing Node Pools,Managing a Node Pool,User Guide",
@@ -3384,7 +3402,7 @@
 		"uri":"cce_10_0660.html",
 		"node_id":"cce_10_0660.xml",
 		"product_code":"cce",
-		"code":"188",
+		"code":"189",
 		"des":"After CCE releases a new OS image, if existing nodes cannot be automatically upgraded, you can manually upgrade them in batches.This section describes how to upgrade an O",
 		"doc_type":"usermanual2",
 		"kw":"Upgrading an OS,Managing a Node Pool,User Guide",
@@ -3402,7 +3420,7 @@
 		"uri":"cce_10_0656.html",
 		"node_id":"cce_10_0656.xml",
 		"product_code":"cce",
-		"code":"189",
+		"code":"190",
 		"des":"You can migrate nodes between node pools within a cluster. Table 1 lists migration scenarios.Migration scenariosMigration ScenarioMigrationOperationSource Node PoolTarget",
 		"doc_type":"usermanual2",
 		"kw":"Migrating a Node,Managing a Node Pool,User Guide",
@@ -3420,7 +3438,7 @@
 		"uri":"cce_10_0657.html",
 		"node_id":"cce_10_0657.xml",
 		"product_code":"cce",
-		"code":"190",
+		"code":"191",
 		"des":"Deleting a node pool will delete nodes in the pool. Pods on these nodes will be automatically migrated to available nodes in other node pools.Deleting a node pool will de",
 		"doc_type":"usermanual2",
 		"kw":"Deleting a Node Pool,Managing a Node Pool,User Guide",
@@ -3438,7 +3456,7 @@
 		"uri":"cce_10_0046.html",
 		"node_id":"cce_10_0046.xml",
 		"product_code":"cce",
-		"code":"191",
+		"code":"192",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Workloads",
@@ -3456,7 +3474,7 @@
 		"uri":"cce_10_0006.html",
 		"node_id":"cce_10_0006.xml",
 		"product_code":"cce",
-		"code":"192",
+		"code":"193",
 		"des":"A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is ",
 		"doc_type":"usermanual2",
 		"kw":"Deployments,StatefulSets,DaemonSets,jobs,cron jobs,Overview,Workloads,User Guide",
@@ -3474,7 +3492,7 @@
 		"uri":"cce_10_0673.html",
 		"node_id":"cce_10_0673.xml",
 		"product_code":"cce",
-		"code":"193",
+		"code":"194",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Workload",
@@ -3492,7 +3510,7 @@
 		"uri":"cce_10_0047.html",
 		"node_id":"cce_10_0047.xml",
 		"product_code":"cce",
-		"code":"194",
+		"code":"195",
 		"des":"Deployments are workloads (for example, Nginx) that do not store any data or status. You can create Deployments on the CCE console or by running kubectl commands.Before c",
 		"doc_type":"usermanual2",
 		"kw":"create a workload using kubectl,Creating a Deployment,Creating a Workload,User Guide",
@@ -3510,7 +3528,7 @@
 		"uri":"cce_10_0048.html",
 		"node_id":"cce_10_0048.xml",
 		"product_code":"cce",
-		"code":"195",
+		"code":"196",
 		"des":"StatefulSets are a type of workloads whose data or status is stored while they are running. For example, MySQL is a StatefulSet because it needs to store new data.A conta",
 		"doc_type":"usermanual2",
 		"kw":"Using kubectl,Creating a StatefulSet,Creating a Workload,User Guide",
@@ -3528,7 +3546,7 @@
 		"uri":"cce_10_0216.html",
 		"node_id":"cce_10_0216.xml",
 		"product_code":"cce",
-		"code":"196",
+		"code":"197",
 		"des":"CCE provides deployment and management capabilities for multiple types of containers and supports features of container workloads, including creation, configuration, moni",
 		"doc_type":"usermanual2",
 		"kw":"create a workload using kubectl,Creating a DaemonSet,Creating a Workload,User Guide",
@@ -3546,7 +3564,7 @@
 		"uri":"cce_10_0150.html",
 		"node_id":"cce_10_0150.xml",
 		"product_code":"cce",
-		"code":"197",
+		"code":"198",
 		"des":"Jobs are short-lived and run for a certain time to completion. They can be executed immediately after being deployed. It is completed after it exits normally (exit 0).A j",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Job,Creating a Workload,User Guide",
@@ -3564,7 +3582,7 @@
 		"uri":"cce_10_0151.html",
 		"node_id":"cce_10_0151.xml",
 		"product_code":"cce",
-		"code":"198",
+		"code":"199",
 		"des":"A CronJob runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A CronJob runs periodically at the specified time.",
 		"doc_type":"usermanual2",
 		"kw":"time synchronization,Creating a CronJob,Creating a Workload,User Guide",
@@ -3582,7 +3600,7 @@
 		"uri":"cce_10_0130.html",
 		"node_id":"cce_10_0130.xml",
 		"product_code":"cce",
-		"code":"199",
+		"code":"200",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Workload",
@@ -3600,7 +3618,7 @@
 		"uri":"cce_10_0463.html",
 		"node_id":"cce_10_0463.xml",
 		"product_code":"cce",
-		"code":"200",
+		"code":"201",
 		"des":"Compared with a common runtime, a secure runtime allows each container (pod) to run on its own micro-VM with a separate OS kernel. This ensures secure isolation at the vi",
 		"doc_type":"usermanual2",
 		"kw":"Secure Runtime and Common Runtime,Configuring a Workload,User Guide",
@@ -3618,7 +3636,7 @@
 		"uri":"cce_10_0354.html",
 		"node_id":"cce_10_0354.xml",
 		"product_code":"cce",
-		"code":"201",
+		"code":"202",
 		"des":"When creating a workload, you can configure containers to use the same time zone as the node. You can enable time zone synchronization when creating a workload.The time z",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Time Zone Synchronization,Configuring a Workload,User Guide",
@@ -3636,7 +3654,7 @@
 		"uri":"cce_10_0353.html",
 		"node_id":"cce_10_0353.xml",
 		"product_code":"cce",
-		"code":"202",
+		"code":"203",
 		"des":"When a workload is created, the container image is pulled from the image repository to the node. The image is also pulled when the workload is restarted or upgraded.By de",
 		"doc_type":"usermanual2",
 		"kw":"Configuring an Image Pull Policy,Configuring a Workload,User Guide",
@@ -3654,7 +3672,7 @@
 		"uri":"cce_10_0009.html",
 		"node_id":"cce_10_0009.xml",
 		"product_code":"cce",
-		"code":"203",
+		"code":"204",
 		"des":"CCE allows you to create workloads using images pulled from third-party image repositories.Generally, a third-party image repository can be accessed only after authentica",
 		"doc_type":"usermanual2",
 		"kw":"Using Third-Party Images,Configuring a Workload,User Guide",
@@ -3672,7 +3690,7 @@
 		"uri":"cce_10_0163.html",
 		"node_id":"cce_10_0163.xml",
 		"product_code":"cce",
-		"code":"204",
+		"code":"205",
 		"des":"CCE allows you to set resource requirements and limits, such as CPU and RAM, for added containers during workload creation. Kubernetes also allows using YAML to set requi",
 		"doc_type":"usermanual2",
 		"kw":"ephemeral storage,Configuring Container Specifications,Configuring a Workload,User Guide",
@@ -3690,7 +3708,7 @@
 		"uri":"cce_10_0105.html",
 		"node_id":"cce_10_0105.xml",
 		"product_code":"cce",
-		"code":"205",
+		"code":"206",
 		"des":"CCE provides callback functions for the lifecycle management of containerized applications. For example, if you want a container to perform a certain operation before sto",
 		"doc_type":"usermanual2",
 		"kw":"Startup Command,Post-Start,Pre-Stop,Configuring Container Lifecycle Parameters,Configuring a Workloa",
@@ -3708,7 +3726,7 @@
 		"uri":"cce_10_0112.html",
 		"node_id":"cce_10_0112.xml",
 		"product_code":"cce",
-		"code":"206",
+		"code":"207",
 		"des":"Health check regularly checks the health status of containers during container running. If the health check function is not configured, a pod cannot detect application ex",
 		"doc_type":"usermanual2",
 		"kw":"Health check,HTTP request,TCP port,CLI,Configuring Container Health Check,Configuring a Workload,Use",
@@ -3726,7 +3744,7 @@
 		"uri":"cce_10_0113.html",
 		"node_id":"cce_10_0113.xml",
 		"product_code":"cce",
-		"code":"207",
+		"code":"208",
 		"des":"An environment variable is a variable whose value can affect the way a running container will behave. You can modify environment variables even after workloads are deploy",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Environment Variables,Configuring a Workload,User Guide",
@@ -3744,7 +3762,7 @@
 		"uri":"cce_10_0397.html",
 		"node_id":"cce_10_0397.xml",
 		"product_code":"cce",
-		"code":"208",
+		"code":"209",
 		"des":"In actual applications, upgrade is a common operation. A Deployment, StatefulSet, or DaemonSet can easily support application upgrade.You can set different upgrade polici",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Workload Upgrade Policies,Configuring a Workload,User Guide",
@@ -3762,7 +3780,7 @@
 		"uri":"cce_10_0728.html",
 		"node_id":"cce_10_0728.xml",
 		"product_code":"cce",
-		"code":"209",
+		"code":"210",
 		"des":"Tolerations allow the scheduler to schedule pods to nodes with target taints. Tolerances work with node taints. Each node allows one or more taints. If no tolerance is co",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Tolerance Policies,Configuring a Workload,User Guide",
@@ -3780,7 +3798,7 @@
 		"uri":"cce_10_0386.html",
 		"node_id":"cce_10_0386.xml",
 		"product_code":"cce",
-		"code":"210",
+		"code":"211",
 		"des":"CCE allows you to add annotations to a YAML file to realize some advanced pod functions. The following table describes the annotations you can add.When you create a workl",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Labels and Annotations,Configuring a Workload,User Guide",
@@ -3798,7 +3816,7 @@
 		"uri":"cce_10_0889.html",
 		"node_id":"cce_10_0889.xml",
 		"product_code":"cce",
-		"code":"211",
+		"code":"212",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Scheduling a Workload",
@@ -3816,7 +3834,7 @@
 		"uri":"cce_10_0232.html",
 		"node_id":"cce_10_0232.xml",
 		"product_code":"cce",
-		"code":"212",
+		"code":"213",
 		"des":"Kubernetes schedules workloads based on pods. After you create a workload, the scheduler automatically assigns pods. For example, the scheduler distributes pods to nodes ",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Scheduling a Workload,User Guide",
@@ -3834,7 +3852,7 @@
 		"uri":"cce_10_0891.html",
 		"node_id":"cce_10_0891.xml",
 		"product_code":"cce",
-		"code":"213",
+		"code":"214",
 		"des":"To select a node for scheduling in Kubernetes, simply configure the nodeSelector field in the workload. This field allows you to configure the label of the desired node t",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Specified Node Scheduling (nodeSelector),Scheduling a Workload,User Guide",
@@ -3852,7 +3870,7 @@
 		"uri":"cce_10_0892.html",
 		"node_id":"cce_10_0892.xml",
 		"product_code":"cce",
-		"code":"214",
+		"code":"215",
 		"des":"Kubernetes can schedule workload pods to affinity nodes based on their labels and label values. For example, some nodes support GPU computing, and node affinity schedulin",
 		"doc_type":"usermanual2",
 		"kw":"Specify node,Specify node pool,Configuring Node Affinity Scheduling (nodeAffinity),Scheduling a Work",
@@ -3870,7 +3888,7 @@
 		"uri":"cce_10_0893.html",
 		"node_id":"cce_10_0893.xml",
 		"product_code":"cce",
-		"code":"215",
+		"code":"216",
 		"des":"Kubernetes offers workload affinity and anti-affinity scheduling, which allows for flexible scheduling of new workloads on either related or unrelated nodes. This results",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity),Schedulin",
@@ -3888,8 +3906,8 @@
 		"uri":"cce_10_00356.html",
 		"node_id":"cce_10_00356.xml",
 		"product_code":"cce",
-		"code":"216",
-		"des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.When kubectl is used in CloudShell, permissions are determined by",
+		"code":"217",
+		"des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.The example output is as follows:NAME                            ",
 		"doc_type":"usermanual2",
 		"kw":"Logging In to a Container,Workloads,User Guide",
 		"search_title":"",
@@ -3906,7 +3924,7 @@
 		"uri":"cce_10_0007.html",
 		"node_id":"cce_10_0007.xml",
 		"product_code":"cce",
-		"code":"217",
+		"code":"218",
 		"des":"After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file.Workload/Job managementOperationDescriptionMo",
 		"doc_type":"usermanual2",
 		"kw":"Managing Workloads,Workloads,User Guide",
@@ -3924,7 +3942,7 @@
 		"uri":"cce_10_0833.html",
 		"node_id":"cce_10_0833.xml",
 		"product_code":"cce",
-		"code":"218",
+		"code":"219",
 		"des":"Custom Resource Definition (CRD) is an extension of Kubernetes APIs. When default Kubernetes resources cannot meet service requirements, you can use CRDs to define new re",
 		"doc_type":"usermanual2",
 		"kw":"Managing Custom Resources,Workloads,User Guide",
@@ -3942,7 +3960,7 @@
 		"uri":"cce_10_0465.html",
 		"node_id":"cce_10_0465.xml",
 		"product_code":"cce",
-		"code":"219",
+		"code":"220",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Pod Security",
@@ -3960,7 +3978,7 @@
 		"uri":"cce_10_0275.html",
 		"node_id":"cce_10_0275.xml",
 		"product_code":"cce",
-		"code":"220",
+		"code":"221",
 		"des":"A pod security policy (PSP) is a cluster-level resource that controls sensitive security aspects of the pod specification. The PodSecurityPolicy object in Kubernetes defi",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Pod Security Policy,Pod Security,User Guide",
@@ -3978,7 +3996,7 @@
 		"uri":"cce_10_0466.html",
 		"node_id":"cce_10_0466.xml",
 		"product_code":"cce",
-		"code":"221",
+		"code":"222",
 		"des":"Before using pod security admission, understand Kubernetes Pod Security Standards. These standards define different isolation levels for pods. They let you define how you",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Pod Security Admission,Pod Security,User Guide",
@@ -3996,7 +4014,7 @@
 		"uri":"cce_10_0674.html",
 		"node_id":"cce_10_0674.xml",
 		"product_code":"cce",
-		"code":"222",
+		"code":"223",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Scheduling",
@@ -4014,7 +4032,7 @@
 		"uri":"cce_10_0702.html",
 		"node_id":"cce_10_0702.xml",
 		"product_code":"cce",
-		"code":"223",
+		"code":"224",
 		"des":"CCE supports different types of resource scheduling and task scheduling, improving application performance and overall cluster resource utilization. This section describe",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Scheduling,User Guide",
@@ -4032,7 +4050,7 @@
 		"uri":"cce_10_0551.html",
 		"node_id":"cce_10_0551.xml",
 		"product_code":"cce",
-		"code":"224",
+		"code":"225",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"CPU Scheduling",
@@ -4050,7 +4068,7 @@
 		"uri":"cce_10_0351.html",
 		"node_id":"cce_10_0351.xml",
 		"product_code":"cce",
-		"code":"225",
+		"code":"226",
 		"des":"By default, kubelet uses CFS quotas to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the",
 		"doc_type":"usermanual2",
 		"kw":"CPU Policy,CPU Scheduling,User Guide",
@@ -4068,7 +4086,7 @@
 		"uri":"cce_10_0552.html",
 		"node_id":"cce_10_0552.xml",
 		"product_code":"cce",
-		"code":"226",
+		"code":"227",
 		"des":"Kubernetes provides two CPU policies: none and static.none: The CPU policy is disabled by default, indicating the existing scheduling behavior.static: The static CPU core",
 		"doc_type":"usermanual2",
 		"kw":"Enhanced CPU Policy,CPU Scheduling,User Guide",
@@ -4086,7 +4104,7 @@
 		"uri":"cce_10_0720.html",
 		"node_id":"cce_10_0720.xml",
 		"product_code":"cce",
-		"code":"227",
+		"code":"228",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"GPU Scheduling",
@@ -4104,7 +4122,7 @@
 		"uri":"cce_10_0345.html",
 		"node_id":"cce_10_0345.xml",
 		"product_code":"cce",
-		"code":"228",
+		"code":"229",
 		"des":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The CCE AI Suite (NVIDIA GPU) add-on has been installed, with the selecte",
 		"doc_type":"usermanual2",
 		"kw":"Default GPU Scheduling in Kubernetes,GPU Scheduling,User Guide",
@@ -4122,7 +4140,7 @@
 		"uri":"cce_10_0955.html",
 		"node_id":"cce_10_0955.xml",
 		"product_code":"cce",
-		"code":"229",
+		"code":"230",
 		"des":"The CCE AI Suite (NVIDIA GPU) add-on provides GPU monitoring metrics. This add-on offers additional GPU observability options. This section describes the metrics provided",
 		"doc_type":"usermanual2",
 		"kw":"GPU Metrics,GPU Scheduling,User Guide",
@@ -4140,7 +4158,7 @@
 		"uri":"cce_10_0423.html",
 		"node_id":"cce_10_0423.xml",
 		"product_code":"cce",
-		"code":"230",
+		"code":"231",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Volcano Scheduling",
@@ -4158,7 +4176,7 @@
 		"uri":"cce_10_0721.html",
 		"node_id":"cce_10_0721.xml",
 		"product_code":"cce",
-		"code":"231",
+		"code":"232",
 		"des":"Volcano is a batch processing platform that runs on Kubernetes for machine learning, deep learning, bioinformatics, genomics, and other big data applications. It provides",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Volcano Scheduling,User Guide",
@@ -4176,7 +4194,7 @@
 		"uri":"cce_10_0722.html",
 		"node_id":"cce_10_0722.xml",
 		"product_code":"cce",
-		"code":"232",
+		"code":"233",
 		"des":"Volcano is a Kubernetes-based batch processing platform with high-performance general computing capabilities like task scheduling engine, heterogeneous chip management, a",
 		"doc_type":"usermanual2",
 		"kw":"Scheduling Workloads,Volcano Scheduling,User Guide",
@@ -4194,7 +4212,7 @@
 		"uri":"cce_10_0768.html",
 		"node_id":"cce_10_0768.xml",
 		"product_code":"cce",
-		"code":"233",
+		"code":"234",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Resource Usage-based Scheduling",
@@ -4212,7 +4230,7 @@
 		"uri":"cce_10_0773.html",
 		"node_id":"cce_10_0773.xml",
 		"product_code":"cce",
-		"code":"234",
+		"code":"235",
 		"des":"Bin packing is an optimization algorithm that aims to properly allocate resources to each job and get the jobs done using the minimum amount of resources. After bin packi",
 		"doc_type":"usermanual2",
 		"kw":"Bin Packing,Resource Usage-based Scheduling,User Guide",
@@ -4230,7 +4248,7 @@
 		"uri":"cce_10_0766.html",
 		"node_id":"cce_10_0766.xml",
 		"product_code":"cce",
-		"code":"235",
+		"code":"236",
 		"des":"Scheduling in a cluster is the process of binding pending pods to nodes, and is performed by a component called kube-scheduler or Volcano Scheduler. The scheduler uses a ",
 		"doc_type":"usermanual2",
 		"kw":"Descheduling,Resource Usage-based Scheduling,User Guide",
@@ -4248,7 +4266,7 @@
 		"uri":"cce_10_0767.html",
 		"node_id":"cce_10_0767.xml",
 		"product_code":"cce",
-		"code":"236",
+		"code":"237",
 		"des":"In scenarios such as node pool replacement and rolling node upgrade, an old resource pool needs to be replaced with a new one. To prevent the node pool replacement from a",
 		"doc_type":"usermanual2",
 		"kw":"Node Pool Affinity,Resource Usage-based Scheduling,User Guide",
@@ -4266,7 +4284,7 @@
 		"uri":"cce_10_0789.html",
 		"node_id":"cce_10_0789.xml",
 		"product_code":"cce",
-		"code":"237",
+		"code":"238",
 		"des":"Volcano Scheduler offers CPU and memory load-aware scheduling for pods and preferentially schedules pods to the node with the lightest load to balance node loads. This pr",
 		"doc_type":"usermanual2",
 		"kw":"Load-aware Scheduling,Resource Usage-based Scheduling,User Guide",
@@ -4284,7 +4302,7 @@
 		"uri":"cce_10_0813.html",
 		"node_id":"cce_10_0813.xml",
 		"product_code":"cce",
-		"code":"238",
+		"code":"239",
 		"des":"Volcano scheduling involves node filtering and scoring, which is used to filter the nodes meeting scheduling conditions and score the filtered nodes to find the one with ",
 		"doc_type":"usermanual2",
 		"kw":"Configuration Cases for Resource Usage-based Scheduling,Resource Usage-based Scheduling,User Guide",
@@ -4302,7 +4320,7 @@
 		"uri":"cce_10_0774.html",
 		"node_id":"cce_10_0774.xml",
 		"product_code":"cce",
-		"code":"239",
+		"code":"240",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Priority-based Scheduling",
@@ -4320,7 +4338,7 @@
 		"uri":"cce_10_0775.html",
 		"node_id":"cce_10_0775.xml",
 		"product_code":"cce",
-		"code":"240",
+		"code":"241",
 		"des":"A pod priority indicates the importance of a pod relative to other pods. Volcano supports pod PriorityClasses in Kubernetes. After PriorityClasses are configured, the sch",
 		"doc_type":"usermanual2",
 		"kw":"Priority-based Scheduling,Priority-based Scheduling,User Guide",
@@ -4338,7 +4356,7 @@
 		"uri":"cce_10_0776.html",
 		"node_id":"cce_10_0776.xml",
 		"product_code":"cce",
-		"code":"241",
+		"code":"242",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"AI Performance-based Scheduling",
@@ -4356,7 +4374,7 @@
 		"uri":"cce_10_0777.html",
 		"node_id":"cce_10_0777.xml",
 		"product_code":"cce",
-		"code":"242",
+		"code":"243",
 		"des":"Dominant Resource Fairness (DRF) is a scheduling algorithm based on the dominant resource of a container group. DRF scheduling can be used to enhance the service throughp",
 		"doc_type":"usermanual2",
 		"kw":"DRF,AI Performance-based Scheduling,User Guide",
@@ -4374,7 +4392,7 @@
 		"uri":"cce_10_0778.html",
 		"node_id":"cce_10_0778.xml",
 		"product_code":"cce",
-		"code":"243",
+		"code":"244",
 		"des":"Gang scheduling is a scheduling algorithm that schedules correlated processes or threads to run simultaneously on different processors. It meets the scheduling requiremen",
 		"doc_type":"usermanual2",
 		"kw":"Gang,AI Performance-based Scheduling,User Guide",
@@ -4392,7 +4410,7 @@
 		"uri":"cce_10_0425.html",
 		"node_id":"cce_10_0425.xml",
 		"product_code":"cce",
-		"code":"244",
+		"code":"245",
 		"des":"In non-uniform memory access (NUMA) architecture, a NUMA node is a fundamental component that includes a processor and local memory. These nodes are physically separate b",
 		"doc_type":"usermanual2",
 		"kw":"NUMA Affinity Scheduling,Volcano Scheduling,User Guide",
@@ -4410,7 +4428,7 @@
 		"uri":"cce_10_0709.html",
 		"node_id":"cce_10_0709.xml",
 		"product_code":"cce",
-		"code":"245",
+		"code":"246",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Hybrid Deployment",
@@ -4428,7 +4446,7 @@
 		"uri":"cce_10_0384.html",
 		"node_id":"cce_10_0384.xml",
 		"product_code":"cce",
-		"code":"246",
+		"code":"247",
 		"des":"Many services see surges in traffic. To ensure performance and stability, resources are often requested at the maximum needed. However, the surges may ebb very shortly an",
 		"doc_type":"usermanual2",
 		"kw":"Dynamic Resource Oversubscription,Cloud Native Hybrid Deployment,User Guide",
@@ -4446,7 +4464,7 @@
 		"uri":"cce_10_0020.html",
 		"node_id":"cce_10_0020.xml",
 		"product_code":"cce",
-		"code":"247",
+		"code":"248",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Network",
@@ -4464,7 +4482,7 @@
 		"uri":"cce_10_0010.html",
 		"node_id":"cce_10_0010.xml",
 		"product_code":"cce",
-		"code":"248",
+		"code":"249",
 		"des":"You can learn about a cluster network from the following two aspects:What is a cluster network like? A cluster consists of multiple nodes, and pods (or containers) are ru",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Network,User Guide",
@@ -4482,7 +4500,7 @@
 		"uri":"cce_10_0280.html",
 		"node_id":"cce_10_0280.xml",
 		"product_code":"cce",
-		"code":"249",
+		"code":"250",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Container Network",
@@ -4500,7 +4518,7 @@
 		"uri":"cce_10_0281.html",
 		"node_id":"cce_10_0281.xml",
 		"product_code":"cce",
-		"code":"250",
+		"code":"251",
 		"des":"The container network assigns IP addresses to pods in a cluster and provides networking services. In CCE, you can select the following network models for your cluster:Clo",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Container Network,User Guide",
@@ -4518,7 +4536,7 @@
 		"uri":"cce_10_0678.html",
 		"node_id":"cce_10_0678.xml",
 		"product_code":"cce",
-		"code":"251",
+		"code":"252",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Network 2.0 Settings",
@@ -4536,7 +4554,7 @@
 		"uri":"cce_10_0284.html",
 		"node_id":"cce_10_0284.xml",
 		"product_code":"cce",
-		"code":"252",
+		"code":"253",
 		"des":"Cloud Native Network 2.0 is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network interface",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Network 2.0,Cloud Native Network 2.0 Settings,User Guide",
@@ -4554,7 +4572,7 @@
 		"uri":"cce_10_0906.html",
 		"node_id":"cce_10_0906.xml",
 		"product_code":"cce",
-		"code":"253",
+		"code":"254",
 		"des":"If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.This function is avail",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Default Container Subnet for a CCE Turbo Cluster,Cloud Native Network 2.0 Settings,Use",
@@ -4572,7 +4590,7 @@
 		"uri":"cce_10_0897.html",
 		"node_id":"cce_10_0897.xml",
 		"product_code":"cce",
-		"code":"254",
+		"code":"255",
 		"des":"In Cloud Native Network 2.0, pods use ENIs or sub-ENIs of the VPC. You can configure a security group for a pod using a pod's annotation.Configure a security group in eit",
 		"doc_type":"usermanual2",
 		"kw":"Binding a Security Group to a Pod Using an Annotation,Cloud Native Network 2.0 Settings,User Guide",
@@ -4590,7 +4608,7 @@
 		"uri":"cce_10_0288.html",
 		"node_id":"cce_10_0288.xml",
 		"product_code":"cce",
-		"code":"255",
+		"code":"256",
 		"des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind security groups and EIPs to pods. To bind CCE pods with security groups, ",
 		"doc_type":"usermanual2",
 		"kw":"Binding a Security Group to a Workload Using a Security Group Policy,Cloud Native Network 2.0 Settin",
@@ -4608,7 +4626,7 @@
 		"uri":"cce_10_0196.html",
 		"node_id":"cce_10_0196.xml",
 		"product_code":"cce",
-		"code":"256",
+		"code":"257",
 		"des":"In a CCE Turbo cluster, you can configure subnets and security groups for containers by namespace or workload using NetworkAttachmentDefinition CRDs. To configure a parti",
 		"doc_type":"usermanual2",
 		"kw":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configurati",
@@ -4626,7 +4644,7 @@
 		"uri":"cce_10_0603.html",
 		"node_id":"cce_10_0603.xml",
 		"product_code":"cce",
-		"code":"257",
+		"code":"258",
 		"des":"In Cloud Native Network 2.0, each pod is associated with an ENI, providing a static IP address to the StatefulSet pods (container ENI). This is a common practice in acces",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Static IP Address for a Pod,Cloud Native Network 2.0 Settings,User Guide",
@@ -4644,7 +4662,7 @@
 		"uri":"cce_10_0734.html",
 		"node_id":"cce_10_0734.xml",
 		"product_code":"cce",
-		"code":"258",
+		"code":"259",
 		"des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind EIPs to pods.To associate an EIP with a pod, simply set the value of the ",
 		"doc_type":"usermanual2",
 		"kw":"Configuring an EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide",
@@ -4662,7 +4680,7 @@
 		"uri":"cce_10_0651.html",
 		"node_id":"cce_10_0651.xml",
 		"product_code":"cce",
-		"code":"259",
+		"code":"260",
 		"des":"In Cloud Native Network 2.0, static public IP addresses (EIPs) can be assigned to StatefulSets or pods created directly.You can configure a static EIP for a pod only in C",
 		"doc_type":"usermanual2",
 		"kw":"static EIPs,Configuring a Static EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide",
@@ -4680,7 +4698,7 @@
 		"uri":"cce_10_0604.html",
 		"node_id":"cce_10_0604.xml",
 		"product_code":"cce",
-		"code":"260",
+		"code":"261",
 		"des":"By default, pods with IPv6 dual-stack ENIs can access only the IPv6 private network. To access the public network, configure shared bandwidth for such pods.Only CCE Turbo",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs,Cloud Native Network 2.0 Settings,U",
@@ -4698,7 +4716,7 @@
 		"uri":"cce_10_0904.html",
 		"node_id":"cce_10_0904.xml",
 		"product_code":"cce",
-		"code":"261",
+		"code":"262",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"VPC Network Settings",
@@ -4716,7 +4734,7 @@
 		"uri":"cce_10_0283.html",
 		"node_id":"cce_10_0283.xml",
 		"product_code":"cce",
-		"code":"262",
+		"code":"263",
 		"des":"The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes al",
 		"doc_type":"usermanual2",
 		"kw":"VPC Network Model,VPC Network Settings,User Guide",
@@ -4734,7 +4752,7 @@
 		"uri":"cce_10_0680.html",
 		"node_id":"cce_10_0680.xml",
 		"product_code":"cce",
-		"code":"263",
+		"code":"264",
 		"des":"If the container CIDR block configured during CCE cluster creation cannot meet service expansion requirements, you can add a container CIDR block for the cluster.This fun",
 		"doc_type":"usermanual2",
 		"kw":"Adding a Container CIDR Block for a Cluster,VPC Network Settings,User Guide",
@@ -4752,7 +4770,7 @@
 		"uri":"cce_10_0677.html",
 		"node_id":"cce_10_0677.xml",
 		"product_code":"cce",
-		"code":"264",
+		"code":"265",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Tunnel Network Settings",
@@ -4770,7 +4788,7 @@
 		"uri":"cce_10_0282.html",
 		"node_id":"cce_10_0282.xml",
 		"product_code":"cce",
-		"code":"265",
+		"code":"266",
 		"des":"A container tunnel network creates a separate network plane for containers by using tunnel encapsulation on the host network plane. The container tunnel network of a CCE ",
 		"doc_type":"usermanual2",
 		"kw":"Tunnel Network Model,Tunnel Network Settings,User Guide",
@@ -4788,7 +4806,7 @@
 		"uri":"cce_10_0675.html",
 		"node_id":"cce_10_0675.xml",
 		"product_code":"cce",
-		"code":"266",
+		"code":"267",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Pod Network Settings",
@@ -4806,7 +4824,7 @@
 		"uri":"cce_10_0402.html",
 		"node_id":"cce_10_0402.xml",
 		"product_code":"cce",
-		"code":"267",
+		"code":"268",
 		"des":"Kubernetes allows pods to directly use the host/node network. When a pod is configured with hostNetwork: true, applications running in the pod can directly view the netwo",
 		"doc_type":"usermanual2",
 		"kw":"Configuring hostNetwork for Pods,Pod Network Settings,User Guide",
@@ -4824,7 +4842,7 @@
 		"uri":"cce_10_0382.html",
 		"node_id":"cce_10_0382.xml",
 		"product_code":"cce",
-		"code":"268",
+		"code":"269",
 		"des":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure bandwidth limitation for the pod to ",
 		"doc_type":"usermanual2",
 		"kw":"Configuring QoS for a Pod,Pod Network Settings,User Guide",
@@ -4842,7 +4860,7 @@
 		"uri":"cce_10_0059.html",
 		"node_id":"cce_10_0059.xml",
 		"product_code":"cce",
-		"code":"269",
+		"code":"270",
 		"des":"Network policies are designed by Kubernetes to restrict pod access. It is equivalent to a firewall at the application layer to enhance network security. The capabilities ",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Network Policies to Restrict Pod Access,Pod Network Settings,User Guide",
@@ -4860,7 +4878,7 @@
 		"uri":"cce_10_0945.html",
 		"node_id":"cce_10_0945.xml",
 		"product_code":"cce",
-		"code":"270",
+		"code":"271",
 		"des":"DataPlane V2 can be enabled for clusters that use Cloud Native 2.0 networks. After this function is enabled, eBPF redirection will be enabled for the capability of networ",
 		"doc_type":"usermanual2",
 		"kw":"DataPlane V2 Network Acceleration,Pod Network Settings,User Guide",
@@ -4878,7 +4896,7 @@
 		"uri":"cce_10_0247.html",
 		"node_id":"cce_10_0247.xml",
 		"product_code":"cce",
-		"code":"271",
+		"code":"272",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Service",
@@ -4896,8 +4914,8 @@
 		"uri":"cce_10_0249.html",
 		"node_id":"cce_10_0249.xml",
 		"product_code":"cce",
-		"code":"272",
-		"des":"After a pod is created, the following problems may occur if you directly access the pod:The pod can be deleted and recreated at any time by a controller such as a Deploym",
+		"code":"273",
+		"des":"After a pod is created, accessing it directly can result in certain problems:The pod can be deleted and recreated at any time by a controller such as a Deployment. If the",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Service,User Guide",
 		"search_title":"",
@@ -4914,7 +4932,7 @@
 		"uri":"cce_10_0011.html",
 		"node_id":"cce_10_0011.xml",
 		"product_code":"cce",
-		"code":"273",
+		"code":"274",
 		"des":"ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.The cluster-internal domain name format is <Service",
 		"doc_type":"usermanual2",
 		"kw":"ClusterIP,Service,User Guide",
@@ -4932,7 +4950,7 @@
 		"uri":"cce_10_0142.html",
 		"node_id":"cce_10_0142.xml",
 		"product_code":"cce",
-		"code":"274",
+		"code":"275",
 		"des":"A Service is exposed on each node's IP address at a static port (NodePort). When you create a NodePort Service, Kubernetes automatically allocates an internal IP address ",
 		"doc_type":"usermanual2",
 		"kw":"NodePort,Service,User Guide",
@@ -4950,7 +4968,7 @@
 		"uri":"cce_10_0014.html",
 		"node_id":"cce_10_0014.xml",
 		"product_code":"cce",
-		"code":"275",
+		"code":"276",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"LoadBalancer",
@@ -4968,7 +4986,7 @@
 		"uri":"cce_10_0681.html",
 		"node_id":"cce_10_0681.xml",
 		"product_code":"cce",
-		"code":"276",
+		"code":"277",
 		"des":"LoadBalancer Services can access workloads from the public network through a load balancer, which is more reliable than EIP-based access. The LoadBalancer access address ",
 		"doc_type":"usermanual2",
 		"kw":"Creating a LoadBalancer Service,LoadBalancer,User Guide",
@@ -4986,7 +5004,7 @@
 		"uri":"cce_10_0385.html",
 		"node_id":"cce_10_0385.xml",
 		"product_code":"cce",
-		"code":"277",
+		"code":"278",
 		"des":"You can add annotations to a YAML file to use some CCE advanced functions. This section describes the available annotations when a LoadBalancer service is created.Interco",
 		"doc_type":"usermanual2",
 		"kw":"Configuring LoadBalancer Services Using Annotations,LoadBalancer,User Guide",
@@ -5004,7 +5022,7 @@
 		"uri":"cce_10_0683.html",
 		"node_id":"cce_10_0683.xml",
 		"product_code":"cce",
-		"code":"278",
+		"code":"279",
 		"des":"Only clusters of v1.19.16 or later support HTTP or HTTPS.Scenarios where a load balancer supports HTTP or HTTPSELB TypeApplicationWhether to Support HTTP or HTTPSDescript",
 		"doc_type":"usermanual2",
 		"kw":"Configuring HTTP/HTTPS for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5022,7 +5040,7 @@
 		"uri":"cce_10_0841.html",
 		"node_id":"cce_10_0841.xml",
 		"product_code":"cce",
-		"code":"279",
+		"code":"280",
 		"des":"An SNI certificate is an extended server certificate that allows the same IP address and port number to provide multiple access domain names for external systems. Differe",
 		"doc_type":"usermanual2",
 		"kw":"SNI,Configuring SNI for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5040,7 +5058,7 @@
 		"uri":"cce_10_0842.html",
 		"node_id":"cce_10_0842.xml",
 		"product_code":"cce",
-		"code":"280",
+		"code":"281",
 		"des":"Services can be exposed via HTTP/2. By default, HTTP/1.x is used between clients and load balancers. HTTP/2 can improve access performance between clients and load balanc",
 		"doc_type":"usermanual2",
 		"kw":"HTTP/2,Configuring HTTP/2 for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5058,7 +5076,7 @@
 		"uri":"cce_10_0729.html",
 		"node_id":"cce_10_0729.xml",
 		"product_code":"cce",
-		"code":"281",
+		"code":"282",
 		"des":"LoadBalancer Services allow you to configure timeout, which is the maximum duration for keeping a connection if no request is received from the client. If no request is r",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Timeout for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5076,7 +5094,7 @@
 		"uri":"cce_10_0831.html",
 		"node_id":"cce_10_0831.xml",
 		"product_code":"cce",
-		"code":"282",
+		"code":"283",
 		"des":"When using a LoadBalancer Service, you can configure a trustlist or blocklist to specify the IP addresses that are allowed or denied accessing a load balancer listener.Tr",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5094,7 +5112,7 @@
 		"uri":"cce_10_0684.html",
 		"node_id":"cce_10_0684.xml",
 		"product_code":"cce",
-		"code":"283",
+		"code":"284",
 		"des":"The health check annotation field of LoadBalancer Services has been upgraded from kubernetes.io/elb.health-check-option to kubernetes.io/elb.health-check-options. You can",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Health Check on Multiple LoadBalancer Service Ports,LoadBalancer,User Guide",
@@ -5112,7 +5130,7 @@
 		"uri":"cce_10_0355.html",
 		"node_id":"cce_10_0355.xml",
 		"product_code":"cce",
-		"code":"284",
+		"code":"285",
 		"des":"kube-proxy, which is responsible for forwarding intra-cluster traffic, adds the IP addresses of load balancers associated with the LoadBalancer Services to nodes' local f",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Passthrough Networking for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5130,7 +5148,7 @@
 		"uri":"cce_10_0916.html",
 		"node_id":"cce_10_0916.xml",
 		"product_code":"cce",
-		"code":"285",
+		"code":"286",
 		"des":"When creating a LoadBalancer Service using a shared load balancer, you can configure annotations for the load balancer listeners to obtain the client IP address.If a dedi",
 		"doc_type":"usermanual2",
 		"kw":"Enabling a LoadBalancer Service to Obtain the Client IP Address,LoadBalancer,User Guide",
@@ -5148,7 +5166,7 @@
 		"uri":"cce_10_0924.html",
 		"node_id":"cce_10_0924.xml",
 		"product_code":"cce",
-		"code":"286",
+		"code":"287",
 		"des":"You can customize the EIP bound to a load balancer that is automatically created by CCE by adding the kubernetes.io/elb.custom-eip-id annotation to a Service.A Kubernetes",
 		"doc_type":"usermanual2",
 		"kw":"Changing a Custom EIP for a LoadBalancer Service,LoadBalancer,User Guide",
@@ -5166,7 +5184,7 @@
 		"uri":"cce_10_0685.html",
 		"node_id":"cce_10_0685.xml",
 		"product_code":"cce",
-		"code":"287",
+		"code":"288",
 		"des":"The ready status of the pod is associated with the ELB health check. After the health check is successful, the pod is ready. This association works with the strategy.roll",
 		"doc_type":"usermanual2",
 		"kw":"readinessGates,Setting the Pod Ready Status Through the ELB Health Check,LoadBalancer,User Guide",
@@ -5184,7 +5202,7 @@
 		"uri":"cce_10_0084.html",
 		"node_id":"cce_10_0084.xml",
 		"product_code":"cce",
-		"code":"288",
+		"code":"289",
 		"des":"If a workload uses UDP for both load balancing and health check, enable ICMP security group rules for the backend servers.",
 		"doc_type":"usermanual2",
 		"kw":"Enabling ICMP Security Group Rules,LoadBalancer,User Guide",
@@ -5202,7 +5220,7 @@
 		"uri":"cce_10_0398.html",
 		"node_id":"cce_10_0398.xml",
 		"product_code":"cce",
-		"code":"289",
+		"code":"290",
 		"des":"Services allow internal and external pod access, but not the following scenarios:Accessing all pods at the same timePods in a Service accessing each otherThis is where he",
 		"doc_type":"usermanual2",
 		"kw":"Headless Services,Service,User Guide",
@@ -5220,7 +5238,7 @@
 		"uri":"cce_10_0248.html",
 		"node_id":"cce_10_0248.xml",
 		"product_code":"cce",
-		"code":"290",
+		"code":"291",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Ingresses",
@@ -5238,7 +5256,7 @@
 		"uri":"cce_10_0094.html",
 		"node_id":"cce_10_0094.xml",
 		"product_code":"cce",
-		"code":"291",
+		"code":"292",
 		"des":"A Service is generally used to forward access requests based on TCP and UDP and provide layer-4 load balancing for clusters. However, in actual scenarios, if there is a l",
 		"doc_type":"usermanual2",
 		"kw":"routing traffic,Overview,Ingresses,User Guide",
@@ -5256,7 +5274,7 @@
 		"uri":"cce_10_0686.html",
 		"node_id":"cce_10_0686.xml",
 		"product_code":"cce",
-		"code":"292",
+		"code":"293",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"LoadBalancer Ingresses",
@@ -5274,7 +5292,7 @@
 		"uri":"cce_10_0251.html",
 		"node_id":"cce_10_0251.xml",
 		"product_code":"cce",
-		"code":"293",
+		"code":"294",
 		"des":"In Kubernetes, an ingress is a resource object that controls how Services within a cluster can be accessed from outside the cluster. You can use ingresses to configure di",
 		"doc_type":"usermanual2",
 		"kw":"LoadBalancer ingress,Creating a LoadBalancer Ingress on the Console,LoadBalancer Ingresses,User Guid",
@@ -5292,7 +5310,7 @@
 		"uri":"cce_10_0252.html",
 		"node_id":"cce_10_0252.xml",
 		"product_code":"cce",
-		"code":"294",
+		"code":"295",
 		"des":"This section uses an Nginx workload as an example to describe how to create a LoadBalancer ingress using kubectl.If no load balancer is available in the same VPC, CCE can",
 		"doc_type":"usermanual2",
 		"kw":"Creating a LoadBalancer Ingress Using kubectl,LoadBalancer Ingresses,User Guide",
@@ -5310,7 +5328,7 @@
 		"uri":"cce_10_0695.html",
 		"node_id":"cce_10_0695.xml",
 		"product_code":"cce",
-		"code":"295",
+		"code":"296",
 		"des":"You can add annotations to a YAML file for more advanced ingress functions. This section describes the annotations that can be used when you create a LoadBalancer ingress",
 		"doc_type":"usermanual2",
 		"kw":"Annotations for Configuring LoadBalancer Ingresses,LoadBalancer Ingresses,User Guide",
@@ -5328,7 +5346,7 @@
 		"uri":"cce_10_0935.html",
 		"node_id":"cce_10_0935.xml",
 		"product_code":"cce",
-		"code":"296",
+		"code":"297",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Advanced Setting Examples of LoadBalancer Ingresses",
@@ -5346,7 +5364,7 @@
 		"uri":"cce_10_0687.html",
 		"node_id":"cce_10_0687.xml",
 		"product_code":"cce",
-		"code":"297",
+		"code":"298",
 		"des":"Ingresses support SSL or TLS certificates, allowing you to secure your Services with HTTPS.You are allowed to use either of the following ways to configure an ingress cer",
 		"doc_type":"usermanual2",
 		"kw":"kubernetes.io/tls,IngressTLS,IngressTLS,kubernetes.io/tls,Configuring an HTTPS Certificate for a Loa",
@@ -5364,7 +5382,7 @@
 		"uri":"cce_10_0930.html",
 		"node_id":"cce_10_0930.xml",
 		"product_code":"cce",
-		"code":"298",
+		"code":"299",
 		"des":"If the HTTPS certificate for a LoadBalancer ingress is about to expire or has expired, follow the operations provided in this section to update it.",
 		"doc_type":"usermanual2",
 		"kw":"Updating the HTTPS Certificate for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer ",
@@ -5382,7 +5400,7 @@
 		"uri":"cce_10_0688.html",
 		"node_id":"cce_10_0688.xml",
 		"product_code":"cce",
-		"code":"299",
+		"code":"300",
 		"des":"An SNI certificate is an extended server certificate that allows the same IP address and port number to provide multiple access domain names for external systems. Differe",
 		"doc_type":"usermanual2",
 		"kw":"SNI,kubernetes.io/tls,IngressTLS,Configuring SNI for a LoadBalancer Ingress,Advanced Setting Example",
@@ -5400,7 +5418,7 @@
 		"uri":"cce_10_0689.html",
 		"node_id":"cce_10_0689.xml",
 		"product_code":"cce",
-		"code":"300",
+		"code":"301",
 		"des":"An ingress can route requests to multiple backend Services based on different matching policies. For example, requests can be routed to three different backend Services s",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Multiple Forwarding Policies for a LoadBalancer Ingress,Advanced Setting Examples of Loa",
@@ -5418,7 +5436,7 @@
 		"uri":"cce_10_0694.html",
 		"node_id":"cce_10_0694.xml",
 		"product_code":"cce",
-		"code":"301",
+		"code":"302",
 		"des":"Ingresses can use HTTP/2 to expose Services. Connections from the load balancer to your application use HTTP/1.x by default. If your application is capable of receiving H",
 		"doc_type":"usermanual2",
 		"kw":"HTTP/2,Configuring HTTP/2 for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingre",
@@ -5436,7 +5454,7 @@
 		"uri":"cce_10_0691.html",
 		"node_id":"cce_10_0691.xml",
 		"product_code":"cce",
-		"code":"302",
+		"code":"303",
 		"des":"Ingresses can interconnect with backend services of different protocols. By default, the backend proxy channel of an ingress is HTTP-compliant. To create an HTTPS channel",
 		"doc_type":"usermanual2",
 		"kw":"Configuring HTTPS Backend Services for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalan",
@@ -5454,7 +5472,7 @@
 		"uri":"cce_10_0730.html",
 		"node_id":"cce_10_0730.xml",
 		"product_code":"cce",
-		"code":"303",
+		"code":"304",
 		"des":"LoadBalancer ingresses support the following timeout settings:Idle timeout setting for client connections: maximum duration for keeping a connection when no client reques",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Timeout for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingresses,U",
@@ -5472,7 +5490,7 @@
 		"uri":"cce_10_0735.html",
 		"node_id":"cce_10_0735.xml",
 		"product_code":"cce",
-		"code":"304",
+		"code":"305",
 		"des":"With slow start configured, a load balancer linearly increases the proportion of requests to backend server pods. When the slow start duration elapses, the load balancer ",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Slow Start for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingres",
@@ -5490,7 +5508,7 @@
 		"uri":"cce_10_0832.html",
 		"node_id":"cce_10_0832.xml",
 		"product_code":"cce",
-		"code":"305",
+		"code":"306",
 		"des":"You can add IP addresses to a trustlist or blocklist to control access to a listener of a LoadBalancer ingress.Trustlist: Only the IP addresses in the list can access the",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Ingress,Advanced Setting Examples",
@@ -5508,7 +5526,7 @@
 		"uri":"cce_10_0937.html",
 		"node_id":"cce_10_0937.xml",
 		"product_code":"cce",
-		"code":"306",
+		"code":"307",
 		"des":"Ingress allows you to customize listening ports. You can configure both HTTP and HTTPS listeners for a Service. For example, a Service can make available both HTTP port 8",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Range of Listening Ports for a LoadBalancer Ingress,Advanced Setting Examples of LoadB",
@@ -5526,7 +5544,7 @@
 		"uri":"cce_10_0939.html",
 		"node_id":"cce_10_0939.xml",
 		"product_code":"cce",
-		"code":"307",
+		"code":"308",
 		"des":"When ingresses use the same load balancer listener, forwarding rules can be prioritized based on the following rules:Forwarding rules of different ingresses: The rules ar",
 		"doc_type":"usermanual2",
 		"kw":"Configuring the Priorities of Forwarding Rules for LoadBalancer Ingresses,Advanced Setting Examples ",
@@ -5544,7 +5562,7 @@
 		"uri":"cce_10_0896.html",
 		"node_id":"cce_10_0896.xml",
 		"product_code":"cce",
-		"code":"308",
+		"code":"309",
 		"des":"Dedicated load balancer ingresses support custom header forwarding policies. You can configure different header key-value pairs to determine the backend Service to which ",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Custom Header Forwarding Policy for a LoadBalancer Ingress,Advanced Setting Examples o",
@@ -5562,7 +5580,7 @@
 		"uri":"cce_10_0925.html",
 		"node_id":"cce_10_0925.xml",
 		"product_code":"cce",
-		"code":"309",
+		"code":"310",
 		"des":"You can customize the EIP bound to a load balancer that is automatically created by CCE by adding the kubernetes.io/elb.custom-eip-id annotation to an ingress.A CCE stand",
 		"doc_type":"usermanual2",
 		"kw":"Configuring a Custom EIP for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingres",
@@ -5580,7 +5598,7 @@
 		"uri":"cce_10_0940.html",
 		"node_id":"cce_10_0940.xml",
 		"product_code":"cce",
-		"code":"310",
+		"code":"311",
 		"des":"Ingresses offer diverse forwarding rules that can match listeners based on different request parameters like HTTP request methods, headers, query strings, CIDR blocks, an",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Advanced Forwarding Rules for a LoadBalancer Ingress,Advanced Setting Examples of LoadBa",
@@ -5598,7 +5616,7 @@
 		"uri":"cce_10_0949.html",
 		"node_id":"cce_10_0949.xml",
 		"product_code":"cce",
-		"code":"311",
+		"code":"312",
 		"des":"Dedicated load balancers offer different forwarding actions to effectively distribute traffic. ELB directs client requests to backend servers based on the specified forwa",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Advanced Forwarding Actions for a LoadBalancer Ingress,Advanced Setting Examples of Load",
@@ -5616,7 +5634,7 @@
 		"uri":"cce_10_0950.html",
 		"node_id":"cce_10_0950.xml",
 		"product_code":"cce",
-		"code":"312",
+		"code":"313",
 		"des":"CCE sets up forwarding policies on the ELB console based on the rules specified in the ingress configurations when creating LoadBalancer ingresses.To handle more complex ",
 		"doc_type":"usermanual2",
 		"kw":"Forwarding Policy Priorities of LoadBalancer Ingresses,LoadBalancer Ingresses,User Guide",
@@ -5634,7 +5652,7 @@
 		"uri":"cce_10_0954.html",
 		"node_id":"cce_10_0954.xml",
 		"product_code":"cce",
-		"code":"313",
+		"code":"314",
 		"des":"In a cluster, multiple ingresses can share a listener, allowing them to use the same port on a single load balancer. If two ingresses have different listener configuratio",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Multiple Ingresses to Use the Same External ELB Port,LoadBalancer Ingresses,User Guide",
@@ -5652,7 +5670,7 @@
 		"uri":"cce_10_0692.html",
 		"node_id":"cce_10_0692.xml",
 		"product_code":"cce",
-		"code":"314",
+		"code":"315",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Nginx Ingresses",
@@ -5670,7 +5688,7 @@
 		"uri":"cce_10_0390.html",
 		"node_id":"cce_10_0390.xml",
 		"product_code":"cce",
-		"code":"315",
+		"code":"316",
 		"des":"In Kubernetes, an ingress is a resource object that controls how Services within a cluster can be accessed from outside the cluster. You can use ingresses to configure di",
 		"doc_type":"usermanual2",
 		"kw":"Nginx ingress,Creating an Nginx Ingress on the Console,Nginx Ingresses,User Guide",
@@ -5688,7 +5706,7 @@
 		"uri":"cce_10_0364.html",
 		"node_id":"cce_10_0364.xml",
 		"product_code":"cce",
-		"code":"316",
+		"code":"317",
 		"des":"This section uses an Nginx workload as an example to describe how to create an Nginx ingress using kubectl.In CCE clusters of v1.23 or later, the ingress version is switc",
 		"doc_type":"usermanual2",
 		"kw":"Creating an Nginx Ingress Using kubectl,Nginx Ingresses,User Guide",
@@ -5706,7 +5724,7 @@
 		"uri":"cce_10_0699.html",
 		"node_id":"cce_10_0699.xml",
 		"product_code":"cce",
-		"code":"317",
+		"code":"318",
 		"des":"The nginx-ingress add-on in CCE uses the community chart and image. If the default add-on parameters cannot meet your demands, you can add annotations to define what you ",
 		"doc_type":"usermanual2",
 		"kw":"Annotations for Configuring Nginx Ingresses,Nginx Ingresses,User Guide",
@@ -5724,7 +5742,7 @@
 		"uri":"cce_10_0936.html",
 		"node_id":"cce_10_0936.xml",
 		"product_code":"cce",
-		"code":"318",
+		"code":"319",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Advanced Setting Examples of Nginx Ingresses",
@@ -5742,7 +5760,7 @@
 		"uri":"cce_10_0693.html",
 		"node_id":"cce_10_0693.xml",
 		"product_code":"cce",
-		"code":"319",
+		"code":"320",
 		"des":"HTTPS certificates can be configured for ingresses to provide security services.Create a YAML file named ingress-test-secret.yaml. The file name can be customized.The YAM",
 		"doc_type":"usermanual2",
 		"kw":"kubernetes.io/tls,IngressTLS,IngressTLS,kubernetes.io/tls,Configuring an HTTPS Certificate for an Ng",
@@ -5760,7 +5778,7 @@
 		"uri":"cce_10_0697.html",
 		"node_id":"cce_10_0697.xml",
 		"product_code":"cce",
-		"code":"320",
+		"code":"321",
 		"des":"Ingress can function as a proxy for backend services using different protocols. By default, the backend proxy channel of an ingress is an HTTP channel. To create an HTTPS",
 		"doc_type":"usermanual2",
 		"kw":"Configuring HTTPS Backend Services for an Nginx Ingress,Advanced Setting Examples of Nginx Ingresses",
@@ -5778,7 +5796,7 @@
 		"uri":"cce_10_0698.html",
 		"node_id":"cce_10_0698.xml",
 		"product_code":"cce",
-		"code":"321",
+		"code":"322",
 		"des":"The native Nginx supports multiple load balancing rules, including weighted round robin and IP hash. Nginx Ingress supports load balancing by using consistent hashing bas",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Consistent Hashing for Load Balancing of an Nginx Ingress,Advanced Setting Examples of N",
@@ -5796,7 +5814,7 @@
 		"uri":"cce_10_0919.html",
 		"node_id":"cce_10_0919.xml",
 		"product_code":"cce",
-		"code":"322",
+		"code":"323",
 		"des":"Ingress objects provide Layer 7 protocols like HTTP and HTTPS for clusters. Among the available options, Nginx ingresses are widely used. CCE has developed a featured ope",
 		"doc_type":"usermanual2",
 		"kw":"Optimizing NGINX Ingress Controller in High-Traffic Scenarios,Advanced Setting Examples of Nginx Ing",
@@ -5814,7 +5832,7 @@
 		"uri":"cce_10_0947.html",
 		"node_id":"cce_10_0947.xml",
 		"product_code":"cce",
-		"code":"323",
+		"code":"324",
 		"des":"CCE provides the following options for configuring ingress certificates for the Nginx Ingress Controller add-on:Secret certificate. Import the required certificate to a C",
 		"doc_type":"usermanual2",
 		"kw":"Configuring an ELB Certificate for NGINX Ingress Controller,Advanced Setting Examples of Nginx Ingre",
@@ -5832,7 +5850,7 @@
 		"uri":"cce_10_0968.html",
 		"node_id":"cce_10_0968.xml",
 		"product_code":"cce",
-		"code":"324",
+		"code":"325",
 		"des":"CCE NGINX Ingress Controller is based on the community version of Ingress NGINX Controller. Upgrades to the community version may introduce new features, optimize existin",
 		"doc_type":"usermanual2",
 		"kw":"NGINX Ingress Controller Upgrade Compatibility,Nginx Ingresses,User Guide",
@@ -5850,7 +5868,7 @@
 		"uri":"cce_10_0359.html",
 		"node_id":"cce_10_0359.xml",
 		"product_code":"cce",
-		"code":"325",
+		"code":"326",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"DNS",
@@ -5868,7 +5886,7 @@
 		"uri":"cce_10_0360.html",
 		"node_id":"cce_10_0360.xml",
 		"product_code":"cce",
-		"code":"326",
+		"code":"327",
 		"des":"When you create a cluster, the CoreDNS add-on is installed to resolve domain names in the cluster.You can view the pod of the CoreDNS add-on in the kube-system namespace.",
 		"doc_type":"usermanual2",
 		"kw":"Overview,DNS,User Guide",
@@ -5886,7 +5904,7 @@
 		"uri":"cce_10_0365.html",
 		"node_id":"cce_10_0365.xml",
 		"product_code":"cce",
-		"code":"327",
+		"code":"328",
 		"des":"Every Kubernetes cluster has a built-in DNS add-on (Kube-DNS or CoreDNS) to provide domain name resolution for workloads in the cluster. When handling a high concurrency ",
 		"doc_type":"usermanual2",
 		"kw":"DNS Configuration,DNS,User Guide",
@@ -5904,7 +5922,7 @@
 		"uri":"cce_10_0361.html",
 		"node_id":"cce_10_0361.xml",
 		"product_code":"cce",
-		"code":"328",
+		"code":"329",
 		"des":"When using CCE, you may need to resolve custom internal domain names in the following scenarios:In the legacy code, a fixed domain name is configured for calling other in",
 		"doc_type":"usermanual2",
 		"kw":"Using CoreDNS for Custom Domain Name Resolution,DNS,User Guide",
@@ -5922,7 +5940,7 @@
 		"uri":"cce_10_0399.html",
 		"node_id":"cce_10_0399.xml",
 		"product_code":"cce",
-		"code":"329",
+		"code":"330",
 		"des":"This section describes how to access an intranet from a container (outside the cluster in a VPC), including intra-VPC access and cross-VPC access.The performance of acces",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Intra-VPC Access,Network,User Guide",
@@ -5940,7 +5958,7 @@
 		"uri":"cce_10_0400.html",
 		"node_id":"cce_10_0400.xml",
 		"product_code":"cce",
-		"code":"330",
+		"code":"331",
 		"des":"Containers can access the Internet in either of the following ways:Bind an EIP to the node where the container is located if the network model is VPC or tunnel.Bind an EI",
 		"doc_type":"usermanual2",
 		"kw":"Accessing the Internet from a Container,Network,User Guide",
@@ -5958,7 +5976,7 @@
 		"uri":"cce_10_0374.html",
 		"node_id":"cce_10_0374.xml",
 		"product_code":"cce",
-		"code":"331",
+		"code":"332",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Storage",
@@ -5976,7 +5994,7 @@
 		"uri":"cce_10_0307.html",
 		"node_id":"cce_10_0307.xml",
 		"product_code":"cce",
-		"code":"332",
+		"code":"333",
 		"des":"CCE container storage is implemented based on Kubernetes container storage APIs (CSI). CCE integrates multiple types of cloud storage and covers different application sce",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Storage,User Guide",
@@ -5994,7 +6012,7 @@
 		"uri":"cce_10_0378.html",
 		"node_id":"cce_10_0378.xml",
 		"product_code":"cce",
-		"code":"333",
+		"code":"334",
 		"des":"On-disk files in a container are ephemeral, which presents the following problems to important applications running in the container:When a container is rebuilt, files in",
 		"doc_type":"usermanual2",
 		"kw":"Statically creating storage volume,VolumeClaimTemplate,Storage Basics,Storage,User Guide",
@@ -6012,7 +6030,7 @@
 		"uri":"cce_10_0044.html",
 		"node_id":"cce_10_0044.xml",
 		"product_code":"cce",
-		"code":"334",
+		"code":"335",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Elastic Volume Service",
@@ -6030,7 +6048,7 @@
 		"uri":"cce_10_0613.html",
 		"node_id":"cce_10_0613.xml",
 		"product_code":"cce",
-		"code":"335",
+		"code":"336",
 		"des":"To achieve persistent storage, CCE allows you to mount the storage volumes created from Elastic Volume Service (EVS) disks to a path of a container. When the container is",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Elastic Volume Service,User Guide",
@@ -6048,7 +6066,7 @@
 		"uri":"cce_10_0614.html",
 		"node_id":"cce_10_0614.xml",
 		"product_code":"cce",
-		"code":"336",
+		"code":"337",
 		"des":"CCE allows you to create a PV using an existing EVS disk. Then, you can create a PVC and bind it to the PV. This method is suitable for scenarios where underlying storage",
 		"doc_type":"usermanual2",
 		"kw":"Data sharing,Using an Existing EVS Disk Through a Static PV,Elastic Volume Service,User Guide",
@@ -6066,7 +6084,7 @@
 		"uri":"cce_10_0615.html",
 		"node_id":"cce_10_0615.xml",
 		"product_code":"cce",
-		"code":"337",
+		"code":"338",
 		"des":"CCE allows you to specify a StorageClass to automatically create an EVS disk and the corresponding PV. This function is applicable when no underlying storage volume is av",
 		"doc_type":"usermanual2",
 		"kw":"Data sharing,Expanding the capacity of an EVS disk,Using an EVS Disk Through a Dynamic PV,Elastic Vo",
@@ -6084,7 +6102,7 @@
 		"uri":"cce_10_0616.html",
 		"node_id":"cce_10_0616.xml",
 		"product_code":"cce",
-		"code":"338",
+		"code":"339",
 		"des":"Dynamic mounting is available only for creating a StatefulSet. It is implemented through a volume claim template (volumeClaimTemplates field) and depends on dynamic creat",
 		"doc_type":"usermanual2",
 		"kw":"Expanding the capacity of an EVS disk,Dynamically Mounting an EVS Disk to a StatefulSet,Elastic Volu",
@@ -6102,7 +6120,7 @@
 		"uri":"cce_10_0859.html",
 		"node_id":"cce_10_0859.xml",
 		"product_code":"cce",
-		"code":"339",
+		"code":"340",
 		"des":"Encrypting cloud disks ensures data privacy and control, making it ideal for scenarios that demand high security or compliance standards. This section describes how to us",
 		"doc_type":"usermanual2",
 		"kw":"Encrypting EVS Disks,Elastic Volume Service,User Guide",
@@ -6120,7 +6138,7 @@
 		"uri":"cce_10_0860.html",
 		"node_id":"cce_10_0860.xml",
 		"product_code":"cce",
-		"code":"340",
+		"code":"341",
 		"des":"If the EVS disk attached to a workload does not have enough space, you can increase its capacity by expanding it. This section describes how to expand the capacity of an ",
 		"doc_type":"usermanual2",
 		"kw":"Expanding the Capacity of an EVS Disk,Elastic Volume Service,User Guide",
@@ -6138,7 +6156,7 @@
 		"uri":"cce_10_0381.html",
 		"node_id":"cce_10_0381.xml",
 		"product_code":"cce",
-		"code":"341",
+		"code":"342",
 		"des":"CCE works with EVS to support snapshots. A snapshot is a complete copy or image of EVS disk data at a certain point of time, which can be used for data DR.You can create ",
 		"doc_type":"usermanual2",
 		"kw":"Snapshots and Backups,Elastic Volume Service,User Guide",
@@ -6156,7 +6174,7 @@
 		"uri":"cce_10_0111.html",
 		"node_id":"cce_10_0111.xml",
 		"product_code":"cce",
-		"code":"342",
+		"code":"343",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Scalable File Service",
@@ -6174,7 +6192,7 @@
 		"uri":"cce_10_0617.html",
 		"node_id":"cce_10_0617.xml",
 		"product_code":"cce",
-		"code":"343",
+		"code":"344",
 		"des":"CCE allows you to mount a volume created from a Scalable File Service (SFS) file system to a container to store data persistently. SFS volumes are commonly used in ReadWr",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Scalable File Service,User Guide",
@@ -6192,7 +6210,7 @@
 		"uri":"cce_10_0619.html",
 		"node_id":"cce_10_0619.xml",
 		"product_code":"cce",
-		"code":"344",
+		"code":"345",
 		"des":"SFS is a network-attached storage (NAS) that provides shared, scalable, and high-performance file storage. It applies to large-capacity expansion and cost-sensitive servi",
 		"doc_type":"usermanual2",
 		"kw":"Using an Existing SFS File System Through a Static PV,Scalable File Service,User Guide",
@@ -6210,7 +6228,7 @@
 		"uri":"cce_10_0620.html",
 		"node_id":"cce_10_0620.xml",
 		"product_code":"cce",
-		"code":"345",
+		"code":"346",
 		"des":"This section describes how to use storage classes to dynamically create PVs and PVCs for data persistence and sharing in workloads.You have created a cluster and installe",
 		"doc_type":"usermanual2",
 		"kw":"Using an SFS File System Through a Dynamic PV,Scalable File Service,User Guide",
@@ -6228,7 +6246,7 @@
 		"uri":"cce_10_0337.html",
 		"node_id":"cce_10_0337.xml",
 		"product_code":"cce",
-		"code":"346",
+		"code":"347",
 		"des":"This section describes how to configure SFS mount options. You can configure mount options in a PV and bind the PV to a PVC. Alternatively, configure mount options in a S",
 		"doc_type":"usermanual2",
 		"kw":"Configuring SFS Volume Mount Options,Scalable File Service,User Guide",
@@ -6246,7 +6264,7 @@
 		"uri":"cce_10_0125.html",
 		"node_id":"cce_10_0125.xml",
 		"product_code":"cce",
-		"code":"347",
+		"code":"348",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"SFS Turbo",
@@ -6264,7 +6282,7 @@
 		"uri":"cce_10_0624.html",
 		"node_id":"cce_10_0624.xml",
 		"product_code":"cce",
-		"code":"348",
+		"code":"349",
 		"des":"CCE allows you to mount storage volumes created by SFS Turbo file systems to a path of a container to meet data persistence requirements. SFS Turbo file systems are fast,",
 		"doc_type":"usermanual2",
 		"kw":"Overview,SFS Turbo,User Guide",
@@ -6282,7 +6300,7 @@
 		"uri":"cce_10_0625.html",
 		"node_id":"cce_10_0625.xml",
 		"product_code":"cce",
-		"code":"349",
+		"code":"350",
 		"des":"SFS Turbo is a shared file system with high availability and durability. It is suitable for applications that contain massive small files and require low latency, and hig",
 		"doc_type":"usermanual2",
 		"kw":"Expanding the capacity of an SFS Turbo volume,Using an Existing SFS Turbo File System Through a Stat",
@@ -6300,7 +6318,7 @@
 		"uri":"cce_10_0626.html",
 		"node_id":"cce_10_0626.xml",
 		"product_code":"cce",
-		"code":"350",
+		"code":"351",
 		"des":"This section describes how to configure SFS Turbo mount options. For SFS Turbo, you can only set mount options in a PV and bind the PV by creating a PVC.The CCE Container",
 		"doc_type":"usermanual2",
 		"kw":"Configuring SFS Turbo Mount Options,SFS Turbo,User Guide",
@@ -6318,7 +6336,7 @@
 		"uri":"cce_10_0839.html",
 		"node_id":"cce_10_0839.xml",
 		"product_code":"cce",
-		"code":"351",
+		"code":"352",
 		"des":"When an SFS Turbo volume is mounted to a workload container, the root directory is mounted to the container by default. However, the minimum capacity of an SFS Turbo volu",
 		"doc_type":"usermanual2",
 		"kw":"(Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV,SFS Turbo,User Guide",
@@ -6336,7 +6354,7 @@
 		"uri":"cce_bestpractice_00253.html",
 		"node_id":"cce_bestpractice_00253.xml",
 		"product_code":"cce",
-		"code":"352",
+		"code":"353",
 		"des":"The minimum capacity of an SFS Turbo file system is 500 GiB. By default, the root directory of an SFS Turbo file system is mounted to a container which, in most case, doe",
 		"doc_type":"usermanual2",
 		"kw":"Dynamically Creating an SFS Turbo Subdirectory Using StorageClass,SFS Turbo,User Guide",
@@ -6354,7 +6372,7 @@
 		"uri":"cce_10_0160.html",
 		"node_id":"cce_10_0160.xml",
 		"product_code":"cce",
-		"code":"353",
+		"code":"354",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Object Storage Service",
@@ -6372,7 +6390,7 @@
 		"uri":"cce_10_0628.html",
 		"node_id":"cce_10_0628.xml",
 		"product_code":"cce",
-		"code":"354",
+		"code":"355",
 		"des":"Object Storage Service (OBS) provides massive, secure, and cost-effective data storage for you to store data of any type and size. You can use it in enterprise backup/arc",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Object Storage Service,User Guide",
@@ -6390,7 +6408,7 @@
 		"uri":"cce_10_0379.html",
 		"node_id":"cce_10_0379.xml",
 		"product_code":"cce",
-		"code":"355",
+		"code":"356",
 		"des":"This section describes how to use an existing Object Storage Service (OBS) bucket to statically create PVs and PVCs for data persistence and sharing in workloads.You have",
 		"doc_type":"usermanual2",
 		"kw":"Updating an access key,Using an Existing OBS Bucket Through a Static PV,Object Storage Service,User ",
@@ -6408,7 +6426,7 @@
 		"uri":"cce_10_0630.html",
 		"node_id":"cce_10_0630.xml",
 		"product_code":"cce",
-		"code":"356",
+		"code":"357",
 		"des":"This section describes how to automatically create an OBS bucket. It is applicable when no underlying storage volume is available.If OBS volumes are used, the owner group",
 		"doc_type":"usermanual2",
 		"kw":"Updating an access key,Using an OBS Bucket Through a Dynamic PV,Object Storage Service,User Guide",
@@ -6426,7 +6444,7 @@
 		"uri":"cce_10_0631.html",
 		"node_id":"cce_10_0631.xml",
 		"product_code":"cce",
-		"code":"357",
+		"code":"358",
 		"des":"This section describes how to configure OBS volume mount options. You can configure mount options in a PV and bind the PV to a PVC. Alternatively, configure mount options",
 		"doc_type":"usermanual2",
 		"kw":"Configuring OBS Mount Options,Object Storage Service,User Guide",
@@ -6444,7 +6462,7 @@
 		"uri":"cce_10_0336.html",
 		"node_id":"cce_10_0336.xml",
 		"product_code":"cce",
-		"code":"358",
+		"code":"359",
 		"des":"CCE Container Storage (Everest) of v1.2.8 or later supports custom access keys. In this way, IAM users can use their own custom access keys to mount an OBS volume.The CCE",
 		"doc_type":"usermanual2",
 		"kw":"Using a Custom Access Key (AK/SK) to Mount an OBS Volume,Object Storage Service,User Guide",
@@ -6462,7 +6480,7 @@
 		"uri":"cce_10_0391.html",
 		"node_id":"cce_10_0391.xml",
 		"product_code":"cce",
-		"code":"359",
+		"code":"360",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Local PVs",
@@ -6480,7 +6498,7 @@
 		"uri":"cce_10_0633.html",
 		"node_id":"cce_10_0633.xml",
 		"product_code":"cce",
-		"code":"360",
+		"code":"361",
 		"des":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. A PV that uses a local persistent vol",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Local PVs,User Guide",
@@ -6498,7 +6516,7 @@
 		"uri":"cce_10_0642.html",
 		"node_id":"cce_10_0642.xml",
 		"product_code":"cce",
-		"code":"361",
+		"code":"362",
 		"des":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. Before creating a local PV, import th",
 		"doc_type":"usermanual2",
 		"kw":"storage pool,Importing a PV to a Storage Pool,Local PVs,User Guide",
@@ -6516,7 +6534,7 @@
 		"uri":"cce_10_0634.html",
 		"node_id":"cce_10_0634.xml",
 		"product_code":"cce",
-		"code":"362",
+		"code":"363",
 		"des":"You have created a cluster and installed the CSI add-on (Everest) in the cluster.To create a cluster using commands, ensure kubectl is used. For details, see Accessing a ",
 		"doc_type":"usermanual2",
 		"kw":"Using a Local PV Through a Dynamic PV,Local PVs,User Guide",
@@ -6534,7 +6552,7 @@
 		"uri":"cce_10_0635.html",
 		"node_id":"cce_10_0635.xml",
 		"product_code":"cce",
-		"code":"363",
+		"code":"364",
 		"des":"Dynamic mounting is available only for creating a StatefulSet. It is implemented through a volume claim template (volumeClaimTemplates field) and depends on dynamic creat",
 		"doc_type":"usermanual2",
 		"kw":"VCT,Dynamically Mounting a Local PV to a StatefulSet,Local PVs,User Guide",
@@ -6552,7 +6570,7 @@
 		"uri":"cce_10_0636.html",
 		"node_id":"cce_10_0636.xml",
 		"product_code":"cce",
-		"code":"364",
+		"code":"365",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Ephemeral Volumes",
@@ -6570,7 +6588,7 @@
 		"uri":"cce_10_0637.html",
 		"node_id":"cce_10_0637.xml",
 		"product_code":"cce",
-		"code":"365",
+		"code":"366",
 		"des":"Some applications require additional storage, but whether the data is still available after a restart is not important. For example, although cache services are limited b",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Ephemeral Volumes,User Guide",
@@ -6588,7 +6606,7 @@
 		"uri":"cce_10_0725.html",
 		"node_id":"cce_10_0725.xml",
 		"product_code":"cce",
-		"code":"366",
+		"code":"367",
 		"des":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. Before creating a local EV, import th",
 		"doc_type":"usermanual2",
 		"kw":"Importing an EV to a Storage Pool,Ephemeral Volumes,User Guide",
@@ -6606,7 +6624,7 @@
 		"uri":"cce_10_0726.html",
 		"node_id":"cce_10_0726.xml",
 		"product_code":"cce",
-		"code":"367",
+		"code":"368",
 		"des":"Local Ephemeral Volumes (EVs) are stored in EV storage pools. Local EVs deliver better performance than the default storage medium of native emptyDir and support scale-ou",
 		"doc_type":"usermanual2",
 		"kw":"Local EV,Ephemeral Volumes,User Guide",
@@ -6624,7 +6642,7 @@
 		"uri":"cce_10_0638.html",
 		"node_id":"cce_10_0638.xml",
 		"product_code":"cce",
-		"code":"368",
+		"code":"369",
 		"des":"A temporary path is of the Kubernetes-native emptyDir type. Its lifecycle is the same as that of a pod. Memory can be specified as the storage medium. When the pod is del",
 		"doc_type":"usermanual2",
 		"kw":"Temporary Path,Ephemeral Volumes,User Guide",
@@ -6642,7 +6660,7 @@
 		"uri":"cce_10_0377.html",
 		"node_id":"cce_10_0377.xml",
 		"product_code":"cce",
-		"code":"369",
+		"code":"370",
 		"des":"hostPath is used for mounting the file directory of the host where the container is located to the specified mount point of the container. If the container needs to acces",
 		"doc_type":"usermanual2",
 		"kw":"hostPath,Storage,User Guide",
@@ -6660,7 +6678,7 @@
 		"uri":"cce_10_0380.html",
 		"node_id":"cce_10_0380.xml",
 		"product_code":"cce",
-		"code":"370",
+		"code":"371",
 		"des":"A StorageClass in Kubernetes is a resource that categorizes storage types in a cluster. It can also serve as a configuration template for creating PVs. When creating a PV",
 		"doc_type":"usermanual2",
 		"kw":"StorageClass,Storage,User Guide",
@@ -6678,7 +6696,7 @@
 		"uri":"cce_10_0207.html",
 		"node_id":"cce_10_0207.xml",
 		"product_code":"cce",
-		"code":"371",
+		"code":"372",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Auto Scaling",
@@ -6696,7 +6714,7 @@
 		"uri":"cce_10_0279.html",
 		"node_id":"cce_10_0279.xml",
 		"product_code":"cce",
-		"code":"372",
+		"code":"373",
 		"des":"Auto scaling is a service that automatically and economically adjusts service resources based on your service requirements and configured policies.More and more applicati",
 		"doc_type":"usermanual2",
 		"kw":"auto scaling,Overview,Auto Scaling,User Guide",
@@ -6714,7 +6732,7 @@
 		"uri":"cce_10_0293.html",
 		"node_id":"cce_10_0293.xml",
 		"product_code":"cce",
-		"code":"373",
+		"code":"374",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Scaling a Workload",
@@ -6732,7 +6750,7 @@
 		"uri":"cce_10_0290.html",
 		"node_id":"cce_10_0290.xml",
 		"product_code":"cce",
-		"code":"374",
+		"code":"375",
 		"des":"CCE supports multiple workload scaling modes. Comparisons between the scaling policies are listed in the following table.Comparisons between auto scaling policiesItemHPAC",
 		"doc_type":"usermanual2",
 		"kw":"Workload Scaling Rules,Scaling a Workload,User Guide",
@@ -6750,7 +6768,7 @@
 		"uri":"cce_10_0208.html",
 		"node_id":"cce_10_0208.xml",
 		"product_code":"cce",
-		"code":"375",
+		"code":"376",
 		"des":"Horizontal Pod Autoscaling (HPA) in Kubernetes implements horizontal scaling of pods. In a CCE HPA policy, you can configure different cooldown time windows and scaling t",
 		"doc_type":"usermanual2",
 		"kw":"Horizontal Pod Autoscaling,horizontal scaling of pods,Creating an HPA Policy,Scaling a Workload,User",
@@ -6768,7 +6786,7 @@
 		"uri":"cce_10_0944.html",
 		"node_id":"cce_10_0944.xml",
 		"product_code":"cce",
-		"code":"376",
+		"code":"377",
 		"des":"Kubernetes' default HPA policy only allows for auto scaling based on CPU and memory usage. However, in more complex service scenarios, this may not be sufficient to meet ",
 		"doc_type":"usermanual2",
 		"kw":"Creating an HPA Policy with Custom Metrics,Scaling a Workload,User Guide",
@@ -6786,7 +6804,7 @@
 		"uri":"cce_10_0415.html",
 		"node_id":"cce_10_0415.xml",
 		"product_code":"cce",
-		"code":"377",
+		"code":"378",
 		"des":"There are predictable and unpredictable traffic peaks for some services. For such services, CCE CronHPA allows you to scale resources in fixed periods. It can work with H",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Scheduled CronHPA Policy,Scaling a Workload,User Guide",
@@ -6804,7 +6822,7 @@
 		"uri":"cce_10_0934.html",
 		"node_id":"cce_10_0934.xml",
 		"product_code":"cce",
-		"code":"378",
+		"code":"379",
 		"des":"The native Horizontal Pod Autoscaler (HPA) in Kubernetes can cause delays in scaling due to its passive triggering mechanism. To address this issue, the Advanced Horizont",
 		"doc_type":"usermanual2",
 		"kw":"Creating an AHPA Policy,Scaling a Workload,User Guide",
@@ -6822,7 +6840,7 @@
 		"uri":"cce_10_0083.html",
 		"node_id":"cce_10_0083.xml",
 		"product_code":"cce",
-		"code":"379",
+		"code":"380",
 		"des":"After a workload scaling policy is created, you can update and delete the policy, as well as edit the YAML file.You can view the rules, latest status, and events of a wor",
 		"doc_type":"usermanual2",
 		"kw":"Managing Workload Scaling Policies,Scaling a Workload,User Guide",
@@ -6840,7 +6858,7 @@
 		"uri":"cce_10_0291.html",
 		"node_id":"cce_10_0291.xml",
 		"product_code":"cce",
-		"code":"380",
+		"code":"381",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Scaling a Node",
@@ -6858,7 +6876,7 @@
 		"uri":"cce_10_0296.html",
 		"node_id":"cce_10_0296.xml",
 		"product_code":"cce",
-		"code":"381",
+		"code":"382",
 		"des":"HPA is designed for pod-level scaling and can dynamically adjust the number of replicas based on workload metrics. However, if cluster resources are insufficient and new ",
 		"doc_type":"usermanual2",
 		"kw":"node scaling,Node Scaling Rules,Scaling a Node,User Guide",
@@ -6876,7 +6894,7 @@
 		"uri":"cce_10_0649.html",
 		"node_id":"cce_10_0649.xml",
 		"product_code":"cce",
-		"code":"382",
+		"code":"383",
 		"des":"To use node flavor priorities, the Autoscaler version must be 1.19.35, 1.21.28, 1.23.30, 1.25.20, or later. To balance load among AZs, the version must be 1.23.122, 1.25.",
 		"doc_type":"usermanual2",
 		"kw":"Priorities for Scaling Node Pools,Scaling a Node,User Guide",
@@ -6894,7 +6912,7 @@
 		"uri":"cce_10_0209.html",
 		"node_id":"cce_10_0209.xml",
 		"product_code":"cce",
-		"code":"383",
+		"code":"384",
 		"des":"CCE provides auto scaling through the CCE Cluster Autoscaler add-on. Nodes with different flavors can be automatically added across AZs on demand.If both a node scaling p",
 		"doc_type":"usermanual2",
 		"kw":"node scaling,Creating a Node Scaling Policy,Scaling a Node,User Guide",
@@ -6912,7 +6930,7 @@
 		"uri":"cce_10_0063.html",
 		"node_id":"cce_10_0063.xml",
 		"product_code":"cce",
-		"code":"384",
+		"code":"385",
 		"des":"After a node scaling policy is created, you can delete, edit, disable, enable, or clone the policy.You can view the associated node pool, rules, and scaling history of a ",
 		"doc_type":"usermanual2",
 		"kw":"Managing Node Scaling Policies,Scaling a Node,User Guide",
@@ -6930,7 +6948,7 @@
 		"uri":"cce_10_0967.html",
 		"node_id":"cce_10_0967.xml",
 		"product_code":"cce",
-		"code":"385",
+		"code":"386",
 		"des":"When you use the CCE Cluster Autoscaler add-on to automatically adjust the number of nodes, you need to specify the scale-in conditions for each node pool in a cluster ba",
 		"doc_type":"usermanual2",
 		"kw":"Specifying Node Scale-in Conditions for a Node Pool,Scaling a Node,User Guide",
@@ -6948,7 +6966,7 @@
 		"uri":"cce_10_0300.html",
 		"node_id":"cce_10_0300.xml",
 		"product_code":"cce",
-		"code":"386",
+		"code":"387",
 		"des":"The best way to handle surging traffic is to automatically adjust the number of machines based on the traffic volume or resource usage, which is called scaling.To prevent",
 		"doc_type":"usermanual2",
 		"kw":"Using HPA and CA for Auto Scaling of Workloads and Nodes,Auto Scaling,User Guide",
@@ -6966,7 +6984,7 @@
 		"uri":"cce_10_0705.html",
 		"node_id":"cce_10_0705.xml",
 		"product_code":"cce",
-		"code":"387",
+		"code":"388",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"O&M",
@@ -6984,7 +7002,7 @@
 		"uri":"cce_10_0553.html",
 		"node_id":"cce_10_0553.xml",
 		"product_code":"cce",
-		"code":"388",
+		"code":"389",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Logging",
@@ -7002,7 +7020,7 @@
 		"uri":"cce_10_0557.html",
 		"node_id":"cce_10_0557.xml",
 		"product_code":"cce",
-		"code":"389",
+		"code":"390",
 		"des":"Kubernetes logs allow you to locate and rectify faults. This section describes how to manage Kubernetes logs using different methods.The following are Kubernetes log mana",
 		"doc_type":"usermanual2",
 		"kw":"Overview,Logging,User Guide",
@@ -7020,7 +7038,7 @@
 		"uri":"cce_10_0182.html",
 		"node_id":"cce_10_0182.xml",
 		"product_code":"cce",
-		"code":"390",
+		"code":"391",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Collecting Container Logs",
@@ -7038,7 +7056,7 @@
 		"uri":"cce_10_0555.html",
 		"node_id":"cce_10_0555.xml",
 		"product_code":"cce",
-		"code":"391",
+		"code":"392",
 		"des":"The Cloud Native Log Collection add-on (Cloud Native Log Collection) is developed based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This ad",
 		"doc_type":"usermanual2",
 		"kw":"Collecting Container Logs Using the Cloud Native Log Collection Add-on,Collecting Container Logs,Use",
@@ -7056,8 +7074,8 @@
 		"uri":"cce_10_0018.html",
 		"node_id":"cce_10_0018.xml",
 		"product_code":"cce",
-		"code":"392",
-		"des":"CCE works with AOM to collect workload logs. When a node is created, ICAgent (a DaemonSet named icagent in the kube-system namespace of a cluster) of AOM is installed by ",
+		"code":"393",
+		"des":"CCE can collect workload logs and report them to AOM 1.0. When a node is created, ICAgent (a DaemonSet named icagent in the kube-system namespace of a cluster) is install",
 		"doc_type":"usermanual2",
 		"kw":"Pod,Pod,Collecting Container Logs Using ICAgent,Collecting Container Logs,User Guide",
 		"search_title":"",
@@ -7074,7 +7092,7 @@
 		"uri":"cce_10_0793.html",
 		"node_id":"cce_10_0793.xml",
 		"product_code":"cce",
-		"code":"393",
+		"code":"394",
 		"des":"The Cloud Native Log Collection add-on works with LTS to collect and store Kubernetes events and works with AOM to generate alarms.To enable Kubernetes event collection, ",
 		"doc_type":"usermanual2",
 		"kw":"Collecting Kubernetes Events,Logging,User Guide",
@@ -7092,7 +7110,7 @@
 		"uri":"cce_10_0554.html",
 		"node_id":"cce_10_0554.xml",
 		"product_code":"cce",
-		"code":"394",
+		"code":"395",
 		"des":"CCE allows you to collect the logs of master nodes. On the Logging page, you can select one or more control plane components (kube-controller-manager, kube-apiserver, and",
 		"doc_type":"usermanual2",
 		"kw":"Collecting Control Plane Component Logs,Logging,User Guide",
@@ -7110,7 +7128,7 @@
 		"uri":"cce_10_0792.html",
 		"node_id":"cce_10_0792.xml",
 		"product_code":"cce",
-		"code":"395",
+		"code":"396",
 		"des":"CCE allows you to collect the logs of master nodes. On the Kubernetes Audit Logs tab of Logging, you can determine whether to report audit logs to LTS.The cluster version",
 		"doc_type":"usermanual2",
 		"kw":"Collecting Audit Logs,Logging,User Guide",
@@ -7128,7 +7146,7 @@
 		"uri":"cce_10_0024.html",
 		"node_id":"cce_10_0024.xml",
 		"product_code":"cce",
-		"code":"396",
+		"code":"397",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Log Auditing",
@@ -7146,7 +7164,7 @@
 		"uri":"cce_10_0025.html",
 		"node_id":"cce_10_0025.xml",
 		"product_code":"cce",
-		"code":"397",
+		"code":"398",
 		"des":"Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the ",
 		"doc_type":"usermanual2",
 		"kw":"CCE Operations Supported by Cloud Trace Service,Log Auditing,User Guide",
@@ -7164,7 +7182,7 @@
 		"uri":"cce_10_0026.html",
 		"node_id":"cce_10_0026.xml",
 		"product_code":"cce",
-		"code":"398",
+		"code":"399",
 		"des":"After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces",
 		"doc_type":"usermanual2",
 		"kw":"Viewing CTS Traces in the Trace List,Log Auditing,User Guide",
@@ -7182,7 +7200,7 @@
 		"uri":"cce_10_0799.html",
 		"node_id":"cce_10_0799.xml",
 		"product_code":"cce",
-		"code":"399",
+		"code":"400",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"O&M FAQ",
@@ -7200,7 +7218,7 @@
 		"uri":"cce_10_0809.html",
 		"node_id":"cce_10_0809.xml",
 		"product_code":"cce",
-		"code":"400",
+		"code":"401",
 		"des":"How Do I Disable Logging?What Can I Do If All Components Except log-operator Are Not Ready?How Do I Handle the Error in Stdout Logs of log-operator?What Can I Do If Conta",
 		"doc_type":"usermanual2",
 		"kw":"Logging FAQ,O&M FAQ,User Guide",
@@ -7218,7 +7236,7 @@
 		"uri":"cce_10_0811.html",
 		"node_id":"cce_10_0811.xml",
 		"product_code":"cce",
-		"code":"401",
+		"code":"402",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"O&M Best Practices",
@@ -7236,7 +7254,7 @@
 		"uri":"cce_10_0373.html",
 		"node_id":"cce_10_0373.xml",
 		"product_code":"cce",
-		"code":"402",
+		"code":"403",
 		"des":"CCE provides the Cloud Native Cluster Monitoring add-on to monitor custom metrics using Prometheus.The following procedure uses an Nginx application as an example to desc",
 		"doc_type":"usermanual2",
 		"kw":"Monitoring Custom Metrics Using Cloud Native Cluster Monitoring,O&M Best Practices,User Guide",
@@ -7254,7 +7272,7 @@
 		"uri":"cce_10_0201.html",
 		"node_id":"cce_10_0201.xml",
 		"product_code":"cce",
-		"code":"403",
+		"code":"404",
 		"des":"CCE allows you to upload custom metrics to AOM. ICAgent on a node periodically calls the metric monitoring API configured on a workload to read monitoring data and then u",
 		"doc_type":"usermanual2",
 		"kw":"Monitoring Custom Metrics on AOM,O&M Best Practices,User Guide",
@@ -7272,7 +7290,7 @@
 		"uri":"cce_10_0030.html",
 		"node_id":"cce_10_0030.xml",
 		"product_code":"cce",
-		"code":"404",
+		"code":"405",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Namespaces",
@@ -7290,7 +7308,7 @@
 		"uri":"cce_10_0278.html",
 		"node_id":"cce_10_0278.xml",
 		"product_code":"cce",
-		"code":"405",
+		"code":"406",
 		"des":"A namespace is a collection of resources and objects. Multiple namespaces can be created inside a cluster and isolated from each other. This enables namespaces to share t",
 		"doc_type":"usermanual2",
 		"kw":"Creating a Namespace,Namespaces,User Guide",
@@ -7308,7 +7326,7 @@
 		"uri":"cce_10_0285.html",
 		"node_id":"cce_10_0285.xml",
 		"product_code":"cce",
-		"code":"406",
+		"code":"407",
 		"des":"When creating a workload, you can select a namespace to isolate resources or users.When querying workloads, you can select a namespace to view all workloads in the namesp",
 		"doc_type":"usermanual2",
 		"kw":"Managing Namespaces,Namespaces,User Guide",
@@ -7326,7 +7344,7 @@
 		"uri":"cce_10_0287.html",
 		"node_id":"cce_10_0287.xml",
 		"product_code":"cce",
-		"code":"407",
+		"code":"408",
 		"des":"Kubernetes provides namespaces for you to group resources in a cluster. Namespaces serve different purposes to meet the needs of multiple users, environments, and applica",
 		"doc_type":"usermanual2",
 		"kw":"Configuring Resource Quotas,Namespaces,User Guide",
@@ -7344,7 +7362,7 @@
 		"uri":"cce_10_0045.html",
 		"node_id":"cce_10_0045.xml",
 		"product_code":"cce",
-		"code":"408",
+		"code":"409",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"ConfigMaps and Secrets",
@@ -7362,7 +7380,7 @@
 		"uri":"cce_10_0152.html",
 		"node_id":"cce_10_0152.xml",
 		"product_code":"cce",
-		"code":"409",
+		"code":"410",
 		"des":"A ConfigMap is a type of resource that stores configuration information required by a workload. Its content is user-defined. After creating ConfigMaps, you can use them a",
 		"doc_type":"usermanual2",
 		"kw":"Creating a ConfigMap,ConfigMaps and Secrets,User Guide",
@@ -7380,7 +7398,7 @@
 		"uri":"cce_10_0015.html",
 		"node_id":"cce_10_0015.xml",
 		"product_code":"cce",
-		"code":"410",
+		"code":"411",
 		"des":"After a ConfigMap is created, it can be used in three workload scenarios: environment variables, command line parameters, and data volumes.Configuring Environment Variabl",
 		"doc_type":"usermanual2",
 		"kw":"environment variables,command line parameters,data volumes,Using a ConfigMap,ConfigMaps and Secrets,",
@@ -7398,7 +7416,7 @@
 		"uri":"cce_10_0153.html",
 		"node_id":"cce_10_0153.xml",
 		"product_code":"cce",
-		"code":"411",
+		"code":"412",
 		"des":"A secret is a type of resource that holds sensitive data, such as authentication and key information. Its content is user-defined. After creating secrets, you can use the",
 		"doc_type":"usermanual2",
 		"kw":"Opaque,kubernetes.io/dockerconfigjson,kubernetes.io/tls,Opaque,kubernetes.io/dockerconfigjson,kubern",
@@ -7416,7 +7434,7 @@
 		"uri":"cce_10_0016.html",
 		"node_id":"cce_10_0016.xml",
 		"product_code":"cce",
-		"code":"412",
+		"code":"413",
 		"des":"After secrets are created, they can be mounted as data volumes or be exposed as environment variables to be used by a container in a pod.Do not perform any operation on t",
 		"doc_type":"usermanual2",
 		"kw":"data volumes,environment variables,Using a Secret,ConfigMaps and Secrets,User Guide",
@@ -7434,7 +7452,7 @@
 		"uri":"cce_10_0388.html",
 		"node_id":"cce_10_0388.xml",
 		"product_code":"cce",
-		"code":"413",
+		"code":"414",
 		"des":"By default, CCE creates the following secrets in each namespace:default-secretpaas.elbdefault-token-xxxxx (xxxxx is a random number.)The functions of these secrets are de",
 		"doc_type":"usermanual2",
 		"kw":"Cluster Secrets,ConfigMaps and Secrets,User Guide",
@@ -7452,7 +7470,7 @@
 		"uri":"cce_10_0064.html",
 		"node_id":"cce_10_0064.xml",
 		"product_code":"cce",
-		"code":"414",
+		"code":"415",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Add-ons",
@@ -7470,7 +7488,7 @@
 		"uri":"cce_10_0277.html",
 		"node_id":"cce_10_0277.xml",
 		"product_code":"cce",
-		"code":"415",
+		"code":"416",
 		"des":"CCE provides multiple types of add-ons to extend cluster functions and meet feature requirements. You can install add-ons as required.CCE uses Helm charts to deploy add-o",
 		"doc_type":"usermanual2",
 		"kw":"This add-on,DNS server,domain name resolution,Kubernetes,chain add-on,Overview,Add-ons,User Guide",
@@ -7488,7 +7506,7 @@
 		"uri":"cce_10_0907.html",
 		"node_id":"cce_10_0907.xml",
 		"product_code":"cce",
-		"code":"416",
+		"code":"417",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Scheduling and Elasticity Add-ons",
@@ -7506,7 +7524,7 @@
 		"uri":"cce_10_0193.html",
 		"node_id":"cce_10_0193.xml",
 		"product_code":"cce",
-		"code":"417",
+		"code":"418",
 		"des":"Volcano is a batch processing platform based on Kubernetes. It provides a series of features required by machine learning, deep learning, bioinformatics, genomics, and ot",
 		"doc_type":"usermanual2",
 		"kw":"Volcano Scheduler,Scheduling and Elasticity Add-ons,User Guide",
@@ -7524,7 +7542,7 @@
 		"uri":"cce_10_0154.html",
 		"node_id":"cce_10_0154.xml",
 		"product_code":"cce",
-		"code":"418",
+		"code":"419",
 		"des":"The CCE Cluster Autoscaler add-on is built on the Autoscaler component of the community. It can automatically adjust the number of cluster nodes based on the resource nee",
 		"doc_type":"usermanual2",
 		"kw":"CCE Cluster Autoscaler,Scheduling and Elasticity Add-ons,User Guide",
@@ -7542,7 +7560,7 @@
 		"uri":"cce_10_0240.html",
 		"node_id":"cce_10_0240.xml",
 		"product_code":"cce",
-		"code":"419",
+		"code":"420",
 		"des":"The CCE Advanced HPA add-on (formerly cce-hpa-controller) is developed by CCE. It can be used to flexibly scale in or out Deployments based on metrics such as CPU usage a",
 		"doc_type":"usermanual2",
 		"kw":"CCE Advanced HPA,Scheduling and Elasticity Add-ons,User Guide",
@@ -7560,7 +7578,7 @@
 		"uri":"cce_10_0908.html",
 		"node_id":"cce_10_0908.xml",
 		"product_code":"cce",
-		"code":"420",
+		"code":"421",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Observability Add-ons",
@@ -7578,7 +7596,7 @@
 		"uri":"cce_10_0406.html",
 		"node_id":"cce_10_0406.xml",
 		"product_code":"cce",
-		"code":"421",
+		"code":"422",
 		"des":"The Cloud Native Cluster Monitoring add-on (formerly kube-prometheus-stack) uses Prometheus-operator and Prometheus and provides easy-to-use, end-to-end Kubernetes cluste",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Cluster Monitoring,Cloud Native Observability Add-ons,User Guide",
@@ -7596,7 +7614,7 @@
 		"uri":"cce_10_0416.html",
 		"node_id":"cce_10_0416.xml",
 		"product_code":"cce",
-		"code":"422",
+		"code":"423",
 		"des":"The Cloud Native Log Collection add-on (formerly log-agent) is developed based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This add-on supp",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Log Collection,Cloud Native Observability Add-ons,User Guide",
@@ -7614,7 +7632,7 @@
 		"uri":"cce_10_0132.html",
 		"node_id":"cce_10_0132.xml",
 		"product_code":"cce",
-		"code":"423",
+		"code":"424",
 		"des":"The CCE Node Problem Detector add-on (formerly NPD) monitors abnormal events of cluster nodes and can connect to a third-party monitoring platform. It is a daemon running",
 		"doc_type":"usermanual2",
 		"kw":"CCE Node Problem Detector,Cloud Native Observability Add-ons,User Guide",
@@ -7632,7 +7650,7 @@
 		"uri":"cce_10_0205.html",
 		"node_id":"cce_10_0205.xml",
 		"product_code":"cce",
-		"code":"424",
+		"code":"425",
 		"des":"From version 1.8 onwards, Kubernetes provides resource usage metrics, such as the container CPU and memory usage, through the Metrics API. These metrics can be directly a",
 		"doc_type":"usermanual2",
 		"kw":"Kubernetes Metrics Server,Cloud Native Observability Add-ons,User Guide",
@@ -7650,7 +7668,7 @@
 		"uri":"cce_10_0909.html",
 		"node_id":"cce_10_0909.xml",
 		"product_code":"cce",
-		"code":"425",
+		"code":"426",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Cloud Native Heterogeneous Computing Add-ons",
@@ -7668,7 +7686,7 @@
 		"uri":"cce_10_0141.html",
 		"node_id":"cce_10_0141.xml",
 		"product_code":"cce",
-		"code":"426",
+		"code":"427",
 		"des":"NVIDIA GPU is a device management add-on that supports GPUs in containers. To use GPU nodes in a cluster, this add-on must be installed.The driver to be downloaded must b",
 		"doc_type":"usermanual2",
 		"kw":"CCE AI Suite (NVIDIA GPU),Cloud Native Heterogeneous Computing Add-ons,User Guide",
@@ -7686,7 +7704,7 @@
 		"uri":"cce_10_0910.html",
 		"node_id":"cce_10_0910.xml",
 		"product_code":"cce",
-		"code":"427",
+		"code":"428",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Container Network Add-ons",
@@ -7704,7 +7722,7 @@
 		"uri":"cce_10_0129.html",
 		"node_id":"cce_10_0129.xml",
 		"product_code":"cce",
-		"code":"428",
+		"code":"429",
 		"des":"CoreDNS is a DNS server that provides domain name resolution for Kubernetes clusters through a chain add-on.CoreDNS is an open-source software and has been a part of CNCF",
 		"doc_type":"usermanual2",
 		"kw":"CoreDNS,CoreDNS,Container Network Add-ons,User Guide",
@@ -7722,7 +7740,7 @@
 		"uri":"cce_10_0034.html",
 		"node_id":"cce_10_0034.xml",
 		"product_code":"cce",
-		"code":"429",
+		"code":"430",
 		"des":"Kubernetes uses kube-proxy to expose Services and provide load balancing. The implementation is at the transport layer. When it comes to Internet applications, where a bu",
 		"doc_type":"usermanual2",
 		"kw":"NGINX Ingress Controller,Container Network Add-ons,User Guide",
@@ -7740,7 +7758,7 @@
 		"uri":"cce_10_0911.html",
 		"node_id":"cce_10_0911.xml",
 		"product_code":"cce",
-		"code":"430",
+		"code":"431",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Container Storage Add-ons",
@@ -7758,7 +7776,7 @@
 		"uri":"cce_10_0066.html",
 		"node_id":"cce_10_0066.xml",
 		"product_code":"cce",
-		"code":"431",
+		"code":"432",
 		"des":"Everest is a cloud native container storage system, which enables clusters of Kubernetes v1.15.6 or later to access cloud storage services through the CSI.Everest is a sy",
 		"doc_type":"usermanual2",
 		"kw":"CCE Container Storage (Everest),Container Storage Add-ons,User Guide",
@@ -7776,7 +7794,7 @@
 		"uri":"cce_10_0127.html",
 		"node_id":"cce_10_0127.xml",
 		"product_code":"cce",
-		"code":"432",
+		"code":"433",
 		"des":"CCE Container Storage (FlexVolume), also called storage-driver, functions as a standard Kubernetes FlexVolume plugin to allow containers to use EVS, SFS, OBS, and SFS Tur",
 		"doc_type":"usermanual2",
 		"kw":"FlexVolume (Discarded),Container Storage Add-ons,User Guide",
@@ -7794,7 +7812,7 @@
 		"uri":"cce_10_0019.html",
 		"node_id":"cce_10_0019.xml",
 		"product_code":"cce",
-		"code":"433",
+		"code":"434",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Helm Chart",
@@ -7812,7 +7830,7 @@
 		"uri":"cce_10_0191.html",
 		"node_id":"cce_10_0191.xml",
 		"product_code":"cce",
-		"code":"434",
+		"code":"435",
 		"des":"CCE provides a console for managing Helm charts, helping you easily deploy applications using the charts and manage applications on the console.Helm is a package manager ",
 		"doc_type":"usermanual2",
 		"kw":"Overview of a Chart,Helm Chart,User Guide",
@@ -7830,7 +7848,7 @@
 		"uri":"cce_10_0146.html",
 		"node_id":"cce_10_0146.xml",
 		"product_code":"cce",
-		"code":"435",
+		"code":"436",
 		"des":"On the CCE console, you can upload a Helm chart package, deploy it, and manage the deployed pods.The number of charts that can be uploaded by a single user is limited. Th",
 		"doc_type":"usermanual2",
 		"kw":"Deploying an Application from a Chart,Helm Chart,User Guide",
@@ -7848,7 +7866,7 @@
 		"uri":"cce_10_0421.html",
 		"node_id":"cce_10_0421.xml",
 		"product_code":"cce",
-		"code":"436",
+		"code":"437",
 		"des":"Helm v2 stops at version 2.17.0. Currently, Helm v3 is the standard in the Helm community. You are advised to switch your charts to Helm v3 format as soon as possible.Cha",
 		"doc_type":"usermanual2",
 		"kw":"Differences Between Helm v2 and Helm v3 and Adaptation Solutions,Helm Chart,User Guide",
@@ -7866,7 +7884,7 @@
 		"uri":"cce_10_0420.html",
 		"node_id":"cce_10_0420.xml",
 		"product_code":"cce",
-		"code":"437",
+		"code":"438",
 		"des":"The Kubernetes cluster created on CCE has been connected to kubectl. For details, see Procedure.This section uses Helm v2.17.0 as an example.For other versions, visit htt",
 		"doc_type":"usermanual2",
 		"kw":"Deploying an Application Through the Helm v2 Client,Helm Chart,User Guide",
@@ -7884,7 +7902,7 @@
 		"uri":"cce_10_0144.html",
 		"node_id":"cce_10_0144.xml",
 		"product_code":"cce",
-		"code":"438",
+		"code":"439",
 		"des":"The Kubernetes cluster created on CCE has been connected to kubectl. For details, see Procedure.To pull a public image when deploying Helm, ensure an EIP has been bound t",
 		"doc_type":"usermanual2",
 		"kw":"Deploying an Application Through the Helm v3 Client,Helm Chart,User Guide",
@@ -7902,7 +7920,7 @@
 		"uri":"cce_10_0422.html",
 		"node_id":"cce_10_0422.xml",
 		"product_code":"cce",
-		"code":"439",
+		"code":"440",
 		"des":"CCE fully supports Helm v3. This section guides you to convert a Helm v2 release to Helm v3. Helm v3 discards or reconstructs some Helm v2 functions at the bottom layer. ",
 		"doc_type":"usermanual2",
 		"kw":"Converting a Release from Helm v2 to v3,Helm Chart,User Guide",
@@ -7920,7 +7938,7 @@
 		"uri":"cce_10_0164.html",
 		"node_id":"cce_10_0164.xml",
 		"product_code":"cce",
-		"code":"440",
+		"code":"441",
 		"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
 		"doc_type":"usermanual2",
 		"kw":"Permissions",
@@ -7938,7 +7956,7 @@
 		"uri":"cce_10_0187.html",
 		"node_id":"cce_10_0187.xml",
 		"product_code":"cce",
-		"code":"441",
+		"code":"442",
 		"des":"CCE permissions management allows you to assign permissions to IAM users and user groups under your tenant accounts. CCE combines the advantages of Identity and Access Ma",
 		"doc_type":"usermanual2",
 		"kw":"Permissions Overview,Permissions,User Guide",
@@ -7956,7 +7974,7 @@
 		"uri":"cce_10_0188.html",
 		"node_id":"cce_10_0188.xml",
 		"product_code":"cce",
-		"code":"442",
+		"code":"443",
 		"des":"CCE cluster-level permissions are assigned based on IAM system policies and custom policies. You can use user groups to assign permissions to IAM users.Cluster permission",
 		"doc_type":"usermanual2",
 		"kw":"Granting Cluster Permissions to an IAM User,Permissions,User Guide",
@@ -7974,7 +7992,7 @@
 		"uri":"cce_10_0189.html",
 		"node_id":"cce_10_0189.xml",
 		"product_code":"cce",
-		"code":"443",
+		"code":"444",
 		"des":"You can regulate users' or user groups' access to Kubernetes resources in a single namespace based on their Kubernetes RBAC roles. The RBAC API declares four kinds of Kub",
 		"doc_type":"usermanual2",
 		"kw":"Namespace Permissions (Kubernetes RBAC-based),Permissions,User Guide",
@@ -7988,24 +8006,6 @@
 		"title":"Namespace Permissions (Kubernetes RBAC-based)",
 		"githuburl":""
 	},
-	{
-		"uri":"cce_10_0957.html",
-		"node_id":"cce_10_0957.xml",
-		"product_code":"cce",
-		"code":"444",
-		"des":"Before assigning permissions to users or user groups, you need to review the information provided in Namespace Permissions (Kubernetes RBAC-based).To use an access policy",
-		"doc_type":"usermanual2",
-		"kw":"Using the AccessPolicy API to Manage Namespace Permissions (Kubernetes RBAC-based),Permissions,User ",
-		"search_title":"",
-		"metedata":[
-			{
-				"prodname":"cce",
-				"documenttype":"usermanual"
-			}
-		],
-		"title":"Using the AccessPolicy API to Manage Namespace Permissions (Kubernetes RBAC-based)",
-		"githuburl":""
-	},
 	{
 		"uri":"cce_10_0245.html",
 		"node_id":"cce_10_0245.xml",
@@ -8913,7 +8913,7 @@
 		"node_id":"cce_bestpractice_0333.xml",
 		"product_code":"cce",
 		"code":"495",
-		"des":"A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK and SK. This h",
+		"des":"A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK/SK. This helps",
 		"doc_type":"usermanual2",
 		"kw":"Configuration Suggestions on CCE Workload Identity Security,Security,User Guide",
 		"search_title":"",
@@ -9651,7 +9651,7 @@
 		"node_id":"cce_bestpractice_00227.xml",
 		"product_code":"cce",
 		"code":"536",
-		"des":"To access a Kubernetes cluster from a client, you can use the Kubernetes command line tool kubectl.Create a daemonSet file.vi daemonSet.yamlAn example YAML file is provid",
+		"des":"To access a Kubernetes cluster from a client, you can use the Kubernetes command line tool kubectl.Create a DaemonSet file.vi daemonset.yamlAn example YAML file is provid",
 		"doc_type":"usermanual2",
 		"kw":"Modifying Kernel Parameters Using a Privileged Container,Container,User Guide",
 		"search_title":"",
@@ -10316,7 +10316,7 @@
 		"node_id":"cce_faq_00020.xml",
 		"product_code":"cce",
 		"code":"573",
-		"des":"SymptomA node is running properly and has GPU resources. However, the following error information is displayed:0/9 nodes are available: 9 insufficient nvidia.com/gpuAnaly",
+		"des":"SymptomA node is running properly and has GPU resources. However, the following error information is displayed:0/9 nodes are available: 9 insufficient nvida.com/gpuAnalys",
 		"doc_type":"usermanual2",
 		"kw":"How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?,Node Runn",
 		"search_title":"",
diff --git a/docs/cce/umn/CLASS.TXT.json b/docs/cce/umn/CLASS.TXT.json
index fb404e7d7..c5a951c1d 100644
--- a/docs/cce/umn/CLASS.TXT.json
+++ b/docs/cce/umn/CLASS.TXT.json
@@ -134,6 +134,15 @@
 		"p_code":"13",
 		"code":"15"
 	},
+	{
+		"desc":"NVIDIA Container Toolkit is an open-source tool package from NVIDIA. It allows you to use NVIDIA GPUs to speed up computing in a containerized environment. The toolkit in",
+		"product_code":"cce",
+		"title":"Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267)",
+		"uri":"CVE-2025-23266.html",
+		"doc_type":"usermanual2",
+		"p_code":"15",
+		"code":"16"
+	},
 	{
 		"desc":"High-risk vulnerabilities:CCE fixes vulnerabilities as soon as possible after the Kubernetes community detects them and releases fixing solutions. The fixing policies are",
 		"product_code":"cce",
@@ -141,7 +150,7 @@
 		"uri":"cce_bulletin_0011.html",
 		"doc_type":"usermanual2",
 		"p_code":"15",
-		"code":"16"
+		"code":"17"
 	},
 	{
 		"desc":"Recently, a security research team disclosed a privilege escalation vulnerability (CVE-2021-4034, also dubbed PwnKit) in PolKit's pkexec. Unprivileged users can gain full",
@@ -150,7 +159,7 @@
 		"uri":"CVE-2021-4034.html",
 		"doc_type":"usermanual2",
 		"p_code":"15",
-		"code":"17"
+		"code":"18"
 	},
 	{
 		"desc":"The Linux Kernel SACK vulnerabilities have been fixed. This section describes the solution to these vulnerabilities.On June 18, 2019, Red Hat released a security notice, ",
@@ -159,7 +168,7 @@
 		"uri":"cce_bulletin_0206.html",
 		"doc_type":"usermanual2",
 		"p_code":"15",
-		"code":"18"
+		"code":"19"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -168,7 +177,7 @@
 		"uri":"cce_qs_0000.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"19"
+		"code":"20"
 	},
 	{
 		"desc":"This section describes how to use Cloud Container Engine (CCE) and provides frequently asked questions (FAQs) to help you quickly get started with CCE.Complete the follow",
@@ -176,8 +185,8 @@
 		"title":"Introduction",
 		"uri":"cce_qs_0001.html",
 		"doc_type":"usermanual2",
-		"p_code":"19",
-		"code":"20"
+		"p_code":"20",
+		"code":"21"
 	},
 	{
 		"desc":"Before using CCE, make the following preparations:Creating an IAM userObtaining Resource Permissions(Optional) Creating a VPC(Optional) Creating a Key PairIf you want to ",
@@ -185,8 +194,8 @@
 		"title":"Preparations",
 		"uri":"cce_qs_0006.html",
 		"doc_type":"usermanual2",
-		"p_code":"19",
-		"code":"21"
+		"p_code":"20",
+		"code":"22"
 	},
 	{
 		"desc":"This section describes how to quickly create a CCE cluster. In this example, the default or simple configurations are in use.If you have no clusters, click Create Cluster",
@@ -194,8 +203,8 @@
 		"title":"Creating a Kubernetes Cluster",
 		"uri":"cce_qs_0008.html",
 		"doc_type":"usermanual2",
-		"p_code":"19",
-		"code":"22"
+		"p_code":"20",
+		"code":"23"
 	},
 	{
 		"desc":"You can use images to quickly create a single-pod workload that can be accessed from public networks. This section describes how to use CCE to quickly deploy an Nginx app",
@@ -203,8 +212,8 @@
 		"title":"Deploying a Deployment (Nginx)",
 		"uri":"cce_qs_0003.html",
 		"doc_type":"usermanual2",
-		"p_code":"19",
-		"code":"23"
+		"p_code":"20",
+		"code":"24"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -212,8 +221,8 @@
 		"title":"Deploying WordPress and MySQL That Depend on Each Other",
 		"uri":"cce_qs_0007.html",
 		"doc_type":"usermanual2",
-		"p_code":"19",
-		"code":"24"
+		"p_code":"20",
+		"code":"25"
 	},
 	{
 		"desc":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser",
@@ -221,8 +230,8 @@
 		"title":"Overview",
 		"uri":"cce_qs_0009.html",
 		"doc_type":"usermanual2",
-		"p_code":"24",
-		"code":"25"
+		"p_code":"25",
+		"code":"26"
 	},
 	{
 		"desc":"WordPress must be used together with MySQL. WordPress runs the content management program while MySQL serves as a database to store data.You have created a CCE cluster th",
@@ -230,8 +239,8 @@
 		"title":"Step 1: Deploying MySQL",
 		"uri":"cce_qs_0004.html",
 		"doc_type":"usermanual2",
-		"p_code":"24",
-		"code":"26"
+		"p_code":"25",
+		"code":"27"
 	},
 	{
 		"desc":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser",
@@ -239,8 +248,8 @@
 		"title":"Step 2: Deploying WordPress",
 		"uri":"cce_qs_0005.html",
 		"doc_type":"usermanual2",
-		"p_code":"24",
-		"code":"27"
+		"p_code":"25",
+		"code":"28"
 	},
 	{
 		"desc":"During service deployment or running, you may trigger high-risk operations at different levels, causing service faults or interruption. To help you better estimate and av",
@@ -249,7 +258,7 @@
 		"uri":"cce_10_0054.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"28"
+		"code":"29"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -258,7 +267,7 @@
 		"uri":"cce_10_0091.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"29"
+		"code":"30"
 	},
 	{
 		"desc":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the entire lifecycle of containerized applications and delivers scalable,",
@@ -266,8 +275,8 @@
 		"title":"Cluster Overview",
 		"uri":"cce_10_0430.html",
 		"doc_type":"usermanual2",
-		"p_code":"29",
-		"code":"30"
+		"p_code":"30",
+		"code":"31"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -275,8 +284,8 @@
 		"title":"Cluster Version Release Notes",
 		"uri":"cce_10_0002.html",
 		"doc_type":"usermanual2",
-		"p_code":"29",
-		"code":"31"
+		"p_code":"30",
+		"code":"32"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -284,71 +293,71 @@
 		"title":"Kubernetes Version Release Notes",
 		"uri":"cce_10_0068.html",
 		"doc_type":"usermanual2",
-		"p_code":"31",
-		"code":"32"
-	},
-	{
-		"desc":"CCE allows you to create Kubernetes clusters 1.31. This section describes the changes made in Kubernetes 1.31.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
-		"product_code":"cce",
-		"title":"Kubernetes 1.31 Release Notes",
-		"uri":"cce_bulletin_0099.html",
-		"doc_type":"usermanual2",
 		"p_code":"32",
 		"code":"33"
 	},
 	{
-		"desc":"CCE allows you to create Kubernetes clusters 1.30. This section describes the changes made in Kubernetes 1.30.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
+		"desc":"CCE allows you to create Kubernetes 1.31 clusters. This section describes the changes made in Kubernetes 1.31.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
+		"product_code":"cce",
+		"title":"Kubernetes 1.31 Release Notes",
+		"uri":"cce_bulletin_0099.html",
+		"doc_type":"usermanual2",
+		"p_code":"33",
+		"code":"34"
+	},
+	{
+		"desc":"CCE allows you to create Kubernetes 1.30 clusters. This section describes the changes made in Kubernetes 1.30.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
 		"product_code":"cce",
 		"title":"Kubernetes 1.30 Release Notes",
 		"uri":"cce_bulletin_0095.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"34"
+		"p_code":"33",
+		"code":"35"
 	},
 	{
-		"desc":"CCE allows you to create Kubernetes clusters 1.29. This section describes the changes made in Kubernetes 1.29.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
+		"desc":"CCE allows you to create Kubernetes 1.29 clusters. This section describes the changes made in Kubernetes 1.29.New and Enhanced FeaturesAPI Changes and RemovalsIncompatibl",
 		"product_code":"cce",
 		"title":"Kubernetes 1.29 Release Notes",
 		"uri":"cce_bulletin_0089.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"35"
+		"p_code":"33",
+		"code":"36"
 	},
 	{
-		"desc":"CCE allows you to create Kubernetes clusters 1.28. This section describes the changes made in Kubernetes 1.28.Important NotesNew and Enhanced FeaturesAPI Changes and Remo",
+		"desc":"CCE allows you to create Kubernetes 1.28 clusters. This section describes the changes made in Kubernetes 1.28.Important NotesNew and Enhanced FeaturesAPI Changes and Remo",
 		"product_code":"cce",
 		"title":"Kubernetes 1.28 Release Notes",
 		"uri":"cce_bulletin_0068.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"36"
+		"p_code":"33",
+		"code":"37"
 	},
 	{
-		"desc":"CCE allows you to create Kubernetes clusters 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations and R",
+		"desc":"CCE allows you to create Kubernetes 1.27 clusters. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations and R",
 		"product_code":"cce",
 		"title":"Kubernetes 1.27 Release Notes",
 		"uri":"cce_bulletin_0059.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"37"
+		"p_code":"33",
+		"code":"38"
 	},
 	{
 		"desc":"This section describes the changes made in Kubernetes 1.25 compared with Kubernetes 1.23.New FeaturesDeprecations and RemovalsEnhanced Kubernetes 1.25 on CCEReferencesKub",
 		"product_code":"cce",
-		"title":"Kubernetes 1.25 Release Notes",
+		"title":"Kubernetes 1.25 (EOM) Release Notes",
 		"uri":"cce_bulletin_0058.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"38"
+		"p_code":"33",
+		"code":"39"
 	},
 	{
 		"desc":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes v1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, an",
 		"product_code":"cce",
-		"title":"Kubernetes 1.23 Release Notes",
+		"title":"Kubernetes 1.23 (EOM) Release Notes",
 		"uri":"cce_bulletin_0027.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"39"
+		"p_code":"33",
+		"code":"40"
 	},
 	{
 		"desc":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes v1.21 Release NotesCronJob is now in the stable state, and the version number changes to batch/v1.The",
@@ -356,8 +365,8 @@
 		"title":"Kubernetes 1.21 (EOM) Release Notes",
 		"uri":"cce_bulletin_0026.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"40"
+		"p_code":"33",
+		"code":"41"
 	},
 	{
 		"desc":"This section describes the updates in CCE Kubernetes 1.19.Kubernetes v1.19 Release NotesvSphere in-tree volumes can be migrated to vSphere CSI drivers. The in-tree vSpher",
@@ -365,8 +374,8 @@
 		"title":"Kubernetes 1.19 (EOM) Release Notes",
 		"uri":"cce_whsnew_0010.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"41"
+		"p_code":"33",
+		"code":"42"
 	},
 	{
 		"desc":"This section describes the updates in CCE Kubernetes 1.17.All resources in the apps/v1beta1 and apps/v1beta2 API versions are no longer served. Migrate to use the apps/v1",
@@ -374,8 +383,8 @@
 		"title":"Kubernetes 1.17 (EOM) Release Notes",
 		"uri":"cce_whsnew_0007.html",
 		"doc_type":"usermanual2",
-		"p_code":"32",
-		"code":"42"
+		"p_code":"33",
+		"code":"43"
 	},
 	{
 		"desc":"In CCE clusters of v1.25, containerd is the default runtime for nodes, except for nodes running EulerOS 2.5. In addition, clusters of v1.25 or later no longer support Eul",
@@ -383,8 +392,8 @@
 		"title":"Patch Version Release Notes",
 		"uri":"cce_10_0405.html",
 		"doc_type":"usermanual2",
-		"p_code":"31",
-		"code":"43"
+		"p_code":"32",
+		"code":"44"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -392,8 +401,8 @@
 		"title":"Creating a Cluster",
 		"uri":"cce_10_0298.html",
 		"doc_type":"usermanual2",
-		"p_code":"29",
-		"code":"44"
+		"p_code":"30",
+		"code":"45"
 	},
 	{
 		"desc":"CCE provides different types of clusters for you to select. The following table lists the differences between them.",
@@ -401,8 +410,8 @@
 		"title":"Comparison Between Cluster Types",
 		"uri":"cce_10_0342.html",
 		"doc_type":"usermanual2",
-		"p_code":"44",
-		"code":"45"
+		"p_code":"45",
+		"code":"46"
 	},
 	{
 		"desc":"On the CCE console, you can easily create Kubernetes clusters. After a cluster is created, the master node is hosted by CCE. You only need to create worker nodes. In this",
@@ -410,8 +419,8 @@
 		"title":"Creating a CCE Standard/Turbo Cluster",
 		"uri":"cce_10_0028.html",
 		"doc_type":"usermanual2",
-		"p_code":"44",
-		"code":"46"
+		"p_code":"45",
+		"code":"47"
 	},
 	{
 		"desc":"kube-proxy is a key component of a Kubernetes cluster. It is used for load balancing and forwarding data between a Service and its backend pods.CCE supports the iptables ",
@@ -419,8 +428,8 @@
 		"title":"Comparing iptables and IPVS",
 		"uri":"cce_10_0349.html",
 		"doc_type":"usermanual2",
-		"p_code":"44",
-		"code":"47"
+		"p_code":"45",
+		"code":"48"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -428,8 +437,8 @@
 		"title":"Connecting to a Cluster",
 		"uri":"cce_10_0140.html",
 		"doc_type":"usermanual2",
-		"p_code":"29",
-		"code":"48"
+		"p_code":"30",
+		"code":"49"
 	},
 	{
 		"desc":"kubectl is a command-line tool provided by Kubernetes, enabling you to manage cluster resources, view cluster status, deploy applications, and debug issues through the CL",
@@ -437,8 +446,8 @@
 		"title":"Accessing a Cluster Using kubectl",
 		"uri":"cce_10_0107.html",
 		"doc_type":"usermanual2",
-		"p_code":"48",
-		"code":"49"
+		"p_code":"49",
+		"code":"50"
 	},
 	{
 		"desc":"X.509 certificates are essential for verifying identities and encrypting communication within CCE clusters. These certificates enable authorized clients to access target ",
@@ -446,8 +455,8 @@
 		"title":"Accessing a Cluster Using an X.509 Certificate",
 		"uri":"cce_10_0175.html",
 		"doc_type":"usermanual2",
-		"p_code":"48",
-		"code":"50"
+		"p_code":"49",
+		"code":"51"
 	},
 	{
 		"desc":"Subject Alternative Name (SAN) enables certificates to be associated with multiple values, including IP addresses and domain names. A SAN is usually used by the client to",
@@ -455,8 +464,8 @@
 		"title":"Accessing a Cluster Using a Custom Domain Name",
 		"uri":"cce_10_0367.html",
 		"doc_type":"usermanual2",
-		"p_code":"48",
-		"code":"51"
+		"p_code":"49",
+		"code":"52"
 	},
 	{
 		"desc":"You can bind an EIP to an API server of a Kubernetes cluster so that the API server can access the Internet.Binding an EIP to an API server for Internet access can pose a",
@@ -464,8 +473,8 @@
 		"title":"Configuring a Cluster's API Server for Internet Access",
 		"uri":"cce_10_0864.html",
 		"doc_type":"usermanual2",
-		"p_code":"48",
-		"code":"52"
+		"p_code":"49",
+		"code":"53"
 	},
 	{
 		"desc":"In multi-tenant scenarios, CCE generates a unique credential (such as a kubeconfig file or an X.509 certificate) for each user to access their designated cluster. These c",
@@ -473,8 +482,8 @@
 		"title":"Revoking a Cluster Access Credential",
 		"uri":"cce_10_0744.html",
 		"doc_type":"usermanual2",
-		"p_code":"48",
-		"code":"53"
+		"p_code":"49",
+		"code":"54"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -482,8 +491,8 @@
 		"title":"Managing a Cluster",
 		"uri":"cce_10_0031.html",
 		"doc_type":"usermanual2",
-		"p_code":"29",
-		"code":"54"
+		"p_code":"30",
+		"code":"55"
 	},
 	{
 		"desc":"Cluster configuration parameters are underlying rules that define node behavior, resource allocation, communication rules, and scaling policies in a distributed system. T",
@@ -491,8 +500,8 @@
 		"title":"Modifying Cluster Configurations",
 		"uri":"cce_10_0213.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"55"
+		"p_code":"55",
+		"code":"56"
 	},
 	{
 		"desc":"Cluster overload occurs when system load such as request volume or resource usage exceeds the system's processing capacity, leading to degraded performance or system fail",
@@ -500,8 +509,8 @@
 		"title":"Enabling Overload Control for a Cluster",
 		"uri":"cce_10_0602.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"56"
+		"p_code":"55",
+		"code":"57"
 	},
 	{
 		"desc":"A cluster scale specifies the maximum number of nodes a cluster can manage. If the current cluster scale cannot meet your requirements, you can scale it out.A cluster tha",
@@ -509,8 +518,8 @@
 		"title":"Changing a Cluster Scale",
 		"uri":"cce_10_0403.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"57"
+		"p_code":"55",
+		"code":"58"
 	},
 	{
 		"desc":"When creating a cluster, you can customize a node security group to centrally manage network security policies. For a created cluster, you can change its default node sec",
@@ -518,8 +527,8 @@
 		"title":"Changing the Default Security Group of a Node",
 		"uri":"cce_10_0426.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"58"
+		"p_code":"55",
+		"code":"59"
 	},
 	{
 		"desc":"Deleting a cluster will delete the workloads and Services in the cluster, and the deleted data cannot be recovered. Before performing this operation, ensure that related ",
@@ -527,8 +536,8 @@
 		"title":"Deleting a Cluster",
 		"uri":"cce_10_0212.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"59"
+		"p_code":"55",
+		"code":"60"
 	},
 	{
 		"desc":"Unexpected deletion of clusters can occur in practice, especially when multiple users share an account and accidentally delete clusters that do not belong to them. To pre",
@@ -536,8 +545,8 @@
 		"title":"Preventing Cluster Deletion",
 		"uri":"cce_10_0927.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"60"
+		"p_code":"55",
+		"code":"61"
 	},
 	{
 		"desc":"If a cluster is not needed temporarily, hibernate it to reduce costs.After a cluster is hibernated, resources such as workloads cannot be created or managed in the cluste",
@@ -545,8 +554,8 @@
 		"title":"Hibernating or Waking Up a Cluster",
 		"uri":"cce_10_0214.html",
 		"doc_type":"usermanual2",
-		"p_code":"54",
-		"code":"61"
+		"p_code":"55",
+		"code":"62"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -554,8 +563,8 @@
 		"title":"Upgrading a Cluster",
 		"uri":"cce_10_0215.html",
 		"doc_type":"usermanual2",
-		"p_code":"29",
-		"code":"62"
+		"p_code":"30",
+		"code":"63"
 	},
 	{
 		"desc":"CCE strictly complies with community consistency authentication. It releases three Kubernetes versions each year and offers a maintenance period of at least 24 months aft",
@@ -563,8 +572,8 @@
 		"title":"Cluster Upgrade Overview",
 		"uri":"cce_10_0197.html",
 		"doc_type":"usermanual2",
-		"p_code":"62",
-		"code":"63"
+		"p_code":"63",
+		"code":"64"
 	},
 	{
 		"desc":"Before the upgrade, you can check whether your cluster can be upgraded and which versions are available on the CCE console. For details, see Cluster Upgrade Overview.Befo",
@@ -572,8 +581,8 @@
 		"title":"Before You Start",
 		"uri":"cce_10_0302.html",
 		"doc_type":"usermanual2",
-		"p_code":"62",
-		"code":"64"
+		"p_code":"63",
+		"code":"65"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -581,8 +590,8 @@
 		"title":"Performing Post-Upgrade Verification",
 		"uri":"cce_10_0560.html",
 		"doc_type":"usermanual2",
-		"p_code":"62",
-		"code":"65"
+		"p_code":"63",
+		"code":"66"
 	},
 	{
 		"desc":"After a cluster is upgraded, check whether the cluster is in the Running state.CCE automatically checks your cluster status. Go to the cluster list page and confirm the c",
@@ -590,8 +599,8 @@
 		"title":"Cluster Status Check",
 		"uri":"cce_10_0568.html",
 		"doc_type":"usermanual2",
-		"p_code":"65",
-		"code":"66"
+		"p_code":"66",
+		"code":"67"
 	},
 	{
 		"desc":"After a cluster is upgraded, check whether nodes in the cluster are in the Running state.CCE automatically checks your node statuses. Go to the node list page and confirm",
@@ -599,8 +608,8 @@
 		"title":"Node Status Check",
 		"uri":"cce_10_0569.html",
 		"doc_type":"usermanual2",
-		"p_code":"65",
-		"code":"67"
+		"p_code":"66",
+		"code":"68"
 	},
 	{
 		"desc":"After a cluster is upgraded, check whether there are any nodes that skip the upgrade in the cluster. These nodes may affect the proper running of the cluster.CCE automati",
@@ -608,8 +617,8 @@
 		"title":"Node Skipping Check",
 		"uri":"cce_10_0567.html",
 		"doc_type":"usermanual2",
-		"p_code":"65",
-		"code":"68"
+		"p_code":"66",
+		"code":"69"
 	},
 	{
 		"desc":"After a cluster is upgraded, check whether its services are running properly.Different services have different verification mode. Select a suitable one and verify the ser",
@@ -617,8 +626,8 @@
 		"title":"Service Check",
 		"uri":"cce_10_0561.html",
 		"doc_type":"usermanual2",
-		"p_code":"65",
-		"code":"69"
+		"p_code":"66",
+		"code":"70"
 	},
 	{
 		"desc":"Check whether nodes can be created in the cluster.If nodes cannot be created in your cluster after the cluster is upgraded, contact technical support.",
@@ -626,8 +635,8 @@
 		"title":"New Node Check",
 		"uri":"cce_10_0565.html",
 		"doc_type":"usermanual2",
-		"p_code":"65",
-		"code":"70"
+		"p_code":"66",
+		"code":"71"
 	},
 	{
 		"desc":"Check whether pods can be created on the existing nodes after the cluster is upgraded.Check whether pods can be created on new nodes after the cluster is upgraded.After c",
@@ -635,8 +644,8 @@
 		"title":"New Pod Check",
 		"uri":"cce_10_0566.html",
 		"doc_type":"usermanual2",
-		"p_code":"65",
-		"code":"71"
+		"p_code":"66",
+		"code":"72"
 	},
 	{
 		"desc":"This section describes how to migrate services from a cluster of an earlier version to a cluster of a later version in CCE.This operation is applicable when a cross-versi",
@@ -644,8 +653,8 @@
 		"title":"Migrating Services Across Clusters of Different Versions",
 		"uri":"cce_10_0210.html",
 		"doc_type":"usermanual2",
-		"p_code":"62",
-		"code":"72"
+		"p_code":"63",
+		"code":"73"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -653,8 +662,8 @@
 		"title":"Troubleshooting for Pre-upgrade Check Exceptions",
 		"uri":"cce_10_0550.html",
 		"doc_type":"usermanual2",
-		"p_code":"62",
-		"code":"73"
+		"p_code":"63",
+		"code":"74"
 	},
 	{
 		"desc":"The system automatically checks a cluster before its upgrade. If the cluster does not meet the pre-upgrade check conditions, the upgrade cannot continue. To avoid risks, ",
@@ -662,8 +671,8 @@
 		"title":"Pre-upgrade Check",
 		"uri":"cce_10_0549.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"74"
+		"p_code":"74",
+		"code":"75"
 	},
 	{
 		"desc":"Check the following items:Check whether the node is available.Check whether the node OS supports the upgrade.Check whether the node is marked with unexpected node pool la",
@@ -671,8 +680,8 @@
 		"title":"Node Restrictions",
 		"uri":"cce_10_0431.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"75"
+		"p_code":"74",
+		"code":"76"
 	},
 	{
 		"desc":"Check whether the target cluster is under upgrade management.CCE may temporarily restrict the cluster upgrade due to the following reasons:The cluster is identified as th",
@@ -680,8 +689,8 @@
 		"title":"Upgrade Management",
 		"uri":"cce_10_0432.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"76"
+		"p_code":"74",
+		"code":"77"
 	},
 	{
 		"desc":"Check the following items:Check whether the add-on status is normal.Check whether the add-on supports the target version.Scenario 1: The add-on malfunctions.Log in to the",
@@ -689,8 +698,8 @@
 		"title":"Add-ons",
 		"uri":"cce_10_0433.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"77"
+		"p_code":"74",
+		"code":"78"
 	},
 	{
 		"desc":"Check whether the current HelmRelease record contains discarded Kubernetes APIs that are not supported by the target cluster version. If yes, the Helm chart may be unavai",
@@ -698,8 +707,8 @@
 		"title":"Helm Charts",
 		"uri":"cce_10_0434.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"78"
+		"p_code":"74",
+		"code":"79"
 	},
 	{
 		"desc":"Check whether your master nodes can be accessed using SSH.There is a low probability that the SSH connectivity check fails due to network fluctuations. Perform the pre-up",
@@ -707,8 +716,8 @@
 		"title":"SSH Connectivity of Master Nodes",
 		"uri":"cce_10_0435.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"79"
+		"p_code":"74",
+		"code":"80"
 	},
 	{
 		"desc":"Check the node pool status.Check whether the node pool OS or container runtime is supported after the upgrade.Scenario: The node pool malfunctions.Log in to the CCE conso",
@@ -716,8 +725,8 @@
 		"title":"Node Pools",
 		"uri":"cce_10_0436.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"80"
+		"p_code":"74",
+		"code":"81"
 	},
 	{
 		"desc":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group rule with the source IP address set to the master ",
@@ -725,8 +734,8 @@
 		"title":"Security Groups",
 		"uri":"cce_10_0437.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"81"
+		"p_code":"74",
+		"code":"82"
 	},
 	{
 		"desc":"Check whether nodes need to be migrated.This issue is caused by either an error in the node's package pull component or the absence of key system components on the node, ",
@@ -734,8 +743,8 @@
 		"title":"Residual Nodes",
 		"uri":"cce_10_0439.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"82"
+		"p_code":"74",
+		"code":"83"
 	},
 	{
 		"desc":"Check whether there are discarded resources in the clusters.Scenario 1: The Service in the clusters of v1.25 or later has discarded annotation tolerate-unready-endpoints.",
@@ -743,8 +752,8 @@
 		"title":"Discarded Kubernetes Resources",
 		"uri":"cce_10_0440.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"83"
+		"p_code":"74",
+		"code":"84"
 	},
 	{
 		"desc":"Read the version compatibility differences and ensure that they are not affected. The patch upgrade does not involve version compatibility differences.",
@@ -752,8 +761,8 @@
 		"title":"Compatibility Risks",
 		"uri":"cce_10_0441.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"84"
+		"p_code":"74",
+		"code":"85"
 	},
 	{
 		"desc":"Check whether cce-agent on the current node is of the latest version.Scenario 1: The error message \"you cce-agent no update, please restart it\" is displayed.This issue oc",
@@ -761,8 +770,8 @@
 		"title":"CCE Agent Versions",
 		"uri":"cce_10_0442.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"85"
+		"p_code":"74",
+		"code":"86"
 	},
 	{
 		"desc":"Check whether the node's CPU usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods to",
@@ -770,8 +779,8 @@
 		"title":"Node CPU Usage",
 		"uri":"cce_10_0443.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"86"
+		"p_code":"74",
+		"code":"87"
 	},
 	{
 		"desc":"Check the following items:Check whether the key CRD packageversions.version.cce.io of the cluster is deleted.Check whether the cluster key CRD network-attachment-definiti",
@@ -779,8 +788,8 @@
 		"title":"CRDs",
 		"uri":"cce_10_0444.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"87"
+		"p_code":"74",
+		"code":"88"
 	},
 	{
 		"desc":"Check the following items:Check whether the key data disks on the node meet the upgrade requirements.Check whether the /tmp directory has 500 MB available space.During th",
@@ -788,8 +797,8 @@
 		"title":"Node Disks",
 		"uri":"cce_10_0445.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"88"
+		"p_code":"74",
+		"code":"89"
 	},
 	{
 		"desc":"Check the following items:Check whether the DNS configuration of the current node can resolve the OBS address.Check whether the current node can access the OBS address of",
@@ -797,8 +806,8 @@
 		"title":"Node DNS",
 		"uri":"cce_10_0446.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"89"
+		"p_code":"74",
+		"code":"90"
 	},
 	{
 		"desc":"Check whether the owner and owner group of the files in the /var/paas directory used by the CCE are both paas.Scenario 1: The error message \"xx file permission has been c",
@@ -806,8 +815,8 @@
 		"title":"Node Key Directory File Permissions",
 		"uri":"cce_10_0447.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"90"
+		"p_code":"74",
+		"code":"91"
 	},
 	{
 		"desc":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node will be unavailable. Restore th",
@@ -815,8 +824,8 @@
 		"title":"kubelet",
 		"uri":"cce_10_0448.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"91"
+		"p_code":"74",
+		"code":"92"
 	},
 	{
 		"desc":"Check whether the node's memory usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods",
@@ -824,8 +833,8 @@
 		"title":"Node Memory",
 		"uri":"cce_10_0449.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"92"
+		"p_code":"74",
+		"code":"93"
 	},
 	{
 		"desc":"Check whether the clock synchronization server ntpd or chronyd of the node is running properly.Scenario 1: ntpd is running abnormally.Log in to the node and run the syste",
@@ -833,8 +842,8 @@
 		"title":"Node Clock Synchronization Server",
 		"uri":"cce_10_0450.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"93"
+		"p_code":"74",
+		"code":"94"
 	},
 	{
 		"desc":"Check whether the OS kernel version of the node is supported by CCE.Case 1: The node image is not a standard CCE image.CCE nodes run depending on the initial standard ker",
@@ -842,8 +851,8 @@
 		"title":"Node OS",
 		"uri":"cce_10_0451.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"94"
+		"p_code":"74",
+		"code":"95"
 	},
 	{
 		"desc":"Verify that the master nodes in your cluster have more than 2 CPU cores.The master nodes have only 2 CPU cores, which may lead to a cluster upgrade failure.Contact techni",
@@ -851,8 +860,8 @@
 		"title":"Node CPU Cores",
 		"uri":"cce_10_0452.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"95"
+		"p_code":"74",
+		"code":"96"
 	},
 	{
 		"desc":"Check whether the Python commands are available on a node.If the command output is not 0, the check fails.Reset the node or manually install Python before attempting the ",
@@ -860,8 +869,8 @@
 		"title":"Node Python Commands",
 		"uri":"cce_10_0453.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"96"
+		"p_code":"74",
+		"code":"97"
 	},
 	{
 		"desc":"Check whether the nodes in the cluster are ready.Scenario 1: The nodes are in the unavailable status.Log in to the CCE console and click the cluster name to access the cl",
@@ -869,8 +878,8 @@
 		"title":"Node Readiness",
 		"uri":"cce_10_0455.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"97"
+		"p_code":"74",
+		"code":"98"
 	},
 	{
 		"desc":"Check whether journald of a node is normal.Log in to the node and run the systemctl is-active systemd-journald command to obtain the running status of journald. If the co",
@@ -878,8 +887,8 @@
 		"title":"Node journald",
 		"uri":"cce_10_0456.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"98"
+		"p_code":"74",
+		"code":"99"
 	},
 	{
 		"desc":"Check whether the containerd.sock file is on the node. This file affects the startup of container runtime in the Euler OS.Scenario: The Docker used by the node is the cus",
@@ -887,8 +896,8 @@
 		"title":"containerd.sock",
 		"uri":"cce_10_0457.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"99"
+		"p_code":"74",
+		"code":"100"
 	},
 	{
 		"desc":"This check item is not typical and implies that an internal error was found during the pre-upgrade check.Perform the pre-upgrade check again.If it fails again, submit a s",
@@ -896,8 +905,8 @@
 		"title":"Internal Error",
 		"uri":"cce_10_0458.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"100"
+		"p_code":"74",
+		"code":"101"
 	},
 	{
 		"desc":"Check whether there are inaccessible mount points on the node.Scenario: There are inaccessible mount points on the node.If NFS (such as obsfs or SFS) is used by the node ",
@@ -905,8 +914,8 @@
 		"title":"Node Mount Points",
 		"uri":"cce_10_0459.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"101"
+		"p_code":"74",
+		"code":"102"
 	},
 	{
 		"desc":"Check whether the taint needed for cluster upgrade exists on the node.Scenario 1: The node is skipped during the cluster upgrade.If the version of the node is different f",
@@ -914,8 +923,8 @@
 		"title":"Kubernetes Node Taints",
 		"uri":"cce_10_0460.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"102"
+		"p_code":"74",
+		"code":"103"
 	},
 	{
 		"desc":"Check whether there are any compatibility restrictions on the current Everest add-on.There are compatibility restrictions on the current Everest add-on and it cannot be u",
@@ -923,8 +932,8 @@
 		"title":"Everest Restrictions",
 		"uri":"cce_10_0478.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"103"
+		"p_code":"74",
+		"code":"104"
 	},
 	{
 		"desc":"Check whether there are compatibility limitations between the current and target cce-controller-hpa add-on versions.There are compatibility limitations between the curren",
@@ -932,8 +941,8 @@
 		"title":"cce-hpa-controller Limitations",
 		"uri":"cce_10_0479.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"104"
+		"p_code":"74",
+		"code":"105"
 	},
 	{
 		"desc":"Check whether the current cluster version and the target version support enhanced CPU policy.Scenario: Only the current cluster version supports the enhanced CPU policy f",
@@ -941,8 +950,8 @@
 		"title":"Enhanced CPU Policies",
 		"uri":"cce_10_0480.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"105"
+		"p_code":"74",
+		"code":"106"
 	},
 	{
 		"desc":"Check whether the container runtime and network components on the worker nodes are healthy.Issue 1: CNI Agent is not active.If your cluster version is earlier than v1.17.",
@@ -950,8 +959,8 @@
 		"title":"Health of Worker Node Components",
 		"uri":"cce_10_0484.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"106"
+		"p_code":"74",
+		"code":"107"
 	},
 	{
 		"desc":"Check whether cluster components such as the Kubernetes component, container runtime component, and network component are running properly before the upgrade.Perform the ",
@@ -959,8 +968,8 @@
 		"title":"Health of Master Node Components",
 		"uri":"cce_10_0485.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"107"
+		"p_code":"74",
+		"code":"108"
 	},
 	{
 		"desc":"Check whether the resources of Kubernetes components, such as etcd and kube-controller-manager, exceed the upper limit.Solution 1: Reduce Kubernetes resources that are ne",
@@ -968,8 +977,8 @@
 		"title":"Memory Resource Limit of Kubernetes Components",
 		"uri":"cce_10_0486.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"108"
+		"p_code":"74",
+		"code":"109"
 	},
 	{
 		"desc":"The system scans the audit logs of the past day to check whether the user calls the deprecated APIs of the target Kubernetes version.Due to the limited time range of audi",
@@ -977,8 +986,8 @@
 		"title":"Discarded Kubernetes APIs",
 		"uri":"cce_10_0487.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"109"
+		"p_code":"74",
+		"code":"110"
 	},
 	{
 		"desc":"If IPv6 is enabled for a CCE Turbo cluster, check whether the target cluster version supports IPv6.CCE Turbo clusters support IPv6 since v1.23. This feature is available ",
@@ -986,8 +995,8 @@
 		"title":"IPv6 Support in CCE Turbo Clusters",
 		"uri":"cce_10_0488.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"110"
+		"p_code":"74",
+		"code":"111"
 	},
 	{
 		"desc":"Check whether NetworkManager of a node is normal.Log in to the node and run the systemctl is-active NetworkManager command to obtain the running status of NetworkManager.",
@@ -995,8 +1004,8 @@
 		"title":"NetworkManager",
 		"uri":"cce_10_0489.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"111"
+		"p_code":"74",
+		"code":"112"
 	},
 	{
 		"desc":"Check the ID file format.",
@@ -1004,8 +1013,8 @@
 		"title":"Node ID File",
 		"uri":"cce_10_0490.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"112"
+		"p_code":"74",
+		"code":"113"
 	},
 	{
 		"desc":"When you upgrade a cluster to v1.19 or later, the system checks whether the following configuration files have been modified on the backend:/opt/cloud/cce/kubernetes/kube",
@@ -1013,8 +1022,8 @@
 		"title":"Node Configuration Consistency",
 		"uri":"cce_10_0491.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"113"
+		"p_code":"74",
+		"code":"114"
 	},
 	{
 		"desc":"Check whether the configuration files of key components exist on the node.The following table lists the files to be checked.Reset the node. For details, see Resetting a N",
@@ -1022,8 +1031,8 @@
 		"title":"Node Configuration File",
 		"uri":"cce_10_0492.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"114"
+		"p_code":"74",
+		"code":"115"
 	},
 	{
 		"desc":"Check whether the current CoreDNS key configuration Corefile is different from the Helm release record. The difference may be overwritten during the add-on upgrade, affec",
@@ -1031,8 +1040,8 @@
 		"title":"CoreDNS Configuration Consistency",
 		"uri":"cce_10_0493.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"115"
+		"p_code":"74",
+		"code":"116"
 	},
 	{
 		"desc":"Check whether the sudo commands and sudo-related files of the node are working.Scenario 1: The sudo command fails to be executed.During the in-place cluster upgrade, the ",
@@ -1040,8 +1049,8 @@
 		"title":"sudo",
 		"uri":"cce_10_0494.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"116"
+		"p_code":"74",
+		"code":"117"
 	},
 	{
 		"desc":"Whether some key commands that the node upgrade depends on are workingScenario 1: Executing the package manager command failed.Executing the rpm or dpkg command failed. I",
@@ -1049,8 +1058,8 @@
 		"title":"Key Node Commands",
 		"uri":"cce_10_0495.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"117"
+		"p_code":"74",
+		"code":"118"
 	},
 	{
 		"desc":"Check whether the docker/containerd.sock file is directly mounted to the pods on a node. During an upgrade, Docker or containerd restarts and the sock file on the host ch",
@@ -1058,8 +1067,8 @@
 		"title":"Mounting of a Sock File on a Node",
 		"uri":"cce_10_0496.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"118"
+		"p_code":"74",
+		"code":"119"
 	},
 	{
 		"desc":"Check whether the certificate used by an HTTPS load balancer has been modified on ELB.The certificate referenced by an HTTPS ingress created on CCE is modified on the ELB",
@@ -1067,8 +1076,8 @@
 		"title":"HTTPS Load Balancer Certificate Consistency",
 		"uri":"cce_10_0497.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"119"
+		"p_code":"74",
+		"code":"120"
 	},
 	{
 		"desc":"Check whether the default mount directory and soft link on the node have been manually mounted or modified.Non-shared diskBy default, /var/lib/docker, containerd, or /mnt",
@@ -1076,8 +1085,8 @@
 		"title":"Node Mounting",
 		"uri":"cce_10_0498.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"120"
+		"p_code":"74",
+		"code":"121"
 	},
 	{
 		"desc":"Check whether user paas is allowed to log in to a node.Run the following command to check whether user paas is allowed to log in to a node:If the permissions assigned to ",
@@ -1085,8 +1094,8 @@
 		"title":"Login Permissions of User paas on a Node",
 		"uri":"cce_10_0499.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"121"
+		"p_code":"74",
+		"code":"122"
 	},
 	{
 		"desc":"Check whether the load balancer associated with a Service is allocated with a private IPv4 address.Solution 1: Delete the Service that is associated with a load balancer ",
@@ -1094,8 +1103,8 @@
 		"title":"Private IPv4 Addresses of Load Balancers",
 		"uri":"cce_10_0500.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"122"
+		"p_code":"74",
+		"code":"123"
 	},
 	{
 		"desc":"Check the historical upgrade records of the cluster and confirm that the current version of the cluster meets the requirements for upgrading to the target version.Upgradi",
@@ -1103,8 +1112,8 @@
 		"title":"Historical Upgrade Records",
 		"uri":"cce_10_0501.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"123"
+		"p_code":"74",
+		"code":"124"
 	},
 	{
 		"desc":"Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.The CIDR block of the management plane has been modifi",
@@ -1112,8 +1121,8 @@
 		"title":"CIDR Block of the Cluster Management Plane",
 		"uri":"cce_10_0502.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"124"
+		"p_code":"74",
+		"code":"125"
 	},
 	{
 		"desc":"CCE AI Suite (NVIDIA GPU) is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The driver of CCE AI Suite (NVIDIA GP",
@@ -1121,8 +1130,8 @@
 		"title":"CCE AI Suite (NVIDIA GPU)",
 		"uri":"cce_10_0503.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"125"
+		"p_code":"74",
+		"code":"126"
 	},
 	{
 		"desc":"Check whether the default system parameter settings on your nodes are modified.If the MTU value of the bond0 network on your BMS node is not the default value 1500, this ",
@@ -1130,8 +1139,8 @@
 		"title":"Nodes' System Parameters",
 		"uri":"cce_10_0504.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"126"
+		"p_code":"74",
+		"code":"127"
 	},
 	{
 		"desc":"Check whether there are residual package version data in the current cluster.A message is displayed indicating that there are residual 10.12.1.109 CRD resources in your c",
@@ -1139,8 +1148,8 @@
 		"title":"Residual Package Version Data",
 		"uri":"cce_10_0505.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"127"
+		"p_code":"74",
+		"code":"128"
 	},
 	{
 		"desc":"Check whether the commands required for the upgrade are available on the node.The cluster upgrade failure is typically caused by the lack of key node commands that are re",
@@ -1148,8 +1157,8 @@
 		"title":"Node Commands",
 		"uri":"cce_10_0506.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"128"
+		"p_code":"74",
+		"code":"129"
 	},
 	{
 		"desc":"Check whether swap has been enabled on CCE nodes.By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of disa",
@@ -1157,8 +1166,8 @@
 		"title":"Node Swap",
 		"uri":"cce_10_0507.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"129"
+		"p_code":"74",
+		"code":"130"
 	},
 	{
 		"desc":"Check item 1: Check whether there is an Nginx Ingress route whose ingress type is not specified (kubernetes.io/ingress.class: nginx is not added to annotations) in the cl",
@@ -1166,8 +1175,8 @@
 		"title":"NGINX Ingress Controller",
 		"uri":"cce_10_0508.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"130"
+		"p_code":"74",
+		"code":"131"
 	},
 	{
 		"desc":"Check whether the service pods running on a containerd node are restarted when containerd is upgraded.containerd on your node may need to be restarted. To minimize the im",
@@ -1175,8 +1184,8 @@
 		"title":"containerd Pod Restart Risks",
 		"uri":"cce_10_0510.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"131"
+		"p_code":"74",
+		"code":"132"
 	},
 	{
 		"desc":"Check whether the configuration of CCE AI Suite (NVIDIA GPU) in a cluster has been intrusively modified. If so, upgrading the cluster may fail.",
@@ -1184,8 +1193,8 @@
 		"title":"Key CCE AI Suite (NVIDIA GPU) Parameters",
 		"uri":"cce_10_0511.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"132"
+		"p_code":"74",
+		"code":"133"
 	},
 	{
 		"desc":"Check whether GPU service pods are rebuilt in a cluster when kubelet is restarted during the upgrade of the cluster.Upgrade the cluster when the impact on services is con",
@@ -1193,8 +1202,8 @@
 		"title":"GPU Pod Rebuild Risks",
 		"uri":"cce_10_0512.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"133"
+		"p_code":"74",
+		"code":"134"
 	},
 	{
 		"desc":"Check whether ELB listener access control has been configured using annotations for the Services in the current cluster.If so, check whether their configurations are corr",
@@ -1202,8 +1211,8 @@
 		"title":"ELB Listener Access Control",
 		"uri":"cce_10_0513.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"134"
+		"p_code":"74",
+		"code":"135"
 	},
 	{
 		"desc":"Check whether the flavor of the master nodes in the cluster is the same as the actual flavor of these nodes.This issue is typically caused by modifications made to the ma",
@@ -1211,8 +1220,8 @@
 		"title":"Master Node Flavor",
 		"uri":"cce_10_0514.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"135"
+		"p_code":"74",
+		"code":"136"
 	},
 	{
 		"desc":"Check whether the number of available IP addresses in the cluster subnet supports rolling upgrade.Rolling upgrade is not supported if there are not enough IP addresses in",
@@ -1220,8 +1229,8 @@
 		"title":"Subnet Quota of Master Nodes",
 		"uri":"cce_10_0515.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"136"
+		"p_code":"74",
+		"code":"137"
 	},
 	{
 		"desc":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If your node's runtime is not ",
@@ -1229,8 +1238,8 @@
 		"title":"Node Runtime",
 		"uri":"cce_10_0516.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"137"
+		"p_code":"74",
+		"code":"138"
 	},
 	{
 		"desc":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If your node pool's runtime is",
@@ -1238,8 +1247,8 @@
 		"title":"Node Pool Runtime",
 		"uri":"cce_10_0517.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"138"
+		"p_code":"74",
+		"code":"139"
 	},
 	{
 		"desc":"Check the number of images on your node. If there are more than 1000 images, it takes a long time for Docker to start, affecting the standard Docker output and functions ",
@@ -1247,8 +1256,8 @@
 		"title":"Number of Node Images",
 		"uri":"cce_10_0518.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"139"
+		"p_code":"74",
+		"code":"140"
 	},
 	{
 		"desc":"Check whether the target version supports secret encryption. If it does not, clusters that have this feature enabled cannot be upgraded to the target version.Secret encry",
@@ -1256,8 +1265,8 @@
 		"title":"Compatibility Check of Secret Encryption",
 		"uri":"cce_10_0520.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"140"
+		"p_code":"74",
+		"code":"141"
 	},
 	{
 		"desc":"Make sure that CCE AI Suite (NVIDIA GPU) and Ubuntu nodes are compatible before using them in a cluster. If the Ubuntu kernel is 5.15.0-113-generic, the driver of the GPU",
@@ -1265,8 +1274,8 @@
 		"title":"Compatibility Between the Ubuntu Kernel and GPU Driver",
 		"uri":"cce_10_0521.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"141"
+		"p_code":"74",
+		"code":"142"
 	},
 	{
 		"desc":"An unfinished drainage task is detected in the cluster, which may resume after the upgrade. If this happens, running pods will be evicted, which could impact your service",
@@ -1274,8 +1283,8 @@
 		"title":"Drainage Tasks",
 		"uri":"cce_10_0522.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"142"
+		"p_code":"74",
+		"code":"143"
 	},
 	{
 		"desc":"Check the number of image layers on your node. If there are more than 5000 layers, it will take a long time for Docker or containerd to start, affecting the stdout of Doc",
@@ -1283,8 +1292,8 @@
 		"title":"Image Layers on a Node",
 		"uri":"cce_10_0523.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"143"
+		"p_code":"74",
+		"code":"144"
 	},
 	{
 		"desc":"Check whether your cluster is eligible for a rolling upgrade. The result shows that the rolling upgrade is not supported.Rolling upgrades cannot be performed if the tenan",
@@ -1292,8 +1301,8 @@
 		"title":"Cluster Rolling Upgrade",
 		"uri":"cce_10_0524.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"144"
+		"p_code":"74",
+		"code":"145"
 	},
 	{
 		"desc":"Check whether the number of certificates on your node is greater than 1000. During an upgrade, certificate files will be processed in batches. An excessive number of cert",
@@ -1301,8 +1310,8 @@
 		"title":"Rotation Certificates",
 		"uri":"cce_10_0525.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"145"
+		"p_code":"74",
+		"code":"146"
 	},
 	{
 		"desc":"Check whether any modifications have been made to the listener, forwarding policy, forwarding rule, backend cloud server group, backend cloud server, or certificate confi",
@@ -1310,8 +1319,8 @@
 		"title":"Ingress and ELB Configuration Consistency",
 		"uri":"cce_10_0526.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"146"
+		"p_code":"74",
+		"code":"147"
 	},
 	{
 		"desc":"Check the network policy settings on the master nodes in your cluster. If any manual modifications have been made, they will be reset during the upgrade.Check whether net",
@@ -1319,8 +1328,8 @@
 		"title":"Network Policies of Cluster Network Components",
 		"uri":"cce_10_0527.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"147"
+		"p_code":"74",
+		"code":"148"
 	},
 	{
 		"desc":"Check whether the nic-max-above-warm-target value configured for the network component of the current cluster exceeds the maximum value allowed.Determine the scope of imp",
@@ -1328,8 +1337,8 @@
 		"title":"Cluster and Node Pool Configurations",
 		"uri":"cce_10_0528.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"148"
+		"p_code":"74",
+		"code":"149"
 	},
 	{
 		"desc":"Check whether the time zone of the master nodes matches the cluster's time zone. If they are different, the master nodes will be updated to match the cluster's time zone ",
@@ -1337,8 +1346,8 @@
 		"title":"Time Zone of Master Nodes",
 		"uri":"cce_10_0529.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"149"
+		"p_code":"74",
+		"code":"150"
 	},
 	{
 		"desc":"Check whether the SNATIPRanges value has changed after the upgrade. This check is available only for CCE Turbo clusters.In a CCE Turbo cluster, the CIDR blocks in SNATIPR",
@@ -1346,8 +1355,8 @@
 		"title":"SNATIPRanges",
 		"uri":"cce_10_0530.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"150"
+		"p_code":"74",
+		"code":"151"
 	},
 	{
 		"desc":"Manual modifications to add-on configuration parameters (typically ConfigMaps), instead of modifications through the CCE console or APIs, may be overwritten after an upgr",
@@ -1355,8 +1364,8 @@
 		"title":"Add-on Configuration Consistency",
 		"uri":"cce_10_0531.html",
 		"doc_type":"usermanual2",
-		"p_code":"73",
-		"code":"151"
+		"p_code":"74",
+		"code":"152"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1365,7 +1374,7 @@
 		"uri":"cce_10_0183.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"152"
+		"code":"153"
 	},
 	{
 		"desc":"A container cluster consists of a set of worker machines, called nodes, that run containerized applications. A node can be a virtual machine (VM) or a physical machine (P",
@@ -1373,8 +1382,8 @@
 		"title":"Node Overview",
 		"uri":"cce_10_0180.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"153"
+		"p_code":"153",
+		"code":"154"
 	},
 	{
 		"desc":"Container engines, one of the most important components of Kubernetes, manage the lifecycle of images and containers. The kubelet interacts with a container runtime throu",
@@ -1382,8 +1391,8 @@
 		"title":"Container Engines",
 		"uri":"cce_10_0462.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"154"
+		"p_code":"153",
+		"code":"155"
 	},
 	{
 		"desc":"This section describes the mappings between released cluster versions and OS versions.",
@@ -1391,8 +1400,8 @@
 		"title":"Node OSs",
 		"uri":"cce_10_0476.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"155"
+		"p_code":"153",
+		"code":"156"
 	},
 	{
 		"desc":"At least one cluster has been created.A key pair has been created for identity authentication upon remote node login.The DNS configuration of a subnet where a node is loc",
@@ -1400,8 +1409,8 @@
 		"title":"Creating a Node",
 		"uri":"cce_10_0363.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"156"
+		"p_code":"153",
+		"code":"157"
 	},
 	{
 		"desc":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.When accepting an ECS, you can reset the ECS OS to a standard ",
@@ -1409,8 +1418,8 @@
 		"title":"Accepting Nodes for Management",
 		"uri":"cce_10_0198.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"157"
+		"p_code":"153",
+		"code":"158"
 	},
 	{
 		"desc":"Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node.Before you log in to a node (an ECS) using SS",
@@ -1418,8 +1427,8 @@
 		"title":"Logging In to a Node",
 		"uri":"cce_10_0185.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"158"
+		"p_code":"153",
+		"code":"159"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1427,8 +1436,8 @@
 		"title":"Management Nodes",
 		"uri":"cce_10_0672.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"159"
+		"p_code":"153",
+		"code":"160"
 	},
 	{
 		"desc":"You can add different labels to nodes and define different attributes for labels. By using these node labels, you can quickly understand the characteristics of each node.",
@@ -1436,8 +1445,8 @@
 		"title":"Managing Node Labels",
 		"uri":"cce_10_0004.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"160"
+		"p_code":"160",
+		"code":"161"
 	},
 	{
 		"desc":"Taints enable a node to repel specific pods to prevent these pods from being scheduled to the node.On the CCE console, you can also batch manage nodes' taints.Enter the k",
@@ -1445,8 +1454,8 @@
 		"title":"Managing Node Taints",
 		"uri":"cce_10_0352.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"161"
+		"p_code":"160",
+		"code":"162"
 	},
 	{
 		"desc":"You can reset a node to modify the node configuration, such as the node OS and login mode.Resetting a node will reinstall the node OS and the Kubernetes software on the n",
@@ -1454,8 +1463,8 @@
 		"title":"Resetting a Node",
 		"uri":"cce_10_0003.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"162"
+		"p_code":"160",
+		"code":"163"
 	},
 	{
 		"desc":"Removing a node from a cluster will re-install the node OS and clear CCE components on the node.Removing a node will not delete the server corresponding to the node. You ",
@@ -1463,8 +1472,8 @@
 		"title":"Removing a Node",
 		"uri":"cce_10_0338.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"163"
+		"p_code":"160",
+		"code":"164"
 	},
 	{
 		"desc":"Each node in a cluster is a cloud server or physical machine. After a cluster node is created, you can change the cloud server name or specifications as required. Modifyi",
@@ -1472,8 +1481,8 @@
 		"title":"Synchronizing the Data of Cloud Servers",
 		"uri":"cce_10_0184.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"164"
+		"p_code":"160",
+		"code":"165"
 	},
 	{
 		"desc":"After you enable nodal drainage on the console, CCE configures the node to be non-schedulable and securely evicts all pods that comply with Rules for Draining Nodes on th",
@@ -1481,8 +1490,8 @@
 		"title":"Draining a Node",
 		"uri":"cce_10_0605.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"165"
+		"p_code":"160",
+		"code":"166"
 	},
 	{
 		"desc":"If a node is no longer needed, delete it from the node list on the CCE console if the node is billed on a pay-per-use basis. Do not manually remove nodes using kubectl de",
@@ -1490,8 +1499,8 @@
 		"title":"Deleting a Node",
 		"uri":"cce_10_0186.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"166"
+		"p_code":"160",
+		"code":"167"
 	},
 	{
 		"desc":"When a node in the cluster is stopped, all services on that node will also be stopped, and the node will no longer be available for scheduling. Check if your services wil",
@@ -1499,8 +1508,8 @@
 		"title":"Stopping a Node",
 		"uri":"cce_10_0036.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"167"
+		"p_code":"160",
+		"code":"168"
 	},
 	{
 		"desc":"In a rolling upgrade, a new node is created, existing workloads are migrated to the new node, and then the old node is deleted. Figure 1 shows the migration process.The o",
@@ -1508,8 +1517,8 @@
 		"title":"Performing Rolling Upgrade for Nodes",
 		"uri":"cce_10_0276.html",
 		"doc_type":"usermanual2",
-		"p_code":"159",
-		"code":"168"
+		"p_code":"160",
+		"code":"169"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1517,8 +1526,8 @@
 		"title":"Node O&M",
 		"uri":"cce_10_0704.html",
 		"doc_type":"usermanual2",
-		"p_code":"152",
-		"code":"169"
+		"p_code":"153",
+		"code":"170"
 	},
 	{
 		"desc":"Some node resources are used to run mandatory Kubernetes system components and resources to make the node as part of your cluster. Therefore, the total number of node res",
@@ -1526,8 +1535,8 @@
 		"title":"Node Resource Reservation Policy",
 		"uri":"cce_10_0178.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"170"
+		"p_code":"170",
+		"code":"171"
 	},
 	{
 		"desc":"This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.In clusters of a version earlier than v1.23.18-r",
@@ -1535,8 +1544,8 @@
 		"title":"Space Allocation of a Data Disk",
 		"uri":"cce_10_0341.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"171"
+		"p_code":"170",
+		"code":"172"
 	},
 	{
 		"desc":"The maximum number of pods that can be created on a node is calculated based on the cluster type:When creating a cluster in the VPC network model, follow the  and specify",
@@ -1544,8 +1553,8 @@
 		"title":"Maximum Number of Pods That Can Be Created on a Node",
 		"uri":"cce_10_0348.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"172"
+		"p_code":"170",
+		"code":"173"
 	},
 	{
 		"desc":"To maintain the stability of nodes, CCE stores Kubernetes and container runtime components on separate data disks. Kubernetes uses the /mnt/paas/kubernetes directory, and",
@@ -1553,8 +1562,8 @@
 		"title":"Differences in kubelet and Runtime Component Configurations Between CCE and the Native Community",
 		"uri":"cce_10_0883.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"173"
+		"p_code":"170",
+		"code":"174"
 	},
 	{
 		"desc":"As of Kubernetes v1.24, dockershim has been deprecated. To maintain compatibility and ensure continued support for future Kubernetes releases, switch your node's containe",
@@ -1562,8 +1571,8 @@
 		"title":"Migrating Nodes from Docker to containerd",
 		"uri":"cce_10_0601.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"174"
+		"p_code":"170",
+		"code":"175"
 	},
 	{
 		"desc":"The node fault detection function depends on the NPD add-on. The add-on instances run on nodes and monitor nodes. This section describes how to enable node fault detectio",
@@ -1571,8 +1580,8 @@
 		"title":"Configuring Node Fault Detection Policies",
 		"uri":"cce_10_0659.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"175"
+		"p_code":"170",
+		"code":"176"
 	},
 	{
 		"desc":"When creating a node, use the pre- or -installation commands to install tools or perform security hardening on the node. This section provides guidance for you to correct",
@@ -1580,8 +1589,8 @@
 		"title":"Executing the Pre- or Post-installation Commands During Node Creation",
 		"uri":"cce_bestpractice_10020.html",
 		"doc_type":"usermanual2",
-		"p_code":"169",
-		"code":"176"
+		"p_code":"170",
+		"code":"177"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1590,7 +1599,7 @@
 		"uri":"cce_10_0035.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"177"
+		"code":"178"
 	},
 	{
 		"desc":"CCE introduces node pools to help you better manage nodes in Kubernetes clusters. A node pool contains one node or a group of nodes with identical configuration in a clus",
@@ -1598,8 +1607,8 @@
 		"title":"Node Pool Overview",
 		"uri":"cce_10_0081.html",
 		"doc_type":"usermanual2",
-		"p_code":"177",
-		"code":"178"
+		"p_code":"178",
+		"code":"179"
 	},
 	{
 		"desc":"This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.Basic SettingsNo",
@@ -1607,8 +1616,8 @@
 		"title":"Creating a Node Pool",
 		"uri":"cce_10_0012.html",
 		"doc_type":"usermanual2",
-		"p_code":"177",
-		"code":"179"
+		"p_code":"178",
+		"code":"180"
 	},
 	{
 		"desc":"You can specify a specification in a node pool for scaling.The default node pool does not support scaling. Use Creating a Node to add a node.Resize: Add or reduce nodes f",
@@ -1616,8 +1625,8 @@
 		"title":"Scaling a Node Pool",
 		"uri":"cce_10_0658.html",
 		"doc_type":"usermanual2",
-		"p_code":"177",
-		"code":"180"
+		"p_code":"178",
+		"code":"181"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1625,8 +1634,8 @@
 		"title":"Managing a Node Pool",
 		"uri":"cce_10_0222.html",
 		"doc_type":"usermanual2",
-		"p_code":"177",
-		"code":"181"
+		"p_code":"178",
+		"code":"182"
 	},
 	{
 		"desc":"Changes to the container engine, OS, or pre-/post-installation script in a node pool take effect only on new nodes. To synchronize the modification onto existing nodes, m",
@@ -1634,8 +1643,8 @@
 		"title":"Updating a Node Pool",
 		"uri":"cce_10_0653.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"182"
+		"p_code":"182",
+		"code":"183"
 	},
 	{
 		"desc":"Auto Scaling (AS) enables elastic scaling of nodes in a node pool based on scaling policies. Without this function, you have to manually adjust the number of nodes in a n",
@@ -1643,8 +1652,8 @@
 		"title":"Updating an AS Configuration",
 		"uri":"cce_10_0727.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"183"
+		"p_code":"182",
+		"code":"184"
 	},
 	{
 		"desc":"The default node pool does not support the management operations described in this section.CCE allows you to highly customize Kubernetes parameter settings on core compon",
@@ -1652,8 +1661,8 @@
 		"title":"Modifying Node Pool Configurations",
 		"uri":"cce_10_0652.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"184"
+		"p_code":"182",
+		"code":"185"
 	},
 	{
 		"desc":"If you want to add a newly created ECS to a node pool in a cluster, or remove a node from a node pool and add it to the node pool again, accept the node.When an ECS is ac",
@@ -1661,8 +1670,8 @@
 		"title":"Accepting Nodes in a Node Pool",
 		"uri":"cce_10_0886.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"185"
+		"p_code":"182",
+		"code":"186"
 	},
 	{
 		"desc":"You can copy the configuration of an existing node pool on the CCE console to create new node pools.",
@@ -1670,8 +1679,8 @@
 		"title":"Copying a Node Pool",
 		"uri":"cce_10_0655.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"186"
+		"p_code":"182",
+		"code":"187"
 	},
 	{
 		"desc":"After the configuration of a node pool is updated, some configurations cannot be automatically synchronized for existing nodes. You can manually synchronize configuration",
@@ -1679,8 +1688,8 @@
 		"title":"Synchronizing Node Pools",
 		"uri":"cce_10_0654.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"187"
+		"p_code":"182",
+		"code":"188"
 	},
 	{
 		"desc":"After CCE releases a new OS image, if existing nodes cannot be automatically upgraded, you can manually upgrade them in batches.This section describes how to upgrade an O",
@@ -1688,8 +1697,8 @@
 		"title":"Upgrading an OS",
 		"uri":"cce_10_0660.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"188"
+		"p_code":"182",
+		"code":"189"
 	},
 	{
 		"desc":"You can migrate nodes between node pools within a cluster. Table 1 lists migration scenarios.Migration scenariosMigration ScenarioMigrationOperationSource Node PoolTarget",
@@ -1697,8 +1706,8 @@
 		"title":"Migrating a Node",
 		"uri":"cce_10_0656.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"189"
+		"p_code":"182",
+		"code":"190"
 	},
 	{
 		"desc":"Deleting a node pool will delete nodes in the pool. Pods on these nodes will be automatically migrated to available nodes in other node pools.Deleting a node pool will de",
@@ -1706,8 +1715,8 @@
 		"title":"Deleting a Node Pool",
 		"uri":"cce_10_0657.html",
 		"doc_type":"usermanual2",
-		"p_code":"181",
-		"code":"190"
+		"p_code":"182",
+		"code":"191"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1716,7 +1725,7 @@
 		"uri":"cce_10_0046.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"191"
+		"code":"192"
 	},
 	{
 		"desc":"A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is ",
@@ -1724,8 +1733,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0006.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"192"
+		"p_code":"192",
+		"code":"193"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1733,8 +1742,8 @@
 		"title":"Creating a Workload",
 		"uri":"cce_10_0673.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"193"
+		"p_code":"192",
+		"code":"194"
 	},
 	{
 		"desc":"Deployments are workloads (for example, Nginx) that do not store any data or status. You can create Deployments on the CCE console or by running kubectl commands.Before c",
@@ -1742,8 +1751,8 @@
 		"title":"Creating a Deployment",
 		"uri":"cce_10_0047.html",
 		"doc_type":"usermanual2",
-		"p_code":"193",
-		"code":"194"
+		"p_code":"194",
+		"code":"195"
 	},
 	{
 		"desc":"StatefulSets are a type of workloads whose data or status is stored while they are running. For example, MySQL is a StatefulSet because it needs to store new data.A conta",
@@ -1751,8 +1760,8 @@
 		"title":"Creating a StatefulSet",
 		"uri":"cce_10_0048.html",
 		"doc_type":"usermanual2",
-		"p_code":"193",
-		"code":"195"
+		"p_code":"194",
+		"code":"196"
 	},
 	{
 		"desc":"CCE provides deployment and management capabilities for multiple types of containers and supports features of container workloads, including creation, configuration, moni",
@@ -1760,8 +1769,8 @@
 		"title":"Creating a DaemonSet",
 		"uri":"cce_10_0216.html",
 		"doc_type":"usermanual2",
-		"p_code":"193",
-		"code":"196"
+		"p_code":"194",
+		"code":"197"
 	},
 	{
 		"desc":"Jobs are short-lived and run for a certain time to completion. They can be executed immediately after being deployed. It is completed after it exits normally (exit 0).A j",
@@ -1769,8 +1778,8 @@
 		"title":"Creating a Job",
 		"uri":"cce_10_0150.html",
 		"doc_type":"usermanual2",
-		"p_code":"193",
-		"code":"197"
+		"p_code":"194",
+		"code":"198"
 	},
 	{
 		"desc":"A CronJob runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A CronJob runs periodically at the specified time.",
@@ -1778,8 +1787,8 @@
 		"title":"Creating a CronJob",
 		"uri":"cce_10_0151.html",
 		"doc_type":"usermanual2",
-		"p_code":"193",
-		"code":"198"
+		"p_code":"194",
+		"code":"199"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1787,8 +1796,8 @@
 		"title":"Configuring a Workload",
 		"uri":"cce_10_0130.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"199"
+		"p_code":"192",
+		"code":"200"
 	},
 	{
 		"desc":"Compared with a common runtime, a secure runtime allows each container (pod) to run on its own micro-VM with a separate OS kernel. This ensures secure isolation at the vi",
@@ -1796,8 +1805,8 @@
 		"title":"Secure Runtime and Common Runtime",
 		"uri":"cce_10_0463.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"200"
+		"p_code":"200",
+		"code":"201"
 	},
 	{
 		"desc":"When creating a workload, you can configure containers to use the same time zone as the node. You can enable time zone synchronization when creating a workload.The time z",
@@ -1805,8 +1814,8 @@
 		"title":"Configuring Time Zone Synchronization",
 		"uri":"cce_10_0354.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"201"
+		"p_code":"200",
+		"code":"202"
 	},
 	{
 		"desc":"When a workload is created, the container image is pulled from the image repository to the node. The image is also pulled when the workload is restarted or upgraded.By de",
@@ -1814,8 +1823,8 @@
 		"title":"Configuring an Image Pull Policy",
 		"uri":"cce_10_0353.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"202"
+		"p_code":"200",
+		"code":"203"
 	},
 	{
 		"desc":"CCE allows you to create workloads using images pulled from third-party image repositories.Generally, a third-party image repository can be accessed only after authentica",
@@ -1823,8 +1832,8 @@
 		"title":"Using Third-Party Images",
 		"uri":"cce_10_0009.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"203"
+		"p_code":"200",
+		"code":"204"
 	},
 	{
 		"desc":"CCE allows you to set resource requirements and limits, such as CPU and RAM, for added containers during workload creation. Kubernetes also allows using YAML to set requi",
@@ -1832,8 +1841,8 @@
 		"title":"Configuring Container Specifications",
 		"uri":"cce_10_0163.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"204"
+		"p_code":"200",
+		"code":"205"
 	},
 	{
 		"desc":"CCE provides callback functions for the lifecycle management of containerized applications. For example, if you want a container to perform a certain operation before sto",
@@ -1841,8 +1850,8 @@
 		"title":"Configuring Container Lifecycle Parameters",
 		"uri":"cce_10_0105.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"205"
+		"p_code":"200",
+		"code":"206"
 	},
 	{
 		"desc":"Health check regularly checks the health status of containers during container running. If the health check function is not configured, a pod cannot detect application ex",
@@ -1850,8 +1859,8 @@
 		"title":"Configuring Container Health Check",
 		"uri":"cce_10_0112.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"206"
+		"p_code":"200",
+		"code":"207"
 	},
 	{
 		"desc":"An environment variable is a variable whose value can affect the way a running container will behave. You can modify environment variables even after workloads are deploy",
@@ -1859,8 +1868,8 @@
 		"title":"Configuring Environment Variables",
 		"uri":"cce_10_0113.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"207"
+		"p_code":"200",
+		"code":"208"
 	},
 	{
 		"desc":"In actual applications, upgrade is a common operation. A Deployment, StatefulSet, or DaemonSet can easily support application upgrade.You can set different upgrade polici",
@@ -1868,8 +1877,8 @@
 		"title":"Configuring Workload Upgrade Policies",
 		"uri":"cce_10_0397.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"208"
+		"p_code":"200",
+		"code":"209"
 	},
 	{
 		"desc":"Tolerations allow the scheduler to schedule pods to nodes with target taints. Tolerances work with node taints. Each node allows one or more taints. If no tolerance is co",
@@ -1877,8 +1886,8 @@
 		"title":"Configuring Tolerance Policies",
 		"uri":"cce_10_0728.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"209"
+		"p_code":"200",
+		"code":"210"
 	},
 	{
 		"desc":"CCE allows you to add annotations to a YAML file to realize some advanced pod functions. The following table describes the annotations you can add.When you create a workl",
@@ -1886,8 +1895,8 @@
 		"title":"Configuring Labels and Annotations",
 		"uri":"cce_10_0386.html",
 		"doc_type":"usermanual2",
-		"p_code":"199",
-		"code":"210"
+		"p_code":"200",
+		"code":"211"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1895,8 +1904,8 @@
 		"title":"Scheduling a Workload",
 		"uri":"cce_10_0889.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"211"
+		"p_code":"192",
+		"code":"212"
 	},
 	{
 		"desc":"Kubernetes schedules workloads based on pods. After you create a workload, the scheduler automatically assigns pods. For example, the scheduler distributes pods to nodes ",
@@ -1904,8 +1913,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0232.html",
 		"doc_type":"usermanual2",
-		"p_code":"211",
-		"code":"212"
+		"p_code":"212",
+		"code":"213"
 	},
 	{
 		"desc":"To select a node for scheduling in Kubernetes, simply configure the nodeSelector field in the workload. This field allows you to configure the label of the desired node t",
@@ -1913,8 +1922,8 @@
 		"title":"Configuring Specified Node Scheduling (nodeSelector)",
 		"uri":"cce_10_0891.html",
 		"doc_type":"usermanual2",
-		"p_code":"211",
-		"code":"213"
+		"p_code":"212",
+		"code":"214"
 	},
 	{
 		"desc":"Kubernetes can schedule workload pods to affinity nodes based on their labels and label values. For example, some nodes support GPU computing, and node affinity schedulin",
@@ -1922,8 +1931,8 @@
 		"title":"Configuring Node Affinity Scheduling (nodeAffinity)",
 		"uri":"cce_10_0892.html",
 		"doc_type":"usermanual2",
-		"p_code":"211",
-		"code":"214"
+		"p_code":"212",
+		"code":"215"
 	},
 	{
 		"desc":"Kubernetes offers workload affinity and anti-affinity scheduling, which allows for flexible scheduling of new workloads on either related or unrelated nodes. This results",
@@ -1931,17 +1940,17 @@
 		"title":"Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity)",
 		"uri":"cce_10_0893.html",
 		"doc_type":"usermanual2",
-		"p_code":"211",
-		"code":"215"
+		"p_code":"212",
+		"code":"216"
 	},
 	{
-		"desc":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.When kubectl is used in CloudShell, permissions are determined by",
+		"desc":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.The example output is as follows:NAME                            ",
 		"product_code":"cce",
 		"title":"Logging In to a Container",
 		"uri":"cce_10_00356.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"216"
+		"p_code":"192",
+		"code":"217"
 	},
 	{
 		"desc":"After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file.Workload/Job managementOperationDescriptionMo",
@@ -1949,8 +1958,8 @@
 		"title":"Managing Workloads",
 		"uri":"cce_10_0007.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"217"
+		"p_code":"192",
+		"code":"218"
 	},
 	{
 		"desc":"Custom Resource Definition (CRD) is an extension of Kubernetes APIs. When default Kubernetes resources cannot meet service requirements, you can use CRDs to define new re",
@@ -1958,8 +1967,8 @@
 		"title":"Managing Custom Resources",
 		"uri":"cce_10_0833.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"218"
+		"p_code":"192",
+		"code":"219"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1967,8 +1976,8 @@
 		"title":"Pod Security",
 		"uri":"cce_10_0465.html",
 		"doc_type":"usermanual2",
-		"p_code":"191",
-		"code":"219"
+		"p_code":"192",
+		"code":"220"
 	},
 	{
 		"desc":"A pod security policy (PSP) is a cluster-level resource that controls sensitive security aspects of the pod specification. The PodSecurityPolicy object in Kubernetes defi",
@@ -1976,8 +1985,8 @@
 		"title":"Configuring a Pod Security Policy",
 		"uri":"cce_10_0275.html",
 		"doc_type":"usermanual2",
-		"p_code":"219",
-		"code":"220"
+		"p_code":"220",
+		"code":"221"
 	},
 	{
 		"desc":"Before using pod security admission, understand Kubernetes Pod Security Standards. These standards define different isolation levels for pods. They let you define how you",
@@ -1985,8 +1994,8 @@
 		"title":"Configuring Pod Security Admission",
 		"uri":"cce_10_0466.html",
 		"doc_type":"usermanual2",
-		"p_code":"219",
-		"code":"221"
+		"p_code":"220",
+		"code":"222"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -1995,7 +2004,7 @@
 		"uri":"cce_10_0674.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"222"
+		"code":"223"
 	},
 	{
 		"desc":"CCE supports different types of resource scheduling and task scheduling, improving application performance and overall cluster resource utilization. This section describe",
@@ -2003,8 +2012,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0702.html",
 		"doc_type":"usermanual2",
-		"p_code":"222",
-		"code":"223"
+		"p_code":"223",
+		"code":"224"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2012,8 +2021,8 @@
 		"title":"CPU Scheduling",
 		"uri":"cce_10_0551.html",
 		"doc_type":"usermanual2",
-		"p_code":"222",
-		"code":"224"
+		"p_code":"223",
+		"code":"225"
 	},
 	{
 		"desc":"By default, kubelet uses CFS quotas to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the",
@@ -2021,8 +2030,8 @@
 		"title":"CPU Policy",
 		"uri":"cce_10_0351.html",
 		"doc_type":"usermanual2",
-		"p_code":"224",
-		"code":"225"
+		"p_code":"225",
+		"code":"226"
 	},
 	{
 		"desc":"Kubernetes provides two CPU policies: none and static.none: The CPU policy is disabled by default, indicating the existing scheduling behavior.static: The static CPU core",
@@ -2030,8 +2039,8 @@
 		"title":"Enhanced CPU Policy",
 		"uri":"cce_10_0552.html",
 		"doc_type":"usermanual2",
-		"p_code":"224",
-		"code":"226"
+		"p_code":"225",
+		"code":"227"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2039,8 +2048,8 @@
 		"title":"GPU Scheduling",
 		"uri":"cce_10_0720.html",
 		"doc_type":"usermanual2",
-		"p_code":"222",
-		"code":"227"
+		"p_code":"223",
+		"code":"228"
 	},
 	{
 		"desc":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The CCE AI Suite (NVIDIA GPU) add-on has been installed, with the selecte",
@@ -2048,8 +2057,8 @@
 		"title":"Default GPU Scheduling in Kubernetes",
 		"uri":"cce_10_0345.html",
 		"doc_type":"usermanual2",
-		"p_code":"227",
-		"code":"228"
+		"p_code":"228",
+		"code":"229"
 	},
 	{
 		"desc":"The CCE AI Suite (NVIDIA GPU) add-on provides GPU monitoring metrics. This add-on offers additional GPU observability options. This section describes the metrics provided",
@@ -2057,8 +2066,8 @@
 		"title":"GPU Metrics",
 		"uri":"cce_10_0955.html",
 		"doc_type":"usermanual2",
-		"p_code":"227",
-		"code":"229"
+		"p_code":"228",
+		"code":"230"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2066,8 +2075,8 @@
 		"title":"Volcano Scheduling",
 		"uri":"cce_10_0423.html",
 		"doc_type":"usermanual2",
-		"p_code":"222",
-		"code":"230"
+		"p_code":"223",
+		"code":"231"
 	},
 	{
 		"desc":"Volcano is a batch processing platform that runs on Kubernetes for machine learning, deep learning, bioinformatics, genomics, and other big data applications. It provides",
@@ -2075,8 +2084,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0721.html",
 		"doc_type":"usermanual2",
-		"p_code":"230",
-		"code":"231"
+		"p_code":"231",
+		"code":"232"
 	},
 	{
 		"desc":"Volcano is a Kubernetes-based batch processing platform with high-performance general computing capabilities like task scheduling engine, heterogeneous chip management, a",
@@ -2084,8 +2093,8 @@
 		"title":"Scheduling Workloads",
 		"uri":"cce_10_0722.html",
 		"doc_type":"usermanual2",
-		"p_code":"230",
-		"code":"232"
+		"p_code":"231",
+		"code":"233"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2093,8 +2102,8 @@
 		"title":"Resource Usage-based Scheduling",
 		"uri":"cce_10_0768.html",
 		"doc_type":"usermanual2",
-		"p_code":"230",
-		"code":"233"
+		"p_code":"231",
+		"code":"234"
 	},
 	{
 		"desc":"Bin packing is an optimization algorithm that aims to properly allocate resources to each job and get the jobs done using the minimum amount of resources. After bin packi",
@@ -2102,8 +2111,8 @@
 		"title":"Bin Packing",
 		"uri":"cce_10_0773.html",
 		"doc_type":"usermanual2",
-		"p_code":"233",
-		"code":"234"
+		"p_code":"234",
+		"code":"235"
 	},
 	{
 		"desc":"Scheduling in a cluster is the process of binding pending pods to nodes, and is performed by a component called kube-scheduler or Volcano Scheduler. The scheduler uses a ",
@@ -2111,8 +2120,8 @@
 		"title":"Descheduling",
 		"uri":"cce_10_0766.html",
 		"doc_type":"usermanual2",
-		"p_code":"233",
-		"code":"235"
+		"p_code":"234",
+		"code":"236"
 	},
 	{
 		"desc":"In scenarios such as node pool replacement and rolling node upgrade, an old resource pool needs to be replaced with a new one. To prevent the node pool replacement from a",
@@ -2120,8 +2129,8 @@
 		"title":"Node Pool Affinity",
 		"uri":"cce_10_0767.html",
 		"doc_type":"usermanual2",
-		"p_code":"233",
-		"code":"236"
+		"p_code":"234",
+		"code":"237"
 	},
 	{
 		"desc":"Volcano Scheduler offers CPU and memory load-aware scheduling for pods and preferentially schedules pods to the node with the lightest load to balance node loads. This pr",
@@ -2129,8 +2138,8 @@
 		"title":"Load-aware Scheduling",
 		"uri":"cce_10_0789.html",
 		"doc_type":"usermanual2",
-		"p_code":"233",
-		"code":"237"
+		"p_code":"234",
+		"code":"238"
 	},
 	{
 		"desc":"Volcano scheduling involves node filtering and scoring, which is used to filter the nodes meeting scheduling conditions and score the filtered nodes to find the one with ",
@@ -2138,8 +2147,8 @@
 		"title":"Configuration Cases for Resource Usage-based Scheduling",
 		"uri":"cce_10_0813.html",
 		"doc_type":"usermanual2",
-		"p_code":"233",
-		"code":"238"
+		"p_code":"234",
+		"code":"239"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2147,8 +2156,8 @@
 		"title":"Priority-based Scheduling",
 		"uri":"cce_10_0774.html",
 		"doc_type":"usermanual2",
-		"p_code":"230",
-		"code":"239"
+		"p_code":"231",
+		"code":"240"
 	},
 	{
 		"desc":"A pod priority indicates the importance of a pod relative to other pods. Volcano supports pod PriorityClasses in Kubernetes. After PriorityClasses are configured, the sch",
@@ -2156,8 +2165,8 @@
 		"title":"Priority-based Scheduling",
 		"uri":"cce_10_0775.html",
 		"doc_type":"usermanual2",
-		"p_code":"239",
-		"code":"240"
+		"p_code":"240",
+		"code":"241"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2165,8 +2174,8 @@
 		"title":"AI Performance-based Scheduling",
 		"uri":"cce_10_0776.html",
 		"doc_type":"usermanual2",
-		"p_code":"230",
-		"code":"241"
+		"p_code":"231",
+		"code":"242"
 	},
 	{
 		"desc":"Dominant Resource Fairness (DRF) is a scheduling algorithm based on the dominant resource of a container group. DRF scheduling can be used to enhance the service throughp",
@@ -2174,8 +2183,8 @@
 		"title":"DRF",
 		"uri":"cce_10_0777.html",
 		"doc_type":"usermanual2",
-		"p_code":"241",
-		"code":"242"
+		"p_code":"242",
+		"code":"243"
 	},
 	{
 		"desc":"Gang scheduling is a scheduling algorithm that schedules correlated processes or threads to run simultaneously on different processors. It meets the scheduling requiremen",
@@ -2183,8 +2192,8 @@
 		"title":"Gang",
 		"uri":"cce_10_0778.html",
 		"doc_type":"usermanual2",
-		"p_code":"241",
-		"code":"243"
+		"p_code":"242",
+		"code":"244"
 	},
 	{
 		"desc":"In non-uniform memory access (NUMA) architecture, a NUMA node is a fundamental component that includes a processor and local memory. These nodes are physically separate b",
@@ -2192,8 +2201,8 @@
 		"title":"NUMA Affinity Scheduling",
 		"uri":"cce_10_0425.html",
 		"doc_type":"usermanual2",
-		"p_code":"230",
-		"code":"244"
+		"p_code":"231",
+		"code":"245"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2201,8 +2210,8 @@
 		"title":"Cloud Native Hybrid Deployment",
 		"uri":"cce_10_0709.html",
 		"doc_type":"usermanual2",
-		"p_code":"222",
-		"code":"245"
+		"p_code":"223",
+		"code":"246"
 	},
 	{
 		"desc":"Many services see surges in traffic. To ensure performance and stability, resources are often requested at the maximum needed. However, the surges may ebb very shortly an",
@@ -2210,8 +2219,8 @@
 		"title":"Dynamic Resource Oversubscription",
 		"uri":"cce_10_0384.html",
 		"doc_type":"usermanual2",
-		"p_code":"245",
-		"code":"246"
+		"p_code":"246",
+		"code":"247"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2220,7 +2229,7 @@
 		"uri":"cce_10_0020.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"247"
+		"code":"248"
 	},
 	{
 		"desc":"You can learn about a cluster network from the following two aspects:What is a cluster network like? A cluster consists of multiple nodes, and pods (or containers) are ru",
@@ -2228,8 +2237,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0010.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"248"
+		"p_code":"248",
+		"code":"249"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2237,8 +2246,8 @@
 		"title":"Container Network",
 		"uri":"cce_10_0280.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"249"
+		"p_code":"248",
+		"code":"250"
 	},
 	{
 		"desc":"The container network assigns IP addresses to pods in a cluster and provides networking services. In CCE, you can select the following network models for your cluster:Clo",
@@ -2246,8 +2255,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0281.html",
 		"doc_type":"usermanual2",
-		"p_code":"249",
-		"code":"250"
+		"p_code":"250",
+		"code":"251"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2255,8 +2264,8 @@
 		"title":"Cloud Native Network 2.0 Settings",
 		"uri":"cce_10_0678.html",
 		"doc_type":"usermanual2",
-		"p_code":"249",
-		"code":"251"
+		"p_code":"250",
+		"code":"252"
 	},
 	{
 		"desc":"Cloud Native Network 2.0 is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network interface",
@@ -2264,8 +2273,8 @@
 		"title":"Cloud Native Network 2.0",
 		"uri":"cce_10_0284.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"252"
+		"p_code":"252",
+		"code":"253"
 	},
 	{
 		"desc":"If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.This function is avail",
@@ -2273,8 +2282,8 @@
 		"title":"Configuring a Default Container Subnet for a CCE Turbo Cluster",
 		"uri":"cce_10_0906.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"253"
+		"p_code":"252",
+		"code":"254"
 	},
 	{
 		"desc":"In Cloud Native Network 2.0, pods use ENIs or sub-ENIs of the VPC. You can configure a security group for a pod using a pod's annotation.Configure a security group in eit",
@@ -2282,8 +2291,8 @@
 		"title":"Binding a Security Group to a Pod Using an Annotation",
 		"uri":"cce_10_0897.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"254"
+		"p_code":"252",
+		"code":"255"
 	},
 	{
 		"desc":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind security groups and EIPs to pods. To bind CCE pods with security groups, ",
@@ -2291,8 +2300,8 @@
 		"title":"Binding a Security Group to a Workload Using a Security Group Policy",
 		"uri":"cce_10_0288.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"255"
+		"p_code":"252",
+		"code":"256"
 	},
 	{
 		"desc":"In a CCE Turbo cluster, you can configure subnets and security groups for containers by namespace or workload using NetworkAttachmentDefinition CRDs. To configure a parti",
@@ -2300,8 +2309,8 @@
 		"title":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration",
 		"uri":"cce_10_0196.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"256"
+		"p_code":"252",
+		"code":"257"
 	},
 	{
 		"desc":"In Cloud Native Network 2.0, each pod is associated with an ENI, providing a static IP address to the StatefulSet pods (container ENI). This is a common practice in acces",
@@ -2309,8 +2318,8 @@
 		"title":"Configuring a Static IP Address for a Pod",
 		"uri":"cce_10_0603.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"257"
+		"p_code":"252",
+		"code":"258"
 	},
 	{
 		"desc":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind EIPs to pods.To associate an EIP with a pod, simply set the value of the ",
@@ -2318,8 +2327,8 @@
 		"title":"Configuring an EIP for a Pod",
 		"uri":"cce_10_0734.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"258"
+		"p_code":"252",
+		"code":"259"
 	},
 	{
 		"desc":"In Cloud Native Network 2.0, static public IP addresses (EIPs) can be assigned to StatefulSets or pods created directly.You can configure a static EIP for a pod only in C",
@@ -2327,8 +2336,8 @@
 		"title":"Configuring a Static EIP for a Pod",
 		"uri":"cce_10_0651.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"259"
+		"p_code":"252",
+		"code":"260"
 	},
 	{
 		"desc":"By default, pods with IPv6 dual-stack ENIs can access only the IPv6 private network. To access the public network, configure shared bandwidth for such pods.Only CCE Turbo",
@@ -2336,8 +2345,8 @@
 		"title":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs",
 		"uri":"cce_10_0604.html",
 		"doc_type":"usermanual2",
-		"p_code":"251",
-		"code":"260"
+		"p_code":"252",
+		"code":"261"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2345,8 +2354,8 @@
 		"title":"VPC Network Settings",
 		"uri":"cce_10_0904.html",
 		"doc_type":"usermanual2",
-		"p_code":"249",
-		"code":"261"
+		"p_code":"250",
+		"code":"262"
 	},
 	{
 		"desc":"The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes al",
@@ -2354,8 +2363,8 @@
 		"title":"VPC Network Model",
 		"uri":"cce_10_0283.html",
 		"doc_type":"usermanual2",
-		"p_code":"261",
-		"code":"262"
+		"p_code":"262",
+		"code":"263"
 	},
 	{
 		"desc":"If the container CIDR block configured during CCE cluster creation cannot meet service expansion requirements, you can add a container CIDR block for the cluster.This fun",
@@ -2363,8 +2372,8 @@
 		"title":"Adding a Container CIDR Block for a Cluster",
 		"uri":"cce_10_0680.html",
 		"doc_type":"usermanual2",
-		"p_code":"261",
-		"code":"263"
+		"p_code":"262",
+		"code":"264"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2372,8 +2381,8 @@
 		"title":"Tunnel Network Settings",
 		"uri":"cce_10_0677.html",
 		"doc_type":"usermanual2",
-		"p_code":"249",
-		"code":"264"
+		"p_code":"250",
+		"code":"265"
 	},
 	{
 		"desc":"A container tunnel network creates a separate network plane for containers by using tunnel encapsulation on the host network plane. The container tunnel network of a CCE ",
@@ -2381,8 +2390,8 @@
 		"title":"Tunnel Network Model",
 		"uri":"cce_10_0282.html",
 		"doc_type":"usermanual2",
-		"p_code":"264",
-		"code":"265"
+		"p_code":"265",
+		"code":"266"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2390,8 +2399,8 @@
 		"title":"Pod Network Settings",
 		"uri":"cce_10_0675.html",
 		"doc_type":"usermanual2",
-		"p_code":"249",
-		"code":"266"
+		"p_code":"250",
+		"code":"267"
 	},
 	{
 		"desc":"Kubernetes allows pods to directly use the host/node network. When a pod is configured with hostNetwork: true, applications running in the pod can directly view the netwo",
@@ -2399,8 +2408,8 @@
 		"title":"Configuring hostNetwork for Pods",
 		"uri":"cce_10_0402.html",
 		"doc_type":"usermanual2",
-		"p_code":"266",
-		"code":"267"
+		"p_code":"267",
+		"code":"268"
 	},
 	{
 		"desc":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure bandwidth limitation for the pod to ",
@@ -2408,8 +2417,8 @@
 		"title":"Configuring QoS for a Pod",
 		"uri":"cce_10_0382.html",
 		"doc_type":"usermanual2",
-		"p_code":"266",
-		"code":"268"
+		"p_code":"267",
+		"code":"269"
 	},
 	{
 		"desc":"Network policies are designed by Kubernetes to restrict pod access. It is equivalent to a firewall at the application layer to enhance network security. The capabilities ",
@@ -2417,8 +2426,8 @@
 		"title":"Configuring Network Policies to Restrict Pod Access",
 		"uri":"cce_10_0059.html",
 		"doc_type":"usermanual2",
-		"p_code":"266",
-		"code":"269"
+		"p_code":"267",
+		"code":"270"
 	},
 	{
 		"desc":"DataPlane V2 can be enabled for clusters that use Cloud Native 2.0 networks. After this function is enabled, eBPF redirection will be enabled for the capability of networ",
@@ -2426,8 +2435,8 @@
 		"title":"DataPlane V2 Network Acceleration",
 		"uri":"cce_10_0945.html",
 		"doc_type":"usermanual2",
-		"p_code":"266",
-		"code":"270"
+		"p_code":"267",
+		"code":"271"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2435,17 +2444,17 @@
 		"title":"Service",
 		"uri":"cce_10_0247.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"271"
+		"p_code":"248",
+		"code":"272"
 	},
 	{
-		"desc":"After a pod is created, the following problems may occur if you directly access the pod:The pod can be deleted and recreated at any time by a controller such as a Deploym",
+		"desc":"After a pod is created, accessing it directly can result in certain problems:The pod can be deleted and recreated at any time by a controller such as a Deployment. If the",
 		"product_code":"cce",
 		"title":"Overview",
 		"uri":"cce_10_0249.html",
 		"doc_type":"usermanual2",
-		"p_code":"271",
-		"code":"272"
+		"p_code":"272",
+		"code":"273"
 	},
 	{
 		"desc":"ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.The cluster-internal domain name format is <Service",
@@ -2453,8 +2462,8 @@
 		"title":"ClusterIP",
 		"uri":"cce_10_0011.html",
 		"doc_type":"usermanual2",
-		"p_code":"271",
-		"code":"273"
+		"p_code":"272",
+		"code":"274"
 	},
 	{
 		"desc":"A Service is exposed on each node's IP address at a static port (NodePort). When you create a NodePort Service, Kubernetes automatically allocates an internal IP address ",
@@ -2462,8 +2471,8 @@
 		"title":"NodePort",
 		"uri":"cce_10_0142.html",
 		"doc_type":"usermanual2",
-		"p_code":"271",
-		"code":"274"
+		"p_code":"272",
+		"code":"275"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2471,8 +2480,8 @@
 		"title":"LoadBalancer",
 		"uri":"cce_10_0014.html",
 		"doc_type":"usermanual2",
-		"p_code":"271",
-		"code":"275"
+		"p_code":"272",
+		"code":"276"
 	},
 	{
 		"desc":"LoadBalancer Services can access workloads from the public network through a load balancer, which is more reliable than EIP-based access. The LoadBalancer access address ",
@@ -2480,8 +2489,8 @@
 		"title":"Creating a LoadBalancer Service",
 		"uri":"cce_10_0681.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"276"
+		"p_code":"276",
+		"code":"277"
 	},
 	{
 		"desc":"You can add annotations to a YAML file to use some CCE advanced functions. This section describes the available annotations when a LoadBalancer service is created.Interco",
@@ -2489,8 +2498,8 @@
 		"title":"Configuring LoadBalancer Services Using Annotations",
 		"uri":"cce_10_0385.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"277"
+		"p_code":"276",
+		"code":"278"
 	},
 	{
 		"desc":"Only clusters of v1.19.16 or later support HTTP or HTTPS.Scenarios where a load balancer supports HTTP or HTTPSELB TypeApplicationWhether to Support HTTP or HTTPSDescript",
@@ -2498,8 +2507,8 @@
 		"title":"Configuring HTTP/HTTPS for a LoadBalancer Service",
 		"uri":"cce_10_0683.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"278"
+		"p_code":"276",
+		"code":"279"
 	},
 	{
 		"desc":"An SNI certificate is an extended server certificate that allows the same IP address and port number to provide multiple access domain names for external systems. Differe",
@@ -2507,8 +2516,8 @@
 		"title":"Configuring SNI for a LoadBalancer Service",
 		"uri":"cce_10_0841.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"279"
+		"p_code":"276",
+		"code":"280"
 	},
 	{
 		"desc":"Services can be exposed via HTTP/2. By default, HTTP/1.x is used between clients and load balancers. HTTP/2 can improve access performance between clients and load balanc",
@@ -2516,8 +2525,8 @@
 		"title":"Configuring HTTP/2 for a LoadBalancer Service",
 		"uri":"cce_10_0842.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"280"
+		"p_code":"276",
+		"code":"281"
 	},
 	{
 		"desc":"LoadBalancer Services allow you to configure timeout, which is the maximum duration for keeping a connection if no request is received from the client. If no request is r",
@@ -2525,8 +2534,8 @@
 		"title":"Configuring Timeout for a LoadBalancer Service",
 		"uri":"cce_10_0729.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"281"
+		"p_code":"276",
+		"code":"282"
 	},
 	{
 		"desc":"When using a LoadBalancer Service, you can configure a trustlist or blocklist to specify the IP addresses that are allowed or denied accessing a load balancer listener.Tr",
@@ -2534,8 +2543,8 @@
 		"title":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Service",
 		"uri":"cce_10_0831.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"282"
+		"p_code":"276",
+		"code":"283"
 	},
 	{
 		"desc":"The health check annotation field of LoadBalancer Services has been upgraded from kubernetes.io/elb.health-check-option to kubernetes.io/elb.health-check-options. You can",
@@ -2543,8 +2552,8 @@
 		"title":"Configuring Health Check on Multiple LoadBalancer Service Ports",
 		"uri":"cce_10_0684.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"283"
+		"p_code":"276",
+		"code":"284"
 	},
 	{
 		"desc":"kube-proxy, which is responsible for forwarding intra-cluster traffic, adds the IP addresses of load balancers associated with the LoadBalancer Services to nodes' local f",
@@ -2552,8 +2561,8 @@
 		"title":"Configuring Passthrough Networking for a LoadBalancer Service",
 		"uri":"cce_10_0355.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"284"
+		"p_code":"276",
+		"code":"285"
 	},
 	{
 		"desc":"When creating a LoadBalancer Service using a shared load balancer, you can configure annotations for the load balancer listeners to obtain the client IP address.If a dedi",
@@ -2561,8 +2570,8 @@
 		"title":"Enabling a LoadBalancer Service to Obtain the Client IP Address",
 		"uri":"cce_10_0916.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"285"
+		"p_code":"276",
+		"code":"286"
 	},
 	{
 		"desc":"You can customize the EIP bound to a load balancer that is automatically created by CCE by adding the kubernetes.io/elb.custom-eip-id annotation to a Service.A Kubernetes",
@@ -2570,8 +2579,8 @@
 		"title":"Changing a Custom EIP for a LoadBalancer Service",
 		"uri":"cce_10_0924.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"286"
+		"p_code":"276",
+		"code":"287"
 	},
 	{
 		"desc":"The ready status of the pod is associated with the ELB health check. After the health check is successful, the pod is ready. This association works with the strategy.roll",
@@ -2579,8 +2588,8 @@
 		"title":"Setting the Pod Ready Status Through the ELB Health Check",
 		"uri":"cce_10_0685.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"287"
+		"p_code":"276",
+		"code":"288"
 	},
 	{
 		"desc":"If a workload uses UDP for both load balancing and health check, enable ICMP security group rules for the backend servers.",
@@ -2588,8 +2597,8 @@
 		"title":"Enabling ICMP Security Group Rules",
 		"uri":"cce_10_0084.html",
 		"doc_type":"usermanual2",
-		"p_code":"275",
-		"code":"288"
+		"p_code":"276",
+		"code":"289"
 	},
 	{
 		"desc":"Services allow internal and external pod access, but not the following scenarios:Accessing all pods at the same timePods in a Service accessing each otherThis is where he",
@@ -2597,8 +2606,8 @@
 		"title":"Headless Services",
 		"uri":"cce_10_0398.html",
 		"doc_type":"usermanual2",
-		"p_code":"271",
-		"code":"289"
+		"p_code":"272",
+		"code":"290"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2606,8 +2615,8 @@
 		"title":"Ingresses",
 		"uri":"cce_10_0248.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"290"
+		"p_code":"248",
+		"code":"291"
 	},
 	{
 		"desc":"A Service is generally used to forward access requests based on TCP and UDP and provide layer-4 load balancing for clusters. However, in actual scenarios, if there is a l",
@@ -2615,8 +2624,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0094.html",
 		"doc_type":"usermanual2",
-		"p_code":"290",
-		"code":"291"
+		"p_code":"291",
+		"code":"292"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2624,8 +2633,8 @@
 		"title":"LoadBalancer Ingresses",
 		"uri":"cce_10_0686.html",
 		"doc_type":"usermanual2",
-		"p_code":"290",
-		"code":"292"
+		"p_code":"291",
+		"code":"293"
 	},
 	{
 		"desc":"In Kubernetes, an ingress is a resource object that controls how Services within a cluster can be accessed from outside the cluster. You can use ingresses to configure di",
@@ -2633,8 +2642,8 @@
 		"title":"Creating a LoadBalancer Ingress on the Console",
 		"uri":"cce_10_0251.html",
 		"doc_type":"usermanual2",
-		"p_code":"292",
-		"code":"293"
+		"p_code":"293",
+		"code":"294"
 	},
 	{
 		"desc":"This section uses an Nginx workload as an example to describe how to create a LoadBalancer ingress using kubectl.If no load balancer is available in the same VPC, CCE can",
@@ -2642,8 +2651,8 @@
 		"title":"Creating a LoadBalancer Ingress Using kubectl",
 		"uri":"cce_10_0252.html",
 		"doc_type":"usermanual2",
-		"p_code":"292",
-		"code":"294"
+		"p_code":"293",
+		"code":"295"
 	},
 	{
 		"desc":"You can add annotations to a YAML file for more advanced ingress functions. This section describes the annotations that can be used when you create a LoadBalancer ingress",
@@ -2651,8 +2660,8 @@
 		"title":"Annotations for Configuring LoadBalancer Ingresses",
 		"uri":"cce_10_0695.html",
 		"doc_type":"usermanual2",
-		"p_code":"292",
-		"code":"295"
+		"p_code":"293",
+		"code":"296"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2660,8 +2669,8 @@
 		"title":"Advanced Setting Examples of LoadBalancer Ingresses",
 		"uri":"cce_10_0935.html",
 		"doc_type":"usermanual2",
-		"p_code":"292",
-		"code":"296"
+		"p_code":"293",
+		"code":"297"
 	},
 	{
 		"desc":"Ingresses support SSL or TLS certificates, allowing you to secure your Services with HTTPS.You are allowed to use either of the following ways to configure an ingress cer",
@@ -2669,8 +2678,8 @@
 		"title":"Configuring an HTTPS Certificate for a LoadBalancer Ingress",
 		"uri":"cce_10_0687.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"297"
+		"p_code":"297",
+		"code":"298"
 	},
 	{
 		"desc":"If the HTTPS certificate for a LoadBalancer ingress is about to expire or has expired, follow the operations provided in this section to update it.",
@@ -2678,8 +2687,8 @@
 		"title":"Updating the HTTPS Certificate for a LoadBalancer Ingress",
 		"uri":"cce_10_0930.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"298"
+		"p_code":"297",
+		"code":"299"
 	},
 	{
 		"desc":"An SNI certificate is an extended server certificate that allows the same IP address and port number to provide multiple access domain names for external systems. Differe",
@@ -2687,8 +2696,8 @@
 		"title":"Configuring SNI for a LoadBalancer Ingress",
 		"uri":"cce_10_0688.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"299"
+		"p_code":"297",
+		"code":"300"
 	},
 	{
 		"desc":"An ingress can route requests to multiple backend Services based on different matching policies. For example, requests can be routed to three different backend Services s",
@@ -2696,8 +2705,8 @@
 		"title":"Configuring Multiple Forwarding Policies for a LoadBalancer Ingress",
 		"uri":"cce_10_0689.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"300"
+		"p_code":"297",
+		"code":"301"
 	},
 	{
 		"desc":"Ingresses can use HTTP/2 to expose Services. Connections from the load balancer to your application use HTTP/1.x by default. If your application is capable of receiving H",
@@ -2705,8 +2714,8 @@
 		"title":"Configuring HTTP/2 for a LoadBalancer Ingress",
 		"uri":"cce_10_0694.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"301"
+		"p_code":"297",
+		"code":"302"
 	},
 	{
 		"desc":"Ingresses can interconnect with backend services of different protocols. By default, the backend proxy channel of an ingress is HTTP-compliant. To create an HTTPS channel",
@@ -2714,8 +2723,8 @@
 		"title":"Configuring HTTPS Backend Services for a LoadBalancer Ingress",
 		"uri":"cce_10_0691.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"302"
+		"p_code":"297",
+		"code":"303"
 	},
 	{
 		"desc":"LoadBalancer ingresses support the following timeout settings:Idle timeout setting for client connections: maximum duration for keeping a connection when no client reques",
@@ -2723,8 +2732,8 @@
 		"title":"Configuring Timeout for a LoadBalancer Ingress",
 		"uri":"cce_10_0730.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"303"
+		"p_code":"297",
+		"code":"304"
 	},
 	{
 		"desc":"With slow start configured, a load balancer linearly increases the proportion of requests to backend server pods. When the slow start duration elapses, the load balancer ",
@@ -2732,8 +2741,8 @@
 		"title":"Configuring a Slow Start for a LoadBalancer Ingress",
 		"uri":"cce_10_0735.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"304"
+		"p_code":"297",
+		"code":"305"
 	},
 	{
 		"desc":"You can add IP addresses to a trustlist or blocklist to control access to a listener of a LoadBalancer ingress.Trustlist: Only the IP addresses in the list can access the",
@@ -2741,8 +2750,8 @@
 		"title":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Ingress",
 		"uri":"cce_10_0832.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"305"
+		"p_code":"297",
+		"code":"306"
 	},
 	{
 		"desc":"Ingress allows you to customize listening ports. You can configure both HTTP and HTTPS listeners for a Service. For example, a Service can make available both HTTP port 8",
@@ -2750,8 +2759,8 @@
 		"title":"Configuring a Range of Listening Ports for a LoadBalancer Ingress",
 		"uri":"cce_10_0937.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"306"
+		"p_code":"297",
+		"code":"307"
 	},
 	{
 		"desc":"When ingresses use the same load balancer listener, forwarding rules can be prioritized based on the following rules:Forwarding rules of different ingresses: The rules ar",
@@ -2759,8 +2768,8 @@
 		"title":"Configuring the Priorities of Forwarding Rules for LoadBalancer Ingresses",
 		"uri":"cce_10_0939.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"307"
+		"p_code":"297",
+		"code":"308"
 	},
 	{
 		"desc":"Dedicated load balancer ingresses support custom header forwarding policies. You can configure different header key-value pairs to determine the backend Service to which ",
@@ -2768,8 +2777,8 @@
 		"title":"Configuring a Custom Header Forwarding Policy for a LoadBalancer Ingress",
 		"uri":"cce_10_0896.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"308"
+		"p_code":"297",
+		"code":"309"
 	},
 	{
 		"desc":"You can customize the EIP bound to a load balancer that is automatically created by CCE by adding the kubernetes.io/elb.custom-eip-id annotation to an ingress.A CCE stand",
@@ -2777,8 +2786,8 @@
 		"title":"Configuring a Custom EIP for a LoadBalancer Ingress",
 		"uri":"cce_10_0925.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"309"
+		"p_code":"297",
+		"code":"310"
 	},
 	{
 		"desc":"Ingresses offer diverse forwarding rules that can match listeners based on different request parameters like HTTP request methods, headers, query strings, CIDR blocks, an",
@@ -2786,8 +2795,8 @@
 		"title":"Configuring Advanced Forwarding Rules for a LoadBalancer Ingress",
 		"uri":"cce_10_0940.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"310"
+		"p_code":"297",
+		"code":"311"
 	},
 	{
 		"desc":"Dedicated load balancers offer different forwarding actions to effectively distribute traffic. ELB directs client requests to backend servers based on the specified forwa",
@@ -2795,8 +2804,8 @@
 		"title":"Configuring Advanced Forwarding Actions for a LoadBalancer Ingress",
 		"uri":"cce_10_0949.html",
 		"doc_type":"usermanual2",
-		"p_code":"296",
-		"code":"311"
+		"p_code":"297",
+		"code":"312"
 	},
 	{
 		"desc":"CCE sets up forwarding policies on the ELB console based on the rules specified in the ingress configurations when creating LoadBalancer ingresses.To handle more complex ",
@@ -2804,8 +2813,8 @@
 		"title":"Forwarding Policy Priorities of LoadBalancer Ingresses",
 		"uri":"cce_10_0950.html",
 		"doc_type":"usermanual2",
-		"p_code":"292",
-		"code":"312"
+		"p_code":"293",
+		"code":"313"
 	},
 	{
 		"desc":"In a cluster, multiple ingresses can share a listener, allowing them to use the same port on a single load balancer. If two ingresses have different listener configuratio",
@@ -2813,8 +2822,8 @@
 		"title":"Configuring Multiple Ingresses to Use the Same External ELB Port",
 		"uri":"cce_10_0954.html",
 		"doc_type":"usermanual2",
-		"p_code":"292",
-		"code":"313"
+		"p_code":"293",
+		"code":"314"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2822,8 +2831,8 @@
 		"title":"Nginx Ingresses",
 		"uri":"cce_10_0692.html",
 		"doc_type":"usermanual2",
-		"p_code":"290",
-		"code":"314"
+		"p_code":"291",
+		"code":"315"
 	},
 	{
 		"desc":"In Kubernetes, an ingress is a resource object that controls how Services within a cluster can be accessed from outside the cluster. You can use ingresses to configure di",
@@ -2831,8 +2840,8 @@
 		"title":"Creating an Nginx Ingress on the Console",
 		"uri":"cce_10_0390.html",
 		"doc_type":"usermanual2",
-		"p_code":"314",
-		"code":"315"
+		"p_code":"315",
+		"code":"316"
 	},
 	{
 		"desc":"This section uses an Nginx workload as an example to describe how to create an Nginx ingress using kubectl.In CCE clusters of v1.23 or later, the ingress version is switc",
@@ -2840,8 +2849,8 @@
 		"title":"Creating an Nginx Ingress Using kubectl",
 		"uri":"cce_10_0364.html",
 		"doc_type":"usermanual2",
-		"p_code":"314",
-		"code":"316"
+		"p_code":"315",
+		"code":"317"
 	},
 	{
 		"desc":"The nginx-ingress add-on in CCE uses the community chart and image. If the default add-on parameters cannot meet your demands, you can add annotations to define what you ",
@@ -2849,8 +2858,8 @@
 		"title":"Annotations for Configuring Nginx Ingresses",
 		"uri":"cce_10_0699.html",
 		"doc_type":"usermanual2",
-		"p_code":"314",
-		"code":"317"
+		"p_code":"315",
+		"code":"318"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2858,8 +2867,8 @@
 		"title":"Advanced Setting Examples of Nginx Ingresses",
 		"uri":"cce_10_0936.html",
 		"doc_type":"usermanual2",
-		"p_code":"314",
-		"code":"318"
+		"p_code":"315",
+		"code":"319"
 	},
 	{
 		"desc":"HTTPS certificates can be configured for ingresses to provide security services.Create a YAML file named ingress-test-secret.yaml. The file name can be customized.The YAM",
@@ -2867,8 +2876,8 @@
 		"title":"Configuring an HTTPS Certificate for an Nginx Ingress",
 		"uri":"cce_10_0693.html",
 		"doc_type":"usermanual2",
-		"p_code":"318",
-		"code":"319"
+		"p_code":"319",
+		"code":"320"
 	},
 	{
 		"desc":"Ingress can function as a proxy for backend services using different protocols. By default, the backend proxy channel of an ingress is an HTTP channel. To create an HTTPS",
@@ -2876,8 +2885,8 @@
 		"title":"Configuring HTTPS Backend Services for an Nginx Ingress",
 		"uri":"cce_10_0697.html",
 		"doc_type":"usermanual2",
-		"p_code":"318",
-		"code":"320"
+		"p_code":"319",
+		"code":"321"
 	},
 	{
 		"desc":"The native Nginx supports multiple load balancing rules, including weighted round robin and IP hash. Nginx Ingress supports load balancing by using consistent hashing bas",
@@ -2885,8 +2894,8 @@
 		"title":"Configuring Consistent Hashing for Load Balancing of an Nginx Ingress",
 		"uri":"cce_10_0698.html",
 		"doc_type":"usermanual2",
-		"p_code":"318",
-		"code":"321"
+		"p_code":"319",
+		"code":"322"
 	},
 	{
 		"desc":"Ingress objects provide Layer 7 protocols like HTTP and HTTPS for clusters. Among the available options, Nginx ingresses are widely used. CCE has developed a featured ope",
@@ -2894,8 +2903,8 @@
 		"title":"Optimizing NGINX Ingress Controller in High-Traffic Scenarios",
 		"uri":"cce_10_0919.html",
 		"doc_type":"usermanual2",
-		"p_code":"318",
-		"code":"322"
+		"p_code":"319",
+		"code":"323"
 	},
 	{
 		"desc":"CCE provides the following options for configuring ingress certificates for the Nginx Ingress Controller add-on:Secret certificate. Import the required certificate to a C",
@@ -2903,8 +2912,8 @@
 		"title":"Configuring an ELB Certificate for NGINX Ingress Controller",
 		"uri":"cce_10_0947.html",
 		"doc_type":"usermanual2",
-		"p_code":"318",
-		"code":"323"
+		"p_code":"319",
+		"code":"324"
 	},
 	{
 		"desc":"CCE NGINX Ingress Controller is based on the community version of Ingress NGINX Controller. Upgrades to the community version may introduce new features, optimize existin",
@@ -2912,8 +2921,8 @@
 		"title":"NGINX Ingress Controller Upgrade Compatibility",
 		"uri":"cce_10_0968.html",
 		"doc_type":"usermanual2",
-		"p_code":"314",
-		"code":"324"
+		"p_code":"315",
+		"code":"325"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2921,8 +2930,8 @@
 		"title":"DNS",
 		"uri":"cce_10_0359.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"325"
+		"p_code":"248",
+		"code":"326"
 	},
 	{
 		"desc":"When you create a cluster, the CoreDNS add-on is installed to resolve domain names in the cluster.You can view the pod of the CoreDNS add-on in the kube-system namespace.",
@@ -2930,8 +2939,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0360.html",
 		"doc_type":"usermanual2",
-		"p_code":"325",
-		"code":"326"
+		"p_code":"326",
+		"code":"327"
 	},
 	{
 		"desc":"Every Kubernetes cluster has a built-in DNS add-on (Kube-DNS or CoreDNS) to provide domain name resolution for workloads in the cluster. When handling a high concurrency ",
@@ -2939,8 +2948,8 @@
 		"title":"DNS Configuration",
 		"uri":"cce_10_0365.html",
 		"doc_type":"usermanual2",
-		"p_code":"325",
-		"code":"327"
+		"p_code":"326",
+		"code":"328"
 	},
 	{
 		"desc":"When using CCE, you may need to resolve custom internal domain names in the following scenarios:In the legacy code, a fixed domain name is configured for calling other in",
@@ -2948,8 +2957,8 @@
 		"title":"Using CoreDNS for Custom Domain Name Resolution",
 		"uri":"cce_10_0361.html",
 		"doc_type":"usermanual2",
-		"p_code":"325",
-		"code":"328"
+		"p_code":"326",
+		"code":"329"
 	},
 	{
 		"desc":"This section describes how to access an intranet from a container (outside the cluster in a VPC), including intra-VPC access and cross-VPC access.The performance of acces",
@@ -2957,8 +2966,8 @@
 		"title":"Configuring Intra-VPC Access",
 		"uri":"cce_10_0399.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"329"
+		"p_code":"248",
+		"code":"330"
 	},
 	{
 		"desc":"Containers can access the Internet in either of the following ways:Bind an EIP to the node where the container is located if the network model is VPC or tunnel.Bind an EI",
@@ -2966,8 +2975,8 @@
 		"title":"Accessing the Internet from a Container",
 		"uri":"cce_10_0400.html",
 		"doc_type":"usermanual2",
-		"p_code":"247",
-		"code":"330"
+		"p_code":"248",
+		"code":"331"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -2976,7 +2985,7 @@
 		"uri":"cce_10_0374.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"331"
+		"code":"332"
 	},
 	{
 		"desc":"CCE container storage is implemented based on Kubernetes container storage APIs (CSI). CCE integrates multiple types of cloud storage and covers different application sce",
@@ -2984,8 +2993,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0307.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"332"
+		"p_code":"332",
+		"code":"333"
 	},
 	{
 		"desc":"On-disk files in a container are ephemeral, which presents the following problems to important applications running in the container:When a container is rebuilt, files in",
@@ -2993,8 +3002,8 @@
 		"title":"Storage Basics",
 		"uri":"cce_10_0378.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"333"
+		"p_code":"332",
+		"code":"334"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3002,8 +3011,8 @@
 		"title":"Elastic Volume Service",
 		"uri":"cce_10_0044.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"334"
+		"p_code":"332",
+		"code":"335"
 	},
 	{
 		"desc":"To achieve persistent storage, CCE allows you to mount the storage volumes created from Elastic Volume Service (EVS) disks to a path of a container. When the container is",
@@ -3011,8 +3020,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0613.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"335"
+		"p_code":"335",
+		"code":"336"
 	},
 	{
 		"desc":"CCE allows you to create a PV using an existing EVS disk. Then, you can create a PVC and bind it to the PV. This method is suitable for scenarios where underlying storage",
@@ -3020,8 +3029,8 @@
 		"title":"Using an Existing EVS Disk Through a Static PV",
 		"uri":"cce_10_0614.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"336"
+		"p_code":"335",
+		"code":"337"
 	},
 	{
 		"desc":"CCE allows you to specify a StorageClass to automatically create an EVS disk and the corresponding PV. This function is applicable when no underlying storage volume is av",
@@ -3029,8 +3038,8 @@
 		"title":"Using an EVS Disk Through a Dynamic PV",
 		"uri":"cce_10_0615.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"337"
+		"p_code":"335",
+		"code":"338"
 	},
 	{
 		"desc":"Dynamic mounting is available only for creating a StatefulSet. It is implemented through a volume claim template (volumeClaimTemplates field) and depends on dynamic creat",
@@ -3038,8 +3047,8 @@
 		"title":"Dynamically Mounting an EVS Disk to a StatefulSet",
 		"uri":"cce_10_0616.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"338"
+		"p_code":"335",
+		"code":"339"
 	},
 	{
 		"desc":"Encrypting cloud disks ensures data privacy and control, making it ideal for scenarios that demand high security or compliance standards. This section describes how to us",
@@ -3047,8 +3056,8 @@
 		"title":"Encrypting EVS Disks",
 		"uri":"cce_10_0859.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"339"
+		"p_code":"335",
+		"code":"340"
 	},
 	{
 		"desc":"If the EVS disk attached to a workload does not have enough space, you can increase its capacity by expanding it. This section describes how to expand the capacity of an ",
@@ -3056,8 +3065,8 @@
 		"title":"Expanding the Capacity of an EVS Disk",
 		"uri":"cce_10_0860.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"340"
+		"p_code":"335",
+		"code":"341"
 	},
 	{
 		"desc":"CCE works with EVS to support snapshots. A snapshot is a complete copy or image of EVS disk data at a certain point of time, which can be used for data DR.You can create ",
@@ -3065,8 +3074,8 @@
 		"title":"Snapshots and Backups",
 		"uri":"cce_10_0381.html",
 		"doc_type":"usermanual2",
-		"p_code":"334",
-		"code":"341"
+		"p_code":"335",
+		"code":"342"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3074,8 +3083,8 @@
 		"title":"Scalable File Service",
 		"uri":"cce_10_0111.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"342"
+		"p_code":"332",
+		"code":"343"
 	},
 	{
 		"desc":"CCE allows you to mount a volume created from a Scalable File Service (SFS) file system to a container to store data persistently. SFS volumes are commonly used in ReadWr",
@@ -3083,8 +3092,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0617.html",
 		"doc_type":"usermanual2",
-		"p_code":"342",
-		"code":"343"
+		"p_code":"343",
+		"code":"344"
 	},
 	{
 		"desc":"SFS is a network-attached storage (NAS) that provides shared, scalable, and high-performance file storage. It applies to large-capacity expansion and cost-sensitive servi",
@@ -3092,8 +3101,8 @@
 		"title":"Using an Existing SFS File System Through a Static PV",
 		"uri":"cce_10_0619.html",
 		"doc_type":"usermanual2",
-		"p_code":"342",
-		"code":"344"
+		"p_code":"343",
+		"code":"345"
 	},
 	{
 		"desc":"This section describes how to use storage classes to dynamically create PVs and PVCs for data persistence and sharing in workloads.You have created a cluster and installe",
@@ -3101,8 +3110,8 @@
 		"title":"Using an SFS File System Through a Dynamic PV",
 		"uri":"cce_10_0620.html",
 		"doc_type":"usermanual2",
-		"p_code":"342",
-		"code":"345"
+		"p_code":"343",
+		"code":"346"
 	},
 	{
 		"desc":"This section describes how to configure SFS mount options. You can configure mount options in a PV and bind the PV to a PVC. Alternatively, configure mount options in a S",
@@ -3110,8 +3119,8 @@
 		"title":"Configuring SFS Volume Mount Options",
 		"uri":"cce_10_0337.html",
 		"doc_type":"usermanual2",
-		"p_code":"342",
-		"code":"346"
+		"p_code":"343",
+		"code":"347"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3119,8 +3128,8 @@
 		"title":"SFS Turbo",
 		"uri":"cce_10_0125.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"347"
+		"p_code":"332",
+		"code":"348"
 	},
 	{
 		"desc":"CCE allows you to mount storage volumes created by SFS Turbo file systems to a path of a container to meet data persistence requirements. SFS Turbo file systems are fast,",
@@ -3128,8 +3137,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0624.html",
 		"doc_type":"usermanual2",
-		"p_code":"347",
-		"code":"348"
+		"p_code":"348",
+		"code":"349"
 	},
 	{
 		"desc":"SFS Turbo is a shared file system with high availability and durability. It is suitable for applications that contain massive small files and require low latency, and hig",
@@ -3137,8 +3146,8 @@
 		"title":"Using an Existing SFS Turbo File System Through a Static PV",
 		"uri":"cce_10_0625.html",
 		"doc_type":"usermanual2",
-		"p_code":"347",
-		"code":"349"
+		"p_code":"348",
+		"code":"350"
 	},
 	{
 		"desc":"This section describes how to configure SFS Turbo mount options. For SFS Turbo, you can only set mount options in a PV and bind the PV by creating a PVC.The CCE Container",
@@ -3146,8 +3155,8 @@
 		"title":"Configuring SFS Turbo Mount Options",
 		"uri":"cce_10_0626.html",
 		"doc_type":"usermanual2",
-		"p_code":"347",
-		"code":"350"
+		"p_code":"348",
+		"code":"351"
 	},
 	{
 		"desc":"When an SFS Turbo volume is mounted to a workload container, the root directory is mounted to the container by default. However, the minimum capacity of an SFS Turbo volu",
@@ -3155,8 +3164,8 @@
 		"title":"(Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV",
 		"uri":"cce_10_0839.html",
 		"doc_type":"usermanual2",
-		"p_code":"347",
-		"code":"351"
+		"p_code":"348",
+		"code":"352"
 	},
 	{
 		"desc":"The minimum capacity of an SFS Turbo file system is 500 GiB. By default, the root directory of an SFS Turbo file system is mounted to a container which, in most case, doe",
@@ -3164,8 +3173,8 @@
 		"title":"Dynamically Creating an SFS Turbo Subdirectory Using StorageClass",
 		"uri":"cce_bestpractice_00253.html",
 		"doc_type":"usermanual2",
-		"p_code":"347",
-		"code":"352"
+		"p_code":"348",
+		"code":"353"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3173,8 +3182,8 @@
 		"title":"Object Storage Service",
 		"uri":"cce_10_0160.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"353"
+		"p_code":"332",
+		"code":"354"
 	},
 	{
 		"desc":"Object Storage Service (OBS) provides massive, secure, and cost-effective data storage for you to store data of any type and size. You can use it in enterprise backup/arc",
@@ -3182,8 +3191,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0628.html",
 		"doc_type":"usermanual2",
-		"p_code":"353",
-		"code":"354"
+		"p_code":"354",
+		"code":"355"
 	},
 	{
 		"desc":"This section describes how to use an existing Object Storage Service (OBS) bucket to statically create PVs and PVCs for data persistence and sharing in workloads.You have",
@@ -3191,8 +3200,8 @@
 		"title":"Using an Existing OBS Bucket Through a Static PV",
 		"uri":"cce_10_0379.html",
 		"doc_type":"usermanual2",
-		"p_code":"353",
-		"code":"355"
+		"p_code":"354",
+		"code":"356"
 	},
 	{
 		"desc":"This section describes how to automatically create an OBS bucket. It is applicable when no underlying storage volume is available.If OBS volumes are used, the owner group",
@@ -3200,8 +3209,8 @@
 		"title":"Using an OBS Bucket Through a Dynamic PV",
 		"uri":"cce_10_0630.html",
 		"doc_type":"usermanual2",
-		"p_code":"353",
-		"code":"356"
+		"p_code":"354",
+		"code":"357"
 	},
 	{
 		"desc":"This section describes how to configure OBS volume mount options. You can configure mount options in a PV and bind the PV to a PVC. Alternatively, configure mount options",
@@ -3209,8 +3218,8 @@
 		"title":"Configuring OBS Mount Options",
 		"uri":"cce_10_0631.html",
 		"doc_type":"usermanual2",
-		"p_code":"353",
-		"code":"357"
+		"p_code":"354",
+		"code":"358"
 	},
 	{
 		"desc":"CCE Container Storage (Everest) of v1.2.8 or later supports custom access keys. In this way, IAM users can use their own custom access keys to mount an OBS volume.The CCE",
@@ -3218,8 +3227,8 @@
 		"title":"Using a Custom Access Key (AK/SK) to Mount an OBS Volume",
 		"uri":"cce_10_0336.html",
 		"doc_type":"usermanual2",
-		"p_code":"353",
-		"code":"358"
+		"p_code":"354",
+		"code":"359"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3227,8 +3236,8 @@
 		"title":"Local PVs",
 		"uri":"cce_10_0391.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"359"
+		"p_code":"332",
+		"code":"360"
 	},
 	{
 		"desc":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. A PV that uses a local persistent vol",
@@ -3236,8 +3245,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0633.html",
 		"doc_type":"usermanual2",
-		"p_code":"359",
-		"code":"360"
+		"p_code":"360",
+		"code":"361"
 	},
 	{
 		"desc":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. Before creating a local PV, import th",
@@ -3245,8 +3254,8 @@
 		"title":"Importing a PV to a Storage Pool",
 		"uri":"cce_10_0642.html",
 		"doc_type":"usermanual2",
-		"p_code":"359",
-		"code":"361"
+		"p_code":"360",
+		"code":"362"
 	},
 	{
 		"desc":"You have created a cluster and installed the CSI add-on (Everest) in the cluster.To create a cluster using commands, ensure kubectl is used. For details, see Accessing a ",
@@ -3254,8 +3263,8 @@
 		"title":"Using a Local PV Through a Dynamic PV",
 		"uri":"cce_10_0634.html",
 		"doc_type":"usermanual2",
-		"p_code":"359",
-		"code":"362"
+		"p_code":"360",
+		"code":"363"
 	},
 	{
 		"desc":"Dynamic mounting is available only for creating a StatefulSet. It is implemented through a volume claim template (volumeClaimTemplates field) and depends on dynamic creat",
@@ -3263,8 +3272,8 @@
 		"title":"Dynamically Mounting a Local PV to a StatefulSet",
 		"uri":"cce_10_0635.html",
 		"doc_type":"usermanual2",
-		"p_code":"359",
-		"code":"363"
+		"p_code":"360",
+		"code":"364"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3272,8 +3281,8 @@
 		"title":"Ephemeral Volumes",
 		"uri":"cce_10_0636.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"364"
+		"p_code":"332",
+		"code":"365"
 	},
 	{
 		"desc":"Some applications require additional storage, but whether the data is still available after a restart is not important. For example, although cache services are limited b",
@@ -3281,8 +3290,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0637.html",
 		"doc_type":"usermanual2",
-		"p_code":"364",
-		"code":"365"
+		"p_code":"365",
+		"code":"366"
 	},
 	{
 		"desc":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. Before creating a local EV, import th",
@@ -3290,8 +3299,8 @@
 		"title":"Importing an EV to a Storage Pool",
 		"uri":"cce_10_0725.html",
 		"doc_type":"usermanual2",
-		"p_code":"364",
-		"code":"366"
+		"p_code":"365",
+		"code":"367"
 	},
 	{
 		"desc":"Local Ephemeral Volumes (EVs) are stored in EV storage pools. Local EVs deliver better performance than the default storage medium of native emptyDir and support scale-ou",
@@ -3299,8 +3308,8 @@
 		"title":"Local EV",
 		"uri":"cce_10_0726.html",
 		"doc_type":"usermanual2",
-		"p_code":"364",
-		"code":"367"
+		"p_code":"365",
+		"code":"368"
 	},
 	{
 		"desc":"A temporary path is of the Kubernetes-native emptyDir type. Its lifecycle is the same as that of a pod. Memory can be specified as the storage medium. When the pod is del",
@@ -3308,8 +3317,8 @@
 		"title":"Temporary Path",
 		"uri":"cce_10_0638.html",
 		"doc_type":"usermanual2",
-		"p_code":"364",
-		"code":"368"
+		"p_code":"365",
+		"code":"369"
 	},
 	{
 		"desc":"hostPath is used for mounting the file directory of the host where the container is located to the specified mount point of the container. If the container needs to acces",
@@ -3317,8 +3326,8 @@
 		"title":"hostPath",
 		"uri":"cce_10_0377.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"369"
+		"p_code":"332",
+		"code":"370"
 	},
 	{
 		"desc":"A StorageClass in Kubernetes is a resource that categorizes storage types in a cluster. It can also serve as a configuration template for creating PVs. When creating a PV",
@@ -3326,8 +3335,8 @@
 		"title":"StorageClass",
 		"uri":"cce_10_0380.html",
 		"doc_type":"usermanual2",
-		"p_code":"331",
-		"code":"370"
+		"p_code":"332",
+		"code":"371"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3336,7 +3345,7 @@
 		"uri":"cce_10_0207.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"371"
+		"code":"372"
 	},
 	{
 		"desc":"Auto scaling is a service that automatically and economically adjusts service resources based on your service requirements and configured policies.More and more applicati",
@@ -3344,8 +3353,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0279.html",
 		"doc_type":"usermanual2",
-		"p_code":"371",
-		"code":"372"
+		"p_code":"372",
+		"code":"373"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3353,8 +3362,8 @@
 		"title":"Scaling a Workload",
 		"uri":"cce_10_0293.html",
 		"doc_type":"usermanual2",
-		"p_code":"371",
-		"code":"373"
+		"p_code":"372",
+		"code":"374"
 	},
 	{
 		"desc":"CCE supports multiple workload scaling modes. Comparisons between the scaling policies are listed in the following table.Comparisons between auto scaling policiesItemHPAC",
@@ -3362,8 +3371,8 @@
 		"title":"Workload Scaling Rules",
 		"uri":"cce_10_0290.html",
 		"doc_type":"usermanual2",
-		"p_code":"373",
-		"code":"374"
+		"p_code":"374",
+		"code":"375"
 	},
 	{
 		"desc":"Horizontal Pod Autoscaling (HPA) in Kubernetes implements horizontal scaling of pods. In a CCE HPA policy, you can configure different cooldown time windows and scaling t",
@@ -3371,8 +3380,8 @@
 		"title":"Creating an HPA Policy",
 		"uri":"cce_10_0208.html",
 		"doc_type":"usermanual2",
-		"p_code":"373",
-		"code":"375"
+		"p_code":"374",
+		"code":"376"
 	},
 	{
 		"desc":"Kubernetes' default HPA policy only allows for auto scaling based on CPU and memory usage. However, in more complex service scenarios, this may not be sufficient to meet ",
@@ -3380,8 +3389,8 @@
 		"title":"Creating an HPA Policy with Custom Metrics",
 		"uri":"cce_10_0944.html",
 		"doc_type":"usermanual2",
-		"p_code":"373",
-		"code":"376"
+		"p_code":"374",
+		"code":"377"
 	},
 	{
 		"desc":"There are predictable and unpredictable traffic peaks for some services. For such services, CCE CronHPA allows you to scale resources in fixed periods. It can work with H",
@@ -3389,8 +3398,8 @@
 		"title":"Creating a Scheduled CronHPA Policy",
 		"uri":"cce_10_0415.html",
 		"doc_type":"usermanual2",
-		"p_code":"373",
-		"code":"377"
+		"p_code":"374",
+		"code":"378"
 	},
 	{
 		"desc":"The native Horizontal Pod Autoscaler (HPA) in Kubernetes can cause delays in scaling due to its passive triggering mechanism. To address this issue, the Advanced Horizont",
@@ -3398,8 +3407,8 @@
 		"title":"Creating an AHPA Policy",
 		"uri":"cce_10_0934.html",
 		"doc_type":"usermanual2",
-		"p_code":"373",
-		"code":"378"
+		"p_code":"374",
+		"code":"379"
 	},
 	{
 		"desc":"After a workload scaling policy is created, you can update and delete the policy, as well as edit the YAML file.You can view the rules, latest status, and events of a wor",
@@ -3407,8 +3416,8 @@
 		"title":"Managing Workload Scaling Policies",
 		"uri":"cce_10_0083.html",
 		"doc_type":"usermanual2",
-		"p_code":"373",
-		"code":"379"
+		"p_code":"374",
+		"code":"380"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3416,8 +3425,8 @@
 		"title":"Scaling a Node",
 		"uri":"cce_10_0291.html",
 		"doc_type":"usermanual2",
-		"p_code":"371",
-		"code":"380"
+		"p_code":"372",
+		"code":"381"
 	},
 	{
 		"desc":"HPA is designed for pod-level scaling and can dynamically adjust the number of replicas based on workload metrics. However, if cluster resources are insufficient and new ",
@@ -3425,8 +3434,8 @@
 		"title":"Node Scaling Rules",
 		"uri":"cce_10_0296.html",
 		"doc_type":"usermanual2",
-		"p_code":"380",
-		"code":"381"
+		"p_code":"381",
+		"code":"382"
 	},
 	{
 		"desc":"To use node flavor priorities, the Autoscaler version must be 1.19.35, 1.21.28, 1.23.30, 1.25.20, or later. To balance load among AZs, the version must be 1.23.122, 1.25.",
@@ -3434,8 +3443,8 @@
 		"title":"Priorities for Scaling Node Pools",
 		"uri":"cce_10_0649.html",
 		"doc_type":"usermanual2",
-		"p_code":"380",
-		"code":"382"
+		"p_code":"381",
+		"code":"383"
 	},
 	{
 		"desc":"CCE provides auto scaling through the CCE Cluster Autoscaler add-on. Nodes with different flavors can be automatically added across AZs on demand.If both a node scaling p",
@@ -3443,8 +3452,8 @@
 		"title":"Creating a Node Scaling Policy",
 		"uri":"cce_10_0209.html",
 		"doc_type":"usermanual2",
-		"p_code":"380",
-		"code":"383"
+		"p_code":"381",
+		"code":"384"
 	},
 	{
 		"desc":"After a node scaling policy is created, you can delete, edit, disable, enable, or clone the policy.You can view the associated node pool, rules, and scaling history of a ",
@@ -3452,8 +3461,8 @@
 		"title":"Managing Node Scaling Policies",
 		"uri":"cce_10_0063.html",
 		"doc_type":"usermanual2",
-		"p_code":"380",
-		"code":"384"
+		"p_code":"381",
+		"code":"385"
 	},
 	{
 		"desc":"When you use the CCE Cluster Autoscaler add-on to automatically adjust the number of nodes, you need to specify the scale-in conditions for each node pool in a cluster ba",
@@ -3461,8 +3470,8 @@
 		"title":"Specifying Node Scale-in Conditions for a Node Pool",
 		"uri":"cce_10_0967.html",
 		"doc_type":"usermanual2",
-		"p_code":"380",
-		"code":"385"
+		"p_code":"381",
+		"code":"386"
 	},
 	{
 		"desc":"The best way to handle surging traffic is to automatically adjust the number of machines based on the traffic volume or resource usage, which is called scaling.To prevent",
@@ -3470,8 +3479,8 @@
 		"title":"Using HPA and CA for Auto Scaling of Workloads and Nodes",
 		"uri":"cce_10_0300.html",
 		"doc_type":"usermanual2",
-		"p_code":"371",
-		"code":"386"
+		"p_code":"372",
+		"code":"387"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3480,7 +3489,7 @@
 		"uri":"cce_10_0705.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"387"
+		"code":"388"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3488,8 +3497,8 @@
 		"title":"Logging",
 		"uri":"cce_10_0553.html",
 		"doc_type":"usermanual2",
-		"p_code":"387",
-		"code":"388"
+		"p_code":"388",
+		"code":"389"
 	},
 	{
 		"desc":"Kubernetes logs allow you to locate and rectify faults. This section describes how to manage Kubernetes logs using different methods.The following are Kubernetes log mana",
@@ -3497,8 +3506,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0557.html",
 		"doc_type":"usermanual2",
-		"p_code":"388",
-		"code":"389"
+		"p_code":"389",
+		"code":"390"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3506,8 +3515,8 @@
 		"title":"Collecting Container Logs",
 		"uri":"cce_10_0182.html",
 		"doc_type":"usermanual2",
-		"p_code":"388",
-		"code":"390"
+		"p_code":"389",
+		"code":"391"
 	},
 	{
 		"desc":"The Cloud Native Log Collection add-on (Cloud Native Log Collection) is developed based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This ad",
@@ -3515,17 +3524,17 @@
 		"title":"Collecting Container Logs Using the Cloud Native Log Collection Add-on",
 		"uri":"cce_10_0555.html",
 		"doc_type":"usermanual2",
-		"p_code":"390",
-		"code":"391"
+		"p_code":"391",
+		"code":"392"
 	},
 	{
-		"desc":"CCE works with AOM to collect workload logs. When a node is created, ICAgent (a DaemonSet named icagent in the kube-system namespace of a cluster) of AOM is installed by ",
+		"desc":"CCE can collect workload logs and report them to AOM 1.0. When a node is created, ICAgent (a DaemonSet named icagent in the kube-system namespace of a cluster) is install",
 		"product_code":"cce",
 		"title":"Collecting Container Logs Using ICAgent",
 		"uri":"cce_10_0018.html",
 		"doc_type":"usermanual2",
-		"p_code":"390",
-		"code":"392"
+		"p_code":"391",
+		"code":"393"
 	},
 	{
 		"desc":"The Cloud Native Log Collection add-on works with LTS to collect and store Kubernetes events and works with AOM to generate alarms.To enable Kubernetes event collection, ",
@@ -3533,8 +3542,8 @@
 		"title":"Collecting Kubernetes Events",
 		"uri":"cce_10_0793.html",
 		"doc_type":"usermanual2",
-		"p_code":"388",
-		"code":"393"
+		"p_code":"389",
+		"code":"394"
 	},
 	{
 		"desc":"CCE allows you to collect the logs of master nodes. On the Logging page, you can select one or more control plane components (kube-controller-manager, kube-apiserver, and",
@@ -3542,8 +3551,8 @@
 		"title":"Collecting Control Plane Component Logs",
 		"uri":"cce_10_0554.html",
 		"doc_type":"usermanual2",
-		"p_code":"388",
-		"code":"394"
+		"p_code":"389",
+		"code":"395"
 	},
 	{
 		"desc":"CCE allows you to collect the logs of master nodes. On the Kubernetes Audit Logs tab of Logging, you can determine whether to report audit logs to LTS.The cluster version",
@@ -3551,8 +3560,8 @@
 		"title":"Collecting Audit Logs",
 		"uri":"cce_10_0792.html",
 		"doc_type":"usermanual2",
-		"p_code":"388",
-		"code":"395"
+		"p_code":"389",
+		"code":"396"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3560,8 +3569,8 @@
 		"title":"Log Auditing",
 		"uri":"cce_10_0024.html",
 		"doc_type":"usermanual2",
-		"p_code":"387",
-		"code":"396"
+		"p_code":"388",
+		"code":"397"
 	},
 	{
 		"desc":"Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the ",
@@ -3569,8 +3578,8 @@
 		"title":"CCE Operations Supported by Cloud Trace Service",
 		"uri":"cce_10_0025.html",
 		"doc_type":"usermanual2",
-		"p_code":"396",
-		"code":"397"
+		"p_code":"397",
+		"code":"398"
 	},
 	{
 		"desc":"After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces",
@@ -3578,8 +3587,8 @@
 		"title":"Viewing CTS Traces in the Trace List",
 		"uri":"cce_10_0026.html",
 		"doc_type":"usermanual2",
-		"p_code":"396",
-		"code":"398"
+		"p_code":"397",
+		"code":"399"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3587,8 +3596,8 @@
 		"title":"O&M FAQ",
 		"uri":"cce_10_0799.html",
 		"doc_type":"usermanual2",
-		"p_code":"387",
-		"code":"399"
+		"p_code":"388",
+		"code":"400"
 	},
 	{
 		"desc":"How Do I Disable Logging?What Can I Do If All Components Except log-operator Are Not Ready?How Do I Handle the Error in Stdout Logs of log-operator?What Can I Do If Conta",
@@ -3596,8 +3605,8 @@
 		"title":"Logging FAQ",
 		"uri":"cce_10_0809.html",
 		"doc_type":"usermanual2",
-		"p_code":"399",
-		"code":"400"
+		"p_code":"400",
+		"code":"401"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3605,8 +3614,8 @@
 		"title":"O&M Best Practices",
 		"uri":"cce_10_0811.html",
 		"doc_type":"usermanual2",
-		"p_code":"387",
-		"code":"401"
+		"p_code":"388",
+		"code":"402"
 	},
 	{
 		"desc":"CCE provides the Cloud Native Cluster Monitoring add-on to monitor custom metrics using Prometheus.The following procedure uses an Nginx application as an example to desc",
@@ -3614,8 +3623,8 @@
 		"title":"Monitoring Custom Metrics Using Cloud Native Cluster Monitoring",
 		"uri":"cce_10_0373.html",
 		"doc_type":"usermanual2",
-		"p_code":"401",
-		"code":"402"
+		"p_code":"402",
+		"code":"403"
 	},
 	{
 		"desc":"CCE allows you to upload custom metrics to AOM. ICAgent on a node periodically calls the metric monitoring API configured on a workload to read monitoring data and then u",
@@ -3623,8 +3632,8 @@
 		"title":"Monitoring Custom Metrics on AOM",
 		"uri":"cce_10_0201.html",
 		"doc_type":"usermanual2",
-		"p_code":"401",
-		"code":"403"
+		"p_code":"402",
+		"code":"404"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3633,7 +3642,7 @@
 		"uri":"cce_10_0030.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"404"
+		"code":"405"
 	},
 	{
 		"desc":"A namespace is a collection of resources and objects. Multiple namespaces can be created inside a cluster and isolated from each other. This enables namespaces to share t",
@@ -3641,8 +3650,8 @@
 		"title":"Creating a Namespace",
 		"uri":"cce_10_0278.html",
 		"doc_type":"usermanual2",
-		"p_code":"404",
-		"code":"405"
+		"p_code":"405",
+		"code":"406"
 	},
 	{
 		"desc":"When creating a workload, you can select a namespace to isolate resources or users.When querying workloads, you can select a namespace to view all workloads in the namesp",
@@ -3650,8 +3659,8 @@
 		"title":"Managing Namespaces",
 		"uri":"cce_10_0285.html",
 		"doc_type":"usermanual2",
-		"p_code":"404",
-		"code":"406"
+		"p_code":"405",
+		"code":"407"
 	},
 	{
 		"desc":"Kubernetes provides namespaces for you to group resources in a cluster. Namespaces serve different purposes to meet the needs of multiple users, environments, and applica",
@@ -3659,8 +3668,8 @@
 		"title":"Configuring Resource Quotas",
 		"uri":"cce_10_0287.html",
 		"doc_type":"usermanual2",
-		"p_code":"404",
-		"code":"407"
+		"p_code":"405",
+		"code":"408"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3669,7 +3678,7 @@
 		"uri":"cce_10_0045.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"408"
+		"code":"409"
 	},
 	{
 		"desc":"A ConfigMap is a type of resource that stores configuration information required by a workload. Its content is user-defined. After creating ConfigMaps, you can use them a",
@@ -3677,8 +3686,8 @@
 		"title":"Creating a ConfigMap",
 		"uri":"cce_10_0152.html",
 		"doc_type":"usermanual2",
-		"p_code":"408",
-		"code":"409"
+		"p_code":"409",
+		"code":"410"
 	},
 	{
 		"desc":"After a ConfigMap is created, it can be used in three workload scenarios: environment variables, command line parameters, and data volumes.Configuring Environment Variabl",
@@ -3686,8 +3695,8 @@
 		"title":"Using a ConfigMap",
 		"uri":"cce_10_0015.html",
 		"doc_type":"usermanual2",
-		"p_code":"408",
-		"code":"410"
+		"p_code":"409",
+		"code":"411"
 	},
 	{
 		"desc":"A secret is a type of resource that holds sensitive data, such as authentication and key information. Its content is user-defined. After creating secrets, you can use the",
@@ -3695,8 +3704,8 @@
 		"title":"Creating a Secret",
 		"uri":"cce_10_0153.html",
 		"doc_type":"usermanual2",
-		"p_code":"408",
-		"code":"411"
+		"p_code":"409",
+		"code":"412"
 	},
 	{
 		"desc":"After secrets are created, they can be mounted as data volumes or be exposed as environment variables to be used by a container in a pod.Do not perform any operation on t",
@@ -3704,8 +3713,8 @@
 		"title":"Using a Secret",
 		"uri":"cce_10_0016.html",
 		"doc_type":"usermanual2",
-		"p_code":"408",
-		"code":"412"
+		"p_code":"409",
+		"code":"413"
 	},
 	{
 		"desc":"By default, CCE creates the following secrets in each namespace:default-secretpaas.elbdefault-token-xxxxx (xxxxx is a random number.)The functions of these secrets are de",
@@ -3713,8 +3722,8 @@
 		"title":"Cluster Secrets",
 		"uri":"cce_10_0388.html",
 		"doc_type":"usermanual2",
-		"p_code":"408",
-		"code":"413"
+		"p_code":"409",
+		"code":"414"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3723,7 +3732,7 @@
 		"uri":"cce_10_0064.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"414"
+		"code":"415"
 	},
 	{
 		"desc":"CCE provides multiple types of add-ons to extend cluster functions and meet feature requirements. You can install add-ons as required.CCE uses Helm charts to deploy add-o",
@@ -3731,8 +3740,8 @@
 		"title":"Overview",
 		"uri":"cce_10_0277.html",
 		"doc_type":"usermanual2",
-		"p_code":"414",
-		"code":"415"
+		"p_code":"415",
+		"code":"416"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3740,8 +3749,8 @@
 		"title":"Scheduling and Elasticity Add-ons",
 		"uri":"cce_10_0907.html",
 		"doc_type":"usermanual2",
-		"p_code":"414",
-		"code":"416"
+		"p_code":"415",
+		"code":"417"
 	},
 	{
 		"desc":"Volcano is a batch processing platform based on Kubernetes. It provides a series of features required by machine learning, deep learning, bioinformatics, genomics, and ot",
@@ -3749,8 +3758,8 @@
 		"title":"Volcano Scheduler",
 		"uri":"cce_10_0193.html",
 		"doc_type":"usermanual2",
-		"p_code":"416",
-		"code":"417"
+		"p_code":"417",
+		"code":"418"
 	},
 	{
 		"desc":"The CCE Cluster Autoscaler add-on is built on the Autoscaler component of the community. It can automatically adjust the number of cluster nodes based on the resource nee",
@@ -3758,8 +3767,8 @@
 		"title":"CCE Cluster Autoscaler",
 		"uri":"cce_10_0154.html",
 		"doc_type":"usermanual2",
-		"p_code":"416",
-		"code":"418"
+		"p_code":"417",
+		"code":"419"
 	},
 	{
 		"desc":"The CCE Advanced HPA add-on (formerly cce-hpa-controller) is developed by CCE. It can be used to flexibly scale in or out Deployments based on metrics such as CPU usage a",
@@ -3767,8 +3776,8 @@
 		"title":"CCE Advanced HPA",
 		"uri":"cce_10_0240.html",
 		"doc_type":"usermanual2",
-		"p_code":"416",
-		"code":"419"
+		"p_code":"417",
+		"code":"420"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3776,8 +3785,8 @@
 		"title":"Cloud Native Observability Add-ons",
 		"uri":"cce_10_0908.html",
 		"doc_type":"usermanual2",
-		"p_code":"414",
-		"code":"420"
+		"p_code":"415",
+		"code":"421"
 	},
 	{
 		"desc":"The Cloud Native Cluster Monitoring add-on (formerly kube-prometheus-stack) uses Prometheus-operator and Prometheus and provides easy-to-use, end-to-end Kubernetes cluste",
@@ -3785,8 +3794,8 @@
 		"title":"Cloud Native Cluster Monitoring",
 		"uri":"cce_10_0406.html",
 		"doc_type":"usermanual2",
-		"p_code":"420",
-		"code":"421"
+		"p_code":"421",
+		"code":"422"
 	},
 	{
 		"desc":"The Cloud Native Log Collection add-on (formerly log-agent) is developed based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This add-on supp",
@@ -3794,8 +3803,8 @@
 		"title":"Cloud Native Log Collection",
 		"uri":"cce_10_0416.html",
 		"doc_type":"usermanual2",
-		"p_code":"420",
-		"code":"422"
+		"p_code":"421",
+		"code":"423"
 	},
 	{
 		"desc":"The CCE Node Problem Detector add-on (formerly NPD) monitors abnormal events of cluster nodes and can connect to a third-party monitoring platform. It is a daemon running",
@@ -3803,8 +3812,8 @@
 		"title":"CCE Node Problem Detector",
 		"uri":"cce_10_0132.html",
 		"doc_type":"usermanual2",
-		"p_code":"420",
-		"code":"423"
+		"p_code":"421",
+		"code":"424"
 	},
 	{
 		"desc":"From version 1.8 onwards, Kubernetes provides resource usage metrics, such as the container CPU and memory usage, through the Metrics API. These metrics can be directly a",
@@ -3812,8 +3821,8 @@
 		"title":"Kubernetes Metrics Server",
 		"uri":"cce_10_0205.html",
 		"doc_type":"usermanual2",
-		"p_code":"420",
-		"code":"424"
+		"p_code":"421",
+		"code":"425"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3821,8 +3830,8 @@
 		"title":"Cloud Native Heterogeneous Computing Add-ons",
 		"uri":"cce_10_0909.html",
 		"doc_type":"usermanual2",
-		"p_code":"414",
-		"code":"425"
+		"p_code":"415",
+		"code":"426"
 	},
 	{
 		"desc":"NVIDIA GPU is a device management add-on that supports GPUs in containers. To use GPU nodes in a cluster, this add-on must be installed.The driver to be downloaded must b",
@@ -3830,8 +3839,8 @@
 		"title":"CCE AI Suite (NVIDIA GPU)",
 		"uri":"cce_10_0141.html",
 		"doc_type":"usermanual2",
-		"p_code":"425",
-		"code":"426"
+		"p_code":"426",
+		"code":"427"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3839,8 +3848,8 @@
 		"title":"Container Network Add-ons",
 		"uri":"cce_10_0910.html",
 		"doc_type":"usermanual2",
-		"p_code":"414",
-		"code":"427"
+		"p_code":"415",
+		"code":"428"
 	},
 	{
 		"desc":"CoreDNS is a DNS server that provides domain name resolution for Kubernetes clusters through a chain add-on.CoreDNS is an open-source software and has been a part of CNCF",
@@ -3848,8 +3857,8 @@
 		"title":"CoreDNS",
 		"uri":"cce_10_0129.html",
 		"doc_type":"usermanual2",
-		"p_code":"427",
-		"code":"428"
+		"p_code":"428",
+		"code":"429"
 	},
 	{
 		"desc":"Kubernetes uses kube-proxy to expose Services and provide load balancing. The implementation is at the transport layer. When it comes to Internet applications, where a bu",
@@ -3857,8 +3866,8 @@
 		"title":"NGINX Ingress Controller",
 		"uri":"cce_10_0034.html",
 		"doc_type":"usermanual2",
-		"p_code":"427",
-		"code":"429"
+		"p_code":"428",
+		"code":"430"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3866,8 +3875,8 @@
 		"title":"Container Storage Add-ons",
 		"uri":"cce_10_0911.html",
 		"doc_type":"usermanual2",
-		"p_code":"414",
-		"code":"430"
+		"p_code":"415",
+		"code":"431"
 	},
 	{
 		"desc":"Everest is a cloud native container storage system, which enables clusters of Kubernetes v1.15.6 or later to access cloud storage services through the CSI.Everest is a sy",
@@ -3875,8 +3884,8 @@
 		"title":"CCE Container Storage (Everest)",
 		"uri":"cce_10_0066.html",
 		"doc_type":"usermanual2",
-		"p_code":"430",
-		"code":"431"
+		"p_code":"431",
+		"code":"432"
 	},
 	{
 		"desc":"CCE Container Storage (FlexVolume), also called storage-driver, functions as a standard Kubernetes FlexVolume plugin to allow containers to use EVS, SFS, OBS, and SFS Tur",
@@ -3884,8 +3893,8 @@
 		"title":"FlexVolume (Discarded)",
 		"uri":"cce_10_0127.html",
 		"doc_type":"usermanual2",
-		"p_code":"430",
-		"code":"432"
+		"p_code":"431",
+		"code":"433"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3894,7 +3903,7 @@
 		"uri":"cce_10_0019.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"433"
+		"code":"434"
 	},
 	{
 		"desc":"CCE provides a console for managing Helm charts, helping you easily deploy applications using the charts and manage applications on the console.Helm is a package manager ",
@@ -3902,8 +3911,8 @@
 		"title":"Overview of a Chart",
 		"uri":"cce_10_0191.html",
 		"doc_type":"usermanual2",
-		"p_code":"433",
-		"code":"434"
+		"p_code":"434",
+		"code":"435"
 	},
 	{
 		"desc":"On the CCE console, you can upload a Helm chart package, deploy it, and manage the deployed pods.The number of charts that can be uploaded by a single user is limited. Th",
@@ -3911,8 +3920,8 @@
 		"title":"Deploying an Application from a Chart",
 		"uri":"cce_10_0146.html",
 		"doc_type":"usermanual2",
-		"p_code":"433",
-		"code":"435"
+		"p_code":"434",
+		"code":"436"
 	},
 	{
 		"desc":"Helm v2 stops at version 2.17.0. Currently, Helm v3 is the standard in the Helm community. You are advised to switch your charts to Helm v3 format as soon as possible.Cha",
@@ -3920,8 +3929,8 @@
 		"title":"Differences Between Helm v2 and Helm v3 and Adaptation Solutions",
 		"uri":"cce_10_0421.html",
 		"doc_type":"usermanual2",
-		"p_code":"433",
-		"code":"436"
+		"p_code":"434",
+		"code":"437"
 	},
 	{
 		"desc":"The Kubernetes cluster created on CCE has been connected to kubectl. For details, see Procedure.This section uses Helm v2.17.0 as an example.For other versions, visit htt",
@@ -3929,8 +3938,8 @@
 		"title":"Deploying an Application Through the Helm v2 Client",
 		"uri":"cce_10_0420.html",
 		"doc_type":"usermanual2",
-		"p_code":"433",
-		"code":"437"
+		"p_code":"434",
+		"code":"438"
 	},
 	{
 		"desc":"The Kubernetes cluster created on CCE has been connected to kubectl. For details, see Procedure.To pull a public image when deploying Helm, ensure an EIP has been bound t",
@@ -3938,8 +3947,8 @@
 		"title":"Deploying an Application Through the Helm v3 Client",
 		"uri":"cce_10_0144.html",
 		"doc_type":"usermanual2",
-		"p_code":"433",
-		"code":"438"
+		"p_code":"434",
+		"code":"439"
 	},
 	{
 		"desc":"CCE fully supports Helm v3. This section guides you to convert a Helm v2 release to Helm v3. Helm v3 discards or reconstructs some Helm v2 functions at the bottom layer. ",
@@ -3947,8 +3956,8 @@
 		"title":"Converting a Release from Helm v2 to v3",
 		"uri":"cce_10_0422.html",
 		"doc_type":"usermanual2",
-		"p_code":"433",
-		"code":"439"
+		"p_code":"434",
+		"code":"440"
 	},
 	{
 		"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -3957,7 +3966,7 @@
 		"uri":"cce_10_0164.html",
 		"doc_type":"usermanual2",
 		"p_code":"",
-		"code":"440"
+		"code":"441"
 	},
 	{
 		"desc":"CCE permissions management allows you to assign permissions to IAM users and user groups under your tenant accounts. CCE combines the advantages of Identity and Access Ma",
@@ -3965,8 +3974,8 @@
 		"title":"Permissions Overview",
 		"uri":"cce_10_0187.html",
 		"doc_type":"usermanual2",
-		"p_code":"440",
-		"code":"441"
+		"p_code":"441",
+		"code":"442"
 	},
 	{
 		"desc":"CCE cluster-level permissions are assigned based on IAM system policies and custom policies. You can use user groups to assign permissions to IAM users.Cluster permission",
@@ -3974,8 +3983,8 @@
 		"title":"Granting Cluster Permissions to an IAM User",
 		"uri":"cce_10_0188.html",
 		"doc_type":"usermanual2",
-		"p_code":"440",
-		"code":"442"
+		"p_code":"441",
+		"code":"443"
 	},
 	{
 		"desc":"You can regulate users' or user groups' access to Kubernetes resources in a single namespace based on their Kubernetes RBAC roles. The RBAC API declares four kinds of Kub",
@@ -3983,16 +3992,7 @@
 		"title":"Namespace Permissions (Kubernetes RBAC-based)",
 		"uri":"cce_10_0189.html",
 		"doc_type":"usermanual2",
-		"p_code":"440",
-		"code":"443"
-	},
-	{
-		"desc":"Before assigning permissions to users or user groups, you need to review the information provided in Namespace Permissions (Kubernetes RBAC-based).To use an access policy",
-		"product_code":"cce",
-		"title":"Using the AccessPolicy API to Manage Namespace Permissions (Kubernetes RBAC-based)",
-		"uri":"cce_10_0957.html",
-		"doc_type":"usermanual2",
-		"p_code":"440",
+		"p_code":"441",
 		"code":"444"
 	},
 	{
@@ -4001,7 +4001,7 @@
 		"title":"Example: Designing and Configuring Permissions for Users in a Department",
 		"uri":"cce_10_0245.html",
 		"doc_type":"usermanual2",
-		"p_code":"440",
+		"p_code":"441",
 		"code":"445"
 	},
 	{
@@ -4010,7 +4010,7 @@
 		"title":"Permission Dependency of the CCE Console",
 		"uri":"cce_10_0190.html",
 		"doc_type":"usermanual2",
-		"p_code":"440",
+		"p_code":"441",
 		"code":"446"
 	},
 	{
@@ -4019,7 +4019,7 @@
 		"title":"Service Account Token Security Improvement",
 		"uri":"cce_10_0477.html",
 		"doc_type":"usermanual2",
-		"p_code":"440",
+		"p_code":"441",
 		"code":"447"
 	},
 	{
@@ -4446,7 +4446,7 @@
 		"code":"494"
 	},
 	{
-		"desc":"A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK and SK. This h",
+		"desc":"A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK/SK. This helps",
 		"product_code":"cce",
 		"title":"Configuration Suggestions on CCE Workload Identity Security",
 		"uri":"cce_bestpractice_0333.html",
@@ -4815,7 +4815,7 @@
 		"code":"535"
 	},
 	{
-		"desc":"To access a Kubernetes cluster from a client, you can use the Kubernetes command line tool kubectl.Create a daemonSet file.vi daemonSet.yamlAn example YAML file is provid",
+		"desc":"To access a Kubernetes cluster from a client, you can use the Kubernetes command line tool kubectl.Create a DaemonSet file.vi daemonset.yamlAn example YAML file is provid",
 		"product_code":"cce",
 		"title":"Modifying Kernel Parameters Using a Privileged Container",
 		"uri":"cce_bestpractice_00227.html",
@@ -5148,7 +5148,7 @@
 		"code":"572"
 	},
 	{
-		"desc":"SymptomA node is running properly and has GPU resources. However, the following error information is displayed:0/9 nodes are available: 9 insufficient nvidia.com/gpuAnaly",
+		"desc":"SymptomA node is running properly and has GPU resources. However, the following error information is displayed:0/9 nodes are available: 9 insufficient nvida.com/gpuAnalys",
 		"product_code":"cce",
 		"title":"How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?",
 		"uri":"cce_faq_00020.html",
diff --git a/docs/cce/umn/CVE-2025-23266.html b/docs/cce/umn/CVE-2025-23266.html
new file mode 100644
index 000000000..df06100c0
--- /dev/null
+++ b/docs/cce/umn/CVE-2025-23266.html
@@ -0,0 +1,60 @@
+<a name="CVE-2025-23266"></a><a name="CVE-2025-23266"></a>
+
+<h1 class="topictitle1">Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267)</h1>
+<div id="body32001227"><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p1318192817101">NVIDIA Container Toolkit is an open-source tool package from NVIDIA. It allows you to use NVIDIA GPUs to speed up computing in a containerized environment. The toolkit includes a container runtime library and utilities for automatically configuring containers to leverage NVIDIA GPUs.</p>
+<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section1217032912611"><h4 class="sectiontitle">Description</h4>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_en-us_topic_0193581139_table1565618845915" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Vulnerability details</caption><thead align="left"><tr id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_en-us_topic_0193581139_row065718811595"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.2.2.2.5.1.1"><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_en-us_topic_0193581139_p265798165915">Type</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.2.2.2.5.1.2"><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_en-us_topic_0193581139_p465798195911">CVE-ID</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.2.2.2.5.1.3"><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p197165314415">Severity</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.2.2.2.5.1.4"><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p568860163217">Discovered</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_en-us_topic_0193581139_row1120510564498"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.1 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p111259410113">Container escape</p>
+</td>
+<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.2 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p8553132017127"><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-23266" target="_blank" rel="noopener noreferrer">CVE-2025-23266</a></p>
+</td>
+<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.3 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p16697543175417">Critical</p>
+</td>
+<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.4 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_p26882020325">2025-07-17</p>
+</td>
+</tr>
+<tr id="CVE-2025-23266__en-us_topic_0000002394138741_row1682703812545"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.1 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_p1282723817549">Data tampering and denial of service</p>
+</td>
+<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.2 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_p8827103865410"><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-23267" target="_blank" rel="noopener noreferrer">CVE-2025-23267</a></p>
+</td>
+<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.3 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_p19827193895419">High</p>
+</td>
+<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.2.2.2.5.1.4 "><p id="CVE-2025-23266__en-us_topic_0000002394138741_p4827193818547">2025-07-17</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section122155314507"><h4 class="sectiontitle">Impact</h4><p id="CVE-2025-23266__en-us_topic_0000002394138741_p556962214815">In NVIDIA Container Toolkit v1.17.7 and earlier versions, an attacker can run a malicious image, which may result in container escape and enables the attacker to obtain host permissions. Successful exploitation of these vulnerabilities may enable privilege escalation, data tampering, information leakage, and denial of service.</p>
+</div>
+<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section226916579125"><h4 class="sectiontitle">Identification Method</h4><ol id="CVE-2025-23266__en-us_topic_0000002394138741_ol10950421495"><li id="CVE-2025-23266__en-us_topic_0000002394138741_li495092894">If the cluster does not have the CCE AI Suite (NVIDIA GPU) add-on installed or the add-on version is earlier than 2.0.0, these vulnerabilities are not relevant.<p id="CVE-2025-23266__en-us_topic_0000002394138741_p75860359503"><a name="CVE-2025-23266__en-us_topic_0000002394138741_li495092894"></a><a name="en-us_topic_0000002394138741_li495092894"></a></p>
+<p id="CVE-2025-23266__en-us_topic_0000002394138741_p11444832219"></p>
+<div class="note" id="CVE-2025-23266__en-us_topic_0000002394138741_note131811144201810"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="CVE-2025-23266__en-us_topic_0000002394138741_p558861081414">In earlier versions, CCE AI Suite (NVIDIA GPU) add-on are named gpu-beta or gpu-device-plugin.</p>
+</div></div>
+</li><li id="CVE-2025-23266__en-us_topic_0000002394138741_li68144233118">If the CCE AI Suite (NVIDIA GPU) add-on version is in the range of 2.0.0 to 2.2.1 or 2.5.0 to 2.8.1, log in to the GPU node and run the following command:<pre class="screen" id="CVE-2025-23266__en-us_topic_0000002394138741_screen1081432133116">nvidia-container-runtime --version</pre>
+<ul id="CVE-2025-23266__en-us_topic_0000002394138741_ul191419819590"><li id="CVE-2025-23266__en-us_topic_0000002394138741_li12141128135919">If no such command is displayed, these vulnerabilities are not present.</li><li id="CVE-2025-23266__en-us_topic_0000002394138741_li914114815594">If the version of nvidia-container-runtime is earlier than 1.17.8, these vulnerabilities are present.<p id="CVE-2025-23266__en-us_topic_0000002394138741_p155991657125816"><a name="CVE-2025-23266__en-us_topic_0000002394138741_li914114815594"></a><a name="en-us_topic_0000002394138741_li914114815594"></a><span><img id="CVE-2025-23266__en-us_topic_0000002394138741_image15351143412490" src="en-us_image_0000002365047420.png"></span></p>
+</li></ul>
+</li></ol>
+</div>
+<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section0651319327"><h4 class="sectiontitle">Solution</h4><p id="CVE-2025-23266__en-us_topic_0000002394138741_p104132591912">Do not run an untrusted container image in the cluster before the vulnerabilities are fixed.</p>
+<p id="CVE-2025-23266__en-us_topic_0000002394138741_p93366712281">CCE will release a new version of the add-on to fix these vulnerabilities. For details, see <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU) Release History</a>.</p>
+</div>
+<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section183061740102419"><h4 class="sectiontitle">Helpful Links</h4><p id="CVE-2025-23266__en-us_topic_0000002394138741_p174671921175419">NVIDIA Container Toolkit Security Bulletin: <a href="https://nvidia.custhelp.com/app/answers/detail/a_id/5659" target="_blank" rel="noopener noreferrer">https://nvidia.custhelp.com/app/answers/detail/a_id/5659</a></p>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_bulletin_0169.html">Security Vulnerability Responses</a></div>
+</div>
+</div>
+
diff --git a/docs/cce/umn/cce_01_0300.html b/docs/cce/umn/cce_01_0300.html
index 75a6fef64..64e8fb822 100644
--- a/docs/cce/umn/cce_01_0300.html
+++ b/docs/cce/umn/cce_01_0300.html
@@ -8,10 +8,28 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_01_0300__row1672312793610"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p372317712362">2025-05-23</p>
+<tbody><tr id="cce_01_0300__row153271013089"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p93277135815">2025-07-25</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p1832717138814">Added <a href="CVE-2025-23266.html">Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267)</a>.</p>
+</td>
+</tr>
+<tr id="cce_01_0300__row198411117281"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p9841101142815">2025-06-30</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p18787624132814">Update:</p>
+<p id="cce_01_0300__p0787202432810">Updated <a href="cce_10_0197.html">Cluster Upgrade Overview</a>.</p>
+<p id="cce_01_0300__p871095682917">Updated <a href="cce_10_0302.html">Before You Start</a>.</p>
+</td>
+</tr>
+<tr id="cce_01_0300__row16582181610456"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p14582171614519">2025-06-23</p>
+</td>
+<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p56586223461">Update:</p>
+<p id="cce_01_0300__p4582191654511">Updated <a href="cce_10_0613.html">Overview</a>. Common I/O disks are the previous-generation product and cannot be created.</p>
+</td>
+</tr>
+<tr id="cce_01_0300__row1672312793610"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p372317712362">2025-05-23</p>
 </td>
 <td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p37306202368">Update:</p>
-<ul id="cce_01_0300__ul7135332163612"><li id="cce_01_0300__li013619326366">Updated <a href="cce_10_0059.html">Configuring Network Policies to Restrict Pod Access</a>.</li><li id="cce_01_0300__li10221163312367">Updated <a href="cce_10_0462.html">Container Engines</a>.</li><li id="cce_01_0300__li299616330369">Updated <a href="cce_10_0476.html">Node OSs</a></li></ul>
+<ul id="cce_01_0300__ul7135332163612"><li id="cce_01_0300__li013619326366">Updated <a href="cce_10_0059.html">Configuring Network Policies to Restrict Pod Access</a>.</li><li id="cce_01_0300__li10221163312367">Updated <a href="cce_10_0462.html">Container Engines</a>.</li><li id="cce_01_0300__li299616330369">Updated <a href="cce_10_0476.html">Node OSs</a>.</li></ul>
 </td>
 </tr>
 <tr id="cce_01_0300__row1257516131090"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p105762136919">2025-05-12</p>
diff --git a/docs/cce/umn/cce_10_0003.html b/docs/cce/umn/cce_10_0003.html
index b59f05025..918af2b25 100644
--- a/docs/cce/umn/cce_10_0003.html
+++ b/docs/cce/umn/cce_10_0003.html
@@ -67,7 +67,7 @@
 </tr>
 <tr id="cce_10_0003__cce_10_0198_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.1 "><p id="cce_10_0003__cce_10_0198_p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><ul id="cce_10_0003__cce_10_0198_ul184351126605"><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0003__cce_10_0198_b53311531183510">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol113317316358"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol12331831193518"><b>Data Disk</b></span>. <strong id="cce_10_0003__cce_10_0198_b1633103163515">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.</li><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><ul id="cce_10_0003__cce_10_0198_ul184351126605"><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0003__cce_10_0198_b13284145912236">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol2284135972312"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol1284135952313"><b>Data Disk</b></span>. <strong id="cce_10_0003__cce_10_0198_b1828495914238">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.</li><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
 <p id="cce_10_0003__cce_10_0198_p3752312011">Click <strong id="cce_10_0003__cce_10_0198_b513813367555">Expand</strong> to configure <strong id="cce_10_0003__cce_10_0198_b13265825195416">Data Disk Space Allocation</strong>. This allocates space for container engines, images, and ephemeral storage to ensure their proper running. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
 <p id="cce_10_0003__cce_10_0198_p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0003__cce_10_0198_b16127101911540">Expand</strong> and select <strong id="cce_10_0003__cce_10_0198_b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. Data disks can also be used as <a href="cce_10_0391.html">local PVs</a> or <a href="cce_10_0726.html">local EVs</a>.</p>
 </td>
diff --git a/docs/cce/umn/cce_10_0006.html b/docs/cce/umn/cce_10_0006.html
index 248e4baef..428e6f516 100644
--- a/docs/cce/umn/cce_10_0006.html
+++ b/docs/cce/umn/cce_10_0006.html
@@ -3,32 +3,32 @@
 <h1 class="topictitle1">Overview</h1>
 <div id="body1522665832344"><p id="cce_10_0006__p1031812215459">A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is an abstract model of a group of pods in Kubernetes. Workloads in Kubernetes are classified as <span class="keyword" id="cce_10_0006__keyword1293375712468">Deployments</span>, <span class="keyword" id="cce_10_0006__keyword1541920224714">StatefulSets</span>, <span class="keyword" id="cce_10_0006__keyword1273972479">DaemonSets</span>, <span class="keyword" id="cce_10_0006__keyword21491010164711">jobs</span>, and <span class="keyword" id="cce_10_0006__keyword19556171584711">cron jobs</span>.</p>
 <p id="cce_10_0006__p11116113204610">CCE provides Kubernetes-native container deployment and management and supports lifecycle management of container workloads, including creation, configuration, monitoring, auto scaling, upgrade, uninstall, service discovery, and load balancing.</p>
-<div class="section" id="cce_10_0006__section9645114684816"><h4 class="sectiontitle">Overview of Pod</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">A pod is the smallest, simplest unit in the Kubernetes object model that you create or deploy. A pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. Each pod has a separate IP address.</p>
+<div class="section" id="cce_10_0006__section9645114684816"><h4 class="sectiontitle">Overview of Pods</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">Pods are the smallest unit that you can create or deploy in Kubernetes. Each pod comprises one or more containers, shared storage (volumes), a unique IP address, and container runtime policies.</p>
 <p id="cce_10_0006__en-us_topic_0254767870_p4629172611480">Pods can be used in either of the following ways:</p>
-<ul id="cce_10_0006__en-us_topic_0254767870_ul062982617481"><li id="cce_10_0006__en-us_topic_0254767870_li1629172611482">A pod runs only one container. This is the most common usage of pods in Kubernetes. You can consider a pod as a container, but Kubernetes directly manages pods instead of containers.</li><li id="cce_10_0006__en-us_topic_0254767870_li1962932615480">A pod runs multiple containers that need to be tightly coupled. In this scenario, a pod contains a main container and several sidecar containers, as shown in <a href="#cce_10_0006__en-us_topic_0254767870_fig347141918551">Figure 1</a>. For example, the main container is a web server that provides file services from a fixed directory, and sidecar containers periodically download files to this fixed directory.<div class="fignone" id="cce_10_0006__en-us_topic_0254767870_fig347141918551"><a name="cce_10_0006__en-us_topic_0254767870_fig347141918551"></a><a name="en-us_topic_0254767870_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>Pod running multiple containers</span><br><span><img id="cce_10_0006__en-us_topic_0254767870_image1835215316361" src="en-us_image_0258392378.png"></span></div>
+<ul id="cce_10_0006__en-us_topic_0254767870_ul062982617481"><li id="cce_10_0006__en-us_topic_0254767870_li1629172611482">A pod runs a single container. This is the most common scenario in Kubernetes. In this case, a pod can be thought of as a container, although Kubernetes manages the pod rather than the container itself.</li><li id="cce_10_0006__en-us_topic_0254767870_li1962932615480">A pod runs multiple tightly coupled containers that need to share resources. In this case, the pod includes a main container and several sidecar containers, as shown in <a href="#cce_10_0006__en-us_topic_0254767870_fig347141918551">Figure 1</a>. For example, the main container might be a web server providing file services from a fixed directory, while sidecar containers periodically download files to that directory.<div class="fignone" id="cce_10_0006__en-us_topic_0254767870_fig347141918551"><a name="cce_10_0006__en-us_topic_0254767870_fig347141918551"></a><a name="en-us_topic_0254767870_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>A pod running multiple containers</span><br><span><img id="cce_10_0006__en-us_topic_0254767870_image1835215316361" src="en-us_image_0258392378.png"></span></div>
 </li></ul>
-<p id="cce_10_0006__en-us_topic_0254767870_p9163143619182">In Kubernetes, pods are rarely created directly. Instead, Kubernetes controller manages pods through pod instances such as Deployments and jobs. A controller typically uses a pod template to create pods. The controller can also manage multiple pods and provide functions such as replica management, rolling upgrade, and self-healing.</p>
+<p id="cce_10_0006__en-us_topic_0254767870_p9163143619182">In Kubernetes, you rarely create pods directly. Instead, controllers like Deployments and jobs create and manage them. These controllers typically use pod templates to create and manage pods, providing features like replica management, rolling upgrades, and self-healing.</p>
 </div>
-<div class="section" id="cce_10_0006__section1972719357496"><h4 class="sectiontitle">Overview of Deployment</h4><p id="cce_10_0006__en-us_topic_0249851113_p13243347131615">A pod is the smallest and simplest unit that you create or deploy in Kubernetes. It is designed to be an ephemeral, one-off entity. A pod can be evicted when node resources are insufficient and disappears along with a cluster node failure. Kubernetes provides controllers to manage pods. Controllers can create and manage pods, and provide replica management, rolling upgrade, and self-healing capabilities. The most commonly used controller is Deployment.</p>
+<div class="section" id="cce_10_0006__section1972719357496"><h4 class="sectiontitle">Overview of Deployments</h4><p id="cce_10_0006__en-us_topic_0249851113_p13243347131615">A pod is the smallest unit that you create or deploy in Kubernetes. It is evicted when resources are tight and gone if its node fails. Kubernetes provides controllers to manage pods. These controllers create and manage pods, providing features like replica management, rolling upgrades, and self-healing. The most common controller is Deployment.</p>
 <div class="fignone" id="cce_10_0006__en-us_topic_0249851113_fig12546173933714"><span class="figcap"><b>Figure 2 </b>Relationship between a Deployment and pods</span><br><span><img id="cce_10_0006__en-us_topic_0249851113_image5671529113711" src="en-us_image_0258095884.png"></span></div>
-<p id="cce_10_0006__en-us_topic_0249851113_p35371248184511">A Deployment can contain one or more pods. These pods have the same role. Therefore, the system automatically distributes requests to multiple pods of a Deployment.</p>
-<p id="cce_10_0006__en-us_topic_0249851113_p11715188281">A Deployment integrates a lot of functions, including online deployment, rolling upgrade, replica creation, and restoration of online jobs. To some extent, Deployments can be used to realize unattended rollout, which greatly reduces difficulties and operation risks in the rollout process.</p>
+<p id="cce_10_0006__en-us_topic_0249851113_p35371248184511">A Deployment runs one or more identical pods. Kubernetes load-balances traffic across them.</p>
+<p id="cce_10_0006__en-us_topic_0249851113_p11715188281">A Deployment handles rollout, rolling upgrades, scaling, and automatic replacement of failed pods. This enables zero-touch releases with minimal risk.</p>
 </div>
-<div class="section" id="cce_10_0006__section14888155424918"><h4 class="sectiontitle">Overview of StatefulSet</h4><p id="cce_10_0006__en-us_topic_0249896621_p12502102192418">All pods under a Deployment have the same characteristics except for the name and IP address. If required, a Deployment can use a pod template to create new pods. If not required, the Deployment can delete any one of the pods.</p>
-<p id="cce_10_0006__en-us_topic_0249896621_p2669143675415">However, Deployments cannot meet the requirements in some distributed scenarios when each pod requires its own status or in a distributed database where each pod requires independent storage.</p>
-<p id="cce_10_0006__en-us_topic_0249896621_p97277467269">Distributed stateful applications involve different roles for different responsibilities. For example, databases work in active/standby mode, and pods depend on each other. To deploy stateful applications in Kubernetes, ensure pods meet the following requirements:</p>
-<ul id="cce_10_0006__en-us_topic_0249896621_ul1181724132317"><li id="cce_10_0006__en-us_topic_0249896621_li10181102419231">Each pod must have a fixed identifier so that it can be recognized by other pods.</li><li id="cce_10_0006__en-us_topic_0249896621_li81819249237">Separate storage resources must be configured for each pod. In this way, the original data can be retrieved after a pod is deleted and restored. Otherwise, the pod status will be changed after the pod is rebuilt.</li></ul>
-<p id="cce_10_0006__en-us_topic_0249896621_p929315724313">To address the preceding requirements, Kubernetes provides StatefulSets.</p>
-<ol id="cce_10_0006__en-us_topic_0249896621_ol117020203559"><li id="cce_10_0006__en-us_topic_0249896621_li183871501692">StatefulSets provide a fixed name for each pod following a fixed number ranging from 0 to N. After a pod is rescheduled, the pod name and the hostname remain unchanged.</li><li id="cce_10_0006__en-us_topic_0249896621_li1789810518913">StatefulSets use a headless Service to allocate a fixed domain name for each pod.</li><li id="cce_10_0006__en-us_topic_0249896621_li43183204569">StatefulSets create PVCs with fixed identifiers to ensure that pods can access the same persistent data after being rescheduled.<div class="fignone" id="cce_10_0006__en-us_topic_0249896621_fig97542112114"><span class="figcap"><b>Figure 3 </b>StatefulSet</span><br><span><img id="cce_10_0006__en-us_topic_0249896621_image9125145402111" src="en-us_image_0258203193.png"></span></div>
+<div class="section" id="cce_10_0006__section14888155424918"><h4 class="sectiontitle">Overview of StatefulSets</h4><p id="cce_10_0006__en-us_topic_0249896621_p12502102192418">All pods under a Deployment are identical except for their names and IP addresses. Deployments can create new pods using a pod template and delete any pod when not needed.</p>
+<p id="cce_10_0006__en-us_topic_0249896621_p2669143675415">However, Deployments are not suitable for distributed scenarios where each pod requires its own status or independent storage, such as in distributed databases.</p>
+<p id="cce_10_0006__en-us_topic_0249896621_p97277467269">Distributed stateful applications often involve different roles and responsibilities. For example, databases may operate in active/standby mode, and pods may depend on each other. To deploy stateful applications in Kubernetes, pods must meet the following requirements:</p>
+<ul id="cce_10_0006__en-us_topic_0249896621_ul1181724132317"><li id="cce_10_0006__en-us_topic_0249896621_li10181102419231">Each pod must have a unique, fixed identifier to be recognized by other pods.</li><li id="cce_10_0006__en-us_topic_0249896621_li81819249237">Each pod should be configured with separate storage resources to ensure data persistence. This allows the original data to be retained and retrieved even after a pod is deleted and recreated. Without dedicated storage, the pod's data will be lost upon deletion, and the new pod will initialize with a different state.</li></ul>
+<p id="cce_10_0006__en-us_topic_0249896621_p929315724313">To address these requirements, Kubernetes provides StatefulSets:</p>
+<ol id="cce_10_0006__en-us_topic_0249896621_ol117020203559"><li id="cce_10_0006__en-us_topic_0249896621_li183871501692">StatefulSets provide a fixed name for each pod, followed by a sequential numeric suffix (for example, pod-0, pod-1, ..., pod-N). After a pod is rescheduled, its name and hostname remain unchanged.</li><li id="cce_10_0006__en-us_topic_0249896621_li1789810518913">StatefulSets use a headless Service to allocate a fixed domain name for each pod.</li><li id="cce_10_0006__en-us_topic_0249896621_li43183204569">StatefulSets create PVCs with fixed identifiers. This ensures that pods can access the original persistent data after being rescheduled.<div class="fignone" id="cce_10_0006__en-us_topic_0249896621_fig97542112114"><span class="figcap"><b>Figure 3 </b>StatefulSet</span><br><span><img id="cce_10_0006__en-us_topic_0249896621_image9125145402111" src="en-us_image_0258203193.png"></span></div>
 </li></ol>
 </div>
-<div class="section" id="cce_10_0006__section7846281504"><h4 class="sectiontitle">Overview of DaemonSet</h4><p id="cce_10_0006__en-us_topic_0249851114_p441104813815">A DaemonSet runs a pod on each node in a cluster and ensures that there is only one pod. This works well for certain system-level applications such as log collection and resource monitoring since they must run on each node and need only a few pods. A good example is kube-proxy.</p>
+<div class="section" id="cce_10_0006__section7846281504"><h4 class="sectiontitle">Overview of DaemonSet</h4><p id="cce_10_0006__en-us_topic_0249851114_p441104813815">A DaemonSet runs a pod on each node in a cluster and ensures that there is only one pod. This works well for certain system-level applications such as log collection and resource monitoring since they must run on each node. A good example is kube-proxy.</p>
 <p id="cce_10_0006__en-us_topic_0249851114_p5986375820">DaemonSets are closely related to nodes. If a node becomes faulty, the DaemonSet will not create the same pods on other nodes.</p>
 <div class="fignone" id="cce_10_0006__en-us_topic_0249851114_fig27588261914"><span class="figcap"><b>Figure 4 </b>DaemonSet</span><br><span><img id="cce_10_0006__en-us_topic_0249851114_image13336133243518" src="en-us_image_0258871213.png"></span></div>
 </div>
-<div class="section" id="cce_10_0006__section153173319578"><h4 class="sectiontitle">Overview of Job and CronJob</h4><p id="cce_10_0006__en-us_topic_0249851115_p10889736123218">Jobs and CronJobs allow you to run short lived, one-off tasks in batch. They ensure the task pods run to completion.</p>
-<ul id="cce_10_0006__en-us_topic_0249851115_ul197714911354"><li id="cce_10_0006__en-us_topic_0249851115_li47711097352">A job is a resource object used by Kubernetes to control batch tasks. Jobs are different from long-term servo tasks (such as Deployments and StatefulSets). The former is started and terminated at specific times, while the latter runs unceasingly unless being terminated. The pods managed by a job will be automatically removed after successfully completing tasks based on user configurations.</li><li id="cce_10_0006__en-us_topic_0249851115_li249061111353">A CronJob runs a job periodically on a specified schedule. A CronJob object is similar to a line of a crontab file in Linux.</li></ul>
-<p id="cce_10_0006__en-us_topic_0249851115_p166171774387">This run-to-completion feature of jobs is especially suitable for one-off tasks, such as continuous integration (CI).</p>
+<div class="section" id="cce_10_0006__section153173319578"><h4 class="sectiontitle">Overview of Jobs and CronJobs</h4><p id="cce_10_0006__en-us_topic_0249851115_p10889736123218">Jobs and CronJobs are Kubernetes resources designed to manage short-lived, one-off tasks that run to completion.</p>
+<ul id="cce_10_0006__en-us_topic_0249851115_ul197714911354"><li id="cce_10_0006__en-us_topic_0249851115_li47711097352">A job is a resource object used to control batch tasks. Jobs start and terminate at specific times, unlike long-running services such as Deployments and StatefulSets, which run continuously unless terminated. Pods managed by a job are automatically removed after successfully completing their tasks, based on the specified settings.</li><li id="cce_10_0006__en-us_topic_0249851115_li249061111353">A CronJob runs a job periodically on a specified schedule. A CronJob object is similar to a line in a crontab file in Linux.</li></ul>
+<p id="cce_10_0006__en-us_topic_0249851115_p166171774387">The run-to-completion feature of workloads makes them particularly suitable for one-off tasks, such as continuous integration (CI) pipelines.</p>
 </div>
 <div class="section" id="cce_10_0006__section3891192610218"><h4 class="sectiontitle">Workload Lifecycle</h4>
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0006__table488465253420" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Status description</caption><thead align="left"><tr id="cce_10_0006__row13888105212343"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.8.2.2.3.1.1"><p id="cce_10_0006__p1788975203415">Status</p>
diff --git a/docs/cce/umn/cce_10_0010.html b/docs/cce/umn/cce_10_0010.html
index 956fe1d6c..a99833169 100644
--- a/docs/cce/umn/cce_10_0010.html
+++ b/docs/cce/umn/cce_10_0010.html
@@ -19,8 +19,8 @@
 <ul id="cce_10_0010__ul953218444116"><li id="cce_10_0010__li87791418174620">ClusterIP: used to make the Service only reachable from within a cluster.</li><li id="cce_10_0010__li17876227144612">NodePort: used for access from outside a cluster. A NodePort Service is accessed through the port on the node.</li><li id="cce_10_0010__li94953274615">LoadBalancer: used for access from outside a cluster. It is an extension of NodePort, to which a load balancer routes, and external systems only need to access the load balancer.</li></ul>
 <p id="cce_10_0010__p1677717174140">For details about the Service, see <a href="cce_10_0249.html">Overview</a>.</p>
 </div>
-<div class="section" id="cce_10_0010__section1248852094313"><a name="cce_10_0010__section1248852094313"></a><a name="section1248852094313"></a><h4 class="sectiontitle">Ingress</h4><p id="cce_10_0010__p96672218193">Services forward requests using layer-4 TCP and UDP protocols. Ingresses forward requests using layer-7 HTTP and HTTPS protocols. Domain names and paths can be used to achieve finer granularities.</p>
-<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 2 </b>Ingress and Service</span><br><span><img id="cce_10_0010__en-us_topic_0249851122_image8371183511310" src="en-us_image_0258961458.png"></span></div>
+<div class="section" id="cce_10_0010__section1248852094313"><a name="cce_10_0010__section1248852094313"></a><a name="section1248852094313"></a><h4 class="sectiontitle">Ingress</h4><p id="cce_10_0010__p96672218193">Services forward requests using TCP and UDP at Layer 4. Ingresses forward requests using HTTP and HTTPS at Layer 7. Domain names and paths can be used for access of finer granularities.</p>
+<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 2 </b>An ingress and associated Services</span><br><span><img id="cce_10_0010__en-us_topic_0249851122_image8371183511310" src="en-us_image_0258961458.png"></span></div>
 <p id="cce_10_0010__p174691141141410">For details about the ingress, see <a href="cce_10_0094.html">Overview</a>.</p>
 </div>
 <div class="section" id="cce_10_0010__section1286493159"><a name="cce_10_0010__section1286493159"></a><a name="section1286493159"></a><h4 class="sectiontitle">Access Scenarios</h4><p id="cce_10_0010__p1558001514155">Workload access scenarios can be categorized as follows:</p>
diff --git a/docs/cce/umn/cce_10_0012.html b/docs/cce/umn/cce_10_0012.html
index 956534554..05a16c4cf 100644
--- a/docs/cce/umn/cce_10_0012.html
+++ b/docs/cce/umn/cce_10_0012.html
@@ -92,7 +92,7 @@
 </tr>
 <tr id="cce_10_0012__cce_10_0363_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><ul id="cce_10_0012__cce_10_0363_ul13347201216402"><li id="cce_10_0012__cce_10_0363_li103472126407"><strong id="cce_10_0012__cce_10_0363_b493614401788">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol16936640683"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol29366400810"><b>Data Disk</b></span>. <strong id="cce_10_0012__cce_10_0363_b79361840284">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><ul id="cce_10_0012__cce_10_0363_ul13347201216402"><li id="cce_10_0012__cce_10_0363_li103472126407"><strong id="cce_10_0012__cce_10_0363_b87711342223">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol1378123452217"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol107853413227"><b>Data Disk</b></span>. <strong id="cce_10_0012__cce_10_0363_b187815343221">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
 </li><li id="cce_10_0012__cce_10_0363_li18830161664015">If <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol19561032184918"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
 <div class="note" id="cce_10_0012__cce_10_0363_note95411755120"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__cce_10_0363_ul1388875765811"><li id="cce_10_0012__cce_10_0363_li9888165712586">If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.</li><li id="cce_10_0012__cce_10_0363_li7888757125811">Local disks may break down and do not ensure data reliability. Store your service data in EVS disks, which are more reliable than local disks.</li></ul>
 </div></div>
diff --git a/docs/cce/umn/cce_10_0018.html b/docs/cce/umn/cce_10_0018.html
index a74b5b756..f517d110b 100644
--- a/docs/cce/umn/cce_10_0018.html
+++ b/docs/cce/umn/cce_10_0018.html
@@ -1,7 +1,7 @@
 <a name="cce_10_0018"></a><a name="cce_10_0018"></a>
 
 <h1 class="topictitle1">Collecting Container Logs Using ICAgent</h1>
-<div id="body1522667123001"><p id="cce_10_0018__p78381781804">CCE works with AOM to collect workload logs. When a node is created, ICAgent (a DaemonSet named <strong id="cce_10_0018__b13829819578">icagent</strong> in the <strong id="cce_10_0018__b697274313582">kube-system</strong> namespace of a cluster) of AOM is installed by default. ICAgent collects workload logs and reports them to AOM. You can view workload logs on the CCE or AOM console.</p>
+<div id="body1522667123001"><p id="cce_10_0018__p78381781804">CCE can collect workload logs and report them to AOM 1.0. When a node is created, ICAgent (a DaemonSet named <strong id="cce_10_0018__b77653570117">icagent</strong> in the <strong id="cce_10_0018__b1876513573112">kube-system</strong> namespace of a cluster) is installed by default. ICAgent collects workload logs and reports them to AOM 1.0. You can view workload logs on the CCE or AOM 1.0 console.</p>
 <div class="section" id="cce_10_0018__section17884754413"><h4 class="sectiontitle">Constraints</h4><p id="cce_10_0018__p23831558355">ICAgent only collects text logs in .log, .trace, and .out formats.</p>
 </div>
 <div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, set logging for the container.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000002218820458.png"></span> to add a log policy.</span><p><p id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary depending on workloads.</p>
@@ -31,7 +31,7 @@
 </tr>
 <tr id="cce_10_0018__row6588187135510"><td class="cellrowborder" valign="top" width="22.12%" headers="mcps1.3.3.2.3.2.1.2.3.1.1 "><p id="cce_10_0018__p758720775520">Extended Host Path</p>
 </td>
-<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><p id="cce_10_0018__p10159815204516">This parameter is mandatory only if <strong id="cce_10_0018__b1319582314326">Volume Type</strong> is set to <span class="uicontrol" id="cce_10_0018__uicontrol104741538114511"><b>HostPath</b></span>.</p>
+<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><p id="cce_10_0018__p10159815204516">This parameter is mandatory only if <strong id="cce_10_0018__b1319582314326">Volume Type</strong> is set to <span class="uicontrol" id="cce_10_0018__uicontrol104741538114511"><b>hostPath</b></span>.</p>
 <p id="cce_10_0018__p15012414486">Extended host paths contain pod IDs or container names to distinguish different containers into which the host path is mounted.</p>
 <p id="cce_10_0018__p158737185514">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword1142267981799">Pod</span>.</p>
 <ul id="cce_10_0018__ul1358877135514"><li id="cce_10_0018__li115872725517"><strong id="cce_10_0018__b67128281231">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li8587474550"><strong id="cce_10_0018__b37109352310">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li14587127185513"><strong id="cce_10_0018__b1246417411639">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li10587117175514"><strong id="cce_10_0018__b1232314820315">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li758816716559"><strong id="cce_10_0018__b15921753534">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
@@ -39,7 +39,7 @@
 </tr>
 <tr id="cce_10_0018__row1740653212476"><td class="cellrowborder" valign="top" width="22.12%" headers="mcps1.3.3.2.3.2.1.2.3.1.1 "><p id="cce_10_0018__p84061032144714">Collection Path</p>
 </td>
-<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><p id="cce_10_0018__p157615551480">A collection path narrows down the scope of collection to specified logs. </p>
+<td class="cellrowborder" valign="top" width="77.88000000000001%" headers="mcps1.3.3.2.3.2.1.2.3.1.2 "><p id="cce_10_0018__p157615551480">A collection path narrows down the scope of collection to specified logs.</p>
 <ul id="cce_10_0018__ul1676055194810"><li id="cce_10_0018__li2761555134814">If no collection path is specified, log files in <strong id="cce_10_0018__b471281022817">.log</strong>, <strong id="cce_10_0018__b1171218102289">.trace</strong>, and <strong id="cce_10_0018__b1671221022818">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li13761955144810"><strong id="cce_10_0018__b71586376261">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b559191242719">.log</strong>, <strong id="cce_10_0018__b1515321718274">.trace</strong>, and <strong id="cce_10_0018__b1766462192711">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li27745518483">* in log file names indicates a fuzzy match.</li></ul>
 <p id="cce_10_0018__p197795574820">Example: The collection path <strong id="cce_10_0018__b591619449318">/tmp/**/test*.log</strong> indicates that all <strong id="cce_10_0018__b4875453173116">.log</strong> files prefixed with <strong id="cce_10_0018__b1651618112234">test</strong> will be collected from <strong id="cce_10_0018__b442040193212">/tmp</strong> and subdirectories at 5 levels deep.</p>
 <div class="caution" id="cce_10_0018__note1039671516135"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><p id="cce_10_0018__p5396171516138">Ensure that ICAgent is of version 5.12.22 or later.</p>
@@ -154,8 +154,8 @@ spec:
 <td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p6329709512">Extended host path</p>
 </td>
 <td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p32881805119">Extended host paths contain pod IDs or container names to distinguish different containers into which the host path is mounted.</p>
-<p id="cce_10_0018__p1728888115112">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword2086484341">Pod</span>.</p>
-<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b1545738741">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b336551886">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b699631887">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b1011057369">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li528898175110"><strong id="cce_10_0018__b8818125942116">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
+<p id="cce_10_0018__p1728888115112">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword1139599226">Pod</span>.</p>
+<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b2096972405">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b1853265394">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b1166760841">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b1153089692">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li528898175110"><strong id="cce_10_0018__b8818125942116">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
 </td>
 </tr>
 <tr id="cce_10_0018__row732915085118"><td class="cellrowborder" valign="top" width="17.06%" headers="mcps1.3.4.7.2.4.1.1 "><p id="cce_10_0018__p17329004514">policy.logs.rotate</p>
@@ -163,7 +163,7 @@ spec:
 <td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p123292055113">Log dump</p>
 </td>
 <td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p1017113396539">Log dump refers to rotating log files on a local host.</p>
-<ul id="cce_10_0018__ul1617120398533"><li id="cce_10_0018__li71711639105316"><strong id="cce_10_0018__b4837638192520">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new <strong id="cce_10_0018__b98429388254">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b2216332192917">.zip</strong> files. When the number of <strong id="cce_10_0018__b1621653252914">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1321623212917">.zip</strong> files will be deleted. After the dump is complete, the log file in AOM will be cleared.</li><li id="cce_10_0018__li817133985315"><strong id="cce_10_0018__b1147822082">Disabled</strong>: AOM does not dump log files.</li></ul>
+<ul id="cce_10_0018__ul1617120398533"><li id="cce_10_0018__li71711639105316"><strong id="cce_10_0018__b4837638192520">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new <strong id="cce_10_0018__b98429388254">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b2216332192917">.zip</strong> files. When the number of <strong id="cce_10_0018__b1621653252914">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1321623212917">.zip</strong> files will be deleted. After the dump is complete, the log file in AOM will be cleared.</li><li id="cce_10_0018__li817133985315"><strong id="cce_10_0018__b904617367">Disabled</strong>: AOM does not dump log files.</li></ul>
 <div class="note" id="cce_10_0018__note121711639195319"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0018__ul817183918533"><li id="cce_10_0018__li9171183945310">AOM rotates log files using copytruncate. Before enabling log dumping, ensure that log files are written in the append mode. Otherwise, file holes may occur.</li><li id="cce_10_0018__li1117153914535">Currently, mainstream log components such as Log4j and Logback support log file rotation. If you have already set rotation for log files, skip the configuration. Otherwise, conflicts may occur.</li><li id="cce_10_0018__li317113915532">You are advised to configure log file rotation for your own services to flexibly control the size and number of rolled files.</li></ul>
 </div></div>
 </td>
@@ -173,7 +173,7 @@ spec:
 <td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p14388112019519">Collection path</p>
 </td>
 <td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p63882201153">A collection path narrows down the scope of collection to specified logs.</p>
-<ul id="cce_10_0018__ul73883209510"><li id="cce_10_0018__li14388162011513">If no collection path is specified, log files in <strong id="cce_10_0018__b66511633">.log</strong>, <strong id="cce_10_0018__b1809733917">.trace</strong>, and <strong id="cce_10_0018__b902667841">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b1859325291">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b545945728">.log</strong>, <strong id="cce_10_0018__b925379927">.trace</strong>, and <strong id="cce_10_0018__b2124849760">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li1938811201058">* in log file names indicates a fuzzy match.</li></ul>
+<ul id="cce_10_0018__ul73883209510"><li id="cce_10_0018__li14388162011513">If no collection path is specified, log files in <strong id="cce_10_0018__b2026342724">.log</strong>, <strong id="cce_10_0018__b1347420583">.trace</strong>, and <strong id="cce_10_0018__b853742260">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b225411883">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b460049641">.log</strong>, <strong id="cce_10_0018__b376857982">.trace</strong>, and <strong id="cce_10_0018__b678268777">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li1938811201058">* in log file names indicates a fuzzy match.</li></ul>
 <p id="cce_10_0018__p17388152013515">Example: The collection path <strong id="cce_10_0018__b19951612237">/tmp/**/test*.log</strong> indicates that all <strong id="cce_10_0018__b49571315239">.log</strong> files prefixed with <strong id="cce_10_0018__b4958101202315">test</strong> will be collected from <strong id="cce_10_0018__b695815172316">/tmp</strong> and subdirectories at 5 levels deep.</p>
 <div class="caution" id="cce_10_0018__note153881220751"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><p id="cce_10_0018__p938810204516">Ensure that ICAgent is of version 5.12.22 or later.</p>
 </div></div>
@@ -202,16 +202,12 @@ spec:
 <div class="section" id="cce_10_0018__section25851847232"><h4 class="sectiontitle">Viewing Logs</h4><p id="cce_10_0018__p209669599247">After a log collection path is configured and the workload is created, the ICAgent collects log files from the configured path. The collection takes about 1 minute.</p>
 <p id="cce_10_0018__p242194515304">After the log collection is complete, go to the workload details page and click <strong id="cce_10_0018__b13484541192818">Logs</strong> in the upper right corner to view logs.</p>
 <p id="cce_10_0018__p32989282515">You can also view logs on the AOM console.</p>
-<p id="cce_10_0018__p160613416815">You can also run the <strong id="cce_10_0018__b9741144192912">kubectl logs</strong> command to view the container stdout.</p>
-<pre class="screen" id="cce_10_0018__screen1210248152712"># View logs of a specified pod.
-kubectl logs &lt;pod_name&gt;
-kubectl logs -f &lt;pod_name&gt; # Similar to <strong id="cce_10_0018__b34131514579">tail -f</strong>
-
-# View logs of a specified container in a specified pod.
-kubectl logs &lt;pod_name&gt; -c &lt;container_name&gt;
-
-kubectl logs pod_name -c container_name -n namespace (one-off query)
-kubectl logs -f &lt;pod_name&gt; -n namespace (real-time query in tail -f mode)</pre>
+<p id="cce_10_0018__p160613416815">You can also run the <strong id="cce_10_0018__b699413283512">kubectl logs</strong> command to view the container stdout.</p>
+<ul id="cce_10_0018__ul1250775418420"><li id="cce_10_0018__li35074541742">View the logs of a specified pod.<pre class="screen" id="cce_10_0018__screen18206109556">kubectl logs <i><span class="varname" id="cce_10_0018__varname1277517298911">&lt;pod_name&gt;</span></i> -n <i><span class="varname" id="cce_10_0018__varname746213329912">&lt;namespace&gt;</span></i></pre>
+</li><li id="cce_10_0018__li193333401053">View the logs of a specified pod in real time.<pre class="screen" id="cce_10_0018__screen73911048357">kubectl logs -f <i><span class="varname" id="cce_10_0018__varname1551920386912">&lt;pod_name&gt;</span></i> -n <i><span class="varname" id="cce_10_0018__varname15549835990">&lt;namespace&gt;</span></i></pre>
+</li><li id="cce_10_0018__li157481141478">View logs of a specified container in a specified pod.<pre class="screen" id="cce_10_0018__screen437143714715">kubectl logs <i><span class="varname" id="cce_10_0018__varname1541816421097">&lt;pod_name&gt;</span></i> -c <i><span class="varname" id="cce_10_0018__varname3838164713913">&lt;container_name&gt;</span></i> -n <i><span class="varname" id="cce_10_0018__varname11814521897">&lt;namespace&gt;</span></i></pre>
+</li><li id="cce_10_0018__li157531051278">View the logs of a specified container in a specified pod in real time.<pre class="screen" id="cce_10_0018__screen12800441689">kubectl logs -f <i><span class="varname" id="cce_10_0018__varname722819579917">&lt;pod_name&gt;</span></i> -c <i><span class="varname" id="cce_10_0018__varname49521702107">&lt;container_name&gt;</span></i> -n <i><span class="varname" id="cce_10_0018__varname73741143105">&lt;namespace&gt;</span></i></pre>
+</li></ul>
 </div>
 </div>
 <div>
diff --git a/docs/cce/umn/cce_10_0028.html b/docs/cce/umn/cce_10_0028.html
index cf61cb744..668a4b988 100644
--- a/docs/cce/umn/cce_10_0028.html
+++ b/docs/cce/umn/cce_10_0028.html
@@ -123,7 +123,7 @@
 <tr id="cce_10_0028__row14617175691617"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.2.3.1.1 "><p id="cce_10_0028__p6617456171619">Container CIDR Block</p>
 </td>
 <td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.11.2.3.1.2 "><p id="cce_10_0028__p6617135619168">Specify the CIDR block for containers, which determines the maximum number of containers allowed in the cluster. This parameter is available only for CCE standard clusters. CCE standard clusters allow both manual and automatic CIDR block settings.</p>
-<ul id="cce_10_0028__ul1912520183312"><li id="cce_10_0028__li112581173311"><strong id="cce_10_0028__b1751792413330">Manually set</strong>: You can customize the container CIDR blocks as needed. For cross-VPC passthrough networking, <strong id="cce_10_0028__b9991830145312">make sure the container CIDR block does not overlap with the VPC CIDR block to be accessed</strong> to prevent conflicts. For details, see <a href="cce_bestpractice_00004.html">Planning CIDR Blocks for a Cluster</a>. The VPC network model allows you to configure multiple CIDR blocks, and container CIDR blocks can be added even after the cluster is created. For details, see <a href="cce_10_0680.html">Adding a Container CIDR Block for a Cluster</a>.</li><li id="cce_10_0028__li13504185216810"><strong id="cce_10_0028__b542814461349">Auto select</strong>: CCE will randomly allocate a non-conflicting CIDR block from the ranges 172.16.0.0/16 to 172.31.0.0/16, or from 10.0.0.0/12, 10.16.0.0/12, 10.32.0.0/12, 10.48.0.0/12, 10.64.0.0/12, 10.80.0.0/12, 10.96.0.0/12, and 10.112.0.0/12. Since the allocated CIRD block cannot be modified after the cluster is created, you are advised to manually configure the CIDR blocks, especially in commercial scenarios.</li></ul>
+<ul id="cce_10_0028__ul1912520183312"><li id="cce_10_0028__li112581173311"><strong id="cce_10_0028__b1751792413330">Manually set</strong>: You can customize the container CIDR blocks as needed. For cross-VPC passthrough networking, <strong id="cce_10_0028__b9991830145312">make sure the container CIDR block does not overlap with the VPC CIDR block to be accessed</strong> to prevent conflicts. For details, see <a href="cce_bestpractice_00004.html">Planning CIDR Blocks for a Cluster</a>. The VPC network model allows you to configure multiple CIDR blocks, and container CIDR blocks can be added even after the cluster is created. For details, see <a href="cce_10_0680.html">Adding a Container CIDR Block for a Cluster</a>.</li><li id="cce_10_0028__li13504185216810"><strong id="cce_10_0028__b542814461349">Auto select</strong>: CCE will randomly allocate a non-conflicting CIDR block from the ranges 172.16.0.0/16 to 172.31.0.0/16, or from 10.0.0.0/12, 10.16.0.0/12, 10.32.0.0/12, 10.48.0.0/12, 10.64.0.0/12, 10.80.0.0/12, 10.96.0.0/12, and 10.112.0.0/12. Since the allocated CIDR block cannot be modified after the cluster is created, you are advised to manually configure the CIDR blocks, especially in commercial scenarios.</li></ul>
 </td>
 </tr>
 <tr id="cce_10_0028__row5402194810320"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.2.3.1.1 "><p id="cce_10_0028__p44501828121020">Pod IP Addresses Reserved for Each Node (supported by CCE standard clusters using a VPC network)</p>
diff --git a/docs/cce/umn/cce_10_0034.html b/docs/cce/umn/cce_10_0034.html
index ef2c393fd..501d6b3fd 100644
--- a/docs/cce/umn/cce_10_0034.html
+++ b/docs/cce/umn/cce_10_0034.html
@@ -17,9 +17,9 @@
 <div class="section" id="cce_10_0034__en-us_topic_0226102211_section92541494210"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0034__en-us_topic_0226102211_p996134411315">Before installing this add-on, you have one available cluster and there is a node running properly. If no cluster is available, create one according to <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</p>
 </div>
 <div class="section" id="cce_10_0034__section1152424015224"><a name="cce_10_0034__section1152424015224"></a><a name="section1152424015224"></a><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0034__ol595195015265"><li id="cce_10_0034__li13183153352515"><span>Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0034__b09296116387"><span id="cce_10_0034__text77103384818">Add-ons</span></strong>, locate <strong id="cce_10_0034__b189291711193814">NGINX Ingress Controller</strong> on the right, and click <strong id="cce_10_0034__b189301611123814">Install</strong>.</span></li><li id="cce_10_0034__li6185135511235"><span>On the <strong id="cce_10_0034__b168313930105924">Install Add-on</strong> page, configure the specifications as needed.</span><p><p id="cce_10_0034__p12804745248">You can adjust the number of add-on pods and resource quotas as required. High availability is not possible with a single pod. If an error occurs on the node where the add-on instance runs, the add-on will fail.</p>
-</p></li><li id="cce_10_0034__li584045813266"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0034__ul741422082911"><li id="cce_10_0034__li0953175016455"><a name="cce_10_0034__li0953175016455"></a><a name="li0953175016455"></a><strong id="cce_10_0034__b247210618418">Ingress Class</strong>: Enter a controller name. The name of each controller in the same cluster must be unique and cannot be set to <strong id="cce_10_0034__b10472106174115">cce</strong> (which is the unique identifier of the ELB ingress controller.) When creating an ingress, you can specify the controller name to declare which controller should manage this ingress.</li><li id="cce_10_0034__li43911954164512"><strong id="cce_10_0034__b87211241203016">Add-on Namespace</strong>: Select a namespace for the ingress controller.</li><li id="cce_10_0034__li194268504296"><strong id="cce_10_0034__b7357351122419">Load Balancer</strong>: Select a shared or dedicated load balancer. If no load balancer is available, create one. The load balancer has at least two listeners, and ports 80 and 443 are not occupied by listeners.</li><li id="cce_10_0034__li19869530141118"><strong id="cce_10_0034__b266512513184">Admission Check</strong>: Admission control is performed on Ingresses to ensure that the controller can generate valid configurations. Admission verification is performed on the configuration of Nginx Ingresses. If the verification fails, the request will be intercepted. For details about admission verification, see <a href="https://kubernetes.github.io/ingress-nginx/e2e-tests/#admission-admission-controller" target="_blank" rel="noopener noreferrer">Access Control</a>.<div class="note" id="cce_10_0034__note13941342101413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0034__ul13288250171411"><li id="cce_10_0034__li1228817507146">Admission check slows down the responses to Ingress requests.</li><li id="cce_10_0034__li172581224167">Only add-ons of version 2.4.1 or later support admission verification.</li></ul>
+</p></li><li id="cce_10_0034__li584045813266"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0034__ul741422082911"><li id="cce_10_0034__li0953175016455"><a name="cce_10_0034__li0953175016455"></a><a name="li0953175016455"></a><strong id="cce_10_0034__b247210618418">Ingress Class</strong>: Enter a controller name. The name of each controller in the same cluster must be unique and cannot be set to <strong id="cce_10_0034__b10472106174115">cce</strong> (which is the unique identifier of the LoadBalancer ingress controller.) When creating an ingress, you can specify the controller name to declare which controller should manage this ingress.</li><li id="cce_10_0034__li43911954164512"><strong id="cce_10_0034__b87211241203016">Add-on Namespace</strong>: Select a namespace for the ingress controller.</li><li id="cce_10_0034__li194268504296"><strong id="cce_10_0034__b7357351122419">Load Balancer</strong>: Select a shared or dedicated load balancer. If no load balancer is available, create one. The load balancer has at least two listeners, and ports 80 and 443 are not occupied by listeners.</li><li id="cce_10_0034__li19869530141118"><strong id="cce_10_0034__b266512513184">Admission Check</strong>: Admission control is performed on Ingresses to ensure that the controller can generate valid configurations. Admission verification is performed on the configuration of Nginx Ingresses. If the verification fails, the request will be intercepted. For details about admission verification, see <a href="https://kubernetes.github.io/ingress-nginx/e2e-tests/#admission-admission-controller" target="_blank" rel="noopener noreferrer">Access Control</a>.<div class="note" id="cce_10_0034__note13941342101413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0034__ul13288250171411"><li id="cce_10_0034__li1228817507146">Admission check slows down the responses to Ingress requests.</li><li id="cce_10_0034__li172581224167">Only add-ons of version 2.4.1 or later support admission verification.</li></ul>
 </div></div>
-</li><li id="cce_10_0034__li66142206315"><strong id="cce_10_0034__b6241732145011">Nginx Parameters</strong>: You can configure the <strong id="cce_10_0034__b1463512386289">nginx.conf</strong> file, which will affect all managed ingresses. You can select <strong id="cce_10_0034__b3983161532">GUI</strong> or <strong id="cce_10_0034__b14983910318">YAML</strong>. <strong id="cce_10_0034__b16984512310">GUI</strong> is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.<p id="cce_10_0034__p1512810221947">To configure custom parameters supported by the Kubernetes community, choose <strong id="cce_10_0034__b23282119319">YAML</strong> and find the related parameters in <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/" target="_blank" rel="noopener noreferrer">ConfigMaps</a>. For example, you can use the <strong id="cce_10_0034__b19750151011317">keep-alive-requests</strong> parameter to describe how to set the maximum number of requests for keeping active connections to 100.</p>
+</li><li id="cce_10_0034__li66142206315"><strong id="cce_10_0034__b6241732145011">Nginx Parameters</strong>: You can configure the <strong id="cce_10_0034__b1463512386289">nginx.conf</strong> file, which will affect all managed ingresses. You can select <strong id="cce_10_0034__b2018813117246">GUI</strong> or <strong id="cce_10_0034__b1918851122410">YAML</strong>. <strong id="cce_10_0034__b1818819182420">GUI</strong> is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.<p id="cce_10_0034__p1512810221947">To configure custom parameters supported by the Kubernetes community, choose <strong id="cce_10_0034__b159349548328">YAML</strong> and find the related parameters in <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/" target="_blank" rel="noopener noreferrer">ConfigMaps</a>. For example, you can use the <strong id="cce_10_0034__b19750151011317">keep-alive-requests</strong> parameter to describe how to set the maximum number of requests for keeping active connections to 100.</p>
 <pre class="screen" id="cce_10_0034__screen6950408718">{
     "keep-alive-requests": "100"
 }</pre>
diff --git a/docs/cce/umn/cce_10_00356.html b/docs/cce/umn/cce_10_00356.html
index c0e1467a9..c842eaaeb 100644
--- a/docs/cce/umn/cce_10_00356.html
+++ b/docs/cce/umn/cce_10_00356.html
@@ -3,8 +3,6 @@
 <h1 class="topictitle1">Logging In to a Container</h1>
 <div id="body0000001151211236"><div class="section" id="cce_10_00356__section7379040716"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_00356__p1134114511811">If you encounter unexpected problems when using a container, you can log in to the container to debug it.</p>
 </div>
-<div class="section" id="cce_10_00356__section1536420242714"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_00356__cce_10_0671_ul1462211293114"><li id="cce_10_00356__cce_10_0671_li126227294120">When kubectl is used in CloudShell, permissions are determined by the logged-in user.</li><li id="cce_10_00356__cce_10_0671_li277014321913">When using CloudShell to access a CCE cluster or container, you can open up to 15 instances concurrently.</li><li id="cce_10_00356__cce_10_0671_li1443882717216">The kubectl certificate in CloudShell is valid for one day. You can reset its validity period by accessing CloudShell through the CCE console.</li></ul>
-</div>
 <div class="section" id="cce_10_00356__section1293318163114"><h4 class="sectiontitle">Using kubectl</h4><ol id="cce_10_00356__ol1392823394416"><li id="cce_10_00356__li1681024195710"><span>Use kubectl to access the cluster. For details, see <a href="cce_10_0107.html">Accessing a Cluster Using kubectl</a>.</span></li><li id="cce_10_00356__li1020013819415"><span>Run the following command to view the created pod:</span><p><pre class="screen" id="cce_10_00356__screen156898195914">kubectl get pod</pre>
 <div class="p" id="cce_10_00356__p18257204595920">The example output is as follows:<pre class="screen" id="cce_10_00356__screen7944553592">NAME                               READY   STATUS    RESTARTS       AGE
 nginx-59d89cb66f-mhljr             1/1     Running   0              11m</pre>
diff --git a/docs/cce/umn/cce_10_0048.html b/docs/cce/umn/cce_10_0048.html
index 1f4142f49..185ebc1fd 100644
--- a/docs/cce/umn/cce_10_0048.html
+++ b/docs/cce/umn/cce_10_0048.html
@@ -95,7 +95,7 @@
 <p id="cce_10_0048__p102354303348">A Service provides external access for pods. With a static IP address, a Service forwards access traffic to pods and automatically balances load for these pods.</p>
 <p id="cce_10_0048__p13343123113612">You can also create a Service after creating a workload. For details about Services of different types, see <a href="cce_10_0249.html">Overview</a>.</p>
 <div class="p" id="cce_10_0048__p310913521612"><strong id="cce_10_0048__b21631580735239">(Optional) Advanced Settings</strong><ul id="cce_10_0048__ul142811417"><li id="cce_10_0048__li0421513417"><strong id="cce_10_0048__cce_10_0047_b15415314859">Upgrade</strong>: Specify the upgrade mode and parameters of the workload. <strong id="cce_10_0048__cce_10_0047_b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0048__cce_10_0047_b1621251402">Replace upgrade</strong> are available. For details, see <a href="cce_10_0397.html">Configuring Workload Upgrade Policies</a>.</li><li id="cce_10_0048__li206428507436"><strong id="cce_10_0048__b1840219331836">Pod Management Policies</strong><p id="cce_10_0048__p151323251334">For some distributed systems, the StatefulSet sequence is unnecessary and/or should not occur. These systems require only uniqueness and identifiers.</p>
-<ul id="cce_10_0048__ul758812493316"><li id="cce_10_0048__li258832417338"><strong id="cce_10_0048__b13534251116">OrderedReady</strong>: The StatefulSet will deploy, delete, or scale pods in order and one by one. (The StatefulSet continues only after the previous pod is ready or deleted.) This is the default policy.</li><li id="cce_10_0048__li1558862416338"><strong id="cce_10_0048__b112293521039">Parallel</strong>: The StatefulSet will create pods in parallel to match the desired scale without waiting, and will delete all pods at once.</li></ul>
+<ul id="cce_10_0048__ul758812493316"><li id="cce_10_0048__li258832417338"><strong id="cce_10_0048__b11948213194116">OrderedReady</strong>: This is the default policy. The StatefulSet will deploy, delete, or scale pods in order and one by one. It continues only after the previous pod is ready or deleted.</li><li id="cce_10_0048__li1558862416338"><strong id="cce_10_0048__b112293521039">Parallel</strong>: The StatefulSet will create pods in parallel to match the desired scale without waiting, and will delete all pods at once.</li></ul>
 </li><li id="cce_10_0048__li7127180594"><strong id="cce_10_0048__cce_10_0047_b289714923012">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Load affinity and node affinity are provided.<ul id="cce_10_0048__cce_10_0047_ul16976133413332"><li id="cce_10_0048__cce_10_0047_li7687143311331"><strong id="cce_10_0048__cce_10_0047_b1243811103214">Load Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0048__cce_10_0047_ul1865517492338"><li id="cce_10_0048__cce_10_0047_li7393234068"><strong id="cce_10_0048__cce_10_0047_b15439175514563">Not configured</strong>: No load affinity policy is configured.</li><li id="cce_10_0048__cce_10_0047_li84431255153310"><strong id="cce_10_0048__cce_10_0047_b1069211531709">Multi-AZ deployment preferred</strong>: Workload pods are <strong id="cce_10_0048__cce_10_0047_b126921353203">preferentially</strong> scheduled to nodes in different AZs through pod anti-affinity.</li><li id="cce_10_0048__cce_10_0047_li10775194183413"><strong id="cce_10_0048__cce_10_0047_b1667575214119">Forcible multi-AZ deployment</strong>: Workload pods are forcibly scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0048__cce_10_0047_b10853186174217">podAntiAffinity</strong>). If there are fewer AZs than pods, the extra pods will fail to run.</li><li id="cce_10_0048__cce_10_0047_li177960111349"><strong id="cce_10_0048__cce_10_0047_b18931103644418">Customize affinity</strong>: Affinity and anti-affinity policies can be customized. For details, see <a href="cce_10_0893.html">Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity)</a>.</li></ul>
 </li><li id="cce_10_0048__cce_10_0047_li136191442193318"><strong id="cce_10_0048__cce_10_0047_b540915914458">Node Affinity</strong>: Common node affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0048__cce_10_0047_ul106562113415"><li id="cce_10_0048__cce_10_0047_li3815113910617"><strong id="cce_10_0048__cce_10_0047_b129361841585">Not configured</strong>: No node affinity policy is configured.</li><li id="cce_10_0048__cce_10_0047_li11588172453415"><strong id="cce_10_0048__cce_10_0047_b1354131044913">Specify node</strong>: Workload pods can be deployed on specified nodes through node affinity (<strong id="cce_10_0048__cce_10_0047_b17387313105016">nodeAffinity</strong>). If no node is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0048__cce_10_0047_li12588142414347"><strong id="cce_10_0048__cce_10_0047_b1143642735217">Specify node pool</strong>: Workload pods can be deployed in a specified node pool through node affinity (<strong id="cce_10_0048__cce_10_0047_b1443715272523">nodeAffinity</strong>). If no node pool is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0048__cce_10_0047_li14588192418347"><strong id="cce_10_0048__cce_10_0047_b145411819458">Customize affinity</strong>: Affinity and anti-affinity policies can be customized. For details, see <a href="cce_10_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a>.</li></ul>
 </li></ul>
diff --git a/docs/cce/umn/cce_10_0059.html b/docs/cce/umn/cce_10_0059.html
index 3d81884d1..6b421a3cb 100644
--- a/docs/cce/umn/cce_10_0059.html
+++ b/docs/cce/umn/cce_10_0059.html
@@ -67,7 +67,7 @@
 <tr id="cce_10_0059__row19522163363014"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.1.4.1.1 mcps1.3.5.2.1.4.2.1 "><p id="cce_10_0059__p14522113320305">Supported OS</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.1.4.1.2 mcps1.3.5.2.1.4.2.2 "><p id="cce_10_0059__p36942011103714">EulerOS</p>
-<p id="cce_10_0059__p8522163311308">HCE 2.0</p>
+<p id="cce_10_0059__p8522163311308">HCE OS 2.0</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.5.2.1.4.1.3 mcps1.3.5.2.1.4.2.3 "><p id="cce_10_0059__p45221033113015">HCE OS 2.0</p>
 </td>
diff --git a/docs/cce/umn/cce_10_0068.html b/docs/cce/umn/cce_10_0068.html
index b37036d47..7ec7e0bae 100644
--- a/docs/cce/umn/cce_10_0068.html
+++ b/docs/cce/umn/cce_10_0068.html
@@ -14,9 +14,9 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_bulletin_0059.html">Kubernetes 1.27 Release Notes</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="cce_bulletin_0058.html">Kubernetes 1.25 Release Notes</a></strong><br>
+<li class="ulchildlink"><strong><a href="cce_bulletin_0058.html">Kubernetes 1.25 (EOM) Release Notes</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="cce_bulletin_0027.html">Kubernetes 1.23 Release Notes</a></strong><br>
+<li class="ulchildlink"><strong><a href="cce_bulletin_0027.html">Kubernetes 1.23 (EOM) Release Notes</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="cce_bulletin_0026.html">Kubernetes 1.21 (EOM) Release Notes</a></strong><br>
 </li>
diff --git a/docs/cce/umn/cce_10_0132.html b/docs/cce/umn/cce_10_0132.html
index 32801e416..520a2220e 100644
--- a/docs/cce/umn/cce_10_0132.html
+++ b/docs/cce/umn/cce_10_0132.html
@@ -100,7 +100,7 @@
 <p id="cce_10_0132__p2317112419618">Typical scenario: Disk I/O suspension causes process suspension.</p>
 </td>
 <td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.6.4.1.2.2.4.1.3 "><p id="cce_10_0132__p16872758114011">Warning event</p>
-<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b592872265">/dev/kmsg</strong></p>
+<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b1029490566">/dev/kmsg</strong></p>
 <p id="cce_10_0132__p153079591241">Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."</p>
 </td>
 </tr>
@@ -112,7 +112,7 @@
 </div></div>
 </td>
 <td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.6.4.1.2.2.4.1.3 "><p id="cce_10_0132__p944535317711">Warning event</p>
-<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b1027686576">/dev/kmsg</strong></p>
+<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b967989253">/dev/kmsg</strong></p>
 <p id="cce_10_0132__p83993101042">Matching rule: <strong id="cce_10_0132__b15200817134219">Remounting filesystem read-only</strong></p>
 </td>
 </tr>
diff --git a/docs/cce/umn/cce_10_0141.html b/docs/cce/umn/cce_10_0141.html
index a74808596..293003e11 100644
--- a/docs/cce/umn/cce_10_0141.html
+++ b/docs/cce/umn/cce_10_0141.html
@@ -42,7 +42,7 @@ cd /usr/local/nvidia/bin &amp;&amp; ./nvidia-smi</pre>
 <p id="cce_10_0141__p78452015208"><span><img id="cce_10_0141__image5372171217135" src="en-us_image_0000002253620561.png"></span></p>
 </div>
 <div class="section" id="cce_10_0141__section95451728192112"><a name="cce_10_0141__section95451728192112"></a><a name="section95451728192112"></a><h4 class="sectiontitle">Obtaining the Driver Link from Public Network</h4><ol id="cce_10_0141__ol1138125974915"><li id="cce_10_0141__li19138125912498"><span>Log in to the CCE console.</span></li><li id="cce_10_0141__li111387599493"><span>Create a node. In the <strong id="cce_10_0141__b2312250103712">Specifications</strong> area, select the GPU node flavor. The GPU card models are displayed in the lower part of the area.</span><p><p id="cce_10_0141__p1618510475363"></p>
-</p></li></ol><ol start="3" id="cce_10_0141__ol195031456154814"><li id="cce_10_0141__li16232124410505"><span>Log in to the <a href="https://www.nvidia.com/en-us/drivers/" target="_blank" rel="noopener noreferrer">NVIDIA driver download page</a> and search for the driver information. The OS must be <strong id="cce_10_0141__b2476101012208">Linux 64-bit</strong>.</span><p><div class="fignone" id="cce_10_0141__fig11696366517"><span class="figcap"><b>Figure 1 </b>Selecting parameters</span><br><span><img id="cce_10_0141__image1519115318213" src="en-us_image_0000002218820674.png"></span></div>
+</p></li></ol><ol start="3" id="cce_10_0141__ol195031456154814"><li id="cce_10_0141__li16232124410505"><span>Log in to the <a href="https://www.nvidia.com/en-us/drivers/" target="_blank" rel="noopener noreferrer">NVIDIA driver download page</a> and search for the driver information. The OS must be <strong id="cce_10_0141__b14922141114113">Linux 64-bit</strong>.</span><p><div class="fignone" id="cce_10_0141__fig11696366517"><span class="figcap"><b>Figure 1 </b>Selecting parameters</span><br><span><img id="cce_10_0141__image1519115318213" src="en-us_image_0000002218820674.png"></span></div>
 </p></li><li id="cce_10_0141__li1682301014493"><span>After confirming the driver information, click <span class="uicontrol" id="cce_10_0141__uicontrol1411775314551"><b>Find</b></span>. On the displayed page, find the driver to be downloaded and click <span class="uicontrol" id="cce_10_0141__uicontrol163131533185618"><b>View</b></span>.</span><p><div class="fignone" id="cce_10_0141__fig7873421145213"><span class="figcap"><b>Figure 2 </b>Viewing the driver information</span><br><span><img id="cce_10_0141__image29015595501" src="en-us_image_0000002218820658.png"></span></div>
 </p></li><li id="cce_10_0141__li624514474513"><span>Click <strong id="cce_10_0141__b89621609439">Download</strong> and copy the download link.</span><p><div class="fignone" id="cce_10_0141__fig635212293546"><span class="figcap"><b>Figure 3 </b>Obtaining the link</span><br><span><img id="cce_10_0141__image99782175560" src="en-us_image_0000002253620537.png"></span></div>
 </p></li></ol>
diff --git a/docs/cce/umn/cce_10_0164.html b/docs/cce/umn/cce_10_0164.html
index ef2253841..07de0fd6c 100644
--- a/docs/cce/umn/cce_10_0164.html
+++ b/docs/cce/umn/cce_10_0164.html
@@ -10,8 +10,6 @@
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0189.html">Namespace Permissions (Kubernetes RBAC-based)</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="cce_10_0957.html">Using the AccessPolicy API to Manage Namespace Permissions (Kubernetes RBAC-based)</a></strong><br>
-</li>
 <li class="ulchildlink"><strong><a href="cce_10_0245.html">Example: Designing and Configuring Permissions for Users in a Department</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="cce_10_0190.html">Permission Dependency of the CCE Console</a></strong><br>
diff --git a/docs/cce/umn/cce_10_0184.html b/docs/cce/umn/cce_10_0184.html
index 6410c7eb5..3ef2eda8e 100644
--- a/docs/cce/umn/cce_10_0184.html
+++ b/docs/cce/umn/cce_10_0184.html
@@ -2,7 +2,7 @@
 
 <h1 class="topictitle1">Synchronizing the Data of Cloud Servers</h1>
 <div id="body1559203372010"><div class="section" id="cce_10_0184__section2175132617712"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0184__p179715213166">Each node in a cluster is a cloud server or physical machine. After a cluster node is created, you can change the cloud server name or specifications as required. Modifying node specifications will affect services. Perform the operation on nodes one by one.</p>
-<p id="cce_10_0184__p116412521617">Some information of CCE nodes is maintained independently from the ECS console. After you change the name, EIP, or specifications of an ECS on the ECS console, <span class="keyword" id="cce_10_0184__keyword1089112476574">synchronize the ECS</span> with the target node on the CCE console. After the synchronization, information on both consoles is consistent.</p>
+<p id="cce_10_0184__p116412521617">Some information of CCE nodes is maintained independently from the ECS console. After you change the name, EIP, or specifications of an ECS on the ECS console, <span class="keyword" id="cce_10_0184__keyword941733216373">synchronize the ECS</span> with the target node on the CCE console. After the synchronization, information on both consoles is consistent.</p>
 </div>
 <div class="section" id="cce_10_0184__section299918342346"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0184__ul121015107312"><li id="cce_10_0184__li3101810193119">Data, including the VM status, ECS names, number of CPUs, size of memory, ECS specifications, and public IP addresses, can be synchronized.</li><li id="cce_10_0184__li8102110103118">The following data cannot be synchronized: OS, image ID, and disk configuration.</li></ul>
 </div>
diff --git a/docs/cce/umn/cce_10_0185.html b/docs/cce/umn/cce_10_0185.html
index c8aac4b0b..db2fd8d8d 100644
--- a/docs/cce/umn/cce_10_0185.html
+++ b/docs/cce/umn/cce_10_0185.html
@@ -1,13 +1,13 @@
 <a name="cce_10_0185"></a><a name="cce_10_0185"></a>
 
 <h1 class="topictitle1">Logging In to a Node</h1>
-<div id="body1559203372010"><div class="section" id="cce_10_0185__section1492661620507"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0185__ul119041718185518"><li id="cce_10_0185__li12182723114411">Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node. </li><li id="cce_10_0185__li490481815515">Before you log in to a node (an ECS) using SSH through the Internet, ensure that the ECS already has an EIP bound.</li><li id="cce_10_0185__li16904121855510">Only login to a running ECS is allowed.</li><li id="cce_10_0185__li3827103362110">Only the user <strong id="cce_10_0185__b197020279318"><span id="cce_10_0185__text12656192763716">linux</span></strong> can log in to a Linux server.</li></ul>
+<div id="body1559203372010"><div class="section" id="cce_10_0185__section1492661620507"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0185__ul119041718185518"><li id="cce_10_0185__li12182723114411">Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node. </li><li id="cce_10_0185__li490481815515">Before you log in to a node (an ECS) using SSH through the Internet, ensure that the ECS already has an EIP bound.</li><li id="cce_10_0185__li16904121855510">Only login to a running ECS is allowed.</li><li id="cce_10_0185__li3827103362110">Only the user <strong id="cce_10_0185__b197020279318"><span id="cce_10_0185__text12656192763716">linux</span></strong><strong id="cce_10_0185__b1468219125715"></strong> can log in to a Linux server.</li></ul>
 </div>
 <div class="section" id="cce_10_0185__section1391822316511"><h4 class="sectiontitle">Login Modes</h4><p id="cce_10_0185__p9647194820547">You can log in to an ECS in either of the following modes:</p>
 <ul id="cce_10_0185__ul03289813567"><li id="cce_10_0185__li3821114685618">Management console (VNC)<p id="cce_10_0185__p957217278576"><a name="cce_10_0185__li3821114685618"></a><a name="li3821114685618"></a>If an ECS has no EIP, log in to the ECS console and click <strong id="cce_10_0185__b2647192473610">Remote Login</strong> in the same row as the ECS.</p>
 <p id="cce_10_0185__p14616164455714">For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/ecs/en-us_topic_0093263550.html" target="_blank" rel="noopener noreferrer">Login Using VNC</a>.</p>
 </li><li id="cce_10_0185__li1893519588571">SSH<p id="cce_10_0185__p14702017584"><a name="cce_10_0185__li1893519588571"></a><a name="li1893519588571"></a>This mode applies only to ECSs running Linux. Usually, you can use a remote login tool, such as PuTTY, Xshell, and SecureCRT, to log in to your ECS. If none of the remote login tools can be used, log in to the ECS console and click <strong id="cce_10_0185__b6609145220365">Remote Login</strong> in the same row as the ECS to view the connection status and running status of the ECS.</p>
-<div class="note" id="cce_10_0185__note207919182211"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0185__ul1678102051"><li id="cce_10_0185__li980235455">When you use the Windows OS to log in to a Linux node, set <strong id="cce_10_0185__b16493233638">Auto-login username</strong> to <strong id="cce_10_0185__b19521524171510"><span id="cce_10_0185__text37277158556">linux</span></strong>.</li><li id="cce_10_0185__li17802205258">The CCE console does not support node OS upgrade. Do not upgrade the node OS using the <strong id="cce_10_0185__b1291344241719">yum update</strong> command. Otherwise, the container networking components will be unavailable. </li></ul>
+<div class="note" id="cce_10_0185__note207919182211"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0185__ul1678102051"><li id="cce_10_0185__li980235455">When you use the Windows OS to log in to a Linux node, set <strong id="cce_10_0185__b241714328579">Auto-login username</strong> to <strong id="cce_10_0185__b6417103215716"><span id="cce_10_0185__text37277158556">linux</span></strong>.</li><li id="cce_10_0185__li17802205258">The CCE console does not support node OS upgrade. Do not upgrade the node OS using the <strong id="cce_10_0185__b1291344241719">yum update</strong> command. Otherwise, the container networking components will be unavailable. </li></ul>
 </div></div>
 </li></ul>
 </div>
diff --git a/docs/cce/umn/cce_10_0189.html b/docs/cce/umn/cce_10_0189.html
index d9b586bf4..e9d5d7e52 100644
--- a/docs/cce/umn/cce_10_0189.html
+++ b/docs/cce/umn/cce_10_0189.html
@@ -54,7 +54,7 @@
 <div class="section" id="cce_10_0189__section1273861718819"><a name="cce_10_0189__section1273861718819"></a><a name="section1273861718819"></a><h4 class="sectiontitle">Using kubectl to Configure Namespace Permissions</h4><div class="note" id="cce_10_0189__note175512112562"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0189__p13538151245610">When you access a cluster using kubectl, CCE uses the <strong id="cce_10_0189__b384710277513">kubeconfig</strong> file generated on the cluster for authentication. This file contains user information, based on which CCE determines which Kubernetes resources can be accessed via kubectl. Since the <strong id="cce_10_0189__b13536322116">kubeconfig</strong> file contains user identity details, the permissions associated with that user are inherited when accessing the cluster via kubectl. For details about user permissions, see <a href="cce_10_0187.html#cce_10_0187__section1464135853519">Cluster Permissions (IAM-based) and Namespace Permissions (Kubernetes RBAC-based)</a>.</p>
 </div></div>
 <p id="cce_10_0189__p201194431987">In addition to cluster-admin, admin, edit, and view, you can define Roles and RoleBindings to configure the permissions to add, delete, modify, and obtain resources, such as pods, Deployments, and Services, in the namespace.</p>
-<p id="cce_10_0189__p9324202361517">The procedure for creating a Role is very simple. To be specific, specify a namespace and then define rules. The rules in the following example are to allow GET and LIST operations on pods in the default namespace.</p>
+<p id="cce_10_0189__p9324202361517">The definition of a Role is simple. You just specify a namespace and some rules. For example, the following rules allow you to perform GET and LIST operations on pods in the <strong id="cce_10_0189__en-us_topic_0249851132_b18822141015514">default</strong> namespace.</p>
 <pre class="screen" id="cce_10_0189__screen197388108173">kind: Role
 apiVersion: rbac.authorization.k8s.io/v1
 metadata:
@@ -83,7 +83,7 @@ subjects:
   name: 0c97ac3cb280f4d91fa7c0096739e1f8 # User ID of the user-example
   apiGroup: rbac.authorization.k8s.io</pre>
 <p id="cce_10_0189__p195507214188">The <strong id="cce_10_0189__b158631241144713">subjects</strong> section binds a Role with an IAM user so that the IAM user can obtain the permissions defined in the Role, as shown in the following figure.</p>
-<div class="fignone" id="cce_10_0189__fig9473195372813"><span class="figcap"><b>Figure 2 </b>Binding a role to a user</span><br><span><img id="cce_10_0189__en-us_topic_0249851132_image35211083405" src="en-us_image_0262051194.png"></span></div>
+<div class="fignone" id="cce_10_0189__fig9473195372813"><span class="figcap"><b>Figure 2 </b>Binding a Role to a user</span><br><span><img id="cce_10_0189__en-us_topic_0249851132_image35211083405" src="en-us_image_0262051194.png"></span></div>
 <p id="cce_10_0189__p430545215225">You can also specify a user group in the <strong id="cce_10_0189__b193732864815">subjects</strong> section. In this case, all users in the user group obtain the permissions defined in the Role.</p>
 <pre class="screen" id="cce_10_0189__screen2269203813232">...
 subjects:
diff --git a/docs/cce/umn/cce_10_0193.html b/docs/cce/umn/cce_10_0193.html
index 4ad835b5a..c2b9be00a 100644
--- a/docs/cce/umn/cce_10_0193.html
+++ b/docs/cce/umn/cce_10_0193.html
@@ -23,7 +23,7 @@
 
 <div class="tablenoborder"><a name="cce_10_0193__table16382122344317"></a><a name="table16382122344317"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0193__table16382122344317" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Recommended requested resources and resource limits for volcano-admission</caption><thead align="left"><tr id="cce_10_0193__row121622711434"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.2.2.2.1.2.4.2.6.1.1"><p id="cce_10_0193__p0216227174312">Cluster Scale</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.2.2.2.1.2.4.2.6.1.2"><p id="cce_10_0193__p192168275433">CPU Request(m)</p>
+<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.2.2.2.1.2.4.2.6.1.2"><p id="cce_10_0193__p192168275433">CPU Request (m)</p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.2.2.2.1.2.4.2.6.1.3"><p id="cce_10_0193__p8216172717430">vCPU Limit (m)</p>
 </th>
@@ -765,7 +765,7 @@ workload_balancer_third_party_types: ''</pre>
 <p id="cce_10_0193__p6646145622517">This section describes how to configure volcano-scheduler.</p>
 <div class="note" id="cce_10_0193__note13388133393710"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0193__p83326372378">Only Volcano of v1.7.1 and later support this function. </p>
 </div></div>
-<p id="cce_10_0193__p195053623613">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0193__b63121803269">Settings</strong> and click the <strong id="cce_10_0193__b73131309268">Scheduling</strong> tab. In the <strong id="cce_10_0193__b6313130152619">Select Cluster Scheduler</strong> area, select <strong id="cce_10_0193__b93139014269">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0193__b1331314017264">Try Now</strong>.</p>
+<p id="cce_10_0193__p195053623613">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0193__b14411174794417">Settings</strong> and click the <strong id="cce_10_0193__b94116477448">Scheduling</strong> tab. In the <strong id="cce_10_0193__b041174720440">Select Cluster Scheduler</strong> area, select <strong id="cce_10_0193__b19412194717448">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0193__b1341254710440">Try Now</strong>.</p>
 <p id="cce_10_0193__p112531142104212"></p>
 <p id="cce_10_0193__p1566143416357"></p>
 <ul id="cce_10_0193__ul6676425408"><li id="cce_10_0193__li46762264018">Using <strong id="cce_10_0193__b073919506719">resource_exporter</strong>:<pre class="screen" id="cce_10_0193__screen7651947143817">...
@@ -1112,7 +1112,7 @@ workload_balancer_third_party_types: ''</pre>
 <p id="cce_10_0193__en-us_topic_0000001609894173_p4910191692212">v1.23</p>
 <p id="cce_10_0193__en-us_topic_0000001609894173_p091021662211">v1.25</p>
 </td>
-<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.8.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul72541248141916"><li id="cce_10_0193__en-us_topic_0000001609894173_li122546488191">Fixed the issue that the counting pipeline pod of the networkresource add-on occupies supplementary network interfaces (sub-ENIs).</li><li id="cce_10_0193__en-us_topic_0000001609894173_li16254248191912">Fixed the issue where the binpack add-on scores nodes with insufficient resources.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li8254204861913">Fixed the issue of processing resources in the pod with unknown end status.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li2255448151914">Optimized event output.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1525519484195">Supported HA deployment by default.</li></ul>
+<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.8.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul72541248141916"><li id="cce_10_0193__en-us_topic_0000001609894173_li122546488191">Fixed the issue that the counting pipeline pod of the networkresource add-on occupies supplementary network interfaces.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li16254248191912">Fixed the issue where the binpack add-on scores nodes with insufficient resources.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li8254204861913">Fixed the issue of processing resources in the pod with unknown end status.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li2255448151914">Optimized event output.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1525519484195">Supported HA deployment by default.</li></ul>
 </td>
 </tr>
 <tr id="cce_10_0193__en-us_topic_0000001609894173_row328716461974"><td class="cellrowborder" valign="top" width="15.21%" headers="mcps1.3.8.3.2.4.1.1 "><p id="cce_10_0193__en-us_topic_0000001609894173_p132879461770">1.7.1</p>
diff --git a/docs/cce/umn/cce_10_0197.html b/docs/cce/umn/cce_10_0197.html
index dbc2c24ea..f342966f0 100644
--- a/docs/cce/umn/cce_10_0197.html
+++ b/docs/cce/umn/cce_10_0197.html
@@ -123,6 +123,20 @@
 <td class="cellrowborder" valign="top" width="18.49630073985203%" headers="mcps1.3.5.6.2.3.1.7.1.6 "><p id="cce_10_0197__p17651164084113">This function is gradually replaced by EVS snapshot backup.</p>
 </td>
 </tr>
+<tr id="cce_10_0197__row9651940144110"><td class="cellrowborder" valign="top" width="16.306738652269544%" headers="mcps1.3.5.6.2.3.1.7.1.1 "><p id="cce_10_0197__p1365110406419">EVS snapshot backup</p>
+</td>
+<td class="cellrowborder" valign="top" width="15.456908618276344%" headers="mcps1.3.5.6.2.3.1.7.1.2 "><p id="cce_10_0197__p3651184012411">Master node disks, including component images, configurations, logs, and etcd data</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.74745050989802%" headers="mcps1.3.5.6.2.3.1.7.1.3 "><p id="cce_10_0197__p1683020419555">One-click backup on a web page (manually triggered)</p>
+</td>
+<td class="cellrowborder" valign="top" width="18.49630073985203%" headers="mcps1.3.5.6.2.3.1.7.1.4 "><p id="cce_10_0197__p965124012419">1-5 minutes</p>
+</td>
+<td class="cellrowborder" valign="top" width="18.49630073985203%" headers="mcps1.3.5.6.2.3.1.7.1.5 "><p id="cce_10_0197__p9651040104113">20 minutes</p>
+</td>
+<td class="cellrowborder" valign="top" width="18.49630073985203%" headers="mcps1.3.5.6.2.3.1.7.1.6 "><p id="cce_10_0197__p1419134263912">This function is coming soon.</p>
+<p id="cce_10_0197__p0664142611390">After this function is released, it will replace CBR cloud server backup.</p>
+</td>
+</tr>
 </tbody>
 </table>
 </div>
diff --git a/docs/cce/umn/cce_10_0198.html b/docs/cce/umn/cce_10_0198.html
index 0549a8e06..c13e3a873 100644
--- a/docs/cce/umn/cce_10_0198.html
+++ b/docs/cce/umn/cce_10_0198.html
@@ -76,7 +76,7 @@
 </tr>
 <tr id="cce_10_0198__row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0198__p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.3.2.4.1.2.3.1.2 "><ul id="cce_10_0198__ul184351126605"><li id="cce_10_0198__en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0198__b53311531183510">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0198__uicontrol113317316358"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0198__uicontrol12331831193518"><b>Data Disk</b></span>. <strong id="cce_10_0198__b1633103163515">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.</li><li id="cce_10_0198__en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0198__uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0198__uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.3.2.4.1.2.3.1.2 "><ul id="cce_10_0198__ul184351126605"><li id="cce_10_0198__en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0198__b13284145912236">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0198__uicontrol2284135972312"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0198__uicontrol1284135952313"><b>Data Disk</b></span>. <strong id="cce_10_0198__b1828495914238">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.</li><li id="cce_10_0198__en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0198__uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0198__uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
 <p id="cce_10_0198__p3752312011">Click <strong id="cce_10_0198__b513813367555">Expand</strong> to configure <strong id="cce_10_0198__b13265825195416">Data Disk Space Allocation</strong>. This allocates space for container engines, images, and ephemeral storage to ensure their proper running. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
 <p id="cce_10_0198__p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0198__b16127101911540">Expand</strong> and select <strong id="cce_10_0198__b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. Data disks can also be used as <a href="cce_10_0391.html">local PVs</a> or <a href="cce_10_0726.html">local EVs</a>.</p>
 </td>
diff --git a/docs/cce/umn/cce_10_0249.html b/docs/cce/umn/cce_10_0249.html
index 4aac614f8..17b0de3b4 100644
--- a/docs/cce/umn/cce_10_0249.html
+++ b/docs/cce/umn/cce_10_0249.html
@@ -1,13 +1,13 @@
 <a name="cce_10_0249"></a><a name="cce_10_0249"></a>
 
 <h1 class="topictitle1">Overview</h1>
-<div id="body1599887621732"><div class="section" id="cce_10_0249__section674023294115"><h4 class="sectiontitle">Direct Access to a Pod</h4><p id="cce_10_0249__en-us_topic_0249851121_p182313125309">After a pod is created, the following problems may occur if you directly access the pod:</p>
-<ul id="cce_10_0249__en-us_topic_0249851121_ul15494121517303"><li id="cce_10_0249__en-us_topic_0249851121_li10494815133012">The pod can be deleted and recreated at any time by a controller such as a Deployment, and the result of accessing the pod becomes unpredictable.</li><li id="cce_10_0249__en-us_topic_0249851121_li20826546103110">The IP address of the pod is allocated only after the pod is started. Before the pod is started, the IP address of the pod is unknown.</li><li id="cce_10_0249__en-us_topic_0249851121_li1452731723014">An application is usually composed of multiple pods that run the same image. Accessing pods one by one is not efficient.</li></ul>
-<p id="cce_10_0249__en-us_topic_0249851121_p191728509184">For example, an application uses Deployments to create the frontend and backend. The frontend calls the backend for computing, as shown in <a href="#cce_10_0249__en-us_topic_0249851121_fig2173165051811">Figure 1</a>. Three pods are running in the backend, which are independent and replaceable. When a backend pod is re-created, the new pod is assigned with a new IP address, of which the frontend pod is unaware.</p>
+<div id="body1599887621732"><div class="section" id="cce_10_0249__section674023294115"><h4 class="sectiontitle">Direct Access to a Pod</h4><p id="cce_10_0249__en-us_topic_0249851121_p182313125309">After a pod is created, accessing it directly can result in certain problems:</p>
+<ul id="cce_10_0249__en-us_topic_0249851121_ul15494121517303"><li id="cce_10_0249__en-us_topic_0249851121_li10494815133012">The pod can be deleted and recreated at any time by a controller such as a Deployment. If the pod is recreated, access to it may fail.</li><li id="cce_10_0249__en-us_topic_0249851121_li20826546103110">An IP address cannot be assigned to a pod until the pod is started. Before the pod is started, its IP address is unknown.</li><li id="cce_10_0249__en-us_topic_0249851121_li1452731723014">Applications usually run on multiple pods that use the same image. Accessing pods one by one is not efficient.</li></ul>
+<p id="cce_10_0249__en-us_topic_0249851121_p191728509184">For example, Deployments are used to deploy the frontend and backend of an application. The frontend calls the backend for computing, as shown in <a href="#cce_10_0249__en-us_topic_0249851121_fig2173165051811">Figure 1</a>. Three pods are running in the backend, and they are independent and replaceable. When a backend pod is recreated, the new pod is assigned a new IP address, but the frontend pod is unaware of this change.</p>
 <div class="fignone" id="cce_10_0249__en-us_topic_0249851121_fig2173165051811"><a name="cce_10_0249__en-us_topic_0249851121_fig2173165051811"></a><a name="en-us_topic_0249851121_fig2173165051811"></a><span class="figcap"><b>Figure 1 </b>Inter-pod access</span><br><span><img id="cce_10_0249__en-us_topic_0249851121_image178354246205" src="en-us_image_0258894622.png"></span></div>
 </div>
-<div class="section" id="cce_10_0249__section84961935194115"><h4 class="sectiontitle">Using Services for Pod Access</h4><p id="cce_10_0249__en-us_topic_0249851121_p173502035163111">Kubernetes Services are used to solve the preceding pod access problems. A Service has a fixed IP address. (When a CCE cluster is created, a Service CIDR block is set, which is used to allocate IP addresses to Services.) A Service forwards requests accessing the Service to pods based on labels, and at the same time, perform load balancing for these pods.</p>
-<p id="cce_10_0249__en-us_topic_0249851121_p1359552620518">In the preceding example, a Service is added for the frontend pod to access the backend pods. In this way, the frontend pod does not need to be aware of the changes on backend pods, as shown in <a href="#cce_10_0249__en-us_topic_0249851121_fig163156154816">Figure 2</a>.</p>
+<div class="section" id="cce_10_0249__section84961935194115"><h4 class="sectiontitle">Using Services for Pod Access</h4><p id="cce_10_0249__en-us_topic_0249851121_p173502035163111">Kubernetes Services are used to solve the preceding pod access problems. A Service has a fixed IP address. (When you create a CCE cluster, you need to specify a Service CIDR block, which is used to allocate IP addresses to Services.) A Service distributes requests across pods based on labels and balances the loads for these pods.</p>
+<p id="cce_10_0249__en-us_topic_0249851121_p1359552620518">In the preceding example, a Service is created for the frontend pod to access the backend pods. In this way, the frontend pod does not need to be aware of the changes on backend pods, as shown in <a href="#cce_10_0249__en-us_topic_0249851121_fig163156154816">Figure 2</a>.</p>
 <div class="fignone" id="cce_10_0249__en-us_topic_0249851121_fig163156154816"><a name="cce_10_0249__en-us_topic_0249851121_fig163156154816"></a><a name="en-us_topic_0249851121_fig163156154816"></a><span class="figcap"><b>Figure 2 </b>Accessing pods through a Service</span><br><span><img id="cce_10_0249__en-us_topic_0249851121_image1926812771312" src="en-us_image_0258889981.png"></span></div>
 </div>
 <div class="section" id="cce_10_0249__section12500411413"><h4 class="sectiontitle">Service Types</h4><p id="cce_10_0249__p133861126184815">Kubernetes allows you to specify a Service of a required type. The values and actions of different types of Services are as follows:</p>
diff --git a/docs/cce/umn/cce_10_0251.html b/docs/cce/umn/cce_10_0251.html
index ed0a77a71..44722b38d 100644
--- a/docs/cce/umn/cce_10_0251.html
+++ b/docs/cce/umn/cce_10_0251.html
@@ -39,7 +39,7 @@
 </li><li id="cce_10_0251__li7651155094013"><strong id="cce_10_0251__b514020733120">SNI</strong>: stands for Server Name Indication (SNI), which is an extended protocol of TLS. SNI allows multiple TLS-compliant domain names for external access using the same IP address and port number, and different domain names can use different security certificates. After SNI is enabled, the client is allowed to submit the requested domain name when initiating a TLS handshake request. After receiving the TLS request, the load balancer searches for the certificate based on the domain name in the request. If the certificate corresponding to the domain name is found, the load balancer returns the certificate for authorization. Otherwise, the default certificate (server certificate) is returned for authorization.<div class="note" id="cce_10_0251__note59161057134120"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0251__ul341785816517"><li id="cce_10_0251__li1541715805115">The <strong id="cce_10_0251__b17512414311">SNI</strong> option is available only when <strong id="cce_10_0251__b77525411312">HTTPS</strong> is used.</li></ul>
 <ul id="cce_10_0251__ul2041716583512"><li id="cce_10_0251__li541725835112">This function is supported only in clusters of v1.15.11 or later.</li><li id="cce_10_0251__li1265688165219">Only one domain name can be specified for each SNI certificate. Wildcard-domain certificates are supported.</li><li id="cce_10_0251__li742517462581">For ingresses connected to the same ELB port, do not configure SNIs with the same domain name but different certificates. Otherwise, the SNIs will be overwritten.</li></ul>
 </div></div>
-</li><li id="cce_10_0251__li58516183919"><strong id="cce_10_0251__b1962254816312">Security Policy</strong>: combinations of different TLS versions and supported cipher suites available to HTTPS listeners.<p id="cce_10_0251__p15856189913">For details about security policies, see <em id="cce_10_0251__i436812054613">Elastic Load Balance User Guide</em>.</p>
+</li><li id="cce_10_0251__li58516183919"><strong id="cce_10_0251__b1962254816312">Security Policy</strong>: combinations of different TLS versions and supported cipher suites available to HTTPS listeners.<p id="cce_10_0251__p15856189913">For details about security policies, see <em id="cce_10_0251__i155222233215">Elastic Load Balance User Guide</em>.</p>
 <div class="note" id="cce_10_0251__note885111811917"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0251__ul6851018492"><li id="cce_10_0251__li15851118697"><strong id="cce_10_0251__b145331732163211">Security Policy</strong> is available only when <strong id="cce_10_0251__b7534173216327">HTTPS</strong> is selected.</li><li id="cce_10_0251__li285171815918">This function is supported only in clusters of v1.17.9 or later.</li></ul>
 </div></div>
 </li><li id="cce_10_0251__li03351122552"><strong id="cce_10_0251__b665691110482">Backend Protocol</strong>:<p id="cce_10_0251__p53133720554">When the <a href="#cce_10_0251__li6851318392">listener</a> is HTTP-compliant, only <strong id="cce_10_0251__b1711814563211">HTTP</strong> can be selected.</p>
diff --git a/docs/cce/umn/cce_10_0252.html b/docs/cce/umn/cce_10_0252.html
index e675a430a..ab4068f2b 100644
--- a/docs/cce/umn/cce_10_0252.html
+++ b/docs/cce/umn/cce_10_0252.html
@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Creating a LoadBalancer Ingress Using kubectl</h1>
 <div id="body0000001204453469"><p id="cce_10_0252__p1557481754814">This section uses an <a href="cce_10_0047.html#cce_10_0047__section155246177178">Nginx workload</a> as an example to describe how to create a LoadBalancer ingress using kubectl.</p>
 <ul id="cce_10_0252__ul849465471710"><li id="cce_10_0252__li17883121171816">If no load balancer is available in the same VPC, CCE can automatically create a load balancer when creating an ingress. For details, see <a href="#cce_10_0252__section3675115714214">Automatically Creating a Load Balancer While Creating an Ingress</a>.</li><li id="cce_10_0252__li549455416173">If a load balancer is available in the same VPC, perform the operation by referring to <a href="#cce_10_0252__section32300431736">Associating an Existing Load Balancer to an Ingress While Creating the Ingress</a>.</li></ul>
-<div class="section" id="cce_10_0252__section8926910153415"><a name="cce_10_0252__section8926910153415"></a><a name="section8926910153415"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Ingress API Version Upgrade in CCE Clusters v1.23</h4></div><div class="dropdowncontext"><p id="cce_10_0252__p192611033418">In CCE clusters of v1.23 or later, the ingress version is switched to <strong id="cce_10_0252__b19267106347">networking.k8s.io/v1</strong>.</p>
+<div class="section" id="cce_10_0252__section8926910153415"><a name="cce_10_0252__section8926910153415"></a><a name="section8926910153415"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Ingress API Version Upgrade in CCE Clusters v1.23</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_10_0252__p192611033418">In CCE clusters of v1.23 or later, the ingress version is switched to <strong id="cce_10_0252__b19267106347">networking.k8s.io/v1</strong>.</p>
 <p id="cce_10_0252__p11926191033418">Compared with v1beta1, v1 has the following differences in parameters:</p>
 <ul id="cce_10_0252__ul13926101018345"><li id="cce_10_0252__li19926191083416">The ingress type is specified by <strong id="cce_10_0252__b0926161011344">spec.ingressClassName</strong> instead of <strong id="cce_10_0252__b119261410123416">kubernetes.io/ingress.class</strong> in <strong id="cce_10_0252__b11151359144410">annotations</strong>.</li><li id="cce_10_0252__li129264101348">The format of <strong id="cce_10_0252__b571072213484">backend</strong> has changed.</li><li id="cce_10_0252__li179261510143415">The <strong id="cce_10_0252__b1783119292013">pathType</strong> parameter must be specified for each path. The options are as follows:<ul id="cce_10_0252__ul2926131012341"><li id="cce_10_0252__li192661083418"><strong id="cce_10_0252__b958119196203">ImplementationSpecific</strong>: The matching method depends on Ingress Controller. The matching method defined by <strong id="cce_10_0252__b1683113113519">ingress.beta.kubernetes.io/url-match-mode</strong> is used in CCE, which is the same as v1beta1.</li><li id="cce_10_0252__li209261310173414"><strong id="cce_10_0252__b19854141864510">Exact</strong>: exact matching of the URL, which is case-sensitive.</li><li id="cce_10_0252__li179264101349"><strong id="cce_10_0252__b0441291458">Prefix</strong>: matching based on the URL prefix separated by a slash (/). The match is case-sensitive, and elements in the path are matched one by one. A path element refers to a list of labels in the path separated by a slash (/).</li></ul>
 </li></ul>
diff --git a/docs/cce/umn/cce_10_0296.html b/docs/cce/umn/cce_10_0296.html
index 940cc4d2b..b564a506a 100644
--- a/docs/cce/umn/cce_10_0296.html
+++ b/docs/cce/umn/cce_10_0296.html
@@ -67,7 +67,7 @@
 <td class="cellrowborder" valign="top" width="19.11%" headers="mcps1.3.5.5.3.3.2.5.1.2 "><p id="cce_10_0296__p15861381131">A combined policy. The priorities for the policies are as follows: priority &gt; least-waste &gt; random.</p>
 <p id="cce_10_0296__p1458623819320">It is an enhanced least-waste policy configured based on the node pool or scaling group priority. If multiple node pools meet the condition, the least-waste policy is used for further decision-making.</p>
 </td>
-<td class="cellrowborder" valign="top" width="32.16%" headers="mcps1.3.5.5.3.3.2.5.1.3 "><p id="cce_10_0296__p1531734565517">This policy allows you to configure the priorities of node pools or scaling groups through the console or API, while the least-waste policy can effectively minimize resource waste in various scenarios. The priority policy is used as the <strong id="cce_10_0296__b1728171714115">default preferred policy</strong> thanks to its good universality.</p>
+<td class="cellrowborder" valign="top" width="32.16%" headers="mcps1.3.5.5.3.3.2.5.1.3 "><p id="cce_10_0296__p1531734565517">This policy allows you to configure the priorities of node pools or scaling groups through the console or API, while the least-waste policy can effectively minimize resource waste in various scenarios. The priority policy is used as the <strong id="cce_10_0296__b9741113322911">default preferred policy</strong> thanks to its good universality.</p>
 </td>
 <td class="cellrowborder" valign="top" width="38.97%" headers="mcps1.3.5.5.3.3.2.5.1.4 "><p id="cce_10_0296__p7937135781718">Assume that auto scaling is enabled for node pools 1 and 2 in the cluster and the scale-out upper limit is not reached. The policy for scaling out the number of pods for a workload is as follows:</p>
 <ol id="cce_10_0296__ol1893717573177"><li id="cce_10_0296__li593785741713">Pending pods trigger the Autoscaler to determine the scale-out process.</li><li id="cce_10_0296__li189371557131710">Autoscaler simulates the scheduling phase and evaluates that some pending pods can be scheduled to the added nodes in both node pools 1 and 2.</li><li id="cce_10_0296__li29371457181711">Autoscaler evaluates that node pool 1 has a higher priority than node pool 2. Therefore, Autoscaler selects node pool 1 for scale-out.</li></ol>
diff --git a/docs/cce/umn/cce_10_0302.html b/docs/cce/umn/cce_10_0302.html
index 6007d37f1..c5e1c1982 100644
--- a/docs/cce/umn/cce_10_0302.html
+++ b/docs/cce/umn/cce_10_0302.html
@@ -580,6 +580,20 @@
 <td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.6.3.1.7.1.6 "><p id="cce_10_0302__en-us_topic_0000001199021198_p17651164084113">This function is gradually replaced by EVS snapshot backup.</p>
 </td>
 </tr>
+<tr id="cce_10_0302__en-us_topic_0000001199021198_row9651940144110"><td class="cellrowborder" valign="top" width="16%" headers="mcps1.3.6.3.1.7.1.1 "><p id="cce_10_0302__en-us_topic_0000001199021198_p1365110406419">EVS snapshot backup</p>
+</td>
+<td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.6.3.1.7.1.2 "><p id="cce_10_0302__en-us_topic_0000001199021198_p3651184012411">Master node disks, including component images, configurations, logs, and etcd data</p>
+</td>
+<td class="cellrowborder" valign="top" width="13%" headers="mcps1.3.6.3.1.7.1.3 "><p id="cce_10_0302__en-us_topic_0000001199021198_p1683020419555">One-click backup on a web page (manually triggered)</p>
+</td>
+<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.6.3.1.7.1.4 "><p id="cce_10_0302__en-us_topic_0000001199021198_p965124012419">1-5 minutes</p>
+</td>
+<td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.6.3.1.7.1.5 "><p id="cce_10_0302__en-us_topic_0000001199021198_p9651040104113">20 minutes</p>
+</td>
+<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.6.3.1.7.1.6 "><p id="cce_10_0302__en-us_topic_0000001199021198_p1419134263912">This function is coming soon.</p>
+<p id="cce_10_0302__en-us_topic_0000001199021198_p0664142611390">After this function is released, it will replace CBR cloud server backup.</p>
+</td>
+</tr>
 </tbody>
 </table>
 </div>
diff --git a/docs/cce/umn/cce_10_0363.html b/docs/cce/umn/cce_10_0363.html
index 06defce5e..ffce1b481 100644
--- a/docs/cce/umn/cce_10_0363.html
+++ b/docs/cce/umn/cce_10_0363.html
@@ -94,7 +94,7 @@
 </tr>
 <tr id="cce_10_0363__row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.3.3.2.4.1.2.3.1.1 "><p id="cce_10_0363__p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.3.3.2.4.1.2.3.1.2 "><ul id="cce_10_0363__ul13347201216402"><li id="cce_10_0363__li103472126407"><strong id="cce_10_0363__b493614401788">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0363__uicontrol16936640683"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0363__uicontrol29366400810"><b>Data Disk</b></span>. <strong id="cce_10_0363__b79361840284">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0363__ul324262033711"><li id="cce_10_0363__li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0363__li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.3.3.2.4.1.2.3.1.2 "><ul id="cce_10_0363__ul13347201216402"><li id="cce_10_0363__li103472126407"><strong id="cce_10_0363__b87711342223">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0363__uicontrol1378123452217"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0363__uicontrol107853413227"><b>Data Disk</b></span>. <strong id="cce_10_0363__b187815343221">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0363__ul324262033711"><li id="cce_10_0363__li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0363__li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
 </li><li id="cce_10_0363__li18830161664015">If <span class="uicontrol" id="cce_10_0363__uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0363__uicontrol19561032184918"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
 <div class="note" id="cce_10_0363__note95411755120"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0363__ul1388875765811"><li id="cce_10_0363__li9888165712586">If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.</li><li id="cce_10_0363__li7888757125811">Local disks may break down and do not ensure data reliability. Store your service data in EVS disks, which are more reliable than local disks.</li></ul>
 </div></div>
diff --git a/docs/cce/umn/cce_10_0364.html b/docs/cce/umn/cce_10_0364.html
index aafd667b0..b60207d2a 100644
--- a/docs/cce/umn/cce_10_0364.html
+++ b/docs/cce/umn/cce_10_0364.html
@@ -2,7 +2,7 @@
 
 <h1 class="topictitle1">Creating an Nginx Ingress Using kubectl</h1>
 <div id="body0000001159132006"><p id="cce_10_0364__p3861320152812">This section uses an <a href="cce_10_0047.html#cce_10_0047__section155246177178">Nginx workload</a> as an example to describe how to create an Nginx ingress using kubectl.</p>
-<div class="section" id="cce_10_0364__section084115985013"><a name="cce_10_0364__section084115985013"></a><a name="section084115985013"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Ingress API Version Upgrade in CCE Clusters v1.23</h4></div><div class="dropdowncontext"><p id="cce_10_0364__p10742171892110">In CCE clusters of v1.23 or later, the ingress version is switched to <strong id="cce_10_0364__b18568943203216">networking.k8s.io/v1</strong>.</p>
+<div class="section" id="cce_10_0364__section084115985013"><a name="cce_10_0364__section084115985013"></a><a name="section084115985013"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Ingress API Version Upgrade in CCE Clusters v1.23</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_10_0364__p10742171892110">In CCE clusters of v1.23 or later, the ingress version is switched to <strong id="cce_10_0364__b18568943203216">networking.k8s.io/v1</strong>.</p>
 <p id="cce_10_0364__p20567113755215">Compared with v1beta1, v1 has the following differences in parameters:</p>
 <ul id="cce_10_0364__ul1047013217172"><li id="cce_10_0364__li10471183221719">The ingress type is specified by <strong id="cce_10_0364__b554645310324">spec.ingressClassName</strong> instead of <strong id="cce_10_0364__b10546953133213">kubernetes.io/ingress.class</strong> in <strong id="cce_10_0364__b85473536327">annotations</strong>.</li><li id="cce_10_0364__li7135111819196">The format of <strong id="cce_10_0364__b20186273336">backend</strong> has changed.</li><li id="cce_10_0364__li10689134614221">The <strong id="cce_10_0364__b1889316613911">pathType</strong> parameter must be specified for each path. The options are as follows:<ul id="cce_10_0364__ul3253194702213"><li id="cce_10_0364__li456213366269"><strong id="cce_10_0364__b1719418277173">ImplementationSpecific</strong>: The matching method depends on Ingress Controller. The matching method defined by <strong id="cce_10_0364__b2693913999">ingress.beta.kubernetes.io/url-match-mode</strong> is used in CCE, which is the same as v1beta1.</li><li id="cce_10_0364__li5172153972613"><strong id="cce_10_0364__b8201155219426">Exact</strong>: exact matching of the URL, which is case-sensitive.</li><li id="cce_10_0364__li584094916222"><strong id="cce_10_0364__b2048754104211">Prefix</strong>: matching based on the URL prefix separated by a slash (/). The match is case-sensitive, and elements in the path are matched one by one. A path element refers to a list of labels in the path separated by a slash (/).</li></ul>
 </li></ul>
diff --git a/docs/cce/umn/cce_10_0380.html b/docs/cce/umn/cce_10_0380.html
index ef4a771e1..f1d8b6160 100644
--- a/docs/cce/umn/cce_10_0380.html
+++ b/docs/cce/umn/cce_10_0380.html
@@ -123,7 +123,7 @@ metadata:
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.3.5.3.2.5.1.3 "><p id="cce_10_0380__p7360105617584">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_10_0380__p936095685819">Driver type. If an EVS disk is used, the parameter value is fixed at <span class="parmvalue" id="cce_10_0380__parmvalue330635280"><b>disk.csi.everest.io</b></span>.</p>
+<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_10_0380__p936095685819">Driver type. If an EVS disk is used, the parameter value is fixed at <span class="parmvalue" id="cce_10_0380__parmvalue1121200374"><b>disk.csi.everest.io</b></span>.</p>
 </td>
 </tr>
 <tr id="cce_10_0380__row13957193955813"><td class="cellrowborder" valign="top" width="11%" headers="mcps1.3.3.5.3.2.5.1.1 "><p id="cce_10_0380__p1132211331519">EVS</p>
@@ -132,8 +132,8 @@ metadata:
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.3.5.3.2.5.1.3 "><p id="cce_10_0380__p13360145610589">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_10_0380__p17361105611585">If an EVS disk is used, the parameter value can be <span class="parmvalue" id="cce_10_0380__parmvalue771666110"><b>ext4</b></span> or <span class="parmvalue" id="cce_10_0380__parmvalue988868842"><b>xfs</b></span>.</p>
-<div class="p" id="cce_10_0380__p1036185645819">The restrictions on using <span class="parmvalue" id="cce_10_0380__parmvalue716121274"><b>xfs</b></span> are as follows:<ul id="cce_10_0380__ul03616566583"><li id="cce_10_0380__li7361115605816">The nodes must run CentOS 7, HCE OS 2.0, or Ubuntu 22.04, and the Everest version in the cluster must be 2.3.2 or later.</li><li id="cce_10_0380__li5361156125820">Only common containers are supported.</li></ul>
+<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_10_0380__p17361105611585">If an EVS disk is used, the parameter value can be <span class="parmvalue" id="cce_10_0380__parmvalue1079257909"><b>ext4</b></span> or <span class="parmvalue" id="cce_10_0380__parmvalue1239687976"><b>xfs</b></span>.</p>
+<div class="p" id="cce_10_0380__p1036185645819">The restrictions on using <span class="parmvalue" id="cce_10_0380__parmvalue1666719131"><b>xfs</b></span> are as follows:<ul id="cce_10_0380__ul03616566583"><li id="cce_10_0380__li7361115605816">The nodes must run CentOS 7, HCE OS 2.0, or Ubuntu 22.04, and the Everest version in the cluster must be 2.3.2 or later.</li><li id="cce_10_0380__li5361156125820">Only common containers are supported.</li></ul>
 </div>
 </td>
 </tr>
@@ -153,7 +153,7 @@ metadata:
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.3.5.3.2.5.1.3 "><p id="cce_10_0380__p636185665814">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_10_0380__p103626560585">The parameter value is fixed at <span class="parmvalue" id="cce_10_0380__parmvalue410198236"><b>true</b></span>, which indicates that the EVS device type is <strong id="cce_10_0380__b1021717869">SCSI</strong>. No other parameter values are allowed.</p>
+<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_10_0380__p103626560585">The parameter value is fixed at <span class="parmvalue" id="cce_10_0380__parmvalue70974216"><b>true</b></span>, which indicates that the EVS device type is <strong id="cce_10_0380__b1776423110">SCSI</strong>. No other parameter values are allowed.</p>
 </td>
 </tr>
 <tr id="cce_10_0380__row1967312234013"><td class="cellrowborder" valign="top" width="11%" headers="mcps1.3.3.5.3.2.5.1.1 "><p id="cce_10_0380__p10936142812010">SFS</p>
diff --git a/docs/cce/umn/cce_10_0382.html b/docs/cce/umn/cce_10_0382.html
index 06c72f705..d528bee70 100644
--- a/docs/cce/umn/cce_10_0382.html
+++ b/docs/cce/umn/cce_10_0382.html
@@ -70,7 +70,7 @@
 </tbody>
 </table>
 </div>
-<ul id="cce_10_0382__ul915183720207"><li id="cce_10_0382__li131618109208">CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.</li><li id="cce_10_0382__li201583762011">After DataPlane V2 network acceleration is enabled, pods on HCE OS 2.0 use Earliest Departure Time (EDT) to limit the egress bandwidth. The ingress bandwidth limitation is not supported. In other network modes, a Token Bucket Filter (TBF) qdisc is used to limit the bandwidth.</li><li id="cce_10_0382__li1011717215237">Pod bandwidth limitation applies to regular containers (runC as the container runtime), not secure containers (Kata Containers as the container runtime).</li><li id="cce_10_0382__li3430191715236">Pod bandwidth limitation does not apply to hostNetwork pods.</li></ul>
+<ul id="cce_10_0382__ul915183720207"><li id="cce_10_0382__li131618109208">CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.</li><li id="cce_10_0382__li201583762011">After DataPlane V2 network acceleration is enabled, pods on the nodes running HCE OS 2.0 use EDT to limit the egress bandwidth. The ingress bandwidth limitation is not supported. In other network modes, a Token Bucket Filter (TBF) qdisc is used to limit the bandwidth.</li><li id="cce_10_0382__li1011717215237">Pod bandwidth limitation applies to regular containers (runC as the container runtime), not secure containers (Kata Containers as the container runtime).</li><li id="cce_10_0382__li3430191715236">Pod bandwidth limitation does not apply to hostNetwork pods.</li></ul>
 </div>
 </div>
 <div class="section" id="cce_10_0382__section2378202810330"><h4 class="sectiontitle">Using the CCE Console</h4><p id="cce_10_0382__p176971010203413">When creating a workload on the console, you can set pod ingress and egress bandwidth limits by clicking <strong id="cce_10_0382__b14297643149">Network Configuration</strong> in the <span class="uicontrol" id="cce_10_0382__uicontrol3231769353"><b>Advanced Settings</b></span> area.</p>
diff --git a/docs/cce/umn/cce_10_0384.html b/docs/cce/umn/cce_10_0384.html
index ff32ba7c6..74923d722 100644
--- a/docs/cce/umn/cce_10_0384.html
+++ b/docs/cce/umn/cce_10_0384.html
@@ -74,7 +74,7 @@
 <div class="section" id="cce_10_0384__section102385261413"><h4 class="sectiontitle">Compatible kubelet Oversubscription</h4><div class="notice" id="cce_10_0384__note111619321513"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><div class="p" id="cce_10_0384__p10679133852220"><strong id="cce_10_0384__b1912720762219">Specifications</strong><ul id="cce_10_0384__ul19383164411191"><li id="cce_10_0384__li10766125111429">Cluster version<ul id="cce_10_0384__ul62201752154212"><li id="cce_10_0384__li1532115594220">v1.19: v1.19.16-r4 or later</li><li id="cce_10_0384__li3107145714213">v1.21: v1.21.7-r0 or later</li><li id="cce_10_0384__li15200194771716">v1.23: v1.23.5-r0 or later</li><li id="cce_10_0384__li514922914311">v1.25 or later</li></ul>
 </li><li id="cce_10_0384__li4200184712177">Cluster type: CCE standard or Turbo</li><li id="cce_10_0384__li132001147111715">Node OS: EulerOS 2.9 (kernel-4.18.0-147.5.1.6.h729.6.eulerosv2r9.x86_64) or HCE OS 2.0</li><li id="cce_10_0384__li9200947201717">Node type: ECS</li><li id="cce_10_0384__li10364142632218">Volcano version: 1.7.0 or later</li></ul>
 </div>
-<div class="p" id="cce_10_0384__p181841243211"><strong id="cce_10_0384__b417872014395">Constraints</strong><ul id="cce_10_0384__ul81841437118"><li id="cce_10_0384__li1741118264206">Before enabling oversubscription, ensure that the overcommit add-on is not enabled on Volcano.</li><li id="cce_10_0384__li3852121519212">Modifying the label of an oversubscribed node does not affect the running pods.</li><li id="cce_10_0384__li269881617214">Running pods cannot be converted between online and offline services. To convert services, rebuild pods.</li><li id="cce_10_0384__li1149628182118">If the label <strong id="cce_10_0384__b646532916397">volcano.sh/oversubscription=true</strong> is configured for a node in the cluster, the <strong id="cce_10_0384__b174656298390">oversubscription</strong> configuration must be added to the Volcano add-on. Otherwise, the scheduling of oversold nodes will be abnormal. Ensure that you have correctly configure labels because the scheduler does not check the add-on and node configurations. For details, see <a href="#cce_10_0384__table152481219311">Table 1</a>.</li><li id="cce_10_0384__li49631856162112">To disable oversubscription, perform the following operations:<ul id="cce_10_0384__ul1112232242215"><li id="cce_10_0384__li12124162022210">Remove the <strong id="cce_10_0384__b139669453393">volcano.sh/oversubscription</strong> label from the oversubscribed node.</li><li id="cce_10_0384__li91251620132217">Set <strong id="cce_10_0384__b34165481393">over-subscription-resource</strong> to <strong id="cce_10_0384__b1541754812396">false</strong>.</li><li id="cce_10_0384__li12125420162210">Modify the configmap of Volcano Scheduler named <strong id="cce_10_0384__b13578205033915">volcano-scheduler-configmap</strong> and remove the oversubscription add-on.</li></ul>
+<div class="p" id="cce_10_0384__p181841243211"><strong id="cce_10_0384__b417872014395">Constraints</strong><ul id="cce_10_0384__ul81841437118"><li id="cce_10_0384__li1741118264206">Before enabling oversubscription, ensure that the overcommit add-on is not enabled on Volcano.</li><li id="cce_10_0384__li3852121519212">Modifying the label of an oversubscribed node does not affect the running pods.</li><li id="cce_10_0384__li269881617214">Running pods cannot be converted between online and offline services. To convert services, rebuild pods.</li><li id="cce_10_0384__li1149628182118">If the label <strong id="cce_10_0384__b646532916397">volcano.sh/oversubscription=true</strong> is configured for a node in the cluster, the <strong id="cce_10_0384__b174656298390">oversubscription</strong> configuration must be added to the Volcano add-on. Otherwise, the scheduling of oversold nodes will be abnormal. Ensure that you have correctly configure labels because the scheduler does not check the add-on and node configurations. For details, see <a href="#cce_10_0384__table152481219311">Table 1</a>.</li><li id="cce_10_0384__li49631856162112">To disable oversubscription, perform the following operations:<ul id="cce_10_0384__ul1112232242215"><li id="cce_10_0384__li12124162022210">Remove the <strong id="cce_10_0384__b139669453393">volcano.sh/oversubscription</strong> label from the oversubscribed node.</li><li id="cce_10_0384__li12125420162210">Modify the configmap of Volcano Scheduler named <strong id="cce_10_0384__b13578205033915">volcano-scheduler-configmap</strong> and remove the oversubscription add-on.</li></ul>
 </li><li id="cce_10_0384__li8879133410365">If you have set <strong id="cce_10_0384__b296455418394">cpu-manager-policy</strong> to statically bind CPU cores on a node, do not assign the QoS class of Guaranteed to offline pods. This is because offline pods may occupy the CPUs of online pods, leading to an online pod startup failure and offline pods failing to start even though they have been successfully scheduled. To prevent this, switch the pods to online pods if CPU core binding is required.</li><li id="cce_10_0384__li10184184311113">If <strong id="cce_10_0384__b1330924394614">cpu-manager-policy</strong> is set to static CPU core binding on a node, do not bind CPU cores to all online pods. This is because doing so can cause online pods to occupy all available CPU or memory resources, leaving only a small number of oversubscribed resources.</li></ul>
 </div>
 </div></div>
@@ -145,8 +145,6 @@ data:
       - name: cce-gpu
 ...</pre>
 </div>
-</p></li><li id="cce_10_0384__li11364155010439"><span>Enable node oversubscription.</span><p><p id="cce_10_0384__p1958412304184">A label can be configured to use oversubscribed resources only after the oversubscription feature is enabled for a node. Related nodes can be created only in a node pool. To enable the oversubscription feature, perform the following steps:</p>
-<ol type="a" id="cce_10_0384__ol181230455528"><li id="cce_10_0384__li15123445115219">Create a node pool.</li><li id="cce_10_0384__li512314518521">Choose <strong id="cce_10_0384__b459139194016">Manage</strong> in the <strong id="cce_10_0384__b145911913409">Operation</strong> column of the created node pool.</li><li id="cce_10_0384__li111231945135219">On the <strong id="cce_10_0384__b15254185317104">Manage Components</strong> page, enable <strong id="cce_10_0384__b201201528122217">Node oversubscription feature (over-subscription-resource)</strong> and click <strong id="cce_10_0384__b52341544229">OK</strong>.</li></ol>
 </p></li><li id="cce_10_0384__li182861216174415"><span>Set the node oversubscription label.</span><p><p id="cce_10_0384__p15827102792019">The <strong id="cce_10_0384__b176001451961">volcano.sh/oversubscription</strong> label needs to be configured for an oversubscribed node. If this label is set for a node and the value is <strong id="cce_10_0384__b6944921463">true</strong>, the node is an oversubscribed node. Otherwise, the node is not an oversubscribed node.</p>
 <pre class="screen" id="cce_10_0384__screen4181417171812">kubectl label node 192.168.0.0 volcano.sh/oversubscription=true</pre>
 <p id="cce_10_0384__p1172017528912">An oversubscribed node also supports the oversubscription thresholds, as listed in <a href="#cce_10_0384__table1853397191112">Table 2</a>. For example:</p>
@@ -160,39 +158,39 @@ Labels:           ...
 Annotations:      ...
                   volcano.sh/evicting-cpu-high-watermark: 70</pre>
 
-<div class="tablenoborder"><a name="cce_10_0384__table1853397191112"></a><a name="table1853397191112"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0384__table1853397191112" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Node oversubscription annotations</caption><thead align="left"><tr id="cce_10_0384__row105951715118"><th align="left" class="cellrowborder" valign="top" width="22%" id="mcps1.3.9.4.2.7.2.3.1.1"><p id="cce_10_0384__p185951711115">Parameter</p>
+<div class="tablenoborder"><a name="cce_10_0384__table1853397191112"></a><a name="table1853397191112"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0384__table1853397191112" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Node oversubscription annotations</caption><thead align="left"><tr id="cce_10_0384__row105951715118"><th align="left" class="cellrowborder" valign="top" width="22%" id="mcps1.3.9.3.2.7.2.3.1.1"><p id="cce_10_0384__p185951711115">Parameter</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="78%" id="mcps1.3.9.4.2.7.2.3.1.2"><p id="cce_10_0384__p259510717114">Description</p>
+<th align="left" class="cellrowborder" valign="top" width="78%" id="mcps1.3.9.3.2.7.2.3.1.2"><p id="cce_10_0384__p259510717114">Description</p>
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_10_0384__row45951176117"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.4.2.7.2.3.1.1 "><p id="cce_10_0384__p259557171110">volcano.sh/evicting-cpu-high-watermark</p>
+<tbody><tr id="cce_10_0384__row45951176117"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.3.2.7.2.3.1.1 "><p id="cce_10_0384__p259557171110">volcano.sh/evicting-cpu-high-watermark</p>
 </td>
-<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.4.2.7.2.3.1.2 "><p id="cce_10_0384__p41092413154">Upper limit for CPU usage. When the CPU usage of a node exceeds the specified value, offline job eviction is triggered and the node becomes unschedulable.</p>
+<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.3.2.7.2.3.1.2 "><p id="cce_10_0384__p41092413154">Upper limit for CPU usage. When the CPU usage of a node exceeds the specified value, offline job eviction is triggered and the node becomes unschedulable.</p>
 <p id="cce_10_0384__p259511741114">The default value is <strong id="cce_10_0384__b44974543419">80</strong>, indicating that offline job eviction is triggered when the CPU usage of a node exceeds 80%.</p>
 </td>
 </tr>
-<tr id="cce_10_0384__row11595577116"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.4.2.7.2.3.1.1 "><p id="cce_10_0384__p1859513716115">volcano.sh/evicting-cpu-low-watermark</p>
+<tr id="cce_10_0384__row11595577116"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.3.2.7.2.3.1.1 "><p id="cce_10_0384__p1859513716115">volcano.sh/evicting-cpu-low-watermark</p>
 </td>
-<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.4.2.7.2.3.1.2 "><p id="cce_10_0384__p17595137161114">Lower limit for CPU usage. When the CPU usage of a node is higher than the upper limit, offline jobs will be evicted. The node accepts the offline jobs again only when the CPU usage of the node is lower than the lower limit.</p>
+<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.3.2.7.2.3.1.2 "><p id="cce_10_0384__p17595137161114">Lower limit for CPU usage. When the CPU usage of a node is higher than the upper limit, offline jobs will be evicted. The node accepts the offline jobs again only when the CPU usage of the node is lower than the lower limit.</p>
 <p id="cce_10_0384__p16595197161115">The default value is <strong id="cce_10_0384__b1914818330384">30</strong>, indicating that offline jobs are accepted again when the CPU usage of a node is lower than 30%.</p>
 </td>
 </tr>
-<tr id="cce_10_0384__row17595167181110"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.4.2.7.2.3.1.1 "><p id="cce_10_0384__p1459517791112">volcano.sh/evicting-memory-high-watermark</p>
+<tr id="cce_10_0384__row17595167181110"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.3.2.7.2.3.1.1 "><p id="cce_10_0384__p1459517791112">volcano.sh/evicting-memory-high-watermark</p>
 </td>
-<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.4.2.7.2.3.1.2 "><p id="cce_10_0384__p13595770114">Upper limit for memory usage. When the memory usage of a node exceeds the specified value, offline job eviction is triggered and the node becomes unschedulable.</p>
+<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.3.2.7.2.3.1.2 "><p id="cce_10_0384__p13595770114">Upper limit for memory usage. When the memory usage of a node exceeds the specified value, offline job eviction is triggered and the node becomes unschedulable.</p>
 <p id="cce_10_0384__p125952715117">The default value is <strong id="cce_10_0384__b2040511225392">60</strong>, indicating that offline job eviction is triggered when the memory usage of a node exceeds 60%.</p>
 </td>
 </tr>
-<tr id="cce_10_0384__row45958731118"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.4.2.7.2.3.1.1 "><p id="cce_10_0384__p105958710119">volcano.sh/evicting-memory-low-watermark</p>
+<tr id="cce_10_0384__row45958731118"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.3.2.7.2.3.1.1 "><p id="cce_10_0384__p105958710119">volcano.sh/evicting-memory-low-watermark</p>
 </td>
-<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.4.2.7.2.3.1.2 "><p id="cce_10_0384__p10595197171117">Lower limit for memory usage. When the memory usage of a node is higher than the upper limit, offline jobs will be evicted. The node accepts the offline jobs again only when the memory usage of the node is lower than the lower limit.</p>
+<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.3.2.7.2.3.1.2 "><p id="cce_10_0384__p10595197171117">Lower limit for memory usage. When the memory usage of a node is higher than the upper limit, offline jobs will be evicted. The node accepts the offline jobs again only when the memory usage of the node is lower than the lower limit.</p>
 <p id="cce_10_0384__p1259519712115">The default value is <strong id="cce_10_0384__b176291225104013">30</strong>, indicating that offline jobs are accepted again when the memory usage of a node is lower than 30%.</p>
 </td>
 </tr>
-<tr id="cce_10_0384__row25953771110"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.4.2.7.2.3.1.1 "><p id="cce_10_0384__p19595974119">volcano.sh/oversubscription-types</p>
+<tr id="cce_10_0384__row25953771110"><td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.9.3.2.7.2.3.1.1 "><p id="cce_10_0384__p19595974119">volcano.sh/oversubscription-types</p>
 </td>
-<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.4.2.7.2.3.1.2 "><p id="cce_10_0384__p1359567101115">Oversubscribed resource type. Options:</p>
+<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.9.3.2.7.2.3.1.2 "><p id="cce_10_0384__p1359567101115">Oversubscribed resource type. Options:</p>
 <ul id="cce_10_0384__ul440551111316"><li id="cce_10_0384__li34075114137"><strong id="cce_10_0384__b1785335734812">cpu</strong>: oversubscribed CPU</li><li id="cce_10_0384__li14401151191319"><strong id="cce_10_0384__b1271616194910">memory</strong>: oversubscribed memory</li><li id="cce_10_0384__li240551141315"><strong id="cce_10_0384__b16367132814491">cpu,memory</strong>: oversubscribed CPU and memory</li></ul>
 <p id="cce_10_0384__p175951741117">The default value is <strong id="cce_10_0384__b1181107142511">cpu,memory</strong>.</p>
 </td>
@@ -219,7 +217,7 @@ preemptionPolicy: PreemptLowerPriority
 value: -90000
  
 EOF</pre>
-</p></li><li id="cce_10_0384__li8503750144419"><span>Deploy online and offline jobs and configure PriorityClasses for these jobs.</span><p><p id="cce_10_0384__p16825144217223">The <strong id="cce_10_0384__b26751520144020">volcano.sh/qos-level</strong> annotation needs to be added to distinguish offline jobs. The value is an integer ranging from -7 to 7. If the value is less than 0, the job is an offline job. If the value is greater than or equal to 0, the job is an online job. You do not need to set this annotation for online jobs. For both online and offline jobs, set <strong id="cce_10_0384__b1352116047">schedulerName</strong> to <strong id="cce_10_0384__b576546895">volcano</strong> to enable Volcano.</p>
+</p></li><li id="cce_10_0384__li8503750144419"><span>Deploy online and offline jobs and configure PriorityClasses for these jobs.</span><p><p id="cce_10_0384__p16825144217223">The <strong id="cce_10_0384__b26751520144020">volcano.sh/qos-level</strong> annotation needs to be added to distinguish offline jobs. The value is an integer ranging from -7 to 7. If the value is less than 0, the job is an offline job. If the value is greater than or equal to 0, the job is an online job. You do not need to set this annotation for online jobs. For both online and offline jobs, set <strong id="cce_10_0384__b923062896">schedulerName</strong> to <strong id="cce_10_0384__b1872363566">volcano</strong> to enable Volcano.</p>
 <div class="note" id="cce_10_0384__note881010430447"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0384__p7811184318442">The priorities between online jobs and between offline jobs are not differentiated, and the value validity is not verified. If the value of <strong id="cce_10_0384__b1330893254011">volcano.sh/qos-level</strong> of an offline job is not a negative integer ranging from -7 to 0, the job is processed as an online job.</p>
 </div></div>
 <p id="cce_10_0384__p84551082233">For an offline job:</p>
diff --git a/docs/cce/umn/cce_10_0385.html b/docs/cce/umn/cce_10_0385.html
index 0ef815f0e..7905d98be 100644
--- a/docs/cce/umn/cce_10_0385.html
+++ b/docs/cce/umn/cce_10_0385.html
@@ -511,7 +511,7 @@ spec:
 </td>
 <td class="cellrowborder" valign="top" width="56.99999999999999%" headers="mcps1.3.11.2.2.5.1.3 "><p id="cce_10_0385__p18882328885">If the pod uses <strong id="cce_10_0385__b192375332571">hostNetwork</strong>, the ELB forwards the request to the host network after this annotation is used.</p>
 <p id="cce_10_0385__p128822282088">Options:</p>
-<ul id="cce_10_0385__ul6882202812817"><li id="cce_10_0385__li1888220285811"><strong id="cce_10_0385__b676113564">true</strong>: enabled</li><li id="cce_10_0385__li1988219284818"><strong id="cce_10_0385__b131375249434210">false</strong> (default): disabled</li></ul>
+<ul id="cce_10_0385__ul6882202812817"><li id="cce_10_0385__li1888220285811"><strong id="cce_10_0385__b2081592279">true</strong>: enabled</li><li id="cce_10_0385__li1988219284818"><strong id="cce_10_0385__b131375249434210">false</strong> (default): disabled</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.11.2.2.5.1.4 "><p id="cce_10_0385__p1688232810812">v1.9 or later</p>
 </td>
diff --git a/docs/cce/umn/cce_10_0405.html b/docs/cce/umn/cce_10_0405.html
index dce4dd3ff..67807fe6b 100644
--- a/docs/cce/umn/cce_10_0405.html
+++ b/docs/cce/umn/cce_10_0405.html
@@ -2,13 +2,13 @@
 
 <h1 class="topictitle1">Patch Version Release Notes</h1>
 <div id="body0000001290854168"><div class="section" id="cce_10_0405__clusterUpgradeTo1_31"><h4 class="sectiontitle">Version 1.31</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table347302505011" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Release notes for the v1.31 patch</caption><thead align="left"><tr id="cce_10_0405__row84731725155019"><th align="left" class="cellrowborder" valign="top" width="11.000000000000002%" id="mcps1.3.1.2.2.6.1.1"><p id="cce_10_0405__p3473125115018"><strong id="cce_10_0405__b1397735847">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table347302505011" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Release notes for the v1.31 patch</caption><thead align="left"><tr id="cce_10_0405__row84731725155019"><th align="left" class="cellrowborder" valign="top" width="11.000000000000002%" id="mcps1.3.1.2.2.6.1.1"><p id="cce_10_0405__p3473125115018"><strong id="cce_10_0405__b823618005">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="13.000000000000004%" id="mcps1.3.1.2.2.6.1.2"><p id="cce_10_0405__p204733254507"><strong id="cce_10_0405__b970060679">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="13.000000000000004%" id="mcps1.3.1.2.2.6.1.2"><p id="cce_10_0405__p204733254507"><strong id="cce_10_0405__b1852839111">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="41%" id="mcps1.3.1.2.2.6.1.3"><p id="cce_10_0405__p1447342512501"><strong id="cce_10_0405__b1795676725">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="41%" id="mcps1.3.1.2.2.6.1.3"><p id="cce_10_0405__p1447342512501"><strong id="cce_10_0405__b1818329806">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="20.000000000000004%" id="mcps1.3.1.2.2.6.1.4"><p id="cce_10_0405__p184731825135018"><strong id="cce_10_0405__b1678825529">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="20.000000000000004%" id="mcps1.3.1.2.2.6.1.4"><p id="cce_10_0405__p184731825135018"><strong id="cce_10_0405__b153844777">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15.000000000000002%" id="mcps1.3.1.2.2.6.1.5"><p id="cce_10_0405__p1247352585015"><strong id="cce_10_0405__b1044065712182">Vulnerability Fixing</strong></p>
 </th>
@@ -18,7 +18,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="13.000000000000004%" headers="mcps1.3.1.2.2.6.1.2 "><p id="cce_10_0405__p15847172174812"><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.31.md#v1314" target="_blank" rel="noopener noreferrer"><u id="cce_10_0405__u1762133719489">v1.31.4</u></a></p>
 </td>
-<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.1.2.2.6.1.3 "><ul id="cce_10_0405__ul6539122810123"><li id="cce_10_0405__li17539928151213">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li13539182815121">ELB ingresses allow you to specify backend server groups for forwarding.</li></ul>
+<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.1.2.2.6.1.3 "><ul id="cce_10_0405__ul6539122810123"><li id="cce_10_0405__li17539928151213">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li13539182815121">LoadBalancer ingresses allow you to specify backend server groups for forwarding.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="20.000000000000004%" headers="mcps1.3.1.2.2.6.1.4 "><p id="cce_10_0405__p10145115612497">-</p>
 </td>
@@ -42,15 +42,15 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_30"><h4 class="sectiontitle">Version 1.30</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table1425117172141" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Release notes for the v1.30 patch</caption><thead align="left"><tr id="cce_10_0405__row625251731416"><th align="left" class="cellrowborder" valign="top" width="10%" id="mcps1.3.2.2.2.6.1.1"><p id="cce_10_0405__p2252817191410"><strong id="cce_10_0405__b2075717102">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table1425117172141" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Release notes for the v1.30 patch</caption><thead align="left"><tr id="cce_10_0405__row625251731416"><th align="left" class="cellrowborder" valign="top" width="10%" id="mcps1.3.2.2.2.6.1.1"><p id="cce_10_0405__p2252817191410"><strong id="cce_10_0405__b1061630124">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="9.99%" id="mcps1.3.2.2.2.6.1.2"><p id="cce_10_0405__p1252111715140"><strong id="cce_10_0405__b512918538">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="9.99%" id="mcps1.3.2.2.2.6.1.2"><p id="cce_10_0405__p1252111715140"><strong id="cce_10_0405__b1998116969">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="32.51%" id="mcps1.3.2.2.2.6.1.3"><p id="cce_10_0405__p825251771414"><strong id="cce_10_0405__b941959941">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="32.51%" id="mcps1.3.2.2.2.6.1.3"><p id="cce_10_0405__p825251771414"><strong id="cce_10_0405__b921500376">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="32.5%" id="mcps1.3.2.2.2.6.1.4"><p id="cce_10_0405__p82523175146"><strong id="cce_10_0405__b1171051239">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="32.5%" id="mcps1.3.2.2.2.6.1.4"><p id="cce_10_0405__p82523175146"><strong id="cce_10_0405__b1940081648">Optimization</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.2.2.2.6.1.5"><p id="cce_10_0405__p82521417191418"><strong id="cce_10_0405__b2084829176">Vulnerability Fixing</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.2.2.2.6.1.5"><p id="cce_10_0405__p82521417191418"><strong id="cce_10_0405__b1741945890">Vulnerability Fixing</strong></p>
 </th>
 </tr>
 </thead>
@@ -58,7 +58,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="9.99%" headers="mcps1.3.2.2.2.6.1.2 "><p id="cce_10_0405__p1160115246496"><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.30.md#v1306" target="_blank" rel="noopener noreferrer"><u id="cce_10_0405__u4782154124920">v1.30.6</u></a></p>
 </td>
-<td class="cellrowborder" valign="top" width="32.51%" headers="mcps1.3.2.2.2.6.1.3 "><ul id="cce_10_0405__ul71999283507"><li id="cce_10_0405__li19199172816502">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li17199228185011">ELB ingresses allow you to specify backend server groups for forwarding.</li></ul>
+<td class="cellrowborder" valign="top" width="32.51%" headers="mcps1.3.2.2.2.6.1.3 "><ul id="cce_10_0405__ul71999283507"><li id="cce_10_0405__li19199172816502">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li17199228185011">LoadBalancer ingresses allow you to specify backend server groups for forwarding.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="32.5%" headers="mcps1.3.2.2.2.6.1.4 "><p id="cce_10_0405__p819922805015">-</p>
 </td>
@@ -104,13 +104,13 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_29"><h4 class="sectiontitle">Version 1.29</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table467555117285" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Release notes for the v1.29 patch</caption><thead align="left"><tr id="cce_10_0405__row186769517285"><th align="left" class="cellrowborder" valign="top" width="11.11111111111111%" id="mcps1.3.3.2.2.6.1.1"><p id="cce_10_0405__p18676851122810"><strong id="cce_10_0405__b335003761">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table467555117285" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Release notes for the v1.29 patch</caption><thead align="left"><tr id="cce_10_0405__row186769517285"><th align="left" class="cellrowborder" valign="top" width="11.11111111111111%" id="mcps1.3.3.2.2.6.1.1"><p id="cce_10_0405__p18676851122810"><strong id="cce_10_0405__b1626916440">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="13.13131313131313%" id="mcps1.3.3.2.2.6.1.2"><p id="cce_10_0405__p06764511287"><strong id="cce_10_0405__b1713445960">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="13.13131313131313%" id="mcps1.3.3.2.2.6.1.2"><p id="cce_10_0405__p06764511287"><strong id="cce_10_0405__b1086425018">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="40.4040404040404%" id="mcps1.3.3.2.2.6.1.3"><p id="cce_10_0405__p2676135110287"><strong id="cce_10_0405__b1377445282">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="40.4040404040404%" id="mcps1.3.3.2.2.6.1.3"><p id="cce_10_0405__p2676135110287"><strong id="cce_10_0405__b2046085405">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="20.2020202020202%" id="mcps1.3.3.2.2.6.1.4"><p id="cce_10_0405__p106768517282"><strong id="cce_10_0405__b1861234303">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="20.2020202020202%" id="mcps1.3.3.2.2.6.1.4"><p id="cce_10_0405__p106768517282"><strong id="cce_10_0405__b675168547">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15.151515151515149%" id="mcps1.3.3.2.2.6.1.5"><p id="cce_10_0405__p26761518288"><strong id="cce_10_0405__b3528155753212">Vulnerability Fixing</strong></p>
 </th>
@@ -120,7 +120,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="13.13131313131313%" headers="mcps1.3.3.2.2.6.1.2 "><p id="cce_10_0405__p19733122825019"><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.29.md#v12910" target="_blank" rel="noopener noreferrer"><u id="cce_10_0405__u18664175565017">v1.29.10</u></a></p>
 </td>
-<td class="cellrowborder" valign="top" width="40.4040404040404%" headers="mcps1.3.3.2.2.6.1.3 "><ul id="cce_10_0405__ul14211618513"><li id="cce_10_0405__li721119117512">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li152111913511">ELB ingresses allow you to specify backend server groups for forwarding.</li></ul>
+<td class="cellrowborder" valign="top" width="40.4040404040404%" headers="mcps1.3.3.2.2.6.1.3 "><ul id="cce_10_0405__ul14211618513"><li id="cce_10_0405__li721119117512">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li152111913511">LoadBalancer ingresses allow you to specify backend server groups for forwarding.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="20.2020202020202%" headers="mcps1.3.3.2.2.6.1.4 "><p id="cce_10_0405__p202113185111">-</p>
 </td>
@@ -165,13 +165,13 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_28"><h4 class="sectiontitle">Version 1.28</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table15201550191211" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Release notes for the v1.28 patch</caption><thead align="left"><tr id="cce_10_0405__row1952110505124"><th align="left" class="cellrowborder" valign="top" width="11.000000000000002%" id="mcps1.3.4.2.2.6.1.1"><p id="cce_10_0405__p20521105021212"><strong id="cce_10_0405__b1337244960">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table15201550191211" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Release notes for the v1.28 patch</caption><thead align="left"><tr id="cce_10_0405__row1952110505124"><th align="left" class="cellrowborder" valign="top" width="11.000000000000002%" id="mcps1.3.4.2.2.6.1.1"><p id="cce_10_0405__p20521105021212"><strong id="cce_10_0405__b956494543">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="13.000000000000004%" id="mcps1.3.4.2.2.6.1.2"><p id="cce_10_0405__p2521145012123"><strong id="cce_10_0405__b778419448">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="13.000000000000004%" id="mcps1.3.4.2.2.6.1.2"><p id="cce_10_0405__p2521145012123"><strong id="cce_10_0405__b1444033593">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="41%" id="mcps1.3.4.2.2.6.1.3"><p id="cce_10_0405__p10521650111213"><strong id="cce_10_0405__b1841289165">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="41%" id="mcps1.3.4.2.2.6.1.3"><p id="cce_10_0405__p10521650111213"><strong id="cce_10_0405__b1746193623">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="20.000000000000004%" id="mcps1.3.4.2.2.6.1.4"><p id="cce_10_0405__p10521195021210"><strong id="cce_10_0405__b813836616">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="20.000000000000004%" id="mcps1.3.4.2.2.6.1.4"><p id="cce_10_0405__p10521195021210"><strong id="cce_10_0405__b391050492">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15.000000000000002%" id="mcps1.3.4.2.2.6.1.5"><p id="cce_10_0405__p552155051220"><strong id="cce_10_0405__b42112134410">Vulnerability Fixing</strong></p>
 </th>
@@ -181,7 +181,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="13.000000000000004%" headers="mcps1.3.4.2.2.6.1.2 "><p id="cce_10_0405__p1440452415116"><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.28.md#v12815" target="_blank" rel="noopener noreferrer"><u id="cce_10_0405__u1849034645118">v1.28.15</u></a></p>
 </td>
-<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.4.2.2.6.1.3 "><ul id="cce_10_0405__ul2466123111167"><li id="cce_10_0405__en-us_topic_0000001290854168_li17539928151213">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__en-us_topic_0000001290854168_li13539182815121">ELB ingresses allow you to specify backend server groups for forwarding.</li></ul>
+<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.4.2.2.6.1.3 "><ul id="cce_10_0405__ul2466123111167"><li id="cce_10_0405__en-us_topic_0000001290854168_li17539928151213">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__en-us_topic_0000001290854168_li13539182815121">LoadBalancer ingresses allow you to specify backend server groups for forwarding.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="20.000000000000004%" headers="mcps1.3.4.2.2.6.1.4 "><p id="cce_10_0405__p184661631171618">-</p>
 </td>
@@ -261,13 +261,13 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_27"><h4 class="sectiontitle">Version 1.27</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table16348192865014" frame="border" border="1" rules="all"><caption><b>Table 5 </b>Release notes for the v1.27 patch</caption><thead align="left"><tr id="cce_10_0405__row1934816285509"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.5.2.2.6.1.1"><p id="cce_10_0405__p12349228205017"><strong id="cce_10_0405__b1423009925">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__table16348192865014" frame="border" border="1" rules="all"><caption><b>Table 5 </b>Release notes for the v1.27 patch</caption><thead align="left"><tr id="cce_10_0405__row1934816285509"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.5.2.2.6.1.1"><p id="cce_10_0405__p12349228205017"><strong id="cce_10_0405__b1094360473">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="13%" id="mcps1.3.5.2.2.6.1.2"><p id="cce_10_0405__p6349162875015"><strong id="cce_10_0405__b157941696">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="13%" id="mcps1.3.5.2.2.6.1.2"><p id="cce_10_0405__p6349162875015"><strong id="cce_10_0405__b1866208191">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="37%" id="mcps1.3.5.2.2.6.1.3"><p id="cce_10_0405__p2034932817502"><strong id="cce_10_0405__b636515935">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="37%" id="mcps1.3.5.2.2.6.1.3"><p id="cce_10_0405__p2034932817502"><strong id="cce_10_0405__b648882388">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="24%" id="mcps1.3.5.2.2.6.1.4"><p id="cce_10_0405__p1334962812505"><strong id="cce_10_0405__b1039668024">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="24%" id="mcps1.3.5.2.2.6.1.4"><p id="cce_10_0405__p1334962812505"><strong id="cce_10_0405__b823272565">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.5.2.2.6.1.5"><p id="cce_10_0405__p83495285501"><strong id="cce_10_0405__b1186210981618">Vulnerability Fixing</strong></p>
 </th>
@@ -277,7 +277,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="13%" headers="mcps1.3.5.2.2.6.1.2 "><p id="cce_10_0405__p03111543526"><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.27.md#v12716" target="_blank" rel="noopener noreferrer"><u id="cce_10_0405__u1772711914524">v1.27.16</u></a></p>
 </td>
-<td class="cellrowborder" valign="top" width="37%" headers="mcps1.3.5.2.2.6.1.3 "><ul id="cce_10_0405__ul1393615453167"><li id="cce_10_0405__li543541312548">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li943920134547">ELB ingresses allow you to specify backend server groups for forwarding.</li></ul>
+<td class="cellrowborder" valign="top" width="37%" headers="mcps1.3.5.2.2.6.1.3 "><ul id="cce_10_0405__ul1393615453167"><li id="cce_10_0405__li543541312548">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li943920134547">LoadBalancer ingresses allow you to specify backend server groups for forwarding.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.5.2.2.6.1.4 "><p id="cce_10_0405__p20936124512166">-</p>
 </td>
@@ -370,13 +370,13 @@
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_25"><h4 class="sectiontitle">Version 1.25</h4><div class="notice" id="cce_10_0405__en-us_topic_0000001597052925_note181919212477"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0405__en-us_topic_0000001597052925_p17819112144717">In CCE clusters of v1.25, containerd is the default runtime for nodes, except for nodes running EulerOS 2.5. In addition, clusters of v1.25 or later no longer support EulerOS 2.5.</p>
 </div></div>
 
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table18271649125313" frame="border" border="1" rules="all"><caption><b>Table 6 </b>Release notes for the v1.25 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row148271849185313"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.6.3.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p782719494538"><strong id="cce_10_0405__b1003174634">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table18271649125313" frame="border" border="1" rules="all"><caption><b>Table 6 </b>Release notes for the v1.25 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row148271849185313"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.6.3.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p782719494538"><strong id="cce_10_0405__b701250358">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="13%" id="mcps1.3.6.3.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p2827154918531"><strong id="cce_10_0405__b694910259">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="13%" id="mcps1.3.6.3.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p2827154918531"><strong id="cce_10_0405__b888369577">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="34%" id="mcps1.3.6.3.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p782710498537"><strong id="cce_10_0405__b1314478653">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="34%" id="mcps1.3.6.3.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p782710498537"><strong id="cce_10_0405__b2082517951">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="27%" id="mcps1.3.6.3.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p582710492535"><strong id="cce_10_0405__b2041045282">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="27%" id="mcps1.3.6.3.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p582710492535"><strong id="cce_10_0405__b911023207">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.6.3.2.6.1.5"><p id="cce_10_0405__en-us_topic_0000001597052925_p188279495531"><strong id="cce_10_0405__b1037914618612">Vulnerability Fixing</strong></p>
 </th>
@@ -386,7 +386,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="13%" headers="mcps1.3.6.3.2.6.1.2 "><p id="cce_10_0405__p2010135345215"><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.25.md#v12516" target="_blank" rel="noopener noreferrer"><u id="cce_10_0405__u21478913533">v1.25.16</u></a></p>
 </td>
-<td class="cellrowborder" valign="top" width="34%" headers="mcps1.3.6.3.2.6.1.3 "><ul id="cce_10_0405__ul87771271716"><li id="cce_10_0405__li9781421135520">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li117851321195515">ELB ingresses allow you to specify backend server groups for forwarding.</li></ul>
+<td class="cellrowborder" valign="top" width="34%" headers="mcps1.3.6.3.2.6.1.3 "><ul id="cce_10_0405__ul87771271716"><li id="cce_10_0405__li9781421135520">Nodes added during a node pool scale-out can be automatically bound with EIPs.</li><li id="cce_10_0405__li117851321195515">LoadBalancer ingresses allow you to specify backend server groups for forwarding.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.6.3.2.6.1.4 "><p id="cce_10_0405__p1877711221711">-</p>
 </td>
@@ -509,13 +509,13 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_23"><h4 class="sectiontitle">Version 1.23</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table58401234105510" frame="border" border="1" rules="all"><caption><b>Table 7 </b>Release notes for the v1.23 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row1841183425519"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.7.2.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p16841133415552"><strong id="cce_10_0405__b336754689">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table58401234105510" frame="border" border="1" rules="all"><caption><b>Table 7 </b>Release notes for the v1.23 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row1841183425519"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.7.2.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p16841133415552"><strong id="cce_10_0405__b1443082805">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="13%" id="mcps1.3.7.2.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p7841173410554"><strong id="cce_10_0405__b1511497715">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="13%" id="mcps1.3.7.2.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p7841173410554"><strong id="cce_10_0405__b1831861607">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="33%" id="mcps1.3.7.2.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p984113416550"><strong id="cce_10_0405__b941202604">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="33%" id="mcps1.3.7.2.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p984113416550"><strong id="cce_10_0405__b1714841753">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="28.000000000000004%" id="mcps1.3.7.2.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p10841534205510"><strong id="cce_10_0405__b1253147744">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="28.000000000000004%" id="mcps1.3.7.2.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p10841534205510"><strong id="cce_10_0405__b1211392522">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.7.2.2.6.1.5"><p id="cce_10_0405__en-us_topic_0000001597052925_p1284163485518"><strong id="cce_10_0405__b9380161616">Vulnerability Fixing</strong></p>
 </th>
@@ -660,13 +660,13 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_21"><h4 class="sectiontitle">Version 1.21</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table238854215819" frame="border" border="1" rules="all"><caption><b>Table 8 </b>Release notes for the v1.21 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row133891042175820"><th align="left" class="cellrowborder" valign="top" width="10.891089108910892%" id="mcps1.3.8.2.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p173897427586"><strong id="cce_10_0405__b1550868539">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table238854215819" frame="border" border="1" rules="all"><caption><b>Table 8 </b>Release notes for the v1.21 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row133891042175820"><th align="left" class="cellrowborder" valign="top" width="10.891089108910892%" id="mcps1.3.8.2.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p173897427586"><strong id="cce_10_0405__b176338638">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="12.871287128712872%" id="mcps1.3.8.2.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p143891142105813"><strong id="cce_10_0405__b1650745934">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="12.871287128712872%" id="mcps1.3.8.2.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p143891142105813"><strong id="cce_10_0405__b40505470">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="33.663366336633665%" id="mcps1.3.8.2.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p19389114214581"><strong id="cce_10_0405__b1679238530">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="33.663366336633665%" id="mcps1.3.8.2.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p19389114214581"><strong id="cce_10_0405__b1149624137">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="27.722772277227726%" id="mcps1.3.8.2.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p0389184265815"><strong id="cce_10_0405__b1142287791">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="27.722772277227726%" id="mcps1.3.8.2.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p0389184265815"><strong id="cce_10_0405__b1258976172">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="14.85148514851485%" id="mcps1.3.8.2.2.6.1.5"><p id="cce_10_0405__en-us_topic_0000001597052925_p43896428585"><strong id="cce_10_0405__b63811761612">Vulnerability Fixing</strong></p>
 </th>
@@ -777,13 +777,13 @@
 </div>
 </div>
 <div class="section" id="cce_10_0405__clusterUpgradeTo1_19"><h4 class="sectiontitle">Version 1.19</h4>
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table958151314010" frame="border" border="1" rules="all"><caption><b>Table 9 </b>Release notes for the v1.19 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row1958181319019"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.9.2.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p9587132010"><strong id="cce_10_0405__b822268068">CCE Cluster Patch Version</strong></p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0405__en-us_topic_0000001597052925_table958151314010" frame="border" border="1" rules="all"><caption><b>Table 9 </b>Release notes for the v1.19 patch</caption><thead align="left"><tr id="cce_10_0405__en-us_topic_0000001597052925_row1958181319019"><th align="left" class="cellrowborder" valign="top" width="11%" id="mcps1.3.9.2.2.6.1.1"><p id="cce_10_0405__en-us_topic_0000001597052925_p9587132010"><strong id="cce_10_0405__b1900198462">CCE Cluster Patch Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="12%" id="mcps1.3.9.2.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p3587138016"><strong id="cce_10_0405__b1551830544">Kubernetes Version</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="12%" id="mcps1.3.9.2.2.6.1.2"><p id="cce_10_0405__en-us_topic_0000001597052925_p3587138016"><strong id="cce_10_0405__b1998418914">Kubernetes Version</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.9.2.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p55831313014"><strong id="cce_10_0405__b1221963403">Feature Updates</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.9.2.2.6.1.3"><p id="cce_10_0405__en-us_topic_0000001597052925_p55831313014"><strong id="cce_10_0405__b1616318963">Feature Updates</strong></p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="32%" id="mcps1.3.9.2.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p185861311018"><strong id="cce_10_0405__b1508532870">Optimization</strong></p>
+<th align="left" class="cellrowborder" valign="top" width="32%" id="mcps1.3.9.2.2.6.1.4"><p id="cce_10_0405__en-us_topic_0000001597052925_p185861311018"><strong id="cce_10_0405__b1998096885">Optimization</strong></p>
 </th>
 <th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.9.2.2.6.1.5"><p id="cce_10_0405__en-us_topic_0000001597052925_p05817132005"><strong id="cce_10_0405__b53823614614">Vulnerability Fixing</strong></p>
 </th>
diff --git a/docs/cce/umn/cce_10_0425.html b/docs/cce/umn/cce_10_0425.html
index 408e47306..491066a46 100644
--- a/docs/cce/umn/cce_10_0425.html
+++ b/docs/cce/umn/cce_10_0425.html
@@ -156,7 +156,7 @@
 </li></ol>
 </p></li><li id="cce_10_0425__li15561124416020"><span>Enable the numa-aware add-on and the <strong id="cce_10_0425__b9915151215516">resource_exporter</strong> function.</span><p><p id="cce_10_0425__p14912576012"><strong id="cce_10_0425__b1822402215554">Volcano 1.7.1 or later</strong></p>
 <ol type="a" id="cce_10_0425__ol29221109112"><li id="cce_10_0425__li1219753519197">Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0425__b230434843215"><span id="cce_10_0425__text6199203591915">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0425__b203041648203220">Volcano Scheduler</strong> on the right, and click <strong id="cce_10_0425__b193049482329">Edit</strong>.</li><li id="cce_10_0425__li62262475194">In the <strong id="cce_10_0425__b610531743916">Extended Functions</strong> area, enable <strong id="cce_10_0425__b512018174511">NUMA Topology Scheduling</strong> and click <strong id="cce_10_0425__b4130132616457">OK</strong>.</li></ol>
-<div class="p" id="cce_10_0425__p187571154204"><strong id="cce_10_0425__b050622018563">Volcano earlier than 1.7.1</strong><ol type="a" id="cce_10_0425__ol0122828903"><li id="cce_10_0425__li2611115310117">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0425__b1792244174710">Settings</strong> and click the <strong id="cce_10_0425__b16715162815487">Scheduling</strong> tab. Select <strong id="cce_10_0425__b250723964910">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0425__b1265615347336">Try Now</strong>.<p id="cce_10_0425__p2949165711111"></p>
+<div class="p" id="cce_10_0425__p187571154204"><strong id="cce_10_0425__b050622018563">Volcano earlier than 1.7.1</strong><ol type="a" id="cce_10_0425__ol0122828903"><li id="cce_10_0425__li2611115310117">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0425__b020111884411">Settings</strong> and click the <strong id="cce_10_0425__b52081813446">Scheduling</strong> tab. Select <strong id="cce_10_0425__b182012183444">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0425__b1921181815449">Try Now</strong>.<p id="cce_10_0425__p2949165711111"></p>
 </li><li id="cce_10_0425__li14122192815012">Enable <strong id="cce_10_0425__b112316322512">resource_exporter_enable</strong> to collect node NUMA information. The following is an example in JSON format:<pre class="screen" id="cce_10_0425__screen7651947143817">{
    "plugins": {
       "eas_service": {
diff --git a/docs/cce/umn/cce_10_0497.html b/docs/cce/umn/cce_10_0497.html
index c4a073480..4bfd40d4c 100644
--- a/docs/cce/umn/cce_10_0497.html
+++ b/docs/cce/umn/cce_10_0497.html
@@ -7,7 +7,7 @@
 <ol id="cce_10_0497__ol159620307494"><li id="cce_10_0497__li192248593919"><span>Log in to the ELB console, choose <strong id="cce_10_0497__b19661312565">Elastic Load Balance</strong> &gt; <strong id="cce_10_0497__b0597837135617">Certificates</strong>, locate the certificate, and find the <strong id="cce_10_0497__b148313125716">secret_id</strong> in the certificate description.</span><p><p id="cce_10_0497__p0642182672313">The <strong id="cce_10_0497__b4781163016591">secret_id</strong> is the <strong id="cce_10_0497__b6916153715598">metadata.uid</strong> of the secret in the cluster. Use this UID to obtain the secret name in the cluster.</p>
 <div class="p" id="cce_10_0497__p2196533194914">Run the following kubectl command to obtain the secret name (replace <em id="cce_10_0497__i1242116942">&lt;secret_id&gt;</em> with the actual value):<pre class="screen" id="cce_10_0497__screen10477123615153">kubectl get secret --all-namespaces -o jsonpath='{range .items[*]}{"uid:"}{.metadata.uid}{" namespace:"}{.metadata.namespace}{" name:"}{.metadata.name}{"\n"}{end}' | grep <i><span class="varname" id="cce_10_0497__varname355565362315">&lt;secret_id&gt;</span></i></pre>
 </div>
-</p></li><li id="cce_10_0497__li19149486344"><span>Only clusters of v1.19.16-r2, v1.21.5-r0, v1.23.3-r0, and later versions support certificates required by load balancers. For clusters of the earlier versions, see <a href="#cce_10_0497__li49931854113415">Solution 1</a>. For clusters of other versions, see <a href="#cce_10_0497__li1126485713418">Solution 2</a>.</span><p><ul id="cce_10_0497__ul799385417345"><li id="cce_10_0497__li49931854113415"><a name="cce_10_0497__li49931854113415"></a><a name="li49931854113415"></a>Solution 1: Replace the certificate used by an ingress with the one used by the load balancer. Then, you can create or edit the certificate on the ELB console.<ol type="a" id="cce_10_0497__ol7391527153413"><li id="cce_10_0497__li1039162719345">Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0497__b14991131353620"><span id="cce_10_0497__text3381227163415">Services &amp; Ingresses</span></strong> in the navigation pane, click the <strong id="cce_10_0497__b10991513113610">Ingresses</strong> tab, locate the row containing the ingress that uses the certificate, and choose <strong id="cce_10_0497__b10992171383617">More</strong> &gt; <strong id="cce_10_0497__b999261313366">Update</strong> in the <strong id="cce_10_0497__b10992313143620">Operation</strong> column. If multiple ingresses are using this certificate, update the certificate for all of these ingresses. To check which ingresses are using a certificate, use the <strong id="cce_10_0497__b155535286219">secretName</strong> parameter in <strong id="cce_10_0497__b86425502111">spec.tls</strong> of the ingress YAML files.<p id="cce_10_0497__p538142717349">Run the following kubectl command to obtain the ingresses using a certificate (replace <i><span class="varname" id="cce_10_0497__varname103892793413">&lt;secret_name&gt;</span></i> with the actual value):</p>
+</p></li><li id="cce_10_0497__li19149486344"><span>Only clusters of v1.19.16-r2, v1.21.5-r0, v1.23.3-r0, and later versions support certificates required by load balancers. For clusters of the earlier versions, see <a href="#cce_10_0497__li49931854113415">Solution 1</a>. For clusters of other versions, see <a href="#cce_10_0497__li1126485713418">Solution 2</a>.</span><p><ul id="cce_10_0497__ul799385417345"><li id="cce_10_0497__li49931854113415"><a name="cce_10_0497__li49931854113415"></a><a name="li49931854113415"></a>Solution 1: Replace the certificate used by an ingress with the one used by the load balancer. Then, you can create or edit the certificate on the ELB console.<ol type="a" id="cce_10_0497__ol7391527153413"><li id="cce_10_0497__li1039162719345">Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0497__b14991131353620"><span id="cce_10_0497__text3381227163415">Services &amp; Ingresses</span></strong> in the navigation pane, click the <strong id="cce_10_0497__b10991513113610">Ingresses</strong> tab, locate the row containing the ingress that uses the certificate, and choose <strong id="cce_10_0497__b10992171383617">More</strong> &gt; <strong id="cce_10_0497__b999261313366">Update</strong> in the <strong id="cce_10_0497__b10992313143620">Operation</strong> column. If multiple ingresses are using this certificate, update the certificate for all of these ingresses. To check which ingresses are using a certificate, use the <strong id="cce_10_0497__b141546531621">secretName</strong> parameter in <strong id="cce_10_0497__b615455318210">spec.tls</strong> of the ingress YAML files.<p id="cce_10_0497__p538142717349">Run the following kubectl command to obtain the ingresses using a certificate (replace <i><span class="varname" id="cce_10_0497__varname103892793413">&lt;secret_name&gt;</span></i> with the actual value):</p>
 <pre class="screen" id="cce_10_0497__screen63962710340">kubectl get ingress --all-namespaces -o jsonpath='{range .items[*]}{"namespace:"}{.metadata.namespace}{" name:"}{.metadata.name}{" tls:"}{.spec.tls[*]}{"\n"}{end}' | grep <i><span class="varname" id="cce_10_0497__varname738152713343">&lt;secret_name&gt;</span></i></pre>
 </li><li id="cce_10_0497__li339727183416">When configuring a listener, select <strong id="cce_10_0497__b1200193932913">ELB server certificate</strong> for <strong id="cce_10_0497__b06897973010">Certificate Source</strong> and click <strong id="cce_10_0497__b1980735163219">OK</strong>. In this way, the certificate can be created or edited on the ELB console.</li><li id="cce_10_0497__li93911272344">On the <strong id="cce_10_0497__b75707411619"><span id="cce_10_0497__text1266312153316">ConfigMaps and Secrets</span></strong> page, delete the target secret. Before the deletion, back up data.</li></ol>
 </li><li id="cce_10_0497__li1126485713418"><a name="cce_10_0497__li1126485713418"></a><a name="li1126485713418"></a>Solution 2: Overwrite the certificate used by an ingress with the corresponding secret resource of the cluster to prevent the certificate being updated on the ELB console during the cluster upgrade.<p id="cce_10_0497__p113291850193410"><a name="cce_10_0497__li1126485713418"></a><a name="li1126485713418"></a>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0497__b2681232195718"><span id="cce_10_0497__text083514442311">ConfigMaps and Secrets</span></strong> from the navigation pane, click the <strong id="cce_10_0497__b16309104213584">Secrets</strong> tab, locate the row containing the target secret, click <strong id="cce_10_0497__b10591151915912">Update</strong> in the <strong id="cce_10_0497__b779113143918">Operation</strong> column, and enter the certificate you are using.</p>
diff --git a/docs/cce/umn/cce_10_0552.html b/docs/cce/umn/cce_10_0552.html
index c30b481f1..259bcff4b 100644
--- a/docs/cce/umn/cce_10_0552.html
+++ b/docs/cce/umn/cce_10_0552.html
@@ -23,7 +23,7 @@ spec:
 <div class="section" id="cce_10_0552__section3877163611611"><h4 class="sectiontitle">Notes and Constraints</h4><p id="cce_10_0552__p19614184551619">To use this feature, the following conditions must be met:</p>
 <ul id="cce_10_0552__ul9614164581618"><li id="cce_10_0552__li11614345111611">The cluster version must be v1.23 or later.</li><li id="cce_10_0552__li16841028143712">The node OS is HCE OS 2.0.</li><li id="cce_10_0552__li76142045171614">The CPU management policy does not apply to ECS (PM) nodes in CCE Turbo clusters.</li></ul>
 </div>
-<div class="section" id="cce_10_0552__section135842493165"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0552__ol72741615245"><li id="cce_10_0552__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0552__li2075471341"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0552__uicontrol14682104464238"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0552__b16123533194238">Node Pools</strong> tab.</span></li><li id="cce_10_0552__li952182622915"><span>Select a node pool whose OS is HCE OS 2.0 and choose <span class="uicontrol" id="cce_10_0552__uicontrol3520268294"><b>Manage</b></span> in the <strong id="cce_10_0552__b1439850102412">Operation</strong> column.</span></li><li id="cce_10_0552__li20922452316"><span>On the <span class="uicontrol" id="cce_10_0552__uicontrol129199122321"><b>Manage Configurations</b></span> page, change the <strong id="cce_10_0552__b169201212183217">cpu-manager-policy</strong> value to <strong id="cce_10_0552__b3654358125916">enhanced-static</strong> in the <strong id="cce_10_0552__b61436531356">kubelet</strong> area.</span></li><li id="cce_10_0552__li206411338151114"><span>Click <strong id="cce_10_0552__b7736191543213">OK</strong>.</span></li></ol>
+<div class="section" id="cce_10_0552__section135842493165"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0552__ol72741615245"><li id="cce_10_0552__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0552__li2075471341"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0552__uicontrol14682104464238"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0552__b16123533194238">Node Pools</strong> tab.</span></li><li id="cce_10_0552__li952182622915"><span>Select a node pool whose OS is HCE OS 2.0 and choose <span class="uicontrol" id="cce_10_0552__uicontrol35407515015"><b>Manage</b></span> in the <strong id="cce_10_0552__b155404513015">Operation</strong> column.</span></li><li id="cce_10_0552__li20922452316"><span>On the <span class="uicontrol" id="cce_10_0552__uicontrol129199122321"><b>Manage Configurations</b></span> page, change the <strong id="cce_10_0552__b169201212183217">cpu-manager-policy</strong> value to <strong id="cce_10_0552__b3654358125916">enhanced-static</strong> in the <strong id="cce_10_0552__b61436531356">kubelet</strong> area.</span></li><li id="cce_10_0552__li206411338151114"><span>Click <strong id="cce_10_0552__b7736191543213">OK</strong>.</span></li></ol>
 </div>
 <div class="section" id="cce_10_0552__section1879811281710"><h4 class="sectiontitle">Verification</h4><p id="cce_10_0552__p111281837193818">Take a node with 8 vCPUs and 32 GiB of memory as an example. Deploy a workload whose CPU request is 1 and limit is 2 in the cluster beforehand.</p>
 <ol id="cce_10_0552__ol19151204143817"><li id="cce_10_0552__li183451339123912"><span>Log in to a node in the node pool and view the <strong id="cce_10_0552__b6895152210323">/var/lib/kubelet/cpu_manager_state</strong> output.</span><p><pre class="screen" id="cce_10_0552__screen734951853913">cat /var/lib/kubelet/cpu_manager_state</pre>
diff --git a/docs/cce/umn/cce_10_0554.html b/docs/cce/umn/cce_10_0554.html
index 66190cdf4..8163668ab 100644
--- a/docs/cce/umn/cce_10_0554.html
+++ b/docs/cce/umn/cce_10_0554.html
@@ -2,7 +2,7 @@
 
 <h1 class="topictitle1">Collecting Control Plane Component Logs</h1>
 <div id="body0000001709722974"><p id="cce_10_0554__p58681151939">CCE allows you to collect the logs of master nodes. On the <strong id="cce_10_0554__b102311591311"><span id="cce_10_0554__text1164315336613">Logging</span></strong> page, you can select one or more control plane components (kube-controller-manager, kube-apiserver, and kube-scheduler) whose logs need to be reported.</p>
-<div class="section" id="cce_10_0554__section15915571101"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0554__ul1145273617100"><li id="cce_10_0554__li124521636151014">The cluster version must be v1.21.7-r0 or later, v1.23.5-r0 or later, or 1.25.</li><li id="cce_10_0554__li945218367100">There is required LTS resource quota.</li></ul>
+<div class="section" id="cce_10_0554__section15915571101"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0554__ul1145273617100"><li id="cce_10_0554__li124521636151014">The cluster version must be v1.21.7-r0 or later, v1.23.5-r0 or later, or 1.25.</li><li id="cce_10_0554__li945218367100">There is required LTS resource quota.</li></ul>
 </div>
 <div class="section" id="cce_10_0554__section133166619593"><a name="cce_10_0554__section133166619593"></a><a name="section133166619593"></a><h4 class="sectiontitle">Control Plane Components</h4><p id="cce_10_0554__p11944191815598">There are three control plane log types. Each log stream corresponds to a component of the Kubernetes control plane. To learn more about these components, see <a href="https://kubernetes.io/docs/concepts/overview/components/" target="_blank" rel="noopener noreferrer">Kubernetes Components</a>.</p>
 
@@ -44,7 +44,7 @@
 </div>
 </div>
 <div class="section" id="cce_10_0554__section1883701101111"><h4 class="sectiontitle">Enabling Control Plane Logging</h4><p id="cce_10_0554__p126238295311"><strong id="cce_10_0554__b1180172663417">Enabling control plane logging during cluster creation</strong></p>
-<ol id="cce_10_0554__ol7219545201112"><li id="cce_10_0554__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0554__li1283621110581">In the upper right corner, click <strong id="cce_10_0554__b15789814153210">Create Cluster</strong>. Then, configure the parameters and click <strong id="cce_10_0554__b15285133215474">Next: Select Add-on</strong>.</li><li id="cce_10_0554__li1932603355813">On the displayed page, select <strong id="cce_10_0554__b690818158491">Cloud Native Log Collection</strong> and click <strong id="cce_10_0554__b5831345494">Next: Add-on Configuration</strong>.</li><li id="cce_10_0554__li1483631175820">On the displayed page, select <strong id="cce_10_0554__b331813114518">Control Plane Logs</strong> for <strong id="cce_10_0554__b15645137105118">Cloud Native Log Collection</strong>.<p id="cce_10_0554__p163268466177"></p>
+<ol id="cce_10_0554__ol7219545201112"><li id="cce_10_0554__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0554__li1283621110581">Click <strong id="cce_10_0554__b153101221369">Create Cluster</strong>. Then, configure the parameters and click <strong id="cce_10_0554__b931082119614">Next: Select Add-on</strong>.</li><li id="cce_10_0554__li1932603355813">On the displayed page, select <strong id="cce_10_0554__b690818158491">Cloud Native Log Collection</strong> and click <strong id="cce_10_0554__b5831345494">Next: Add-on Configuration</strong>.</li><li id="cce_10_0554__li1483631175820">On the displayed page, select <strong id="cce_10_0554__b331813114518">Control Plane Logs</strong> for <strong id="cce_10_0554__b15645137105118">Cloud Native Log Collection</strong>.<p id="cce_10_0554__p163268466177"></p>
 </li><li id="cce_10_0554__li189746151115">Click <strong id="cce_10_0554__b358214685212">Next: Confirm configuration</strong>.</li></ol>
 <div class="p" id="cce_10_0554__p871324410308"><strong id="cce_10_0554__b97823310164">Enabling control plane logging for an existing cluster</strong><ol id="cce_10_0554__ol38732022182716"><li id="cce_10_0554__li13873172219274">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0554__b628517393918">Logging</strong>.</li><li id="cce_10_0554__li17873022162717">Click the <strong id="cce_10_0554__b177716167186">Control Plane Logs</strong> tab and modify the settings in <strong id="cce_10_0554__b238610581918">Logging Settings</strong>.<div class="fignone" id="cce_10_0554__fig98810154215"><span class="figcap"><b>Figure 1 </b>Modifying logging settings</span><br><span><img id="cce_10_0554__image153861344516" src="en-us_image_0000002253779657.png"></span></div>
 </li><li id="cce_10_0554__li198731722132710">Determine whether to enable logging for each component. If yes, click <span><img id="cce_10_0554__image34861534151720" src="en-us_image_0000002218660022.png"></span>.</li></ol>
diff --git a/docs/cce/umn/cce_10_0555.html b/docs/cce/umn/cce_10_0555.html
index af3802b77..01d35c65b 100644
--- a/docs/cce/umn/cce_10_0555.html
+++ b/docs/cce/umn/cce_10_0555.html
@@ -5,7 +5,7 @@
 <div class="section" id="cce_10_0555__section1995018241214"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0555__ul38996572032"><li id="cce_10_0555__li1437118282351">Up to 100 log rules can be created for each cluster.</li><li id="cce_10_0555__li3899057134">The Cloud Native Log Collection add-on cannot collect .gz, .tar, and .zip logs and cannot access symbolic links of logs.</li><li id="cce_10_0555__li48992575320">If the node <a href="cce_10_0341.html#cce_10_0341__section1473612279214">storage driver</a> is Device Mapper, container file logs must be collected from the path where the data disk is attached to the node.</li><li id="cce_10_0555__li789910571632">If the container runtime is containerd, each stdout log cannot be in multiple lines. (This does not apply to the Cloud Native Log Collection add-on of version 1.3.0 or later.)</li><li id="cce_10_0555__li1319974510478">If a volume is mounted to the directory of a service container, this add-on cannot collect data from the parent directory. In this case, you need to configure a complete data directory.</li><li id="cce_10_0555__li930217527219">If the lifetime of a container is less than 1 minute, logs cannot be collected in a timely manner. As a result, logs may be lost.</li></ul>
 </div>
 <div class="section" id="cce_10_0555__section53625241484"><h4 class="sectiontitle">Enabling Logging on the Console</h4><ol id="cce_10_0555__ol7318196796"><li id="cce_10_0555__li03181161493"><span>Enable logging.</span><p><p id="cce_10_0555__p18411191814578"><strong id="cce_10_0555__b7437453122312">Enabling logging during cluster creation</strong></p>
-<ol type="a" id="cce_10_0555__ol183617113584"><li id="cce_10_0555__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0555__li1283621110581">Click <strong id="cce_10_0555__b1081016564140">Create</strong><strong id="cce_10_0555__b1236194719215"> Cluster</strong> from the top menu.</li><li id="cce_10_0555__li1076913581016">Configure the parameters by referring to <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>. Then, click <span class="uicontrol" id="cce_10_0555__uicontrol133868598013"><b>Next: Select Add-on</b></span> in the lower right corner.</li><li id="cce_10_0555__li163681377132">On the <strong id="cce_10_0555__b553513241554">Select Add-on</strong> page, select <strong id="cce_10_0555__b25361624053">Cloud Native Log Collection</strong>.</li><li id="cce_10_0555__en-us_topic_0000001757561941_li1483631175820">Click <strong id="cce_10_0555__b1787703317193">Next: Add-on Configuration</strong> in the lower right corner and select the required logs.<ul id="cce_10_0555__ul15382152171319"><li id="cce_10_0555__li11382142171315">Container logs: A log collection policy named <strong id="cce_10_0555__b665404815196">default-stdout</strong> will be created, and stdout logs in all namespaces will be reported to LTS.</li><li id="cce_10_0555__li03821021171318">Kubernetes events: A log collection policy named <strong id="cce_10_0555__b163281917172013">default-event</strong> will be created, and Kubernetes events in all namespaces will be reported to LTS.</li></ul>
+<ol type="a" id="cce_10_0555__ol183617113584"><li id="cce_10_0555__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0555__li1283621110581">Click <strong id="cce_10_0555__b2464341634">Create</strong><strong id="cce_10_0555__b16466348311"> Cluster</strong> from the top menu.</li><li id="cce_10_0555__li1076913581016">Configure the parameters by referring to <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>. Then, click <span class="uicontrol" id="cce_10_0555__uicontrol133868598013"><b>Next: Select Add-on</b></span> in the lower right corner.</li><li id="cce_10_0555__li163681377132">On the <strong id="cce_10_0555__b553513241554">Select Add-on</strong> page, select <strong id="cce_10_0555__b25361624053">Cloud Native Log Collection</strong>.</li><li id="cce_10_0555__en-us_topic_0000001757561941_li1483631175820">Click <strong id="cce_10_0555__b1787703317193">Next: Add-on Configuration</strong> in the lower right corner and select the required logs.<ul id="cce_10_0555__ul15382152171319"><li id="cce_10_0555__li11382142171315">Container logs: A log collection policy named <strong id="cce_10_0555__b665404815196">default-stdout</strong> will be created, and stdout logs in all namespaces will be reported to LTS.</li><li id="cce_10_0555__li03821021171318">Kubernetes events: A log collection policy named <strong id="cce_10_0555__b163281917172013">default-event</strong> will be created, and Kubernetes events in all namespaces will be reported to LTS.</li></ul>
 </li><li id="cce_10_0555__en-us_topic_0000001757561941_li19681527171613">Click <strong id="cce_10_0555__b205211845354">Next: Confirm configuration</strong> in the lower right corner. On the displayed page, click <strong id="cce_10_0555__b55217452057">Submit</strong>.</li></ol>
 </p></li><li id="cce_10_0555__li193114172910"><span>View and configure log collection policies.</span><p><ol type="a" id="cce_10_0555__ol1431973318574"><li id="cce_10_0555__li1931973335715">On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0555__b15558833102218"><span id="cce_10_0555__text67912038372">Logging</span></strong>.</li><li id="cce_10_0555__li10603839205711"><p id="cce_10_0555__p2604131442418"><a name="cce_10_0555__li10603839205711"></a><a name="li10603839205711"></a>Click <strong id="cce_10_0555__b17604111432413">View Log Collection Policies</strong> in the upper right corner.</p>
 <p id="cce_10_0555__li10603839205711p0">All log collection policies reported to LTS are displayed.</p>
@@ -23,9 +23,9 @@
 </thead>
 <tbody><tr id="cce_10_0555__row669314101768"><td class="cellrowborder" valign="top" width="8%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p169316101963">Log Type</p>
 </td>
-<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p5693610564"><strong id="cce_10_0555__b497338715">Container standard output</strong>: used to collect container stdout logs. You can create a log collection policy by namespace, workload name, or instance label.</p>
+<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p5693610564"><strong id="cce_10_0555__b541124698">Container standard output</strong>: used to collect container stdout logs. You can create a log collection policy by namespace, workload name, or instance label.</p>
 </td>
-<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p6693010767"><strong id="cce_10_0555__b270938178">Container file log</strong>: used to collect text logs. You can specify a workload or instance label to create a log collection policy.</p>
+<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p6693010767"><strong id="cce_10_0555__b1231486688">Container file log</strong>: used to collect text logs. You can specify a workload or instance label to create a log collection policy.</p>
 </td>
 <td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p369317101617"><strong id="cce_10_0555__b186410191176">Node file log</strong>: used to collect logs from a node. Only one file path can be configured for a log collection policy.</p>
 </td>
@@ -34,9 +34,9 @@
 </tr>
 <tr id="cce_10_0555__row1869371011614"><td class="cellrowborder" valign="top" width="8%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p96934102619">Log Source</p>
 </td>
-<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul1469317101666"><li id="cce_10_0555__li1769314101061"><strong id="cce_10_0555__b660057536">All containers</strong>: You can specify all containers in a namespace. If this parameter is not specified, logs of containers in all namespaces will be collected.</li><li id="cce_10_0555__li1693151015616"><strong id="cce_10_0555__b331220939">Workload</strong>: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li><li id="cce_10_0555__li06938104617"><strong id="cce_10_0555__b391466222">Workload with target label</strong>: You can specify a workload by label and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li></ul>
+<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul1469317101666"><li id="cce_10_0555__li1769314101061"><strong id="cce_10_0555__b408037650">All containers</strong>: You can specify all containers in a namespace. If this parameter is not specified, logs of containers in all namespaces will be collected.</li><li id="cce_10_0555__li1693151015616"><strong id="cce_10_0555__b1204507806">Workload</strong>: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li><li id="cce_10_0555__li06938104617"><strong id="cce_10_0555__b602343138">Workload with target label</strong>: You can specify a workload by label and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li></ul>
 </td>
-<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul269381019616"><li id="cce_10_0555__li16933101664"><strong id="cce_10_0555__b412319155">Workload</strong>: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li><li id="cce_10_0555__li1669311101161"><strong id="cce_10_0555__b900337732">Workload with target label</strong>: You can specify a workload by label and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li></ul>
+<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul269381019616"><li id="cce_10_0555__li16933101664"><strong id="cce_10_0555__b1639761660">Workload</strong>: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li><li id="cce_10_0555__li1669311101161"><strong id="cce_10_0555__b1276722362">Workload with target label</strong>: You can specify a workload by label and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li></ul>
 <p id="cce_10_0555__p16693171011611">You also need to specify the log collection path. For details, see the <a href="#cce_10_0555__li87655474588">log path configuration requirements</a>.</p>
 </td>
 <td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p116933101664"><strong id="cce_10_0555__b16893544192019">Collection Path</strong>: used to configure the log collection path. For details, see the <a href="#cce_10_0555__li87655474588">log path configuration requirements</a>.</p>
@@ -46,9 +46,9 @@
 </tr>
 <tr id="cce_10_0555__row769351010619"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p269491010614">Log Format</p>
 </td>
-<td class="cellrowborder" colspan="4" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul869412103615"><li id="cce_10_0555__li86941101269"><strong id="cce_10_0555__b1040982962">Single-line</strong><p id="cce_10_0555__p869431018612">Each log contains only one line of text. The newline character \n denotes the start of a new log.</p>
-</li><li id="cce_10_0555__li369420105617"><strong id="cce_10_0555__b694122194">Multi-line</strong><p id="cce_10_0555__p1969418108616">Some programs (for example, Java program) print a log that occupies multiple lines. By default, logs are collected by line. If you want to display logs as a single message, you can enable multi-line logging and use the regular pattern. When you select <strong id="cce_10_0555__b56129678">Multi-line</strong>, configure <strong id="cce_10_0555__b1958818069">Log Matching Format</strong>.</p>
-<p id="cce_10_0555__p8694510161">For example, if logs need to be collected by line and each log starts with a date and occupies three lines, you can set <strong id="cce_10_0555__b1761583613">Log Matching Format</strong> to the regular expression of the date, for example, <strong id="cce_10_0555__b293895163">\d{4}-\d{2}-\d{2} \d{2}\:\d{2}\:\d{2}.*</strong>.</p>
+<td class="cellrowborder" colspan="4" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul869412103615"><li id="cce_10_0555__li86941101269"><strong id="cce_10_0555__b865109605">Single-line</strong><p id="cce_10_0555__p869431018612">Each log contains only one line of text. The newline character \n denotes the start of a new log.</p>
+</li><li id="cce_10_0555__li369420105617"><strong id="cce_10_0555__b437524006">Multi-line</strong><p id="cce_10_0555__p1969418108616">Some programs (for example, Java program) print a log that occupies multiple lines. By default, logs are collected by line. If you want to display logs as a single message, you can enable multi-line logging and use the regular pattern. When you select <strong id="cce_10_0555__b1301281406">Multi-line</strong>, configure <strong id="cce_10_0555__b2071850135">Log Matching Format</strong>.</p>
+<p id="cce_10_0555__p8694510161">For example, if logs need to be collected by line and each log starts with a date and occupies three lines, you can set <strong id="cce_10_0555__b2039547748">Log Matching Format</strong> to the regular expression of the date, for example, <strong id="cce_10_0555__b509891045">\d{4}-\d{2}-\d{2} \d{2}\:\d{2}\:\d{2}.*</strong>.</p>
 <div class="p" id="cce_10_0555__p369418101463">The three lines starting with the date are regarded as a log.<pre class="screen" id="cce_10_0555__screen16694191014611">2022-01-01 00:00:00 Exception in thread "main" java.lang.RuntimeException: Something has gone wrong, aborting!
 at com.myproject.module.MyProject.badMethod(MyProject.java:22)
 at com.myproject.module.MyProject.oneMoreMethod(MyProject.java:18)</pre>
@@ -60,8 +60,8 @@ at com.myproject.module.MyProject.oneMoreMethod(MyProject.java:18)</pre>
 <tr id="cce_10_0555__row1369491011610"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p56941410768">LTS Collection</p>
 </td>
 <td class="cellrowborder" colspan="4" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p1469414108617">This parameter is used to configure the log group and log stream for log reporting.</p>
-<ul id="cce_10_0555__ul8694310061"><li id="cce_10_0555__li269410109613"><strong id="cce_10_0555__b1547792719220">Centralized</strong>: The default log group (<strong id="cce_10_0555__b1947711274227">k8s-log-</strong><em id="cce_10_0555__i16477727132215">{Cluster ID}</em>) and default log stream (<strong id="cce_10_0555__b4477172792213">stdout-</strong><em id="cce_10_0555__i6477227132215">{Cluster ID}</em>) are automatically selected.</li><li id="cce_10_0555__li1969431013614"><strong id="cce_10_0555__b6140638191813">Custom</strong>: Select a log group and log stream from the drop-down list.<ul id="cce_10_0555__ul26946100611"><li id="cce_10_0555__li169411107614"><strong id="cce_10_0555__b19866758122313">Log Group</strong>: A log group is the basic unit for LTS to manage logs. If you do not have a log group, CCE prompts you to create one. The default name is <strong id="cce_10_0555__b304410870">k8s-log-</strong><em id="cce_10_0555__i1165756574">{Cluster ID}</em>, for example, <strong id="cce_10_0555__b529813433">k8s-log-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong>.</li><li id="cce_10_0555__li1269415102611"><strong id="cce_10_0555__b98848727">Log Stream</strong>: A log stream is the basic unit for reading and writing logs. You can put different types of logs into different streams to ease management. When you install the add-on or create a log collection policy based on the policy template, the following log streams are automatically created:<p id="cce_10_0555__p2694131010611">- <strong id="cce_10_0555__b1245864880">stdout-</strong><em id="cce_10_0555__i93004590">{Cluster ID}</em> for container logs, for example, <strong id="cce_10_0555__b241726757">stdout-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong></p>
-<p id="cce_10_0555__p116946104619">- <strong id="cce_10_0555__b1944728033">event-</strong><em id="cce_10_0555__i142844410">{Cluster ID}</em> for Kubernetes events, for example, <strong id="cce_10_0555__b135594273">event-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong></p>
+<ul id="cce_10_0555__ul8694310061"><li id="cce_10_0555__li269410109613"><strong id="cce_10_0555__b1547792719220">Centralized</strong>: The default log group (<strong id="cce_10_0555__b1947711274227">k8s-log-</strong><em id="cce_10_0555__i16477727132215">{Cluster ID}</em>) and default log stream (<strong id="cce_10_0555__b4477172792213">stdout-</strong><em id="cce_10_0555__i6477227132215">{Cluster ID}</em>) are automatically selected.</li><li id="cce_10_0555__li1969431013614"><strong id="cce_10_0555__b6140638191813">Custom</strong>: Select a log group and log stream from the drop-down list.<ul id="cce_10_0555__ul26946100611"><li id="cce_10_0555__li169411107614"><strong id="cce_10_0555__b19866758122313">Log Group</strong>: A log group is the basic unit for LTS to manage logs. If you do not have a log group, CCE prompts you to create one. The default name is <strong id="cce_10_0555__b1393040243">k8s-log-</strong><em id="cce_10_0555__i1282116826">{Cluster ID}</em>, for example, <strong id="cce_10_0555__b1613475008">k8s-log-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong>.</li><li id="cce_10_0555__li1269415102611"><strong id="cce_10_0555__b1549304971">Log Stream</strong>: A log stream is the basic unit for reading and writing logs. You can put different types of logs into different streams to ease management. When you install the add-on or create a log collection policy based on the policy template, the following log streams are automatically created:<p id="cce_10_0555__p2694131010611">- <strong id="cce_10_0555__b267622045">stdout-</strong><em id="cce_10_0555__i159149061">{Cluster ID}</em> for container logs, for example, <strong id="cce_10_0555__b936652102">stdout-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong></p>
+<p id="cce_10_0555__p116946104619">- <strong id="cce_10_0555__b2030552358">event-</strong><em id="cce_10_0555__i14220303">{Cluster ID}</em> for Kubernetes events, for example, <strong id="cce_10_0555__b1205181461">event-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong></p>
 </li></ul>
 </li></ul>
 <p id="cce_10_0555__p12465650672"></p>
diff --git a/docs/cce/umn/cce_10_0557.html b/docs/cce/umn/cce_10_0557.html
index 3099bf636..407350312 100644
--- a/docs/cce/umn/cce_10_0557.html
+++ b/docs/cce/umn/cce_10_0557.html
@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Overview</h1>
 <div id="body0000001709722970"><p id="cce_10_0557__p15811134085211">Kubernetes logs allow you to locate and rectify faults. This section describes how to manage Kubernetes logs using different methods.</p>
 <p id="cce_10_0557__p1581110407521">The following are Kubernetes log management methods:</p>
-<ul id="cce_10_0557__ul1581124010529"><li id="cce_10_0557__li1581184015527">Use the Cloud Native Log Collection add-on to collect application logs and report them to LTS, which provides log statistics and analysis. For details, see <a href="cce_10_0555.html">Collecting Container Logs Using the Cloud Native Log Collection Add-on</a>.</li><li id="cce_10_0557__li72390542383">Connect CCE to AOM. For details, see <a href="cce_10_0018.html">Collecting Container Logs Using ICAgent</a>.</li><li id="cce_10_0557__li1811240125214">Collect control plane component logs and Kubernetes audit logs from the CCE control plane and add them to the LTS log streams in your account. For details, see <a href="cce_10_0554.html">Collecting Control Plane Component Logs</a> and <a href="cce_10_0792.html">Collecting Audit Logs</a>.</li><li id="cce_10_0557__li08111840105213">Collect Kubernetes events and add them to the LTS log stream in your account for persistent storage and statistical analysis. For details, see <a href="cce_10_0793.html">Collecting Kubernetes Events</a>.</li></ul>
+<ul id="cce_10_0557__ul1581124010529"><li id="cce_10_0557__li1581184015527">Use the Cloud Native Log Collection add-on to collect application logs and report them to LTS, which provides log statistics and analysis. For details, see <a href="cce_10_0555.html">Collecting Container Logs Using the Cloud Native Log Collection Add-on</a>.</li><li id="cce_10_0557__li72390542383">Connect CCE to AOM 1.0. For details, see <a href="cce_10_0018.html">Collecting Container Logs Using ICAgent</a>.</li><li id="cce_10_0557__li1811240125214">Collect control plane component logs and Kubernetes audit logs from the CCE control plane and add them to the LTS log streams in your account. For details, see <a href="cce_10_0554.html">Collecting Control Plane Component Logs</a> and <a href="cce_10_0792.html">Collecting Audit Logs</a>.</li><li id="cce_10_0557__li08111840105213">Collect Kubernetes events and add them to the LTS log stream in your account for persistent storage and statistical analysis. For details, see <a href="cce_10_0793.html">Collecting Kubernetes Events</a>.</li></ul>
 </div>
 <div>
 <div class="familylinks">
diff --git a/docs/cce/umn/cce_10_0613.html b/docs/cce/umn/cce_10_0613.html
index 2176dde4c..fe8478301 100644
--- a/docs/cce/umn/cce_10_0613.html
+++ b/docs/cce/umn/cce_10_0613.html
@@ -2,125 +2,127 @@
 
 <h1 class="topictitle1">Overview</h1>
 <div id="body0000001492419990"><p id="cce_10_0613__p8060118">To achieve persistent storage, CCE allows you to mount the storage volumes created from Elastic Volume Service (EVS) disks to a path of a container. When the container is migrated within an AZ, the mounted EVS volumes are also migrated. By using EVS volumes, you can mount the remote file directory of a storage system to a container so that data in the data volume is permanently preserved. Even if the container is deleted, the data in the data volume is still stored in the storage system.</p>
+<div class="note" id="cce_10_0613__note1598020156518"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0613__p0980131520514">Common I/O disks are the previous-generation product and cannot be created.</p>
+</div></div>
 <div class="section" id="cce_10_0613__section16496164821814"><h4 class="sectiontitle">EVS Disk Performance Specifications</h4><p id="cce_10_0613__p9165134482217">EVS performance metrics include:</p>
 <ul id="cce_10_0613__ul8165544182213"><li id="cce_10_0613__li1716504462213">IOPS: the number of input/output operations performed by an EVS disk per second</li><li id="cce_10_0613__li6165174452219">Throughput: the amount of data read from and written into an EVS disk per second</li><li id="cce_10_0613__li12165194412214">I/O latency: the minimum interval between two consecutive I/O operations on an EVS disk</li></ul>
 
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0613__table96842242313" frame="border" border="1" rules="all"><caption><b>Table 1 </b>EVS disk performance specifications</caption><thead align="left"><tr id="cce_10_0613__row36859218231"><th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.2.4.2.7.1.1"><p id="cce_10_0613__p2685162112314">Parameter</p>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0613__table96842242313" frame="border" border="1" rules="all"><caption><b>Table 1 </b>EVS disk performance specifications</caption><thead align="left"><tr id="cce_10_0613__row36859218231"><th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.3.4.2.7.1.1"><p id="cce_10_0613__p2685162112314">Parameter</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.2.4.2.7.1.2"><p id="cce_10_0613__p1668518219236">Extreme SSD</p>
+<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.3.4.2.7.1.2"><p id="cce_10_0613__p1668518219236">Extreme SSD</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.2.4.2.7.1.3"><p id="cce_10_0613__p6685112182312">General Purpose SSD</p>
+<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.3.4.2.7.1.3"><p id="cce_10_0613__p6685112182312">General Purpose SSD</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.2.4.2.7.1.4"><p id="cce_10_0613__p146851216232">Ultra-high I/O</p>
+<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.3.4.2.7.1.4"><p id="cce_10_0613__p146851216232">Ultra-high I/O</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.2.4.2.7.1.5"><p id="cce_10_0613__p1268592142316">High I/O</p>
+<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.3.4.2.7.1.5"><p id="cce_10_0613__p1268592142316">High I/O</p>
 </th>
-<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.2.4.2.7.1.6"><p id="cce_10_0613__p18430203253">Common I/O</p>
+<th align="left" class="cellrowborder" valign="top" width="16.666666666666664%" id="mcps1.3.3.4.2.7.1.6"><p id="cce_10_0613__p18430203253">Common I/O (Previous Generation Product)</p>
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_10_0613__row1068511202310"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p868511272311">Max. capacity (GiB)</p>
+<tbody><tr id="cce_10_0613__row1068511202310"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p868511272311">Max. capacity (GiB)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><ul id="cce_10_0613__ul19212826143119"><li id="cce_10_0613__li3212122683117">System disk: 1,024</li><li id="cce_10_0613__li1821212614311">Data disk: 32,768</li></ul>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><ul id="cce_10_0613__ul19212826143119"><li id="cce_10_0613__li3212122683117">System disk: 1,024</li><li id="cce_10_0613__li1821212614311">Data disk: 32,768</li></ul>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><ul id="cce_10_0613__ul0774193653112"><li id="cce_10_0613__li177741536113110">System disk: 1,024</li><li id="cce_10_0613__li0775736173117">Data disk: 32,768</li></ul>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><ul id="cce_10_0613__ul0774193653112"><li id="cce_10_0613__li177741536113110">System disk: 1,024</li><li id="cce_10_0613__li0775736173117">Data disk: 32,768</li></ul>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><ul id="cce_10_0613__ul17676123713311"><li id="cce_10_0613__li167693783119">System disk: 1,024</li><li id="cce_10_0613__li467619375312">Data disk: 32,768</li></ul>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><ul id="cce_10_0613__ul17676123713311"><li id="cce_10_0613__li167693783119">System disk: 1,024</li><li id="cce_10_0613__li467619375312">Data disk: 32,768</li></ul>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><ul id="cce_10_0613__ul2299113819318"><li id="cce_10_0613__li17299163863117">System disk: 1,024</li><li id="cce_10_0613__li10299153843114">Data disk: 32,768</li></ul>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><ul id="cce_10_0613__ul2299113819318"><li id="cce_10_0613__li17299163863117">System disk: 1,024</li><li id="cce_10_0613__li10299153843114">Data disk: 32,768</li></ul>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><ul id="cce_10_0613__ul1396423833116"><li id="cce_10_0613__li6964163820313">System disk: 1,024</li><li id="cce_10_0613__li1296417383311">Data disk: 32,768</li></ul>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><ul id="cce_10_0613__ul1396423833116"><li id="cce_10_0613__li6964163820313">System disk: 1,024</li><li id="cce_10_0613__li1296417383311">Data disk: 32,768</li></ul>
 </td>
 </tr>
-<tr id="cce_10_0613__row568552182317"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p10685162152318">Max. IOPS</p>
+<tr id="cce_10_0613__row568552182317"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p10685162152318">Max. IOPS</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p196506714327">128,000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p196506714327">128,000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p378361973219">20,000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p378361973219">20,000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p156502716323">50,000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p156502716323">50,000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p196516773214">5000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p196516773214">5000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p14753083218">2200</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p14753083218">2200</p>
 </td>
 </tr>
-<tr id="cce_10_0613__row1685172152315"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p10685182122315">Max. throughput (MiB/s)</p>
+<tr id="cce_10_0613__row1685172152315"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p10685182122315">Max. throughput (MiB/s)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p11934511163317">1000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p11934511163317">1000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p59341911163313">250</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p59341911163313">250</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p19349114334">350</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p19349114334">350</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p14653318103315">150</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p14653318103315">150</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p14934131153315">50</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p14934131153315">50</p>
 </td>
 </tr>
-<tr id="cce_10_0613__row19571517152720"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p10571417132715">Burst IOPS limit</p>
+<tr id="cce_10_0613__row19571517152720"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p10571417132715">Burst IOPS limit</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p2754882347">64,000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p2754882347">64,000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p860901812341">8000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p860901812341">8000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p97591822133413">16,000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p97591822133413">16,000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p1175411813419">5000</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p1175411813419">5000</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p1675478133418">2200</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p1675478133418">2200</p>
 </td>
 </tr>
-<tr id="cce_10_0613__row3891131752713"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p889151792710">Disk IOPS</p>
+<tr id="cce_10_0613__row3891131752713"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p889151792710">Disk IOPS</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p98911417132715">Min. (128,000, 1800 + 50 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p98911417132715">Min. (128,000, 1800 + 50 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p6891201792714">Min. (20,000, 1800 + 12 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p6891201792714">Min. (20,000, 1800 + 12 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p1989111722712">Min. (50,000, 1800 + 50 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p1989111722712">Min. (50,000, 1800 + 50 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p13891181711278">Min. (5000, 1800 + 8 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p13891181711278">Min. (5000, 1800 + 8 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p1089131718271">Min. (2200, 500 + 2 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p1089131718271">Min. (2200, 500 + 2 x Capacity)</p>
 </td>
 </tr>
-<tr id="cce_10_0613__row1852181813274"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p1252111822713">Disk throughput (MiB/s)</p>
+<tr id="cce_10_0613__row1852181813274"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p1252111822713">Disk throughput (MiB/s)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p2052114187272">Min. (1000, 120 + 0.5 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p2052114187272">Min. (1000, 120 + 0.5 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p1352114186278">Min. (250, 100 + 0.5 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p1352114186278">Min. (250, 100 + 0.5 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p1052118189277">Min. (350, 120 + 0.5 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p1052118189277">Min. (350, 120 + 0.5 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p7521161818278">Min. (150, 100 + 0.15 x Capacity)</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p7521161818278">Min. (150, 100 + 0.15 x Capacity)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p20521171832713">50</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p20521171832713">50</p>
 </td>
 </tr>
-<tr id="cce_10_0613__row151914199272"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p1419116192272">Single-queue access latency (ms)</p>
+<tr id="cce_10_0613__row151914199272"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p1419116192272">Single-queue access latency (ms)</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p151911419162716">Sub-millisecond</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p151911419162716">Sub-millisecond</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p2191131911279">1</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p2191131911279">1</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p819111942719">1</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p819111942719">1</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p2191121962717">1–3</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p2191121962717">1–3</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p191911199278">5–10</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p191911199278">5–10</p>
 </td>
 </tr>
-<tr id="cce_10_0613__row9618162115278"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.1 "><p id="cce_10_0613__p46181421112719">API name</p>
+<tr id="cce_10_0613__row9618162115278"><td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.1 "><p id="cce_10_0613__p46181421112719">API name</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.2 "><p id="cce_10_0613__p861882113279">ESSD</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.2 "><p id="cce_10_0613__p861882113279">ESSD</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.3 "><p id="cce_10_0613__p161832112711">GPSSD</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.3 "><p id="cce_10_0613__p161832112711">GPSSD</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.4 "><p id="cce_10_0613__p5618162111274">SSD</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.4 "><p id="cce_10_0613__p5618162111274">SSD</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.5 "><p id="cce_10_0613__p9618202116273">SAS</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.5 "><p id="cce_10_0613__p9618202116273">SAS</p>
 </td>
-<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.2.4.2.7.1.6 "><p id="cce_10_0613__p166181621112714">SATA</p>
+<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.3.4.2.7.1.6 "><p id="cce_10_0613__p166181621112714">SATA</p>
 </td>
 </tr>
 </tbody>
diff --git a/docs/cce/umn/cce_10_0625.html b/docs/cce/umn/cce_10_0625.html
index 0aab5cd86..20716b2df 100644
--- a/docs/cce/umn/cce_10_0625.html
+++ b/docs/cce/umn/cce_10_0625.html
@@ -291,7 +291,7 @@ spec:
 </li></ol>
 </p></li></ol>
 </div>
-<div class="section" id="cce_10_0625__section15626135823118"><h4 class="sectiontitle">Using Subdirectories of an Existing SFS Turbo File System Through kubectl</h4><ol id="cce_10_0625__ol15626135823114"><li id="cce_10_0625__li1862614589311"><span>Use kubectl to access the cluster.</span></li><li id="cce_10_0625__li126261358203111"><span>Create a PV.</span><p><ol type="a" id="cce_10_0625__ol206261758183113"><li id="cce_10_0625__li186261858193110"><a name="cce_10_0625__li186261858193110"></a><a name="li186261858193110"></a>Create the <strong id="cce_10_0625__b303136625">pv-sfsturbo.yaml</strong> file.<div class="p" id="cce_10_0625__p962618581313">Example:<pre class="screen" id="cce_10_0625__screen1626205811316">apiVersion: v1
+<div class="section" id="cce_10_0625__section15626135823118"><h4 class="sectiontitle">Using Subdirectories of an Existing SFS Turbo File System Through kubectl</h4><ol id="cce_10_0625__ol15626135823114"><li id="cce_10_0625__li1862614589311"><span>Use kubectl to access the cluster.</span></li><li id="cce_10_0625__li126261358203111"><span>Create a PV.</span><p><ol type="a" id="cce_10_0625__ol206261758183113"><li id="cce_10_0625__li186261858193110"><a name="cce_10_0625__li186261858193110"></a><a name="li186261858193110"></a>Create the <strong id="cce_10_0625__b129295921">pv-sfsturbo.yaml</strong> file.<div class="p" id="cce_10_0625__p962618581313">Example:<pre class="screen" id="cce_10_0625__screen1626205811316">apiVersion: v1
 kind: PersistentVolume
 metadata:
   annotations:
@@ -300,9 +300,9 @@ metadata:
   name: <i><span class="varname" id="cce_10_0625__varname1562765816317">pv-sfsturbo</span></i>    # PV name
 spec:
   accessModes:
-  - ReadWriteMany      # Access mode. The value must be <strong id="cce_10_0625__b993775346">ReadWriteMany</strong> for SFS Turbo.
+  - ReadWriteMany      # Access mode. The value must be <strong id="cce_10_0625__b1682474562">ReadWriteMany</strong> for SFS Turbo.
   capacity:
-    <strong id="cce_10_0625__b1273685874">storage: <i><span class="varname" id="cce_10_0625__varname209826907">500Gi</span></i></strong>       # SFS Turbo volume capacity
+    <strong id="cce_10_0625__b1247915342">storage: <i><span class="varname" id="cce_10_0625__varname387709424">500Gi</span></i></strong>       # SFS Turbo volume capacity
   csi:
     driver: sfsturbo.csi.everest.io    # Dependent storage driver for the mounting
     fsType: nfs
@@ -362,7 +362,7 @@ spec:
 <td class="cellrowborder" valign="top" width="16%" headers="mcps1.3.6.2.2.2.1.1.3.2.4.1.2 "><p id="cce_10_0625__p46284583314">Yes</p>
 </td>
 <td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.6.2.2.2.1.1.3.2.4.1.3 "><p id="cce_10_0625__p14628958183117">A reclaim policy is supported when the cluster version is or later than 1.19.10 and the Everest version is or later than 1.2.9. For details, see <a href="cce_10_0378.html#cce_10_0378__section19999142414413">PV Reclaim Policy</a>.</p>
-<p id="cce_10_0625__p1362855833119"><strong id="cce_10_0625__b155867568">Retain</strong>: When a PVC is deleted, both the PV and underlying storage resources will be retained. You need to manually delete these resources. After the PVC is deleted, the PV is in the <strong id="cce_10_0625__b1520900336">Released</strong> state and cannot be bound to a PVC again.</p>
+<p id="cce_10_0625__p1362855833119"><strong id="cce_10_0625__b1783712519">Retain</strong>: When a PVC is deleted, both the PV and underlying storage resources will be retained. You need to manually delete these resources. After the PVC is deleted, the PV is in the <strong id="cce_10_0625__b2082038724">Released</strong> state and cannot be bound to a PVC again.</p>
 <p id="cce_10_0625__p116281058153117"><strong id="cce_10_0625__b735716192914">Delete</strong>: This parameter can be configured when subdirectories are automatically created, indicating that the PV is deleted when a PVC is deleted.</p>
 </td>
 </tr>
@@ -403,7 +403,7 @@ spec:
 </td>
 <td class="cellrowborder" valign="top" width="16%" headers="mcps1.3.6.2.2.2.1.1.3.2.4.1.2 "><p id="cce_10_0625__p5629258123114">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.6.2.2.2.1.1.3.2.4.1.3 "><p id="cce_10_0625__p7629358133118">The StorageClass name of SFS Turbo volumes is <strong id="cce_10_0625__b1942469617">csi-sfsturbo</strong>.</p>
+<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.6.2.2.2.1.1.3.2.4.1.3 "><p id="cce_10_0625__p7629358133118">The StorageClass name of SFS Turbo volumes is <strong id="cce_10_0625__b180549281">csi-sfsturbo</strong>.</p>
 </td>
 </tr>
 </tbody>
@@ -411,7 +411,7 @@ spec:
 </div>
 </li><li id="cce_10_0625__li106291658193117">Run the following command to create a PV:<pre class="screen" id="cce_10_0625__screen762935823111">kubectl apply -f pv-sfsturbo.yaml</pre>
 </li></ol>
-</p></li><li id="cce_10_0625__li663111586311"><span>Create a PVC.</span><p><ol type="a" id="cce_10_0625__ol15631558113115"><li id="cce_10_0625__li9631195819314">Create the <strong id="cce_10_0625__b1341472831">pvc-sfsturbo.yaml</strong> file.<pre class="screen" id="cce_10_0625__screen1363112586311">apiVersion: v1
+</p></li><li id="cce_10_0625__li663111586311"><span>Create a PVC.</span><p><ol type="a" id="cce_10_0625__ol15631558113115"><li id="cce_10_0625__li9631195819314">Create the <strong id="cce_10_0625__b999605548">pvc-sfsturbo.yaml</strong> file.<pre class="screen" id="cce_10_0625__screen1363112586311">apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
   name: <i><span class="varname" id="cce_10_0625__varname1763135811316">pvc-sfsturbo</span></i>
@@ -421,12 +421,12 @@ metadata:
 
 spec:
   accessModes:
-  - ReadWriteMany                  # The value must be <strong id="cce_10_0625__b1766470846">ReadWriteMany</strong> for SFS Turbo.
+  - ReadWriteMany                  # The value must be <strong id="cce_10_0625__b1664919121">ReadWriteMany</strong> for SFS Turbo.
   resources:
     requests:
-      <strong id="cce_10_0625__b2035063829">storage: <i><span class="varname" id="cce_10_0625__varname859115299">500Gi</span></i></strong>               # SFS Turbo volume capacity.
-  <strong id="cce_10_0625__b1981417918">storageClassName: <i><span class="varname" id="cce_10_0625__varname123053233">csi-sfsturbo</span></i></strong>       # StorageClass name of the SFS Turbo file system, which must be the same as that of the PV
-  <strong id="cce_10_0625__b1566200411">volumeName: <i><span class="varname" id="cce_10_0625__varname360562489">pv-sfsturbo</span></i></strong>    # PV name</pre>
+      <strong id="cce_10_0625__b929959415">storage: <i><span class="varname" id="cce_10_0625__varname1296505875">500Gi</span></i></strong>               # SFS Turbo volume capacity.
+  <strong id="cce_10_0625__b340056459">storageClassName: <i><span class="varname" id="cce_10_0625__varname1299064119">csi-sfsturbo</span></i></strong>       # StorageClass name of the SFS Turbo file system, which must be the same as that of the PV
+  <strong id="cce_10_0625__b2012415138">volumeName: <i><span class="varname" id="cce_10_0625__varname875791533">pv-sfsturbo</span></i></strong>    # PV name</pre>
 
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0625__table3631958193117" frame="border" border="1" rules="all"><caption><b>Table 5 </b>Key parameters</caption><thead align="left"><tr id="cce_10_0625__row146321858143116"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.6.2.3.2.1.1.3.2.4.1.1"><p id="cce_10_0625__p6632175818310">Parameter</p>
 </th>
diff --git a/docs/cce/umn/cce_10_0652.html b/docs/cce/umn/cce_10_0652.html
index 86161fc26..1e4a900e5 100644
--- a/docs/cce/umn/cce_10_0652.html
+++ b/docs/cce/umn/cce_10_0652.html
@@ -565,12 +565,12 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="cce_10_0652__row1170915321921"><td class="cellrowborder" valign="top" width="13.050000000000002%" headers="mcps1.3.6.2.1.6.1.1 "><p id="cce_10_0652__p670911321926">Maximum size of a container <strong id="cce_10_0652__b706433838">core</strong> file</p>
+<tbody><tr id="cce_10_0652__row1170915321921"><td class="cellrowborder" valign="top" width="13.050000000000002%" headers="mcps1.3.6.2.1.6.1.1 "><p id="cce_10_0652__p670911321926">Maximum size of a container <strong id="cce_10_0652__b106043570">core</strong> file</p>
 </td>
 <td class="cellrowborder" valign="top" width="12.970000000000004%" headers="mcps1.3.6.2.1.6.1.2 "><p id="cce_10_0652__p157098328217">limitcore</p>
 </td>
 <td class="cellrowborder" valign="top" width="27.740000000000002%" headers="mcps1.3.6.2.1.6.1.3 "><p id="cce_10_0652__p17097324213">Maximum size of a core file in a container. The unit is byte.</p>
-<p id="cce_10_0652__p1970910327218">If not specified, the value is <strong id="cce_10_0652__b889180877">infinity</strong>.</p>
+<p id="cce_10_0652__p1970910327218">If not specified, the value is <strong id="cce_10_0652__b1439271286">infinity</strong>.</p>
 </td>
 <td class="cellrowborder" valign="top" width="18.500000000000004%" headers="mcps1.3.6.2.1.6.1.4 "><p id="cce_10_0652__p270913321223">Default: 5368709120</p>
 </td>
@@ -586,7 +586,7 @@
 <td class="cellrowborder" valign="top" width="18.500000000000004%" headers="mcps1.3.6.2.1.6.1.4 "><p id="cce_10_0652__p16709103210210">Default: 1048576</p>
 </td>
 <td class="cellrowborder" valign="top" width="27.740000000000002%" headers="mcps1.3.6.2.1.6.1.5 "><p id="cce_10_0652__p0709143213210">The value cannot exceed the value of the kernel parameter <strong id="cce_10_0652__b7301143015102">nr_open</strong> and cannot be a negative number.</p>
-<p id="cce_10_0652__p77092327210">You can run the following command to obtain the kernel parameter <strong id="cce_10_0652__b1583099143">nr_open</strong>:</p>
+<p id="cce_10_0652__p77092327210">You can run the following command to obtain the kernel parameter <strong id="cce_10_0652__b848437943">nr_open</strong>:</p>
 <pre class="screen" id="cce_10_0652__screen870919321321">sysctl -a | grep nr_open</pre>
 </td>
 </tr>
diff --git a/docs/cce/umn/cce_10_0653.html b/docs/cce/umn/cce_10_0653.html
index 2d2a13289..e14c030e6 100644
--- a/docs/cce/umn/cce_10_0653.html
+++ b/docs/cce/umn/cce_10_0653.html
@@ -97,7 +97,7 @@
 </tr>
 <tr id="cce_10_0653__en-us_topic_0000001199021246_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.3.2.2.3.1.1 "><p id="cce_10_0653__en-us_topic_0000001199021246_p0669147185817">Data Disk</p>
 </td>
-<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.3.2.2.3.1.2 "><ul id="cce_10_0653__ul138301057194017"><li id="cce_10_0653__cce_10_0363_li103472126407"><strong id="cce_10_0653__cce_10_0363_b493614401788">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0653__cce_10_0363_uicontrol16936640683"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0653__cce_10_0363_uicontrol29366400810"><b>Data Disk</b></span>. <strong id="cce_10_0653__cce_10_0363_b79361840284">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0653__cce_10_0363_ul324262033711"><li id="cce_10_0653__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0653__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
+<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.3.2.2.3.1.2 "><ul id="cce_10_0653__ul138301057194017"><li id="cce_10_0653__cce_10_0363_li103472126407"><strong id="cce_10_0653__cce_10_0363_b87711342223">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0653__cce_10_0363_uicontrol1378123452217"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0653__cce_10_0363_uicontrol107853413227"><b>Data Disk</b></span>. <strong id="cce_10_0653__cce_10_0363_b187815343221">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0653__cce_10_0363_ul324262033711"><li id="cce_10_0653__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0653__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
 </li><li id="cce_10_0653__cce_10_0363_li18830161664015">If <span class="uicontrol" id="cce_10_0653__cce_10_0363_uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0653__cce_10_0363_uicontrol19561032184918"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
 <div class="note" id="cce_10_0653__note21798915509"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p13544143175218">After the data disk configuration is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.</p>
 </div></div>
@@ -105,7 +105,7 @@
 <div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><p id="cce_10_0653__en-us_topic_0000001199021246_p3752312011">Expand the area and configure the following parameters:</p></div>
 <div class="dropdowncontext"><ul id="cce_10_0653__en-us_topic_0000001199021246_ul197721145155911"><li id="cce_10_0653__en-us_topic_0000001199021246_li12110343014"><strong id="cce_10_0653__b11121533832215">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.<div class="note" id="cce_10_0653__note165242505419"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p196522251548">After the data disk space allocation configuration is modified, the modification takes effect only for new nodes. The configuration cannot take effect for the existing nodes even if they are reset.</p>
 </div></div>
-</li><li id="cce_10_0653__en-us_topic_0000001199021246_li1095641711169"><strong id="cce_10_0653__b71171410204510">Enabled</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <ul id="cce_10_0653__en-us_topic_0000001199021246_ul1924511512168"><li id="cce_10_0653__en-us_topic_0000001199021246_li4245181561611"><strong id="cce_10_0653__b1122736904">Not encrypted</strong> is selected by default.</li><li id="cce_10_0653__en-us_topic_0000001199021246_li17245415121616">After setting <strong id="cce_10_0653__b119442517458">Data Disk Encryption</strong> to <strong id="cce_10_0653__b6194192554518">Enabled</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0653__b2019512253459">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li></ul>
+</li><li id="cce_10_0653__en-us_topic_0000001199021246_li1095641711169"><strong id="cce_10_0653__b71171410204510">Enabled</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <ul id="cce_10_0653__en-us_topic_0000001199021246_ul1924511512168"><li id="cce_10_0653__en-us_topic_0000001199021246_li4245181561611"><strong id="cce_10_0653__b211242923">Not encrypted</strong> is selected by default.</li><li id="cce_10_0653__en-us_topic_0000001199021246_li17245415121616">After setting <strong id="cce_10_0653__b119442517458">Data Disk Encryption</strong> to <strong id="cce_10_0653__b6194192554518">Enabled</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0653__b2019512253459">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li></ul>
 <div class="note" id="cce_10_0653__note17572111875311"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p05729189537">After the <strong id="cce_10_0653__b7507148121716">Data Disk Encryption</strong> is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.</p>
 </div></div>
 </li></ul>
diff --git a/docs/cce/umn/cce_10_0656.html b/docs/cce/umn/cce_10_0656.html
index 8ab5930a3..24b3eb2d4 100644
--- a/docs/cce/umn/cce_10_0656.html
+++ b/docs/cce/umn/cce_10_0656.html
@@ -50,7 +50,7 @@
 </div></div>
 </p></li></ol>
 </div>
-<div class="section" id="cce_10_0656__section7117453155012"><a name="cce_10_0656__section7117453155012"></a><a name="section7117453155012"></a><h4 class="sectiontitle">Migrating Nodes from the Default Node Pool to a Custom Node Pool</h4><ol id="cce_10_0656__ol10650132575118"><li id="cce_10_0656__li1765032575120"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0656__li4650132575113"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0656__uicontrol7381192011385"><b>Nodes</b></span> and click the <span class="uicontrol" id="cce_10_0656__uicontrol7381720113812"><b>Node Pools</b></span> tab.</span></li><li id="cce_10_0656__li15651172514517"><span>Locate the target node pool and choose <strong id="cce_10_0656__b17230173873816">More</strong> &gt; <strong id="cce_10_0656__b66841812397">Accept Node</strong>.</span></li><li id="cce_10_0656__li1856013330389"><span>In the <span class="uicontrol" id="cce_10_0656__uicontrol20561193318385"><b>Accept Node</b></span> dialog box, select the nodes that meet the following conditions:</span><p><ul id="cce_10_0656__ul1966705163816"><li id="cce_10_0656__li36671851103812">The nodes and the current node pool are deployed in the same VPC and subnet.</li><li id="cce_10_0656__li19667185113385">The nodes and the current node pool are in the same cloud server group.</li><li id="cce_10_0656__li2667135153814">The billing mode of the nodes is supported by the current node pool.</li><li id="cce_10_0656__li26671451183818">The nodes are running and they are from the default node pool.</li><li id="cce_10_0656__li1766718517385">The flavor, AZ, resource reservation, container engine, and OS configurations of the nodes are the same as those of the node pool.</li></ul>
+<div class="section" id="cce_10_0656__section7117453155012"><a name="cce_10_0656__section7117453155012"></a><a name="section7117453155012"></a><h4 class="sectiontitle">Migrating Nodes from the Default Node Pool to a Custom Node Pool</h4><ol id="cce_10_0656__ol10650132575118"><li id="cce_10_0656__li1765032575120"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0656__li4650132575113"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0656__uicontrol7381192011385"><b>Nodes</b></span> and click the <span class="uicontrol" id="cce_10_0656__uicontrol7381720113812"><b>Node Pools</b></span> tab.</span></li><li id="cce_10_0656__li15651172514517"><span>Locate the target node pool and choose <strong id="cce_10_0656__b1144865192212">More</strong> &gt; <strong id="cce_10_0656__b1744815517223">Migrate Node</strong>.</span></li><li id="cce_10_0656__li1856013330389"><span>In the <span class="uicontrol" id="cce_10_0656__uicontrol120205811228"><b>Migrate Node</b></span> dialog box, select the nodes that meet the following conditions:</span><p><ul id="cce_10_0656__ul1966705163816"><li id="cce_10_0656__li36671851103812">The nodes and the current node pool are deployed in the same VPC and subnet.</li><li id="cce_10_0656__li19667185113385">The nodes and the current node pool are in the same cloud server group.</li><li id="cce_10_0656__li2667135153814">The billing mode of the nodes is supported by the current node pool.</li><li id="cce_10_0656__li26671451183818">The nodes are running and they are from the default node pool.</li><li id="cce_10_0656__li1766718517385">The flavor, AZ, resource reservation, container engine, and OS configurations of the nodes are the same as those of the node pool.</li></ul>
 </p></li><li id="cce_10_0656__li5651102516519"><span>Click <strong id="cce_10_0656__b0354153674818">OK</strong>.</span><p><div class="note" id="cce_10_0656__note9651125145110"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0656__ul17651152520513"><li id="cce_10_0656__li365132575112">After nodes are migrated into a node pool, the pool's resource tags, Kubernetes labels, and Kubernetes taints will be synchronized to the nodes. If there is a conflict, the node pool's configurations will take precedence.</li><li id="cce_10_0656__li42279347352">After the migration, the pool's security group will take over the nodes' original security group.</li><li id="cce_10_0656__li0982821191117">After the migration, the pool's agency will take over the nodes' original agency.</li><li id="cce_10_0656__li2227173403518">After the migration, the nodes' original login mode will remain unchanged.</li><li id="cce_10_0656__li652931133617">After a node is migrated to a node pool after being accepted by the cluster, its acceptance tag will be removed. Scaling in the node pool may result in the removal of the node.</li></ul>
 </div></div>
 </p></li></ol>
diff --git a/docs/cce/umn/cce_10_0659.html b/docs/cce/umn/cce_10_0659.html
index 1dc0b50c6..3b58de4e3 100644
--- a/docs/cce/umn/cce_10_0659.html
+++ b/docs/cce/umn/cce_10_0659.html
@@ -69,7 +69,7 @@
 <p id="cce_10_0659__cce_10_0132_p2317112419618">Typical scenario: Disk I/O suspension causes process suspension.</p>
 </td>
 <td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.5.4.1.2.2.4.1.3 "><p id="cce_10_0659__cce_10_0132_p16872758114011">Warning event</p>
-<p id="cce_10_0659__cce_10_0132_p173071159247">Listening object: <strong id="cce_10_0659__cce_10_0132_b592872265">/dev/kmsg</strong></p>
+<p id="cce_10_0659__cce_10_0132_p173071159247">Listening object: <strong id="cce_10_0659__cce_10_0132_b1029490566">/dev/kmsg</strong></p>
 <p id="cce_10_0659__cce_10_0132_p153079591241">Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."</p>
 </td>
 </tr>
@@ -81,7 +81,7 @@
 </div></div>
 </td>
 <td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.5.4.1.2.2.4.1.3 "><p id="cce_10_0659__cce_10_0132_p944535317711">Warning event</p>
-<p id="cce_10_0659__cce_10_0132_p183981710948">Listening object: <strong id="cce_10_0659__cce_10_0132_b1027686576">/dev/kmsg</strong></p>
+<p id="cce_10_0659__cce_10_0132_p183981710948">Listening object: <strong id="cce_10_0659__cce_10_0132_b967989253">/dev/kmsg</strong></p>
 <p id="cce_10_0659__cce_10_0132_p83993101042">Matching rule: <strong id="cce_10_0659__cce_10_0132_b15200817134219">Remounting filesystem read-only</strong></p>
 </td>
 </tr>
diff --git a/docs/cce/umn/cce_10_0681.html b/docs/cce/umn/cce_10_0681.html
index 747884b8d..b59d1d1be 100644
--- a/docs/cce/umn/cce_10_0681.html
+++ b/docs/cce/umn/cce_10_0681.html
@@ -12,7 +12,7 @@
 </li><li id="cce_10_0681__li128551156114310">After a Service is created, if the affinity setting is switched from the cluster level to the node level, the connection tracing table will not be cleared. Do not modify the Service affinity setting after the Service is created. To modify it, create a Service again.</li><li id="cce_10_0681__li1553715571314">If service affinity is set to the node level (that is, <a href="cce_10_0249.html#cce_10_0249__section18134208069">externalTrafficPolicy</a> is set to <strong id="cce_10_0681__b771833995021">Local</strong>), the cluster may fail to access the Service by using the ELB address. For details, see <a href="cce_10_0249.html#cce_10_0249__section52631714117">Why a Service Fail to Be Accessed from Within the Cluster</a>.</li><li id="cce_10_0681__li62831358182017">In a CCE Turbo cluster that utilizes Cloud Native Network 2.0, node-level affinity is supported only when the Service backend is connected to a hostNetwork pod.</li><li id="cce_10_0681__li35821536336">Dedicated ELB load balancers can be used only in clusters of v1.17 and later.</li><li id="cce_10_0681__li13903431185814">Dedicated load balancers must support private networks (with private IP addresses). If the Service needs to support HTTP, the dedicated load balancers must be of the application (HTTP/HTTPS) type.</li><li id="cce_10_0681__li1031414582416">When the cluster service forwarding (proxy) mode is IPVS, the node IP cannot be configured as the external IP of the Service. Otherwise, the node is unavailable.</li><li id="cce_10_0681__li202253469362">If you have an IPVS-backed cluster and use the same ELB load balancer for both the ingress and Service in the same cluster or for the Service ports in different clusters, you will not be able to access the ingress from the nodes or containers in the cluster, or the Service ports in other clusters. This is because kube-proxy mounts the LoadBalancer Service address to the ipvs-0 bridge, which intercepts the load balancer traffic. Use separate load balancers for these ingresses and Services.</li></ul>
 </div>
 <div class="section" id="cce_10_0681__section84162025538"><a name="cce_10_0681__section84162025538"></a><a name="section84162025538"></a><h4 class="sectiontitle">Using the Console</h4><ol id="cce_10_0681__ol751935681319"><li id="cce_10_0681__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0681__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0681__b156552313155"><span id="cce_10_0681__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0681__uicontrol365152341517"><b>Create Service</b></span>.</span></li><li id="cce_10_0681__li185190567138"><span>Configure parameters.</span><p><ul id="cce_10_0681__ul4446314017144"><li id="cce_10_0681__li6462394317144"><strong id="cce_10_0681__b184589110485">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0681__li89543531070"><strong id="cce_10_0681__b36010193819">Service Type</strong>: Select <strong id="cce_10_0681__b10639751102410">LoadBalancer</strong>.</li><li id="cce_10_0681__li4800017144"><strong id="cce_10_0681__b2525621144818">Namespace</strong>: namespace that the workload belongs to.</li><li id="cce_10_0681__li1758110116149"><strong id="cce_10_0681__b145812011111415">Service Affinity</strong>: For details, see <a href="cce_10_0249.html#cce_10_0249__section18134208069">externalTrafficPolicy (Service Affinity)</a>.<ul id="cce_10_0681__ul158101161412"><li id="cce_10_0681__li105815113141"><strong id="cce_10_0681__b23340713595021">Cluster level</strong>: The IP addresses and access ports of all nodes in a cluster can access the workload associated with the Service. Accessing the Service will result in a decrease in performance due to route redirection, and the source IP address of the client cannot be obtained.</li><li id="cce_10_0681__li185817117145"><strong id="cce_10_0681__b48376456095021">Node level</strong>: Only the IP address and access port of the node where the workload is located can access the workload associated with the Service. Accessing the Service will not result in a decrease in performance due to route redirection, and the source IP address of the client can be obtained.</li></ul>
-</li><li id="cce_10_0681__li43200017144"><strong id="cce_10_0681__b96551525164816">Selector</strong>: Add a label and click <strong id="cce_10_0681__b7640145162420">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0681__b64644610295021">Reference Workload Label</strong> to use the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0681__b80189846895021">OK</strong>.</li><li id="cce_10_0681__li142435567390"><strong id="cce_10_0681__b274262713418">Protocol Version</strong>: This function is disabled by default. After this function is enabled, the cluster IP address of the Service can be set to an IPv6 address.  <strong id="cce_10_0681__b160917813995021">This parameter is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).</strong></li><li id="cce_10_0681__li14384123818176"><strong id="cce_10_0681__b735014212194">Load Balancer</strong>: Select a load balancer type and creation mode.<p id="cce_10_0681__p16957182024010">A load balancer can be dedicated or shared. A dedicated load balancer supports <span class="uicontrol" id="cce_10_0681__uicontrol18781155918012"><b>Network (TCP/UDP)</b></span>, <span class="uicontrol" id="cce_10_0681__uicontrol478215591013"><b>Application (HTTP/HTTPS)</b></span>, or <span class="uicontrol" id="cce_10_0681__uicontrol14782175916010"><b>Network (TCP/UDP) &amp; Application (HTTP/HTTPS)</b></span>.</p>
+</li><li id="cce_10_0681__li43200017144"><strong id="cce_10_0681__b96551525164816">Selector</strong>: Add a label and click <strong id="cce_10_0681__b7640145162420">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0681__b64644610295021">Reference Workload Label</strong> to use the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0681__b80189846895021">OK</strong>.</li><li id="cce_10_0681__li142435567390"><strong id="cce_10_0681__b274262713418">Protocol Version</strong>: This function is disabled by default. After this function is enabled, the cluster IP address of the Service can be set to an IPv6 address. <strong id="cce_10_0681__b160917813995021">This function is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).</strong></li><li id="cce_10_0681__li14384123818176"><strong id="cce_10_0681__b735014212194">Load Balancer</strong>: Select a load balancer type and creation mode.<p id="cce_10_0681__p16957182024010">A load balancer can be dedicated or shared. A dedicated load balancer supports <span class="uicontrol" id="cce_10_0681__uicontrol18781155918012"><b>Network (TCP/UDP)</b></span>, <span class="uicontrol" id="cce_10_0681__uicontrol478215591013"><b>Application (HTTP/HTTPS)</b></span>, or <span class="uicontrol" id="cce_10_0681__uicontrol14782175916010"><b>Network (TCP/UDP) &amp; Application (HTTP/HTTPS)</b></span>.</p>
 <div class="p" id="cce_10_0681__p118821032125215">You can select <strong id="cce_10_0681__b1335114510238">Use existing</strong> or <strong id="cce_10_0681__b4525145472310">Auto create</strong> to obtain a load balancer. For details about the configuration of different creation modes, see <a href="#cce_10_0681__table026610571395">Table 1</a>.
 <div class="tablenoborder"><a name="cce_10_0681__table026610571395"></a><a name="table026610571395"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0681__table026610571395" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Load balancer configurations</caption><thead align="left"><tr id="cce_10_0681__row16266155712396"><th align="left" class="cellrowborder" valign="top" width="16.17%" id="mcps1.3.3.2.3.2.1.7.3.4.2.3.1.1"><p id="cce_10_0681__p826618579394">How to Create</p>
 </th>
@@ -562,7 +562,7 @@ spec:
 </td>
 <td class="cellrowborder" valign="top" width="57.99999999999999%" headers="mcps1.3.5.3.3.2.8.2.5.1.4 "><p id="cce_10_0681__p0333699508">Specifies the load balancing algorithm of the backend server group. The default value is <strong id="cce_10_0681__b49019934719">ROUND_ROBIN</strong>.</p>
 <p id="cce_10_0681__p6333198503">Options:</p>
-<ul id="cce_10_0681__ul13337919508"><li id="cce_10_0681__li3333893501"><strong id="cce_10_0681__b348504127">ROUND_ROBIN</strong>: weighted round robin algorithm</li><li id="cce_10_0681__li93331191509"><strong id="cce_10_0681__b1268496185">LEAST_CONNECTIONS</strong>: weighted least connections algorithm</li><li id="cce_10_0681__li1333379105016"><strong id="cce_10_0681__b362099940">SOURCE_IP</strong>: source IP hash algorithm</li></ul>
+<ul id="cce_10_0681__ul13337919508"><li id="cce_10_0681__li3333893501"><strong id="cce_10_0681__b2057485612">ROUND_ROBIN</strong>: weighted round robin algorithm</li><li id="cce_10_0681__li93331191509"><strong id="cce_10_0681__b2098510234">LEAST_CONNECTIONS</strong>: weighted least connections algorithm</li><li id="cce_10_0681__li1333379105016"><strong id="cce_10_0681__b1246437111">SOURCE_IP</strong>: source IP hash algorithm</li></ul>
 <div class="note" id="cce_10_0681__note1434111223537"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0681__p53417224532">If this parameter is set to <strong id="cce_10_0681__b173272016476">SOURCE_IP</strong>, the weight setting (<strong id="cce_10_0681__b3329207471">weight</strong> field) of backend servers bound to the backend server group is invalid, and sticky session cannot be enabled.</p>
 </div></div>
 </td>
diff --git a/docs/cce/umn/cce_10_0683.html b/docs/cce/umn/cce_10_0683.html
index 556dd55b7..6644bca77 100644
--- a/docs/cce/umn/cce_10_0683.html
+++ b/docs/cce/umn/cce_10_0683.html
@@ -50,7 +50,7 @@
 </li><li id="cce_10_0683__li425842212236">Do not connect an ingress and a Service that uses HTTP or HTTPS to the same listener of the same load balancer. Otherwise, a port conflict occurs.</li></ul>
 </div>
 <div class="section" id="cce_10_0683__section11366115274719"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0683__ol11182813184815"><li id="cce_10_0683__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0683__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0683__b22451421203410"><span id="cce_10_0683__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0683__uicontrol202461521133413"><b>Create Service</b></span>.</span></li><li id="cce_10_0683__li185190567138"><span>Configure Service parameters. In this example, only mandatory parameters required for using HTTP/HTTPS are listed. For details about how to configure other parameters, see <a href="cce_10_0681.html#cce_10_0681__section84162025538">Using the Console</a>.</span><p><ul id="cce_10_0683__ul4446314017144"><li id="cce_10_0683__li6462394317144"><strong id="cce_10_0683__b3447131173716">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0683__li89543531070"><strong id="cce_10_0683__b18167920123718">Service Type</strong>: Select <strong id="cce_10_0683__b8167420123719">LoadBalancer</strong>.</li><li id="cce_10_0683__li43200017144"><strong id="cce_10_0683__b615732913719">Selector</strong>: Add a label and click <strong id="cce_10_0683__b13157162916379">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0683__b3767165514386">Reference Workload Label</strong> to use the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0683__b4767175512387">OK</strong>.</li><li id="cce_10_0683__li14384123818176"><strong id="cce_10_0683__b133866950741940">Load Balancer</strong>: Select a load balancer type and creation mode.<ul id="cce_10_0683__ul589211413819"><li id="cce_10_0683__li1995101610373"><a name="cce_10_0683__li1995101610373"></a><a name="li1995101610373"></a>A load balancer can be dedicated or shared. To enable HTTP/HTTPS on the listener port of a dedicated load balancer, the type of the load balancer must be <span class="uicontrol" id="cce_10_0683__uicontrol10880161884218"><b>Application (HTTP/HTTPS)</b></span> or <span class="uicontrol" id="cce_10_0683__uicontrol69316238422"><b>Network (TCP/UDP) &amp; Application (HTTP/HTTPS)</b></span>.</li><li id="cce_10_0683__li13266657143911">This section uses an existing load balancer as an example. For details about the parameters for automatically creating a load balancer, see <a href="cce_10_0681.html#cce_10_0681__table026610571395">Table 1</a>.</li></ul>
-</li><li id="cce_10_0683__li158271501592"><strong id="cce_10_0683__b118960577162836">Ports</strong><ul id="cce_10_0683__ul3499201217144"><li id="cce_10_0683__li4649265917144"><strong id="cce_10_0683__b6586105724417">Protocol</strong>: Select <strong id="cce_10_0683__b1267442920551">TCP</strong>. If you select <strong id="cce_10_0683__b1991173725512">UDP</strong>, HTTP and HTTPS will be unavailable.</li><li id="cce_10_0683__li353122153610"><strong id="cce_10_0683__b17823158134414">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0683__li475042104417"><strong id="cce_10_0683__b1632833124516">Container Port</strong>: listener port of the workload. For example, Nginx uses port 80 by default.</li><li id="cce_10_0683__li8911126175719"><a name="cce_10_0683__li8911126175719"></a><a name="li8911126175719"></a><strong id="cce_10_0683__b1676102210519">Frontend Protocol</strong>: specifies whether to enable HTTP/HTTPS on the listener port. For a <a href="#cce_10_0683__li1995101610373">dedicated load balancer</a>, to use HTTP/HTTPS, the type of the load balancer must be <strong id="cce_10_0683__b260413592111">Application (HTTP/HTTPS)</strong>.</li></ul>
+</li><li id="cce_10_0683__li158271501592"><strong id="cce_10_0683__b118960577162836">Ports</strong><ul id="cce_10_0683__ul3499201217144"><li id="cce_10_0683__li4649265917144"><strong id="cce_10_0683__b6586105724417">Protocol</strong>: Select <strong id="cce_10_0683__b1267442920551">TCP</strong>. If you select <strong id="cce_10_0683__b1991173725512">UDP</strong>, HTTP and HTTPS will be unavailable.</li><li id="cce_10_0683__li353122153610"><strong id="cce_10_0683__b17823158134414">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0683__li475042104417"><strong id="cce_10_0683__b1632833124516">Container Port</strong>: listener port of the workload. For example, Nginx uses port 80 by default.</li><li id="cce_10_0683__li8911126175719"><a name="cce_10_0683__li8911126175719"></a><a name="li8911126175719"></a><strong id="cce_10_0683__b1676102210519">Frontend Protocol</strong>: specifies whether to enable HTTP/HTTPS on the listener port. For a <a href="#cce_10_0683__li1995101610373">dedicated load balancer</a>, to use HTTP/HTTPS, the type of the load balancer must be <strong id="cce_10_0683__b1317719361412">Application (HTTP/HTTPS)</strong>.</li></ul>
 </li><li id="cce_10_0683__li1567510365916"><strong id="cce_10_0683__b632318213454">Listener</strong><ul id="cce_10_0683__ul38353035910"><li id="cce_10_0683__li187883173610"><strong id="cce_10_0683__b5685124184515">SSL Authentication</strong>: Select this option if <a href="#cce_10_0683__li8911126175719">HTTPS</a> is enabled on the listener port. This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions.<ul id="cce_10_0683__ul1710811473613"><li id="cce_10_0683__li1837443723520"><strong id="cce_10_0683__b154661108351219">One-way authentication</strong>: Only the backend server is authenticated. If you also need to authenticate the identity of the client, select mutual authentication.</li><li id="cce_10_0683__li6964158133615"><strong id="cce_10_0683__b135429033451343">Mutual authentication</strong>: If you want the clients and the load balancer to authenticate each other, select this option. Only authenticated clients will be allowed to access the load balancer.</li></ul>
 </li><li id="cce_10_0683__li1219103263614"><strong id="cce_10_0683__b88900673851437">CA Certificate</strong>: If <strong id="cce_10_0683__b211768832651437">SSL Authentication</strong> is set to <strong id="cce_10_0683__b121632582051437">Mutual authentication</strong>, add a CA certificate to authenticate the client. A CA certificate is issued by a certificate authority (CA) and used to verify the certificate issuer. If HTTPS mutual authentication is required, HTTPS connections can be established only when the client provides a certificate issued by a specific CA.</li><li id="cce_10_0683__li983517014595"><strong id="cce_10_0683__b1407173094519">Server Certificate</strong>: If <a href="#cce_10_0683__li8911126175719">HTTPS</a> is enabled on the listener port, you must select a server certificate. </li><li id="cce_10_0683__li1883511013595"><strong id="cce_10_0683__b1959873514454">SNI</strong>: If <a href="#cce_10_0683__li8911126175719">HTTPS</a> is enabled on the listener port, you must determine whether to add an SNI certificate. Before adding an SNI certificate, ensure the certificate contains a domain name. </li><li id="cce_10_0683__li1027969193913"><strong id="cce_10_0683__b176999176434">Security Policy</strong>: If <a href="#cce_10_0683__li8911126175719">HTTPS</a> is enabled on the listener port, you can select a security policy. This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions.</li><li id="cce_10_0683__li142441213914"><strong id="cce_10_0683__b210114004103814">Backend Protocol</strong>: If <a href="#cce_10_0683__li8911126175719">HTTPS</a> is enabled on the listener port, HTTP or HTTPS can be used to access the backend server. The default value is <strong id="cce_10_0683__b818860717103814">HTTP</strong>. This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions.</li></ul>
 <div class="note" id="cce_10_0683__note44941912310"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0683__p449919113113">If multiple HTTPS Services are released, all listeners will use the same certificate configuration.</p>
diff --git a/docs/cce/umn/cce_10_0695.html b/docs/cce/umn/cce_10_0695.html
index c5b8328ee..9f70f6e91 100644
--- a/docs/cce/umn/cce_10_0695.html
+++ b/docs/cce/umn/cce_10_0695.html
@@ -255,7 +255,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="10.101010101010102%" headers="mcps1.3.7.3.2.5.1.2 "><p id="cce_10_0695__p152717184211">String</p>
 </td>
-<td class="cellrowborder" valign="top" width="49.494949494949495%" headers="mcps1.3.7.3.2.5.1.3 "><p id="cce_10_0695__p1271218624">To interconnect with HTTPS backend services, set this parameter to <strong id="cce_10_0695__b1496976411">https</strong>.</p>
+<td class="cellrowborder" valign="top" width="49.494949494949495%" headers="mcps1.3.7.3.2.5.1.3 "><p id="cce_10_0695__p1271218624">To interconnect with HTTPS backend services, set this parameter to <strong id="cce_10_0695__b2009044910">https</strong>.</p>
 </td>
 <td class="cellrowborder" valign="top" width="24.242424242424242%" headers="mcps1.3.7.3.2.5.1.4 "><p id="cce_10_0695__p82713181929">v1.23.8, v1.25.3, or later</p>
 </td>
diff --git a/docs/cce/umn/cce_10_0766.html b/docs/cce/umn/cce_10_0766.html
index e51b98f53..0e2278f15 100644
--- a/docs/cce/umn/cce_10_0766.html
+++ b/docs/cce/umn/cce_10_0766.html
@@ -16,7 +16,7 @@
 <div class="section" id="cce_10_0766__section3832511163"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0766__ul11600144419477"><li id="cce_10_0766__li86001544164712">Pods need to be rescheduled using a scheduler, and no scheduler can label pods or nodes. Therefore, an evicted pod might be rescheduled to the original node.</li><li id="cce_10_0766__li1360064434710">Descheduling does not support anti-affinity between pods. An evicted pod is in anti-affinity relationship with other running pods. Therefore, the scheduler may still schedule the pod back to the node where the pod was evicted from.</li><li id="cce_10_0766__li1723104634716">When configuring load-aware descheduling, you are required to enable load-aware scheduling on Volcano Scheduler. When configuring HighNodeUtilization, you are required to enable bin packing on Volcano Scheduler.</li></ul>
 </div>
 <div class="section" id="cce_10_0766__section2205422165218"><h4 class="sectiontitle">Configuring a Load-aware Descheduling Policy</h4><p id="cce_10_0766__p981242083313">When configuring a load-aware descheduling policy, do as follows to enable load-aware scheduling on Volcano Scheduler:</p>
-<ol id="cce_10_0766__ol1191102425017"><li id="cce_10_0766__li788513403566"><span>Log in to the CCE console and click the cluster name to access the cluster details page. Choose <strong id="cce_10_0766__b28237332516"><span id="cce_10_0766__text588134045613">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0766__b1988144010560">Volcano Scheduler</strong> on the right, and click <span class="uicontrol" id="cce_10_0766__uicontrol10884194020561"><b>Edit</b></span>. In the <span class="uicontrol" id="cce_10_0766__uicontrol68841640195611"><b>Extended Functions</b></span> area, enable descheduling and click <span class="uicontrol" id="cce_10_0766__uicontrol944062611576"><b>OK</b></span> to update the add-on configuration.</span></li><li id="cce_10_0766__li1133512612611"><span>In the navigation pane, choose <strong id="cce_10_0766__b1316533520534">Settings</strong>. On the <strong id="cce_10_0766__b10641210195419">Scheduling</strong> tab page, enable load-aware scheduling. For details, see <a href="cce_10_0789.html">Load-aware Scheduling</a>.</span></li><li id="cce_10_0766__li2611115310117"><span>On the <strong id="cce_10_0766__b141041210102615">Scheduling</strong> tab page, select <strong id="cce_10_0766__b52141526122619">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0766__b18431228144412">Try Now</strong>.</span><p><p id="cce_10_0766__p1271124317302"></p>
+<ol id="cce_10_0766__ol1191102425017"><li id="cce_10_0766__li788513403566"><span>Log in to the CCE console and click the cluster name to access the cluster details page. Choose <strong id="cce_10_0766__b28237332516"><span id="cce_10_0766__text588134045613">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0766__b1988144010560">Volcano Scheduler</strong> on the right, and click <span class="uicontrol" id="cce_10_0766__uicontrol10884194020561"><b>Edit</b></span>. In the <span class="uicontrol" id="cce_10_0766__uicontrol68841640195611"><b>Extended Functions</b></span> area, enable descheduling and click <span class="uicontrol" id="cce_10_0766__uicontrol944062611576"><b>OK</b></span> to update the add-on configuration.</span></li><li id="cce_10_0766__li1133512612611"><span>In the navigation pane, choose <strong id="cce_10_0766__b1316533520534">Settings</strong>. On the <strong id="cce_10_0766__b10641210195419">Scheduling</strong> tab page, enable load-aware scheduling. For details, see <a href="cce_10_0789.html">Load-aware Scheduling</a>.</span></li><li id="cce_10_0766__li2611115310117"><span>On the <strong id="cce_10_0766__b471919382428">Scheduling</strong> tab page, select <strong id="cce_10_0766__b87194389422">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0766__b971913389422">Try Now</strong>.</span><p><p id="cce_10_0766__p1271124317302"></p>
 <p id="cce_10_0766__p2949165711111"></p>
 </p></li><li id="cce_10_0766__li15509139199"><span>Configure a load-aware descheduling policy. If you are using Volcano v1.11.21 or later, refer to the example JSON parameter settings below. For more parameters, see the JSON example in <span class="uicontrol" id="cce_10_0766__uicontrol49003534221"><b>Getting Started</b></span> on the console.</span><p><pre class="screen" id="cce_10_0766__screen2088962213541">{
 ...
@@ -143,7 +143,7 @@
 </p></li><li id="cce_10_0766__li1459653101119"><span>Click <strong id="cce_10_0766__b629716144368">OK</strong>.</span></li></ol>
 </div>
 <div class="section" id="cce_10_0766__section75319387422"><h4 class="sectiontitle">Configuring a HighNodeUtilization Policy</h4><p id="cce_10_0766__p2487714153411">When configuring a HighNodeUtilization policy, do as follows to enable the bin packing policy on Volcano Scheduler:</p>
-<ol id="cce_10_0766__ol1641174513119"><li id="cce_10_0766__li1136151955814"><span>Log in to the CCE console and click the cluster name to access the cluster details page. Choose <strong id="cce_10_0766__b17273112445318"><span id="cce_10_0766__text18361219165813">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0766__b20273202420533">Volcano Scheduler</strong> on the right, and click <span class="uicontrol" id="cce_10_0766__uicontrol7273124155318"><b>Edit</b></span>. In the <span class="uicontrol" id="cce_10_0766__uicontrol142731524105312"><b>Extended Functions</b></span> area, enable descheduling and click <span class="uicontrol" id="cce_10_0766__uicontrol327313245532"><b>OK</b></span> to update the add-on configuration.</span></li><li id="cce_10_0766__li790735120245"><span>In the navigation pane, choose <strong id="cce_10_0766__b39827473541">Settings</strong>. On the <strong id="cce_10_0766__b15982647105419">Scheduling</strong> tab page, enable bin packing. For details, see <a href="cce_10_0773.html">Bin Packing</a>.</span></li><li id="cce_10_0766__li1551132718146"><span>On the <strong id="cce_10_0766__b1698654110292">Scheduling</strong> tab page, select <strong id="cce_10_0766__b1498613413297">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0766__b1608191054716">Try Now</strong>.</span><p><p id="cce_10_0766__p166302073311"></p>
+<ol id="cce_10_0766__ol1641174513119"><li id="cce_10_0766__li1136151955814"><span>Log in to the CCE console and click the cluster name to access the cluster details page. Choose <strong id="cce_10_0766__b17273112445318"><span id="cce_10_0766__text18361219165813">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0766__b20273202420533">Volcano Scheduler</strong> on the right, and click <span class="uicontrol" id="cce_10_0766__uicontrol7273124155318"><b>Edit</b></span>. In the <span class="uicontrol" id="cce_10_0766__uicontrol142731524105312"><b>Extended Functions</b></span> area, enable descheduling and click <span class="uicontrol" id="cce_10_0766__uicontrol327313245532"><b>OK</b></span> to update the add-on configuration.</span></li><li id="cce_10_0766__li790735120245"><span>In the navigation pane, choose <strong id="cce_10_0766__b39827473541">Settings</strong>. On the <strong id="cce_10_0766__b15982647105419">Scheduling</strong> tab page, enable bin packing. For details, see <a href="cce_10_0773.html">Bin Packing</a>.</span></li><li id="cce_10_0766__li1551132718146"><span>On the <strong id="cce_10_0766__b5166115115422">Scheduling</strong> tab page, select <strong id="cce_10_0766__b9166115124217">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0766__b20168851184216">Try Now</strong>.</span><p><p id="cce_10_0766__p166302073311"></p>
 <p id="cce_10_0766__p14513278140"></p>
 </p></li><li id="cce_10_0766__li564114501116"><span>If you are using a resource defragmentation policy, refer to the example JSON parameter settings below. For more parameters, see the JSON example in <span class="uicontrol" id="cce_10_0766__uicontrol1096263214387"><b>Getting Started</b></span> on the console.</span><p><pre class="screen" id="cce_10_0766__screen56411245181118">{
 ... 
diff --git a/docs/cce/umn/cce_10_0767.html b/docs/cce/umn/cce_10_0767.html
index d88cd1768..1f720ff8e 100644
--- a/docs/cce/umn/cce_10_0767.html
+++ b/docs/cce/umn/cce_10_0767.html
@@ -13,7 +13,7 @@
 <div class="section" id="cce_10_0767__section14961545145018"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0767__ul0573143445117"><li id="cce_10_0767__li157315346519">A cluster of v1.19.16 or later is available. For details, see <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_10_0767__li15731334145112">Volcano of v1.11.5 or later has been installed in the cluster. For details, see <a href="cce_10_0193.html">Volcano Scheduler</a>.</li></ul>
 </div>
 <div class="section" id="cce_10_0767__section354413379271"><h4 class="sectiontitle">Configuring Soft Affinity Scheduling for Volcano Node Pools</h4><ol id="cce_10_0767__ol167317110297"><li id="cce_10_0767__li29881874313"><span>Configure labels for affinity scheduling in the node pool.</span><p><ol type="a" id="cce_10_0767__ol174734373319"><li id="cce_10_0767__li422214216316">Log in to the CCE console.</li><li id="cce_10_0767__li91948153218">Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0767__uicontrol1845914484513"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0767__b1845910448450">Node Pools</strong> tab.</li><li id="cce_10_0767__li1447333716313">Click <strong id="cce_10_0767__b6433133374612">Update</strong> of the target node pool. On the page that is displayed, configure labels in the <strong id="cce_10_0767__b3696144014519">Kubernetes Label</strong> area.</li></ol>
-</p></li><li id="cce_10_0767__li2611115310117"><span>In the navigation pane, choose <strong id="cce_10_0767__b1588865815584">Settings</strong> and click the <strong id="cce_10_0767__b17664413599">Scheduling</strong> tab. Select <strong id="cce_10_0767__b1864197591">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0767__b167539363129">Try Now</strong>.</span><p><p id="cce_10_0767__p2416127183119"></p>
+</p></li><li id="cce_10_0767__li2611115310117"><span>In the navigation pane, choose <strong id="cce_10_0767__b5284135120438">Settings</strong> and click the <strong id="cce_10_0767__b928435114312">Scheduling</strong> tab. Select <strong id="cce_10_0767__b1284105112434">Volcano scheduler</strong>, find the expert mode, and click <strong id="cce_10_0767__b1628418516432">Try Now</strong>.</span><p><p id="cce_10_0767__p2416127183119"></p>
 <p id="cce_10_0767__p2949165711111"></p>
 </p></li><li id="cce_10_0767__li177316122916"><span>Configure Volcano scheduler parameters. The following shows a configuration example in JSON format:</span><p><pre class="screen" id="cce_10_0767__screen10942175162718">...
     "default_scheduler_conf": {
diff --git a/docs/cce/umn/cce_10_0792.html b/docs/cce/umn/cce_10_0792.html
index 1ea018446..67c8d7817 100644
--- a/docs/cce/umn/cce_10_0792.html
+++ b/docs/cce/umn/cce_10_0792.html
@@ -1,7 +1,7 @@
 <a name="cce_10_0792"></a><a name="cce_10_0792"></a>
 
 <h1 class="topictitle1">Collecting Audit Logs</h1>
-<div id="body0000001757642129"><p id="cce_10_0792__p12206121914264">CCE allows you to collect the logs of master nodes. On the <span class="uicontrol" id="cce_10_0792__uicontrol753711213414"><b>Kubernetes Audit Logs</b></span> tab of <strong id="cce_10_0792__b653731214411"><span id="cce_10_0792__text12537312447">Logging</span></strong>, you can determine whether to report audit logs to LTS.</p>
+<div id="body0000001757642129"><p id="cce_10_0792__p12206121914264">CCE allows you to collect the logs of master nodes. On the <span class="uicontrol" id="cce_10_0792__uicontrol163801659142811"><b>Kubernetes Audit Logs</b></span> tab of <strong id="cce_10_0792__b653731214411"><span id="cce_10_0792__text12537312447">Logging</span></strong>, you can determine whether to report audit logs to LTS.</p>
 <div class="section" id="cce_10_0792__section15915571101"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0792__ul1145273617100"><li id="cce_10_0792__li124521636151014">The cluster version must be v1.21.7-r0 or later, v1.23.5-r0 or later, or 1.25.</li><li id="cce_10_0792__li945218367100">There is required LTS resource quota.</li></ul>
 </div>
 <div class="section" id="cce_10_0792__section133166619593"><h4 class="sectiontitle">Audit Logs</h4>
@@ -29,18 +29,18 @@
 </div>
 </div>
 <div class="section" id="cce_10_0792__section1883701101111"><h4 class="sectiontitle">Enabling <span id="cce_10_0792__ph1643272414239">Kubernetes</span> Audit Logging</h4><p id="cce_10_0792__p126238295311"><strong id="cce_10_0792__b34221452191019">Enabling audit logging during cluster creation</strong></p>
-<ol id="cce_10_0792__ol7219545201112"><li id="cce_10_0792__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0792__li428804217210">In the upper right corner, click <strong id="cce_10_0792__b15799145291918">Create Cluster</strong>. Then, configure the parameters and click <strong id="cce_10_0792__b118001522191">Next: Select Add-on</strong>.</li><li id="cce_10_0792__li1932603355813">On the displayed page, select <strong id="cce_10_0792__b1616314912275">Cloud Native Log Collection</strong> and click <strong id="cce_10_0792__b9163194902712">Next: Add-on Configuration</strong>.</li><li id="cce_10_0792__li112881342423">On the displayed page, select <strong id="cce_10_0792__b195211191166">Kubernetes Audit Logs</strong> for <strong id="cce_10_0792__b165212196162">Cloud Native Log Collection</strong>.<p id="cce_10_0792__p1185204016207"></p>
+<ol id="cce_10_0792__ol7219545201112"><li id="cce_10_0792__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0792__li428804217210">Click <strong id="cce_10_0792__b17447104220116">Create Cluster</strong>. Then, configure the parameters and click <strong id="cce_10_0792__b94475424119">Next: Select Add-on</strong>.</li><li id="cce_10_0792__li1932603355813">On the displayed page, select <strong id="cce_10_0792__b1616314912275">Cloud Native Log Collection</strong> and click <strong id="cce_10_0792__b9163194902712">Next: Add-on Configuration</strong>.</li><li id="cce_10_0792__li112881342423">On the displayed page, select <strong id="cce_10_0792__b195211191166">Kubernetes Audit Logs</strong> for <strong id="cce_10_0792__b165212196162">Cloud Native Log Collection</strong>.<p id="cce_10_0792__p1185204016207"></p>
 </li><li id="cce_10_0792__li189746151115">Click <strong id="cce_10_0792__b124921525151618">Next: Confirm configuration</strong>.</li></ol>
 <div class="p" id="cce_10_0792__p871324410308"><strong id="cce_10_0792__b12354189132416">Enabling audit logging for an existing cluster</strong><ol id="cce_10_0792__ol1864131782711"><li id="cce_10_0792__li1964717152717">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0792__b17167125242">Logging</strong>.</li><li id="cce_10_0792__li5641177276">Click the <strong id="cce_10_0792__b31012257812">Kubernetes Audit Logs</strong> tab and modify the settings in <strong id="cce_10_0792__b010112513814">Logging Settings</strong>.<div class="fignone" id="cce_10_0792__fig1952155113243"><span class="figcap"><b>Figure 1 </b>Enabling audit logging for an existing cluster</span><br><span><img id="cce_10_0792__image799815232302" src="en-us_image_0000002218820214.png"></span></div>
 </li><li id="cce_10_0792__li1864181762717">Determine whether to enable logging for the audit component. If yes, click <span><img id="cce_10_0792__image34861534151720" src="en-us_image_0000002218820226.png"></span>.</li></ol>
 </div>
 </div>
-<div class="section" id="cce_10_0792__section69816278134"><h4 class="sectiontitle">Viewing <span id="cce_10_0792__ph26015349396">Kubernetes</span> Audit Logs</h4><p id="cce_10_0792__p1415353118133"><strong id="cce_10_0792__b1681219618408">Viewing <span id="cce_10_0792__ph198127614402">Kubernetes</span> audit logs on the CCE console</strong></p>
-<ol id="cce_10_0792__ol10360346161319"><li id="cce_10_0792__li736014469130">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0792__b178704495199"><span id="cce_10_0792__text19441132515716">Logging</span></strong>.</li><li id="cce_10_0792__li1360204610135">Click the <span class="uicontrol" id="cce_10_0792__uicontrol1720919368814"><b>Kubernetes Audit Logs</b></span> tab to view audit logs in the cluster. For details about related operations, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/lts/lts_04_1053.html" target="_blank" rel="noopener noreferrer">Log Tank Service User Guide</a>.</li></ol>
-<p id="cce_10_0792__p6343278586"><strong id="cce_10_0792__b17654203195213">Viewing <span id="cce_10_0792__ph1295813316915">Kubernetes</span> audit logs on the TLS console</strong></p>
+<div class="section" id="cce_10_0792__section69816278134"><h4 class="sectiontitle">Viewing <span id="cce_10_0792__ph03941023102416">Kubernetes</span> Audit Logs</h4><p id="cce_10_0792__p1415353118133"><strong id="cce_10_0792__b108861143183410">Viewing <span id="cce_10_0792__ph9515950132417">Kubernetes</span> audit logs on the CCE console</strong></p>
+<ol id="cce_10_0792__ol10360346161319"><li id="cce_10_0792__li736014469130">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0792__b178704495199"><span id="cce_10_0792__text19441132515716">Logging</span></strong>.</li><li id="cce_10_0792__li1360204610135">Click the <span class="uicontrol" id="cce_10_0792__uicontrol1185152216378"><b>Kubernetes Audit Logs</b></span> tab to view audit logs in the cluster. For details about related operations, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/lts/lts_04_1053.html" target="_blank" rel="noopener noreferrer">Log Tank Service User Guide</a>.</li></ol>
+<p id="cce_10_0792__p6343278586"><strong id="cce_10_0792__b164928538342">Viewing <span id="cce_10_0792__ph1295813316915">Kubernetes</span> audit logs on the LTS console</strong></p>
 <ol id="cce_10_0792__ol18717852131410"><li id="cce_10_0792__li10717135261411">Log in to the LTS console and choose <strong id="cce_10_0792__b697385134413">Log Management</strong>.</li><li id="cce_10_0792__li371710527141">Search for the log group by cluster ID and click the log group name to view the log streams. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/lts/lts_04_1053.html" target="_blank" rel="noopener noreferrer">Log Tank Service User Guide</a>.</li></ol>
 </div>
-<div class="section" id="cce_10_0792__section1450954712188"><h4 class="sectiontitle">Disabling <span id="cce_10_0792__ph53707944119">Kubernetes</span> Audit Logging</h4><ol id="cce_10_0792__ol1060255016193"><li id="cce_10_0792__li660375011919">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0792__b1079713932015"><span id="cce_10_0792__text161291556477">Logging</span></strong>.</li><li id="cce_10_0792__li10603450121916">Click the <span class="uicontrol" id="cce_10_0792__uicontrol152700264122"><b>Kubernetes Audit Logs</b></span> tab.</li><li id="cce_10_0792__li1696341572112">Disable the audit component and click <span><img id="cce_10_0792__image1126525920146" src="en-us_image_0000002218660366.png"></span>.<div class="note" id="cce_10_0792__note76261859132113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0792__p17627059162114">After you disable audit logging, logs are no longer written to the original log stream, but the existing logs will not be deleted and expenditures may be incurred for this.</p>
+<div class="section" id="cce_10_0792__section1450954712188"><h4 class="sectiontitle">Disabling <span id="cce_10_0792__ph101591655192512">Kubernetes</span> Audit Logging</h4><ol id="cce_10_0792__ol1060255016193"><li id="cce_10_0792__li660375011919">Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0792__b1079713932015"><span id="cce_10_0792__text161291556477">Logging</span></strong>.</li><li id="cce_10_0792__li10603450121916">Click the <span class="uicontrol" id="cce_10_0792__uicontrol39121833193820"><b>Kubernetes Audit Logs</b></span> tab.</li><li id="cce_10_0792__li1696341572112">Disable the audit component and click <span><img id="cce_10_0792__image1126525920146" src="en-us_image_0000002218660366.png"></span>.<div class="note" id="cce_10_0792__note76261859132113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0792__p17627059162114">After you disable audit logging, logs are no longer written to the original log stream, but the existing logs will not be deleted and expenditures may be incurred for this.</p>
 </div></div>
 </li></ol>
 </div>
diff --git a/docs/cce/umn/cce_10_0809.html b/docs/cce/umn/cce_10_0809.html
index 44d104cd9..1859423f4 100644
--- a/docs/cce/umn/cce_10_0809.html
+++ b/docs/cce/umn/cce_10_0809.html
@@ -9,8 +9,8 @@
 <p id="cce_10_0809__p521703113532"></p>
 <p id="cce_10_0809__p433984175319"><strong id="cce_10_0809__b18399205610525">Disabling log collection for control plane components</strong></p>
 <p id="cce_10_0809__p174109935514">Choose <strong id="cce_10_0809__b1036841015418">Logging</strong> &gt; <strong id="cce_10_0809__b18402272549">Control Plane Logs</strong> and deselect one or more components whose logs do not need to be collected.</p>
-<p id="cce_10_0809__p10155246105511"><strong id="cce_10_0809__b14521940471">Disabling <span id="cce_10_0809__ph6521040974">Kubernetes audit log</span> collection</strong></p>
-<p id="cce_10_0809__p1783671625613">Choose <span id="cce_10_0809__ph14105125016244"><strong id="cce_10_0809__b71051050112414">Logging</strong> &gt; <strong id="cce_10_0809__b61051950142413">Kubernetes Audit Logs</strong></span> and deselect the component whose logs do not need to be collected.</p>
+<p id="cce_10_0809__p10155246105511"><strong id="cce_10_0809__b14521940471">Disabling <span id="cce_10_0809__ph127879615124">Kubernetes audit log</span> collection</strong></p>
+<p id="cce_10_0809__p1783671625613">Choose <span id="cce_10_0809__ph1142692911101"><strong id="cce_10_0809__b71051050112414">Logging</strong> &gt; <strong id="cce_10_0809__b61051950142413">Kubernetes Audit Logs</strong></span> and deselect the component whose logs do not need to be collected.</p>
 </div>
 <div class="section" id="cce_10_0809__section4325193116367"><a name="cce_10_0809__section4325193116367"></a><a name="section4325193116367"></a><h4 class="sectiontitle">What Can I Do If All Components Except log-operator Are Not Ready?</h4><p id="cce_10_0809__p78701837173415"><strong id="cce_10_0809__b96601129203015">Symptom</strong>: All components except log-operator are not ready, and the volume failed to be mounted to the node.</p>
 <p id="cce_10_0809__p16325163113363"><strong id="cce_10_0809__b1032553119366">Solution</strong>: Check the logs of log-operator. During add-on installation, the configuration files required by other components are generated by log-operator. If the configuration files are invalid, all components cannot be started.</p>
diff --git a/docs/cce/umn/cce_10_0836.html b/docs/cce/umn/cce_10_0836.html
index d3b701542..c25bd5115 100644
--- a/docs/cce/umn/cce_10_0836.html
+++ b/docs/cce/umn/cce_10_0836.html
@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Monitoring</h1>
 <div id="body0000001795451700"><p id="cce_10_0836__p1681814431898">CCE monitors applications and resources and collects metrics and events to analyze application health status. You can choose <strong id="cce_10_0836__b879320616568">Settings</strong> from the navigation pane, click the <strong id="cce_10_0836__b67451215567">Monitoring</strong> tab, and change monitoring parameters on the console.</p>
 <div class="section" id="cce_10_0836__section143206310413"><h4 class="sectiontitle">Log Configuration</h4><p id="cce_10_0836__p158281751164115"><strong id="cce_10_0836__b1638710420589">Collection configuration</strong></p>
-<p id="cce_10_0836__p1719215402054"><strong id="cce_10_0836__b1606710231">Send stdout Logs to AOM 1.0</strong> (<strong id="cce_10_0836__b46057142310">No more evolution</strong>): Logging in AOM 1.0 has not been improved, so you are advised to disable this function and use LTS logging instead. </p>
+<p id="cce_10_0836__p1719215402054"><strong id="cce_10_0836__b228520922414">Send stdout Logs to AOM 1.0</strong> (<strong id="cce_10_0836__b1285169102413">No more evolution</strong>): Logging in AOM 1.0 has not been improved, so you are advised to disable this function and use LTS logging instead. </p>
 </div>
 </div>
 <div>
diff --git a/docs/cce/umn/cce_10_0842.html b/docs/cce/umn/cce_10_0842.html
index ea6e035aa..cb78e3972 100644
--- a/docs/cce/umn/cce_10_0842.html
+++ b/docs/cce/umn/cce_10_0842.html
@@ -11,7 +11,7 @@
 <div class="section" id="cce_10_0842__section112955584"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0842__ol11182813184815"><li id="cce_10_0842__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0842__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0842__b119360049953444"><span id="cce_10_0842__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0842__uicontrol160898021553444"><b>Create Service</b></span>.</span></li><li id="cce_10_0842__li185190567138"><span>Configure Service parameters. In this example, only mandatory parameters are listed. For details about how to configure other parameters, see <a href="cce_10_0681.html#cce_10_0681__section84162025538">Using the Console</a>.</span><p><ul id="cce_10_0842__ul4446314017144"><li id="cce_10_0842__li6462394317144"><strong id="cce_10_0842__b114677863842449">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0842__li89543531070"><strong id="cce_10_0842__b190685509043029">Service Type</strong>: Select <strong id="cce_10_0842__b105165345543029">LoadBalancer</strong>.</li><li id="cce_10_0842__li43200017144"><strong id="cce_10_0842__b12655684945393">Selector</strong>: Add a label and click <strong id="cce_10_0842__b1390317105393">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0842__b212286449353948">Reference Workload Label</strong> to use the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0842__b25887632553948">OK</strong>.</li><li id="cce_10_0842__li14384123818176"><strong id="cce_10_0842__b103001266141942">Load Balancer</strong>: Select a load balancer type and creation mode.<ul id="cce_10_0842__ul589211413819"><li id="cce_10_0842__li1995101610373"><a name="cce_10_0842__li1995101610373"></a><a name="li1995101610373"></a>A load balancer can be dedicated or shared. To enable HTTP/HTTPS on the listener port of a dedicated load balancer, the type of the load balancer must be <span class="uicontrol" id="cce_10_0842__uicontrol65106158254343"><b>Application (HTTP/HTTPS)</b></span> or <span class="uicontrol" id="cce_10_0842__uicontrol161484302054343"><b>Network (TCP/UDP) &amp; Application (HTTP/HTTPS)</b></span>.</li><li id="cce_10_0842__li13266657143911">This section uses an existing load balancer as an example. For details about the parameters for automatically creating a load balancer, see <a href="cce_10_0681.html#cce_10_0681__table026610571395">Table 1</a>.</li></ul>
 </li><li id="cce_10_0842__li158271501592"><strong id="cce_10_0842__b133787816944219">Ports</strong><ul id="cce_10_0842__ul3499201217144"><li id="cce_10_0842__li4649265917144"><strong id="cce_10_0842__b13964133019298">Protocol</strong>: Select <strong id="cce_10_0842__b19965163020292">TCP</strong>. If you select <strong id="cce_10_0842__b59651830152912">UDP</strong>, HTTP and HTTPS will be unavailable.</li><li id="cce_10_0842__li353122153610"><strong id="cce_10_0842__b69081136355610">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0842__li475042104417"><strong id="cce_10_0842__b98583464761352">Container Port</strong>: listener port of the workload. For example, Nginx uses port 80 by default.</li><li id="cce_10_0842__li8911126175719"><strong id="cce_10_0842__b145662413914">Frontend Protocol</strong>: In this example, HTTPS must be enabled for the Service to use HTTP/2. For a <a href="#cce_10_0842__li1995101610373">dedicated load balancer</a>, to use HTTP/HTTPS, the type of the load balancer must be <strong id="cce_10_0842__b137381731172719">Application (HTTP/HTTPS)</strong>.</li></ul>
 </li><li id="cce_10_0842__li1567510365916"><strong id="cce_10_0842__b176682727844329">Listener</strong><ul id="cce_10_0842__ul38353035910"><li id="cce_10_0842__li187883173610">SSL authentication is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions.<ul id="cce_10_0842__ul1710811473613"><li id="cce_10_0842__li1837443723520"><strong id="cce_10_0842__b64798224451222">One-way authentication</strong>: Only the backend server is authenticated. If you also need to authenticate the identity of the client, select mutual authentication.</li><li id="cce_10_0842__li6964158133615"><strong id="cce_10_0842__b206106925751345">Mutual authentication</strong>: If you want the clients and the load balancer to authenticate each other, select this option. Only authenticated clients will be allowed to access the load balancer.</li></ul>
-</li><li id="cce_10_0842__li1219103263614"><strong id="cce_10_0842__b113863382051439">CA Certificate</strong>: If <strong id="cce_10_0842__b181241949251439">SSL Authentication</strong> is set to <strong id="cce_10_0842__b100887686751439">Mutual authentication</strong>, add a CA certificate to authenticate the client. A CA certificate is issued by a certificate authority (CA) and used to verify the certificate issuer. If HTTPS mutual authentication is required, HTTPS connections can be established only when the client provides a certificate issued by a specific CA.</li><li id="cce_10_0842__li983517014595"><strong id="cce_10_0842__b01886592409">Server Certificate</strong>: Select a server certificate when HTTPS is used. </li><li id="cce_10_0842__li1883511013595"><strong id="cce_10_0842__b500300385103450">SNI</strong>: Add an SNI certificate containing a domain name. </li><li id="cce_10_0842__li6249544109"><strong id="cce_10_0842__b8339195614114">Advanced Options</strong>: Click <strong id="cce_10_0842__b3752223134213">Add custom container network settings</strong> and enable HTTP/2.</li></ul>
+</li><li id="cce_10_0842__li1219103263614"><strong id="cce_10_0842__b113863382051439">CA Certificate</strong>: If <strong id="cce_10_0842__b181241949251439">SSL Authentication</strong> is set to <strong id="cce_10_0842__b100887686751439">Mutual authentication</strong>, add a CA certificate to authenticate the client. A CA certificate is issued by a certificate authority (CA) and used to verify the certificate issuer. If HTTPS mutual authentication is required, HTTPS connections can be established only when the client provides a certificate issued by a specific CA.</li><li id="cce_10_0842__li983517014595"><strong id="cce_10_0842__b01886592409">Server Certificate</strong>: Select a server certificate when HTTPS is used. </li><li id="cce_10_0842__li1883511013595"><strong id="cce_10_0842__b500300385103450">SNI</strong>: Add an SNI certificate containing a domain name. </li><li id="cce_10_0842__li6249544109"><strong id="cce_10_0842__b43271413152711">Advanced Options</strong>: Click <strong id="cce_10_0842__b163276131271">Add advanced options</strong> and enable HTTP/2.</li></ul>
 </li></ul>
 </p></li><li id="cce_10_0842__li179082217613"><span>Click <strong id="cce_10_0842__b19162196385463">OK</strong>.</span></li></ol>
 </div>
diff --git a/docs/cce/umn/cce_10_0919.html b/docs/cce/umn/cce_10_0919.html
index afd95ad4a..5c68b0e73 100644
--- a/docs/cce/umn/cce_10_0919.html
+++ b/docs/cce/umn/cce_10_0919.html
@@ -8,13 +8,13 @@
 </div>
 <div class="section" id="cce_10_0919__section13788070130"><h4 class="sectiontitle">Suggestions</h4><p id="cce_10_0919__p85901311171316">The following provides some suggestions on optimizing the NGINX Ingress Controller add-on in high-traffic scenarios.</p>
 </div>
-<div class="section" id="cce_10_0919__section1190619449153"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Using a High-Performance Node</h4></div><div class="dropdowncontext"><p id="cce_10_0919__p101341159145710">In high-concurrency scenarios, ingresses typically need a large number of CPUs and network connections, so you can select a computing-plus ECS to run the add-on instances.</p>
+<div class="section" id="cce_10_0919__section1190619449153"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Using a High-Performance Node</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_10_0919__p101341159145710">In high-concurrency scenarios, ingresses typically need a large number of CPUs and network connections, so you can select a computing-plus ECS to run the add-on instances.</p>
 <ol id="cce_10_0919__ol1045875261511"><li id="cce_10_0919__li1228914610462"><span>Log in to the CCE console.</span></li><li id="cce_10_0919__li2075471341"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0919__uicontrol188503710912"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0919__b08866371698">Node Pools</strong> tab.</span></li><li id="cce_10_0919__li3387652384"><span>Click <span class="uicontrol" id="cce_10_0919__uicontrol1366674493817"><b>Create Node Pool</b></span> in the upper right corner to create a node pool and add two nodes to the node pool. The node pool can be dedicated for the NGINX Ingress Controller add-on. For details, see <a href="cce_10_0012.html">Creating a Node Pool</a>.</span><p><p id="cce_10_0919__p2346100202">For high-concurrency scenarios, you can select a high-performance ECS such as the general computing-plus c7.8xlarge.2 ECS, with 32 cores, 64 GiB of memory, a maximum bandwidth of 30 Gbit/s, and 5.5 million PPS.</p>
 </p></li><li id="cce_10_0919__li1458155219151"><span>In the <strong id="cce_10_0919__b7880154073513">Advanced Settings</strong> area, configure labels and taints for the node pool.</span><p><ul id="cce_10_0919__ul1857971314911"><li id="cce_10_0919__li1057981374915">Configure a taint and set its key to <strong id="cce_10_0919__b1847718437381">nginx-ingress-pod-reserved</strong>, value to <strong id="cce_10_0919__b33281225391">true</strong>, and the effect to <strong id="cce_10_0919__b11959144410391">NoExecute</strong>.</li><li id="cce_10_0919__li95793133498">Configure a label and set its key to <strong id="cce_10_0919__b1568634112401">nginx-ingress-pod-reserved</strong> and value to <strong id="cce_10_0919__b592619497407">true</strong>.</li></ul>
 </p></li><li id="cce_10_0919__li101971215135016"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0919__uicontrol1619816150505"><b>Add-ons</b></span>, edit the configurations of NGINX Ingress Controller, and modify the scheduling policies.</span><p><ul id="cce_10_0919__ul1646982010508"><li id="cce_10_0919__li146371464501"><strong id="cce_10_0919__b1020023119435">Node Affinity</strong>: Set it to <strong id="cce_10_0919__b341104104415">Customize affinity</strong> and configure the add-on to be affinity for the <strong id="cce_10_0919__b5883101616451">nginx-ingress-pod-reserved: true</strong> label.</li><li id="cce_10_0919__li10469162005020"><strong id="cce_10_0919__b69282054164512">Toleration</strong>: Add a toleration and configure the add-on to tolerate the taint whose label is <strong id="cce_10_0919__b156321154194613">nginx-ingress-pod-reserved: true</strong> and the taint policy is <strong id="cce_10_0919__b10920165104816">NoExecute</strong>.</li></ul>
 </p></li></ol>
 </div></div></div>
-<div class="section" id="cce_10_0919__section20100134816178"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Modifying the NGINX Ingress Controller Configuration</h4></div><div class="dropdowncontext"><div class="p" id="cce_10_0919__p12207165619594">You can perform the following operations when installing or editing NGINX Ingress Controller:<ul id="cce_10_0919__ul6536735151815"><li id="cce_10_0919__li16238172214140">Change the resource limit of the <strong id="cce_10_0919__b77811456115416">nginx-ingress-controller</strong> container. If an application processes HTTP requests with a PRS of 300,000, you can configure the CPU and memory limits, as well as the requested CPU and memory, to 16 vCPU cores and 20 GiB of memory.</li><li id="cce_10_0919__li2037111271815">Set the number of pods to be greater than or equal to 2.</li></ul>
+<div class="section" id="cce_10_0919__section20100134816178"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Modifying the NGINX Ingress Controller Configuration</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><div class="p" id="cce_10_0919__p12207165619594">You can perform the following operations when installing or editing NGINX Ingress Controller:<ul id="cce_10_0919__ul6536735151815"><li id="cce_10_0919__li16238172214140">Change the resource limit of the <strong id="cce_10_0919__b77811456115416">nginx-ingress-controller</strong> container. If an application processes HTTP requests with a PRS of 300,000, you can configure the CPU and memory limits, as well as the requested CPU and memory, to 16 vCPU cores and 20 GiB of memory.</li><li id="cce_10_0919__li2037111271815">Set the number of pods to be greater than or equal to 2.</li></ul>
 </div>
 <ul id="cce_10_0919__ul14376128189"><li id="cce_10_0919__li156113331186">Disable the metric collection of the add-on.<p id="cce_10_0919__p142435405181"><a name="cce_10_0919__li156113331186"></a><a name="li156113331186"></a>If you do not need to obtain metrics, you are advised to disable metric collection to reduce the CPU and memory usage of the Nginx container.</p>
 </li><li id="cce_10_0919__li179625475185">Optimize the global configuration by doing as follows:<ul id="cce_10_0919__ul1533362513191"><li id="cce_10_0919__li1672954415103"><strong id="cce_10_0919__b12729744101018">Increase the maximum number of requests that a keepalive connection can handle.</strong><p id="cce_10_0919__p1625013451101">Nginx provides the <strong id="cce_10_0919__b5648634887">keepalive_requests</strong> parameter to control how many requests a single keepalive connection between a client and an upstream server can handle. This parameter defaults to 100.</p>
@@ -31,7 +31,7 @@
 </li></ul>
 </li></ul>
 </div></div></div>
-<div class="section" id="cce_10_0919__section037393643618"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Optimizing Nginx Kernel Parameters</h4></div><div class="dropdowncontext"><div class="caution" id="cce_10_0919__note1570612618387"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="cce_10_0919__p1719777193818">Before modifying a kernel parameter, it is important to have a full understanding of its meaning and function. Exercise caution when making changes, because incorrect settings can lead to unexpected system errors and instability.</p>
+<div class="section" id="cce_10_0919__section037393643618"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Optimizing Nginx Kernel Parameters</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><div class="caution" id="cce_10_0919__note1570612618387"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="cce_10_0919__p1719777193818">Before modifying a kernel parameter, it is important to have a full understanding of its meaning and function. Exercise caution when making changes, because incorrect settings can lead to unexpected system errors and instability.</p>
 <p id="cce_10_0919__p181971714381">You need to make sure that:</p>
 <ol id="cce_10_0919__ol141971712385"><li id="cce_10_0919__li18197187173818">You have fully understood the functions and impacts of kernel parameters. This helps you set kernel parameters correctly.</li><li id="cce_10_0919__li419757183817">The parameter values you entered must be valid and meet the expectation, or the modification will not take effect.</li></ol>
 </div></div>
diff --git a/docs/cce/umn/cce_10_0945.html b/docs/cce/umn/cce_10_0945.html
index 8d29aa470..e512e5243 100644
--- a/docs/cce/umn/cce_10_0945.html
+++ b/docs/cce/umn/cce_10_0945.html
@@ -40,7 +40,7 @@
 </tr>
 <tr id="cce_10_0945__row783164219368"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.3.1.3.1.1 "><p id="cce_10_0945__p6436174417360">Bandwidth</p>
 </td>
-<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.3.1.3.1.2 "><p id="cce_10_0945__p716417591111">After DataPlane V2 network acceleration is enabled, pods on HCE OS 2.0 use EDT to limit the egress bandwidth. The ingress bandwidth limitation is not supported. In other network modes, a TBF qdisc is used to limit the bandwidth. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</p>
+<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.3.1.3.1.2 "><p id="cce_10_0945__p716417591111">After DataPlane V2 network acceleration is enabled, pods on the nodes running HCE OS 2.0 use EDT to limit the egress bandwidth. The ingress bandwidth limitation is not supported. In other network modes, a TBF qdisc is used to limit the bandwidth. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</p>
 </td>
 </tr>
 <tr id="cce_10_0945__row762764213612"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.3.1.3.1.1 "><p id="cce_10_0945__p5436244113616">NetworkPolicy</p>
diff --git a/docs/cce/umn/cce_10_0949.html b/docs/cce/umn/cce_10_0949.html
index e032210b7..e1fd1979b 100644
--- a/docs/cce/umn/cce_10_0949.html
+++ b/docs/cce/umn/cce_10_0949.html
@@ -72,7 +72,7 @@
 </tbody>
 </table>
 </div>
-<div class="note" id="cce_10_0949__note41721640154412"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0949__p88932312274">CCE allows you to configure and traffic limit on requests, based on ELB's <span id="cce_10_0949__ph124386479552">advanced forwarding</span> for LoadBalancer ingresses. These functions are coming soon. To use some advanced forwarding actions that are not available on the console yet, submit a <span id="cce_10_0949__ph1659161265618">service ticket</span> to enable required functions.</p>
+<div class="note" id="cce_10_0949__note41721640154412"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0949__p88932312274">CCE allows you to configure and traffic limit on requests, based on ELB's <span id="cce_10_0949__ph19898155510416">advanced forwarding</span> for LoadBalancer ingresses. These functions are coming soon. To use some advanced forwarding actions that are not available on the console yet, submit a <span id="cce_10_0949__ph1659161265618">service ticket</span> to enable required functions.</p>
 </div></div>
 <div class="section" id="cce_10_0949__section1217816043419"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0949__ul11453637191613"><li id="cce_10_0949__li1193592633115">A CCE standard or Turbo cluster is available, and the cluster version meets the requirements.</li><li id="cce_10_0949__li2045311379169">The cluster can be accessed using kubectl. For details, see <a href="cce_10_0107.html">Accessing a Cluster Using kubectl</a>.</li></ul>
 </div>
@@ -283,7 +283,7 @@ ingress-test  cce      *         121.**.**.**     80      10s</pre>
 </div>
 <div class="section" id="cce_10_0949__section8498141262"><a name="cce_10_0949__section8498141262"></a><a name="section8498141262"></a><h4 class="sectiontitle">Configuring a Custom Backend Server Group for a LoadBalancer Ingress</h4><div class="notice" id="cce_10_0949__note1446114217202"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0949__ul1505174319209"><li id="cce_10_0949__li1160712151115">Configuring a custom backend server group for a LoadBalancer ingress is subject to the capabilities of your ELB service. Before using this feature, submit a service ticket to enable the required ELB capabilities.</li><li id="cce_10_0949__li1950604322011">Custom backend server groups cannot be used for grayscale release or fixed responses.</li><li id="cce_10_0949__li1050654316204">If you configure a custom backend server group for a LoadBalancer ingress, the <strong id="cce_10_0949__b1793384312490">number</strong> field for the backend Services of the ingress will be invalid and the port name must be set to <strong id="cce_10_0949__b1529512715014">use-annotation</strong>. For details, see the example provided in this section.</li><li id="cce_10_0949__li1950664317203">When configuring a custom backend server group for a LoadBalancer ingress, ensure that each Service name and backend server group ID are unique.</li></ul>
 </div></div>
-<ol id="cce_10_0949__ol16498348614"><li id="cce_10_0949__li114981941166"><span>Use kubectl to access the cluster. For details, see <a href="cce_10_0107.html">Accessing a Cluster Using kubectl</a>.</span></li><li id="cce_10_0949__li8499846616"><span>Create a YAML file named <strong id="cce_10_0949__b2001757089">ingress-test.yaml</strong>. The file name can be customized.</span><p><pre class="screen" id="cce_10_0949__screen10499184261">vi ingress-test.yaml</pre>
+<ol id="cce_10_0949__ol16498348614"><li id="cce_10_0949__li114981941166"><span>Use kubectl to access the cluster. For details, see <a href="cce_10_0107.html">Accessing a Cluster Using kubectl</a>.</span></li><li id="cce_10_0949__li8499846616"><span>Create a YAML file named <strong id="cce_10_0949__b1818190940">ingress-test.yaml</strong>. The file name can be customized.</span><p><pre class="screen" id="cce_10_0949__screen10499184261">vi ingress-test.yaml</pre>
 <div class="p" id="cce_10_0949__p64998417613">An example YAML file of an ingress created using an existing load balancer is as follows:<pre class="screen" id="cce_10_0949__screen0499041763">apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
diff --git a/docs/cce/umn/cce_10_0957.html b/docs/cce/umn/cce_10_0957.html
deleted file mode 100644
index 294e12f50..000000000
--- a/docs/cce/umn/cce_10_0957.html
+++ /dev/null
@@ -1,118 +0,0 @@
-<a name="cce_10_0957"></a><a name="cce_10_0957"></a>
-
-<h1 class="topictitle1">Using the AccessPolicy API to Manage Namespace Permissions (Kubernetes RBAC-based)</h1>
-<div id="body0000002146697640"><div class="section" id="cce_10_0957__section16601203895318"><h4 class="sectiontitle">Prerequisites</h4><ul id="cce_10_0957__ul115321234510"><li id="cce_10_0957__li653512104517">Before assigning permissions to users or user groups, you need to review the information provided in <a href="cce_10_0189.html">Namespace Permissions (Kubernetes RBAC-based)</a>.</li><li id="cce_10_0957__li267771813457">To use an access policy, an IAM user or user group must have the specific permissions. These include CreateAccessPolicy, UpdateAccessPolicy, DeleteAccessPolicy, ListAccessPolicy, and GetAccessPolicy. Learn about the CCE system policies that can be added to a user group and select appropriate ones as needed. For details about how to assign permissions to a user group, see <a href="cce_10_0188.html">Granting Cluster Permissions to an IAM User</a>.</li></ul>
-</div>
-<div class="section" id="cce_10_0957__section634060102919"><h4 class="sectiontitle">Configuring Namespace Permissions Through APIs</h4><p id="cce_10_0957__p94861220192915">You can regulate users' or user groups' access to Kubernetes resources in a single namespace based on their Kubernetes RBAC roles. Users with the configuration permission can configure access policies through APIs.</p>
-<p id="cce_10_0957__p169611733202613"><span><img class="eddx" id="cce_10_0957__image189611033202619" src="en-us_image_0000002218820614.png"></span></p>
-<ol id="cce_10_0957__ol851910234308"><li id="cce_10_0957__li2519122313306"><span>Call the API to create an access policy. </span><p><p id="cce_10_0957__p101241362306"><strong id="cce_10_0957__b137721537153319">POST   /api/v3/access-policies</strong></p>
-<p id="cce_10_0957__p099354112309">Request body:</p>
-<pre class="screen" id="cce_10_0957__screen943775117309">{
-    "kind": "AccessPolicy",
-    "apiVersion": "v3",
-    "name": "policy-test",
-    "clusters": [ "*" ],
-    "accessScope": {
-        "namespaces": [ "ns1", "ns2" ]
-    },
-    "policyType": "CCEAdminPolicy/CCEClusterAdminPolicy/CCEEditPolicy/CCEViewPolicy",
-    "principal": {
-        "type": "user/group/agency",
-        "ids": ["id1", "id2" ]
-    }
-}</pre>
-
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0957__table1629551953116" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0957__row1829620199312"><th align="left" class="cellrowborder" valign="top" width="22.43224322432243%" id="mcps1.3.2.4.1.2.4.1.4.1.1"><p id="cce_10_0957__p194053313118">Parameter</p>
-</th>
-<th align="left" class="cellrowborder" valign="top" width="16.471647164716472%" id="mcps1.3.2.4.1.2.4.1.4.1.2"><p id="cce_10_0957__p1494053353114">Item</p>
-</th>
-<th align="left" class="cellrowborder" valign="top" width="61.09610961096109%" id="mcps1.3.2.4.1.2.4.1.4.1.3"><p id="cce_10_0957__p994013333311">Description</p>
-</th>
-</tr>
-</thead>
-<tbody><tr id="cce_10_0957__row52968193313"><td class="cellrowborder" valign="top" width="22.43224322432243%" headers="mcps1.3.2.4.1.2.4.1.4.1.1 "><p id="cce_10_0957__p1940433193112">name</p>
-</td>
-<td class="cellrowborder" valign="top" width="16.471647164716472%" headers="mcps1.3.2.4.1.2.4.1.4.1.2 "><p id="cce_10_0957__p894093333120">Name</p>
-</td>
-<td class="cellrowborder" valign="top" width="61.09610961096109%" headers="mcps1.3.2.4.1.2.4.1.4.1.3 "><p id="cce_10_0957__p209401133173114">Name of the access policy.</p>
-</td>
-</tr>
-<tr id="cce_10_0957__row162961919143119"><td class="cellrowborder" valign="top" width="22.43224322432243%" headers="mcps1.3.2.4.1.2.4.1.4.1.1 "><p id="cce_10_0957__p109401336317">clusters</p>
-</td>
-<td class="cellrowborder" valign="top" width="16.471647164716472%" headers="mcps1.3.2.4.1.2.4.1.4.1.2 "><p id="cce_10_0957__p1594015335314">Cluster list</p>
-</td>
-<td class="cellrowborder" valign="top" width="61.09610961096109%" headers="mcps1.3.2.4.1.2.4.1.4.1.3 "><p id="cce_10_0957__p894033313319">IDs of the clusters to which access policies are to be added. Wildcard characters (*) are supported.</p>
-</td>
-</tr>
-<tr id="cce_10_0957__row17296919113115"><td class="cellrowborder" valign="top" width="22.43224322432243%" headers="mcps1.3.2.4.1.2.4.1.4.1.1 "><p id="cce_10_0957__p9940173303112">namespaces</p>
-</td>
-<td class="cellrowborder" valign="top" width="16.471647164716472%" headers="mcps1.3.2.4.1.2.4.1.4.1.2 "><p id="cce_10_0957__p1194073343111">Namespaces</p>
-</td>
-<td class="cellrowborder" valign="top" width="61.09610961096109%" headers="mcps1.3.2.4.1.2.4.1.4.1.3 "><p id="cce_10_0957__p694073393119">Namespaces to which access policies are to be added. Wildcard characters (*) are supported.</p>
-</td>
-</tr>
-<tr id="cce_10_0957__row1029613198311"><td class="cellrowborder" valign="top" width="22.43224322432243%" headers="mcps1.3.2.4.1.2.4.1.4.1.1 "><p id="cce_10_0957__p20940103353112">policyType</p>
-</td>
-<td class="cellrowborder" valign="top" width="16.471647164716472%" headers="mcps1.3.2.4.1.2.4.1.4.1.2 "><p id="cce_10_0957__p1794043343118">Permission type</p>
-</td>
-<td class="cellrowborder" valign="top" width="61.09610961096109%" headers="mcps1.3.2.4.1.2.4.1.4.1.3 "><p id="cce_10_0957__p1494073312315">Permission type. Options:</p>
-<ul id="cce_10_0957__ul11647494321"><li id="cce_10_0957__li1164716923219"><strong id="cce_10_0957__b17129141320432">CCEClusterAdminPolicy</strong>: administrator permission</li><li id="cce_10_0957__li17647592321"><strong id="cce_10_0957__b9862530431">CCEAdminPolicy</strong>: O&amp;M permission</li><li id="cce_10_0957__li26471798321"><strong id="cce_10_0957__b1911017624417">CCEEditPolicy</strong>: developer permission</li><li id="cce_10_0957__li264710963214"><strong id="cce_10_0957__b1969443114412">CCEViewPolicy</strong>: read-only permission</li></ul>
-</td>
-</tr>
-<tr id="cce_10_0957__row13459931163110"><td class="cellrowborder" valign="top" width="22.43224322432243%" headers="mcps1.3.2.4.1.2.4.1.4.1.1 "><p id="cce_10_0957__p20941143393111">principalType</p>
-</td>
-<td class="cellrowborder" valign="top" width="16.471647164716472%" headers="mcps1.3.2.4.1.2.4.1.4.1.2 "><p id="cce_10_0957__p59411333193112">User or user group type</p>
-</td>
-<td class="cellrowborder" valign="top" width="61.09610961096109%" headers="mcps1.3.2.4.1.2.4.1.4.1.3 "><p id="cce_10_0957__p6941123323114">Type of a user or user group. Options:</p>
-<ul id="cce_10_0957__ul3124111417332"><li id="cce_10_0957__li012451412336"><strong id="cce_10_0957__b1887201918315">user</strong>: user</li><li id="cce_10_0957__li121241114143311"><strong id="cce_10_0957__b11393181816319">group</strong>: user group</li><li id="cce_10_0957__li17124614203318"><strong id="cce_10_0957__b315622016451">agency</strong>: agency account</li></ul>
-</td>
-</tr>
-<tr id="cce_10_0957__row151683213313"><td class="cellrowborder" valign="top" width="22.43224322432243%" headers="mcps1.3.2.4.1.2.4.1.4.1.1 "><p id="cce_10_0957__p6941143373114">principalId</p>
-</td>
-<td class="cellrowborder" valign="top" width="16.471647164716472%" headers="mcps1.3.2.4.1.2.4.1.4.1.2 "><p id="cce_10_0957__p794183373116">User or user group list</p>
-</td>
-<td class="cellrowborder" valign="top" width="61.09610961096109%" headers="mcps1.3.2.4.1.2.4.1.4.1.3 "><p id="cce_10_0957__p494183312318">IDs of the users or user groups to be authorized.</p>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-</p></li><li id="cce_10_0957__li198814073614"><span>The CCE management plane automatically synchronizes the access policies to the associated cluster. Run the <strong id="cce_10_0957__b170813492469">kubectl</strong> command. Then, RoleBinding or ClusterRoleBinding will be created in the cluster.</span><p><div class="note" id="cce_10_0957__note130681173911"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0957__p16867726393">The synchronization will take several minutes to take effect.</p>
-</div></div>
-<ol type="a" id="cce_10_0957__ol279161516371"><li id="cce_10_0957__li979131511378">Check RoleBinding in the cluster.<pre class="screen" id="cce_10_0957__screen1925712599364">kubectl get rolebinding</pre>
-<p id="cce_10_0957__p19294185610365">In the following command output, <strong id="cce_10_0957__b1855733616487">clusterrole_access_policy_069fcc2116c347b89869eae3cd38ba23</strong> is the automatically created RoleBinding:</p>
-<pre class="screen" id="cce_10_0957__screen2718103717363">NAME                                                         ROLE                AGE
-clusterrole_access_policy_069fcc2116c347b89869eae3cd38ba23   ClusterRole/admin   18s</pre>
-</li><li id="cce_10_0957__li087810492377">Check RoleBinding details.<pre class="screen" id="cce_10_0957__screen1249037143811">kubectl get rolebinding <i><span class="varname" id="cce_10_0957__varname019731613382">clusterrole_access_policy_069fcc2116c347b89869eae3cd38ba23</span></i> -oyaml</pre>
-<p id="cce_10_0957__p4180145973716">Command output:</p>
-<pre class="screen" id="cce_10_0957__screen1487184211375">apiVersion: rbac.authorization.k8s.io/v1
-kind: RoleBinding
-metadata:
-  annotations:
-CCE.com/IAM: "true"
-  label:
-rbac.kubernetes.io/GeneratedByAccessPolicy: "true"
-  creationTimestamp: "2021-06-24T01:30:08Z"
-  name: clusterrole_admin_group0c96fad22880f32a3f84c009862af6f7
-  resourceVersion: "36963685"
-  selfLink: /apis/rbac.authorization.k8s.io/v1/namespaces/default/rolebindings/clusterrole_admin_group0c96fad22880f32a3f84c009862af6f7
-  uid: 6c6f46a6-8584-47da-83f5-9eef1f7b75d6
-roleRef:
-  apiGroup: rbac.authorization.k8s.io
-  kind: ClusterRole
-  name: admin
-subjects:
-- apiGroup: rbac.authorization.k8s.io
-  kind: Group
-  name: 0c96fad22880f32a3f84c009862af6f7</pre>
-</li></ol>
-</p></li><li id="cce_10_0957__li1073044210391"><span>Log in to the CCE console as the newly authorized IAM user for verification. </span><p><p id="cce_10_0957__p11104202014412">In the service list, choose <strong id="cce_10_0957__b1396563916499">Cloud Container Engine</strong>. On the CCE console, access the cluster and choose the target namespace. If only the <strong id="cce_10_0957__b06911219519">default</strong> namespace is authorized and the <strong id="cce_10_0957__b394024105012">kube-system</strong> namespace is unavailable, the access policy has taken effect.</p>
-</p></li></ol>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0164.html">Permissions</a></div>
-</div>
-</div>
-
diff --git a/docs/cce/umn/cce_10_0967.html b/docs/cce/umn/cce_10_0967.html
index 22fbe3d94..e3f8f5c70 100644
--- a/docs/cce/umn/cce_10_0967.html
+++ b/docs/cce/umn/cce_10_0967.html
@@ -44,7 +44,7 @@
 </div>
 <div class="section" id="cce_10_0967__en-us_topic_0000002251898545_section1221141473"><h4 class="sectiontitle">Step 3: Verify that the Custom Scale-in Conditions Take Effect</h4><p id="cce_10_0967__en-us_topic_0000002251898545_p19987141217814">In this example, the custom scale-in threshold is set to 30% for the node pool, while the default scale-in threshold is 50%. If the node CPU and memory in the node pool remains between 30% and 50% and scale-in is not triggered, the node pool preferentially follows the custom scale-in conditions instead of the default scale-in conditions.</p>
 </div>
-<div class="section" id="cce_10_0967__en-us_topic_0000002251898545_section2050292719420"><h4 class="sectiontitle">Related Operations</h4><ul id="cce_10_0967__en-us_topic_0000002251898545_ul385154012422"><li id="cce_10_0967__en-us_topic_0000002251898545_li68515408426">For details about the CCE Cluster Autoscaler add-on, see <a href="cce_10_0193.html">CCE Cluster Autoscaler</a>.</li><li id="cce_10_0967__en-us_topic_0000002251898545_li11384507437">For details about the steps of how to create an auto scaling policy and the parameters, see <a href="cce_10_0209.html">Creating a Node Scaling Policy</a>.</li></ul>
+<div class="section" id="cce_10_0967__en-us_topic_0000002251898545_section2050292719420"><h4 class="sectiontitle">Helpful Links</h4><ul id="cce_10_0967__en-us_topic_0000002251898545_ul385154012422"><li id="cce_10_0967__en-us_topic_0000002251898545_li68515408426">For details about the CCE Cluster Autoscaler add-on, see <a href="cce_10_0193.html">CCE Cluster Autoscaler</a>.</li><li id="cce_10_0967__en-us_topic_0000002251898545_li11384507437">For details about the steps of how to create an auto scaling policy and the parameters, see <a href="cce_10_0209.html">Creating a Node Scaling Policy</a>.</li></ul>
 </div>
 </div>
 <div>
diff --git a/docs/cce/umn/cce_10_0968.html b/docs/cce/umn/cce_10_0968.html
index de99fad12..39c3248b5 100644
--- a/docs/cce/umn/cce_10_0968.html
+++ b/docs/cce/umn/cce_10_0968.html
@@ -5,8 +5,8 @@
 <p id="cce_10_0968__en-us_topic_0000002227814252_p196591042153713">Before upgrading the NGINX Ingress Controller, pay attention to the following compatibility issues identified by CCE:</p>
 <ul id="cce_10_0968__en-us_topic_0000002227814252_ul12929183312239"><li id="cce_10_0968__en-us_topic_0000002227814252_li1092916337236"><a href="#cce_10_0968__en-us_topic_0000002227814252_section6945154553715">Native Nginx Validity Check Disabled by Default</a></li><li id="cce_10_0968__en-us_topic_0000002227814252_li15677155372318"><a href="#cce_10_0968__en-us_topic_0000002227814252_section11701729145314">Snippet Annotations Disabled by Default</a></li><li id="cce_10_0968__en-us_topic_0000002227814252_li03071857182311"><a href="#cce_10_0968__en-us_topic_0000002227814252_section02315551454">Earlier TLS Versions Not Supported</a></li><li id="cce_10_0968__en-us_topic_0000002227814252_li8748057152312"><a href="#cce_10_0968__en-us_topic_0000002227814252_section8367415152019">Nginx Native root and alias Directives Not Supported</a></li><li id="cce_10_0968__en-us_topic_0000002227814252_li8272058172318"><a href="#cce_10_0968__en-us_topic_0000002227814252_section810118942211">Graceful Upgrades Supported by NGINX Ingress Controller</a></li></ul>
 </div>
-<div class="section" id="cce_10_0968__en-us_topic_0000002227814252_section6945154553715"><a name="cce_10_0968__en-us_topic_0000002227814252_section6945154553715"></a><a name="en-us_topic_0000002227814252_section6945154553715"></a><h4 class="sectiontitle">Native Nginx Validity Check Disabled by Default</h4><p id="cce_10_0968__en-us_topic_0000002227814252_p562718503917"><strong id="cce_10_0968__en-us_topic_0000002227814252_b169811104393">Affected versions: earlier than 3.0.33</strong></p>
-<p id="cce_10_0968__en-us_topic_0000002227814252_p3425326113910">The NGINX Ingress Controller v3.0.33 corresponds to community version <a href="https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.11.5" target="_blank" rel="noopener noreferrer">v1.11.5</a>. In this community version, the security vulnerability <strong id="cce_10_0968__en-us_topic_0000002227814252_b642514264397">CVE-2025-1974</strong> has been fixed, and <i><span class="varname" id="cce_10_0968__en-us_topic_0000002227814252_varname255571755211">nginx -t</span></i> (syntax check) has been removed from webhooks. In the community version <a href="https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.11.5" target="_blank" rel="noopener noreferrer">v1.11.5</a>, the format of ingress resources is still verified using admission webhooks. However, if you enable snippet annotations and the configuration contains syntax errors, invalid configurations may be directly injected into the <strong id="cce_10_0968__en-us_topic_0000002227814252_b108725994011">nginx.conf</strong> file. Since there is no pre-check to validate the injected configuration, such errors may cause the Nginx configuration reload to fail. Therefore, if you enable snippet annotations, check NGINX Ingress Controller's pod logs for errors each time you modify the ingress rules. To do so, run the following command:</p>
+<div class="section" id="cce_10_0968__en-us_topic_0000002227814252_section6945154553715"><a name="cce_10_0968__en-us_topic_0000002227814252_section6945154553715"></a><a name="en-us_topic_0000002227814252_section6945154553715"></a><h4 class="sectiontitle">Native Nginx Validity Check Disabled by Default</h4><p id="cce_10_0968__en-us_topic_0000002227814252_p562718503917"><strong id="cce_10_0968__en-us_topic_0000002227814252_b169811104393">Affected versions: earlier than 3.0.34</strong></p>
+<p id="cce_10_0968__en-us_topic_0000002227814252_p3425326113910">The NGINX Ingress Controller v3.0.34 corresponds to community version <a href="https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.11.5" target="_blank" rel="noopener noreferrer">v1.11.5</a>. In this community version, the security vulnerability <strong id="cce_10_0968__en-us_topic_0000002227814252_b642514264397">CVE-2025-1974</strong> has been fixed, and <i><span class="varname" id="cce_10_0968__en-us_topic_0000002227814252_varname255571755211">nginx -t</span></i> (syntax check) has been removed from webhooks. In the community version <a href="https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.11.5" target="_blank" rel="noopener noreferrer">v1.11.5</a>, the format of ingress resources is still verified using admission webhooks. However, if you enable snippet annotations and the configuration contains syntax errors, invalid configurations may be directly injected into the <strong id="cce_10_0968__en-us_topic_0000002227814252_b108725994011">nginx.conf</strong> file. Since there is no pre-check to validate the injected configuration, such errors may cause the Nginx configuration reload to fail. Therefore, if you enable snippet annotations, check NGINX Ingress Controller's pod logs for errors each time you modify the ingress rules. To do so, run the following command:</p>
 <pre class="screen" id="cce_10_0968__en-us_topic_0000002227814252_screen430414418451">kubectl logs -f <i><span class="varname" id="cce_10_0968__en-us_topic_0000002227814252_varname102017624616">{nginx-ingress-controller-pod-name}</span></i> -n kube-system | grep Error</pre>
 </div>
 <div class="section" id="cce_10_0968__en-us_topic_0000002227814252_section11701729145314"><a name="cce_10_0968__en-us_topic_0000002227814252_section11701729145314"></a><a name="en-us_topic_0000002227814252_section11701729145314"></a><h4 class="sectiontitle">Snippet Annotations Disabled by Default</h4><p id="cce_10_0968__en-us_topic_0000002227814252_p1870114195315"><strong id="cce_10_0968__en-us_topic_0000002227814252_b107621247155310">Affected versions: earlier than 2.4.6</strong></p>
diff --git a/docs/cce/umn/cce_bestpractice_00199.html b/docs/cce/umn/cce_bestpractice_00199.html
index 880a38fdb..8ff20a417 100644
--- a/docs/cce/umn/cce_bestpractice_00199.html
+++ b/docs/cce/umn/cce_bestpractice_00199.html
@@ -228,7 +228,7 @@ spec:
 </thead>
 <tbody><tr id="cce_bestpractice_00199__row584975914233"><td class="cellrowborder" valign="top" width="14.74%" headers="mcps1.3.5.3.3.2.6.2.4.1.1 "><p id="cce_bestpractice_00199__p188491159172312">mountOptions.default_acl</p>
 </td>
-<td class="cellrowborder" valign="top" width="58.77%" headers="mcps1.3.5.3.3.2.6.2.4.1.2 "><p id="cce_bestpractice_00199__p1784914596232">Specify access control policies for a bucket and objects in the bucket. In this example, account A owns the bucket, and both account A and account B have the ability to upload data.</p>
+<td class="cellrowborder" valign="top" width="58.77%" headers="mcps1.3.5.3.3.2.6.2.4.1.2 "><p id="cce_bestpractice_00199__p1784914596232">Specify access control policies for a bucket and objects in the bucket. In this example, account A owns the bucket, and both account A and account B can upload data.</p>
 <ul id="cce_bestpractice_00199__ul48221749172616"><li id="cce_bestpractice_00199__li6822749132614"><strong id="cce_bestpractice_00199__b16329136193415">private</strong>: The bucket or objects can only be fully accessed by the owner of the bucket.</li><li id="cce_bestpractice_00199__li12731194277"><strong id="cce_bestpractice_00199__b167311246163413">public-read</strong>: The owner of the bucket has complete control over both the bucket and its objects. While other users can read data from the bucket, they are unable to modify, delete, or upload any data within it.</li><li id="cce_bestpractice_00199__li1545214355273"><strong id="cce_bestpractice_00199__b10818356123511">public-read-write</strong>: The owner of the bucket has complete control over the bucket and its objects. Other users can read and write data from and to the bucket.</li><li id="cce_bestpractice_00199__li14837939123011"><strong id="cce_bestpractice_00199__b2436121915379">bucket-owner-read</strong>: Users who have uploaded objects to the bucket has complete control over the objects, while the bucket owner is only granted read permissions for said objects. <strong id="cce_bestpractice_00199__b1483718395305">This mode is usually used in cross-account sharing scenarios</strong>.</li><li id="cce_bestpractice_00199__li11439171295"><strong id="cce_bestpractice_00199__b1256393183918">bucket-owner-full-control</strong>: Users who have uploaded objects to the bucket are granted write permissions for those specific objects, but not read permissions by default. The bucket owner has complete control over all objects within the bucket. <strong id="cce_bestpractice_00199__b16113223413">This mode is usually used in cross-account sharing scenarios.</strong></li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="26.490000000000002%" headers="mcps1.3.5.3.3.2.6.2.4.1.3 "><p id="cce_bestpractice_00199__p18849175962315">bucket-owner-full-control</p>
@@ -416,7 +416,7 @@ obs-deployment-example-6b4dfd7b57-frfxv   1/1     Running             0
 </td>
 <td class="cellrowborder" valign="top" width="63.470000000000006%" headers="mcps1.3.8.3.2.4.1.3 "><ol id="cce_bestpractice_00199__ol19891536559"><li id="cce_bestpractice_00199__li6989103612511">Check whether the ConfigMap is present.<pre class="screen" id="cce_bestpractice_00199__screen9989436156">kubectl get configmap -n kube-system</pre>
 <p id="cce_bestpractice_00199__p7989153616516">If it is present, the ConfigMap may be incorrectly configured. If it is not present, you can create one by referring to <a href="#cce_bestpractice_00199__li840004701911">1</a>.</p>
-</li><li id="cce_bestpractice_00199__li1398911361453">Check the ConfigMap parameter configurations. The following shows the common issues:<ul id="cce_bestpractice_00199__ul1698915361856"><li id="cce_bestpractice_00199__li39899367520">The <strong id="cce_bestpractice_00199__b2662287418">name</strong> parameter is not set to <strong id="cce_bestpractice_00199__b9861121094110">paas-obs-endpoint</strong>.</li><li id="cce_bestpractice_00199__li398911361156">The <strong id="cce_bestpractice_00199__b1033142054118">namespace</strong> parameter is not set to <strong id="cce_bestpractice_00199__b641223384112">kube-system</strong>.</li><li id="cce_bestpractice_00199__li20923720197">The region name is not set to the region where the OBS bucket is located.</li></ul>
+</li><li id="cce_bestpractice_00199__li1398911361453">Check the ConfigMap parameter configurations. The following shows the common issues:<ul id="cce_bestpractice_00199__ul1698915361856"><li id="cce_bestpractice_00199__li39899367520">The <strong id="cce_bestpractice_00199__b2662287418">name</strong> parameter is not set to <strong id="cce_bestpractice_00199__b9861121094110">paas-obs-endpoint</strong>.</li><li id="cce_bestpractice_00199__li398911361156">The <strong id="cce_bestpractice_00199__b17153131718361">namespace</strong> parameter is not set to <strong id="cce_bestpractice_00199__b1815391720366">kube-system</strong>.</li><li id="cce_bestpractice_00199__li20923720197">The region name is not set to the region where the OBS bucket is located.</li></ul>
 </li></ol>
 </td>
 </tr>
diff --git a/docs/cce/umn/cce_bestpractice_00227.html b/docs/cce/umn/cce_bestpractice_00227.html
index 4f6d021a0..58e138418 100644
--- a/docs/cce/umn/cce_bestpractice_00227.html
+++ b/docs/cce/umn/cce_bestpractice_00227.html
@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Modifying Kernel Parameters Using a Privileged Container</h1>
 <div id="body8662426"><div class="section" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_section136132011171713"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p44821585237">To access a Kubernetes cluster from a client, you can use the Kubernetes command line tool kubectl. </p>
 </div>
-<div class="section" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_section195893610174"><h4 class="sectiontitle">Procedure</h4><ol id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_ol8890756191816"><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li38911568185"><span>Create a DaemonSet in the background, select the Nginx image, enable the Privileged Container, configure the lifecycle, and add the <span class="parmname" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_parmname42281654101420"><b>hostNetwork</b></span> field (value: <span class="parmvalue" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_parmvalue993921719153"><b>true</b></span>).</span><p><ol type="a" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_ol8206143982618"><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li172064392266">Create a <strong id="cce_bestpractice_00227__en-us_topic_0261817690_b749811813615">daemonSet</strong> file.<p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p96145582611"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b0319716270">vi daemonSet.yaml</strong></p>
+<div class="section" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_section195893610174"><h4 class="sectiontitle">Procedure</h4><ol id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_ol8890756191816"><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li38911568185"><span>Create a DaemonSet on the backend, select the Nginx image, enable the privileged container, configure the lifecycle, and specify <strong id="cce_bestpractice_00227__en-us_topic_0261817690_b1330915216347">hostNetwork: true</strong>.</span><p><ol type="a" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_ol8206143982618"><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li172064392266">Create a DaemonSet file.<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen772873513453">vi daemonset.yaml</pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p14871934289">An example YAML file is provided as follows:</p>
 <div class="notice" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_note1414511022814"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p9146121092817">The <span class="parmname" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_parmname988311433197"><b>spec.spec.containers.lifecycle</b></span> field indicates the command that will be run after the container is started.</p>
 </div></div>
@@ -43,23 +43,24 @@ spec:
           privileged: true
       imagePullSecrets:
       - name: default-secret</pre>
-</li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li16654143132615">Create a DaemonSet.<p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p19378714202719"><a name="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li16654143132615"></a><a name="en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li16654143132615"></a><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b449172122717">kubectl create –f daemonSet.yaml</strong></p>
+</li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li16654143132615">Create the DaemonSet.<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen7351645174513">kubectl create –f daemonSet.yaml</pre>
 </li></ol>
-</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li1989115691812"><span>Check whether the DaemonSet is successfully created.</span><p><p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p330213205299"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_b63374531347">kubectl get daemonset</strong> <em id="cce_bestpractice_00227__en-us_topic_0261817690_i333775323415">DaemonSet name</em></p>
+</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li1989115691812"><span>Check whether the DaemonSet has been created.</span><p><pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen6399115564515">kubectl get daemonset <i><span class="varname" id="cce_bestpractice_00227__en-us_topic_0261817690_varname15498248460">{daemonset_name}</span></i></pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p8260371304">In this example, run the following command:</p>
-<p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p262474111301"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b77659461301">kubectl get daemonset</strong><strong id="cce_bestpractice_00227__en-us_topic_0261817690_b8120171084611"> daemonset-test</strong></p>
+<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen825441714619">kubectl get daemonset <i><span class="varname" id="cce_bestpractice_00227__en-us_topic_0261817690_varname91962030204612">daemonset-test</span></i></pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p144280503115">Information similar to the following is displayed:</p>
 <pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_screen041418164230">NAME               DESIRED    CURRENT   READY    UP-T0-DATE    AVAILABLE     NODE SELECTOR   AGE
 daemonset-test     2          2         2        2             2             &lt;node&gt;          2h</pre>
-</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li1721483962911"><span>Query the container ID of DaemonSet on the node.</span><p><p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p12251648182918"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b111781214152816">docker ps -a|grep</strong> <em id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_i1982214204285">DaemonSet name</em></p>
+</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li1721483962911"><span>Obtain the IDs of the DaemonSet pods on the nodes.</span><p><pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen19706104912467">kubectl get pod | grep <i><span class="varname" id="cce_bestpractice_00227__en-us_topic_0261817690_varname19881959144619">{daemonset_name}</span></i></pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p189121843183518">In this example, run the following command:</p>
-<p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p76951258133513"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b911611592355">docker ps -a|grep</strong><strong id="cce_bestpractice_00227__en-us_topic_0261817690_b019242954620"> daemonset-test</strong></p>
+<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen14987144114616">kubectl get pod | grep <i><span class="varname" id="cce_bestpractice_00227__en-us_topic_0261817690_varname1511812754712">daemonset-test</span></i></pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p188115139361">Information similar to the following is displayed:</p>
-<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_screen103471223397"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b13543202713918">897b99faa9ce</strong>        3e094d5696c1                           "/bin/sh  -c while..."     31 minutes ago     Up  30 minutes  ault_fa7cc313-4ac1-11e9-a716-fa163e0aalba_0</pre>
-</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li19804143193010"><span>Access the container.</span><p><p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p182991085304"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b276893373511">docker exec -it </strong><em id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_i14770103393513">containerid </em><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b9769113311351">/bin/sh</strong></p>
+<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_screen103471223397">daemonset-test-mqdpv               1/1     Running             0          2h
+daemonset-test-n56vm               1/1     Running             0          2h</pre>
+</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li19804143193010"><span>Access the container.</span><p><pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen14241584568">kubectl exec -it <i><span class="varname" id="cce_bestpractice_00227__en-us_topic_0261817690_varname840136155715">{pod_name}</span></i> -- /bin/sh</pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p15306932143920">In this example, run the following command:</p>
-<p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p198991238153914"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b18533853133912">docker exec -it </strong><em id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_i65351253173916">897b99faa9ce</em><em id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_i3535105383911"> </em><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b14105174703917">/bin/sh</strong></p>
-</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li515613122228"><span>Check whether the configured command is executed after the container is started.</span><p><p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p12382171293513"><strong id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_b1270341517351">sysctl -a |grep net.ipv4.tcp_tw_reuse</strong></p>
+<pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen58311405564">kubectl exec -it <i><span class="varname" id="cce_bestpractice_00227__en-us_topic_0261817690_varname745462325612">daemonset-test-mqdpv</span></i> -- /bin/sh</pre>
+</p></li><li id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_li515613122228"><span>Check whether the configured command is executed after the container is started.</span><p><pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_screen48351536174712">sysctl -a |grep net.ipv4.tcp_tw_reuse</pre>
 <p id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_p5351202754015">If the following information is displayed, the system parameters are modified successfully:</p>
 <pre class="screen" id="cce_bestpractice_00227__en-us_topic_0261817690_en-us_topic_0226102201_en-us_topic_0179003019_screen4589125014013">net.ipv4.tcp_tw_reuse=1</pre>
 </p></li></ol>
diff --git a/docs/cce/umn/cce_bestpractice_00228.html b/docs/cce/umn/cce_bestpractice_00228.html
index 3a39d69db..fe3c91fb9 100644
--- a/docs/cce/umn/cce_bestpractice_00228.html
+++ b/docs/cce/umn/cce_bestpractice_00228.html
@@ -8,7 +8,7 @@
 <ul id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_ul11231611202114"><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li10231211122115"><strong id="cce_bestpractice_00228__en-us_topic_0261817691_b17904249161119">Scenario 1: Wait for other modules to be ready.</strong> For example, an application contains two containerized services: web server and database. The web server service needs to access the database service. However, when the application is started, the database service may have not been started. Therefore, web server may fail to access database. To solve this problem, you can use an init container in the pod where web server is running to check whether database is ready. The init container runs to completion only when database is accessible. Then, web server is started and initiates a formal access request to database. </li><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li15231101110218"><strong id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_b19862142313314">Scenario 2: Initialize the configuration.</strong> For example, the init container can check all existing member nodes in the cluster and prepare the cluster configuration information for the application container. After the application container is started, it can be added to the cluster using the configuration information.</li><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li923181119211"><strong id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_b91511427113312">Other scenarios</strong>: For example, a pod is registered with a central database and application dependencies are downloaded.</li></ul>
 <p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p10749659162017">For details, see <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/" target="_blank" rel="noopener noreferrer">Init Containers</a>.</p>
 </div>
-<div class="section" id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_section8930186205313"><h4 class="sectiontitle">Procedure</h4><ol id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_ol18594151312411"><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li881417212911"><span>Edit the YAML file of the init container workload.</span><p><p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p139726306911"><strong id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_b721101417465">vi deployment.yaml</strong></p>
+<div class="section" id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_section8930186205313"><h4 class="sectiontitle">Procedure</h4><ol id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_ol18594151312411"><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li881417212911"><span>Edit the YAML file of the init container workload.</span><p><pre class="screen" id="cce_bestpractice_00228__en-us_topic_0261817691_screen481214117440">vi deployment.yaml</pre>
 <p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p1114204610911">An example YAML file is provided as follows:</p>
 <pre class="screen" id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_screen13274102010419">apiVersion: apps/v1
 kind: Deployment
@@ -44,10 +44,10 @@ spec:
         env:
         - name: MYSQL_ROOT_PASSWORD
           value: "mysql"</pre>
-</p></li><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li88441356418"><span>Create an init container workload.</span><p><p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p915693164615"><strong id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_b18517361468">kubectl create -f deployment.yaml</strong></p>
+</p></li><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li88441356418"><span>Create an init container workload.</span><p><pre class="screen" id="cce_bestpractice_00228__en-us_topic_0261817691_screen7646823104412">kubectl create -f deployment.yaml</pre>
 <p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p8360144734611">Information similar to the following is displayed:</p>
 <pre class="screen" id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_screen25907581469">deployment.apps/mysql created</pre>
-</p></li><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li17517174055517"><span>Query the created Docker container on the node where the workload is running.</span><p><p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p129597220482"><strong id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_b114921319184810">docker ps -a|grep mysql</strong></p>
+</p></li><li id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_li17517174055517"><span>Query the created Docker container on the node where the workload is running.</span><p><pre class="screen" id="cce_bestpractice_00228__en-us_topic_0261817691_screen68117309447">docker ps -a|grep mysql</pre>
 <p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p18451347135510">The init container will exit after it runs to completion. The query result <span class="parmvalue" id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_parmvalue23838296528"><b>Exited (0)</b></span> shows the exit status of the init container.</p>
 <p id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_p446582104816"><span><img id="cce_bestpractice_00228__en-us_topic_0261817691_en-us_topic_0226102202_en-us_topic_0181631534_image16211124395516" src="en-us_image_0261818867.png"></span></p>
 </p></li></ol>
diff --git a/docs/cce/umn/cce_bestpractice_00231.html b/docs/cce/umn/cce_bestpractice_00231.html
index 4df5de4ba..fdc8b090e 100644
--- a/docs/cce/umn/cce_bestpractice_00231.html
+++ b/docs/cce/umn/cce_bestpractice_00231.html
@@ -39,7 +39,7 @@
 <div class="note" id="cce_bestpractice_00231__note1465725842820"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_bestpractice_00231__p1165795842820">When creating a load balancer, configure sticky sessions by setting <strong id="cce_bestpractice_00231__b1358719443113">kubernetes.io/elb.lb-algorithm</strong> to <strong id="cce_bestpractice_00231__b567022017125">ROUND_ROBIN</strong> or <strong id="cce_bestpractice_00231__b9575193719121">kubernetes.io/elb.lb-algorithm</strong> to <strong id="cce_bestpractice_00231__b783944781219">LEAST_CONNECTIONS</strong>. If you set <strong id="cce_bestpractice_00231__b206833430130">kubernetes.io/elb.lb-algorithm</strong> is to <strong id="cce_bestpractice_00231__b137807554139">SOURCE_IP</strong>, source IP address-based sticky sessions are supported. In this case, you do not need to configure sticky sessions again.</p>
 </div></div>
 </div>
-<div class="section" id="cce_bestpractice_00231__section18774182114516"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 4 Sticky Session in a CCE Standard Cluster</h4></div><div class="dropdowncontext"><div class="p" id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_p17432131472">In a CCE standard cluster, to enable source IP address-based sticky session for a Service, ensure the following conditions are met:<ol id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_ol146719359478"><li id="cce_bestpractice_00231__li968014117386"><strong id="cce_bestpractice_00231__b934719564717">Service Affinity</strong> of the Service must be set to <strong id="cce_bestpractice_00231__b03475584718">Node-level</strong>, where the <strong id="cce_bestpractice_00231__b6347175134720">externalTrafficPolicy</strong> value of the Service must be <strong id="cce_bestpractice_00231__b434819554719">Local</strong>.</li><li id="cce_bestpractice_00231__li17209113813914">Anti-affinity has been enabled on the backend applications of the Service to prevent all pods from being deployed on the same node.</li></ol>
+<div class="section" id="cce_bestpractice_00231__section18774182114516"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 4 Sticky Session in a CCE Standard Cluster</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><div class="p" id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_p17432131472">In a CCE standard cluster, to enable source IP address-based sticky session for a Service, ensure the following conditions are met:<ol id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_ol146719359478"><li id="cce_bestpractice_00231__li968014117386"><strong id="cce_bestpractice_00231__b934719564717">Service Affinity</strong> of the Service must be set to <strong id="cce_bestpractice_00231__b03475584718">Node-level</strong>, where the <strong id="cce_bestpractice_00231__b6347175134720">externalTrafficPolicy</strong> value of the Service must be <strong id="cce_bestpractice_00231__b434819554719">Local</strong>.</li><li id="cce_bestpractice_00231__li17209113813914">Anti-affinity has been enabled on the backend applications of the Service to prevent all pods from being deployed on the same node.</li></ol>
 </div>
 <p id="cce_bestpractice_00231__p64221636173611"><strong id="cce_bestpractice_00231__b174854209162">Procedure</strong></p>
 <ol id="cce_bestpractice_00231__ol1583613073618"><li id="cce_bestpractice_00231__li54221136163614"><span>Create an Nginx workload.</span><p><div class="p" id="cce_bestpractice_00231__p164221236173617">Set the number of pods to 3 and configure podAntiAffinity.<pre class="screen" id="cce_bestpractice_00231__screen1042215368362">kind: Deployment
@@ -105,7 +105,7 @@ spec:
 </li></ol>
 </p></li></ol>
 </div></div></div>
-<div class="section" id="cce_bestpractice_00231__section157301511124915"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 4 Sticky Session in a CCE Turbo Cluster</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_00231__p98950242614">In a CCE Turbo cluster, enabling source IP address-based sticky session for a Service relies on the load balancer type.</p>
+<div class="section" id="cce_bestpractice_00231__section157301511124915"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 4 Sticky Session in a CCE Turbo Cluster</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_00231__p98950242614">In a CCE Turbo cluster, enabling source IP address-based sticky session for a Service relies on the load balancer type.</p>
 <ul id="cce_bestpractice_00231__ul1267214278620"><li id="cce_bestpractice_00231__li111513504311">When a dedicated load balancer is used, passthrough networking is allowed between the load balancer and pods, and pods function as the backend server group of the load balancer. Therefore, you do not need to configure Service affinity or application anti-affinity when enabling source IP address-based sticky session for the Service.</li><li id="cce_bestpractice_00231__li13957457103311">If a shared load balancer is used, sticky session cannot be enabled.</li></ul>
 <p id="cce_bestpractice_00231__p480281932720"><strong id="cce_bestpractice_00231__b114869203165">Procedure</strong></p>
 <ul id="cce_bestpractice_00231__ul984771992718"><li id="cce_bestpractice_00231__li384711912715"><strong id="cce_bestpractice_00231__b1516904864716">For dedicated load balancers</strong><div class="p" id="cce_bestpractice_00231__p17847619202717">The following shows an example YAML file for configuring source IP address-based sticky sessions for a Service that uses an existing load balancer:<pre class="screen" id="cce_bestpractice_00231__screen1484781911276">apiVersion: v1
@@ -135,7 +135,7 @@ spec:
 </div>
 </li></ul>
 </div></div></div>
-<div class="section" id="cce_bestpractice_00231__section1545510243112"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 7 Sticky Session in a CCE Standard Cluster</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_p819192517506">To enable cookie-based sticky session on an ingress, ensure the following conditions are met:</p>
+<div class="section" id="cce_bestpractice_00231__section1545510243112"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 7 Sticky Session in a CCE Standard Cluster</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_p819192517506">To enable cookie-based sticky session on an ingress, ensure the following conditions are met:</p>
 <ol id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_ol13704202116515"><li id="cce_bestpractice_00231__li1327633572913"><strong id="cce_bestpractice_00231__b13948141534718">Service Affinity</strong> of the ingress must be set to <strong id="cce_bestpractice_00231__b1494821517471">Node-level</strong>, where the <strong id="cce_bestpractice_00231__b5948191517477">externalTrafficPolicy</strong> value of the Service must be <strong id="cce_bestpractice_00231__b119485158479">Local</strong>.</li><li id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_li1370462195119">Anti-affinity must be enabled for the ingress workload to prevent all pods from being deployed on the same node.</li></ol>
 <p id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_p514014531516"><strong id="cce_bestpractice_00231__b20486162051620">Procedure</strong></p>
 <ol id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_ol12391642125610"><li id="cce_bestpractice_00231__en-us_topic_0226102205_en-us_topic_0179003349_li19541156676"><span>Create an Nginx workload.</span><p><div class="p" id="cce_bestpractice_00231__cce_bestpractice_00231_p164221236173617">Set the number of pods to 3 and configure podAntiAffinity.<pre class="screen" id="cce_bestpractice_00231__cce_bestpractice_00231_screen1042215368362">kind: Deployment
@@ -248,7 +248,7 @@ spec:
 </li></ol>
 </p></li></ol>
 </div></div></div>
-<div class="section" id="cce_bestpractice_00231__section1176317569577"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 7 Sticky Session in a CCE Turbo Cluster</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_00231__p49257405816">Enable cookie-based sticky session on the ingress.</p>
+<div class="section" id="cce_bestpractice_00231__section1176317569577"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Layer 7 Sticky Session in a CCE Turbo Cluster</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_00231__p49257405816">Enable cookie-based sticky session on the ingress.</p>
 <ul id="cce_bestpractice_00231__ul164141535185811"><li id="cce_bestpractice_00231__li1070228144111">When a dedicated load balancer is used, passthrough networking is allowed between the load balancer and pods, and pods function as the backend server group of the load balancer. Therefore, you do not need to configure Service affinity or application anti-affinity when enabling cookie-based sticky session for the ingress.</li><li id="cce_bestpractice_00231__li02411345143413">If a shared load balancer is used, sticky session cannot be enabled.</li></ul>
 <p id="cce_bestpractice_00231__p1092517445819"><strong id="cce_bestpractice_00231__b19943171811615">Procedure</strong></p>
 <ul id="cce_bestpractice_00231__ul4790763592"><li id="cce_bestpractice_00231__li13875141015017"><strong id="cce_bestpractice_00231__b0974197712">For dedicated load balancers</strong><ol id="cce_bestpractice_00231__ol14282115018017"><li id="cce_bestpractice_00231__li15282195013013">Create a Service for the workload. In a CCE Turbo cluster, the ingresses that use a dedicated load balancer must interconnect with ClusterIP Services.<div class="p" id="cce_bestpractice_00231__p842193818019"><a name="cce_bestpractice_00231__li15282195013013"></a><a name="li15282195013013"></a>Configure sticky sessions during the creation of a Service. An ingress can access multiple Services, and each Service can have different sticky sessions.<pre class="screen" id="cce_bestpractice_00231__screen642438503">apiVersion: v1
diff --git a/docs/cce/umn/cce_bestpractice_00281.html b/docs/cce/umn/cce_bestpractice_00281.html
index 5c5673a14..936c0812a 100644
--- a/docs/cce/umn/cce_bestpractice_00281.html
+++ b/docs/cce/umn/cce_bestpractice_00281.html
@@ -117,7 +117,7 @@ metadata:
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.3.5.3.2.5.1.3 "><p id="cce_bestpractice_00281__cce_10_0380_p7360105617584">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_bestpractice_00281__cce_10_0380_p936095685819">Driver type. If an EVS disk is used, the parameter value is fixed at <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue330635280"><b>disk.csi.everest.io</b></span>.</p>
+<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_bestpractice_00281__cce_10_0380_p936095685819">Driver type. If an EVS disk is used, the parameter value is fixed at <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue1121200374"><b>disk.csi.everest.io</b></span>.</p>
 </td>
 </tr>
 <tr id="cce_bestpractice_00281__cce_10_0380_row13957193955813"><td class="cellrowborder" valign="top" width="11%" headers="mcps1.3.3.5.3.2.5.1.1 "><p id="cce_bestpractice_00281__cce_10_0380_p1132211331519">EVS</p>
@@ -126,8 +126,8 @@ metadata:
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.3.5.3.2.5.1.3 "><p id="cce_bestpractice_00281__cce_10_0380_p13360145610589">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_bestpractice_00281__cce_10_0380_p17361105611585">If an EVS disk is used, the parameter value can be <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue771666110"><b>ext4</b></span> or <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue988868842"><b>xfs</b></span>.</p>
-<div class="p" id="cce_bestpractice_00281__cce_10_0380_p1036185645819">The restrictions on using <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue716121274"><b>xfs</b></span> are as follows:<ul id="cce_bestpractice_00281__cce_10_0380_ul03616566583"><li id="cce_bestpractice_00281__cce_10_0380_li7361115605816">The nodes must run CentOS 7, HCE OS 2.0, or Ubuntu 22.04, and the Everest version in the cluster must be 2.3.2 or later.</li><li id="cce_bestpractice_00281__cce_10_0380_li5361156125820">Only common containers are supported.</li></ul>
+<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_bestpractice_00281__cce_10_0380_p17361105611585">If an EVS disk is used, the parameter value can be <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue1079257909"><b>ext4</b></span> or <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue1239687976"><b>xfs</b></span>.</p>
+<div class="p" id="cce_bestpractice_00281__cce_10_0380_p1036185645819">The restrictions on using <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue1666719131"><b>xfs</b></span> are as follows:<ul id="cce_bestpractice_00281__cce_10_0380_ul03616566583"><li id="cce_bestpractice_00281__cce_10_0380_li7361115605816">The nodes must run CentOS 7, HCE OS 2.0, or Ubuntu 22.04, and the Everest version in the cluster must be 2.3.2 or later.</li><li id="cce_bestpractice_00281__cce_10_0380_li5361156125820">Only common containers are supported.</li></ul>
 </div>
 </td>
 </tr>
@@ -147,7 +147,7 @@ metadata:
 </td>
 <td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.3.5.3.2.5.1.3 "><p id="cce_bestpractice_00281__cce_10_0380_p636185665814">Yes</p>
 </td>
-<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_bestpractice_00281__cce_10_0380_p103626560585">The parameter value is fixed at <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue410198236"><b>true</b></span>, which indicates that the EVS device type is <strong id="cce_bestpractice_00281__cce_10_0380_b1021717869">SCSI</strong>. No other parameter values are allowed.</p>
+<td class="cellrowborder" valign="top" width="51%" headers="mcps1.3.3.5.3.2.5.1.4 "><p id="cce_bestpractice_00281__cce_10_0380_p103626560585">The parameter value is fixed at <span class="parmvalue" id="cce_bestpractice_00281__cce_10_0380_parmvalue70974216"><b>true</b></span>, which indicates that the EVS device type is <strong id="cce_bestpractice_00281__cce_10_0380_b1776423110">SCSI</strong>. No other parameter values are allowed.</p>
 </td>
 </tr>
 <tr id="cce_bestpractice_00281__cce_10_0380_row1967312234013"><td class="cellrowborder" valign="top" width="11%" headers="mcps1.3.3.5.3.2.5.1.1 "><p id="cce_bestpractice_00281__cce_10_0380_p10936142812010">SFS</p>
diff --git a/docs/cce/umn/cce_bestpractice_0300.html b/docs/cce/umn/cce_bestpractice_0300.html
index 5f818282d..0e8a2977b 100644
--- a/docs/cce/umn/cce_bestpractice_0300.html
+++ b/docs/cce/umn/cce_bestpractice_0300.html
@@ -5,8 +5,8 @@
 <p id="cce_bestpractice_0300__p1772415327139">Currently, the CCE console provides four types of namespace-level ClusterRole permissions by default: cluster-admin, admin, edit, and view. However, these permissions apply to resources in the namespace regardless of resource types (pods, Deployments, and Services).</p>
 </div>
 <div class="section" id="cce_bestpractice_0300__section10137819385"><h4 class="sectiontitle">Solution</h4><p id="cce_bestpractice_0300__p413018510381">Kubernetes RBAC enables you to easily control permissions on namespace resources.</p>
-<ul id="cce_bestpractice_0300__ul561413529305"><li id="cce_bestpractice_0300__en-us_topic_0249851132_li1481515491386">Role: defines a set of rules for accessing Kubernetes resources in a namespace.</li><li id="cce_bestpractice_0300__en-us_topic_0249851132_li1224120528819">RoleBinding: defines the relationship between users and roles.</li><li id="cce_bestpractice_0300__en-us_topic_0249851132_li11770153233818">ClusterRole: defines a set of rules for accessing Kubernetes resources in a cluster (including all namespaces).</li><li id="cce_bestpractice_0300__en-us_topic_0249851132_li15813127781">ClusterRoleBinding: defines the relationship between users and cluster roles.</li></ul>
-<p id="cce_bestpractice_0300__p18561191633117">Role and ClusterRole specify actions that can be performed on specific resources. RoleBinding and ClusterRoleBinding bind roles to specific users, user groups, or ServiceAccounts. See the following figure.</p>
+<ul id="cce_bestpractice_0300__ul561413529305"><li id="cce_bestpractice_0300__en-us_topic_0249851132_li1481515491386">Roles: define a set of rules for accessing Kubernetes resources in a namespace.</li><li id="cce_bestpractice_0300__en-us_topic_0249851132_li1224120528819">RoleBindings: define the relationship between users and roles.</li><li id="cce_bestpractice_0300__en-us_topic_0249851132_li11770153233818">ClusterRoles: define a set of rules for accessing Kubernetes resources in a cluster (including all namespaces).</li><li id="cce_bestpractice_0300__en-us_topic_0249851132_li15813127781">ClusterRoleBindings: define the relationship between users and cluster roles.</li></ul>
+<p id="cce_bestpractice_0300__p18561191633117">Roles and ClusterRoles specify actions that can be performed on specific resources. RoleBindings and ClusterRoleBindings bind Roles to specific users, user groups, or service accounts.</p>
 <div class="fignone" id="cce_bestpractice_0300__fig1592685919319"><span class="figcap"><b>Figure 1 </b>Role binding</span><br><span><img id="cce_bestpractice_0300__en-us_topic_0249851132_image19499911182110" src="en-us_image_0261301557.png"></span></div>
 <p id="cce_bestpractice_0300__p19188192173211">The user in the preceding figure can be an IAM user or user group in CCE. You can efficiently control permissions on namespace resources through RoleBindings.</p>
 <p id="cce_bestpractice_0300__p1835217151375">The section describes how to use Kubernetes RBAC to grant user <strong id="cce_bestpractice_0300__b14421201314015">user-example</strong> with the permission for viewing pods. (This is the only permission the user has.)</p>
@@ -29,7 +29,7 @@ Error from server (Forbidden): deployments.apps is forbidden: User "0c97ac3cb280
 <div class="section" id="cce_bestpractice_0300__section105059416216"><h4 class="sectiontitle">Creating a Role and RoleBinding</h4><p id="cce_bestpractice_0300__p54591427193119">Log in to the CCE console, <a href="cce_10_0107.html">download the kubectl configuration file in the cluster and access the cluster</a>, and create a Role and RoleBinding.</p>
 <div class="note" id="cce_bestpractice_0300__note171671754143314"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_bestpractice_0300__p1516845483317">Log in as the account used to create the cluster because CCE automatically assigns the cluster-admin permissions to the account, which means that the account has the permissions to create Roles and RoleBindings. Alternatively, you can use IAM users who have the permissions to create Roles and RoleBindings.</p>
 </div></div>
-<p id="cce_bestpractice_0300__p9324202361517">The procedure for creating a Role is very simple. To be specific, specify a namespace and then define rules. The rules in the following example are to allow GET and LIST operations on pods in the default namespace.</p>
+<p id="cce_bestpractice_0300__p9324202361517">The definition of a Role is simple. You just specify a namespace and some rules. For example, the following rules allow you to perform GET and LIST operations on pods in the <strong id="cce_bestpractice_0300__en-us_topic_0249851132_b18822141015514">default</strong> namespace.</p>
 <pre class="screen" id="cce_bestpractice_0300__screen197388108173">kind: Role
 apiVersion: rbac.authorization.k8s.io/v1
 metadata:
@@ -58,7 +58,7 @@ subjects:
   name: 0c97ac3cb280f4d91fa7c0096739e1f8    # IAM user ID
   apiGroup: rbac.authorization.k8s.io</pre>
 <p id="cce_bestpractice_0300__p195507214188">The <strong id="cce_bestpractice_0300__b68978321689">subjects</strong> section binds a Role with an IAM user so that the IAM user can obtain the permissions defined in the Role, as shown in the following figure.</p>
-<div class="fignone" id="cce_bestpractice_0300__fig9473195372813"><span class="figcap"><b>Figure 2 </b>Binding a role to a user</span><br><span><img id="cce_bestpractice_0300__en-us_topic_0249851132_image35211083405" src="en-us_image_0262051194.png"></span></div>
+<div class="fignone" id="cce_bestpractice_0300__fig9473195372813"><span class="figcap"><b>Figure 2 </b>Binding a Role to a user</span><br><span><img id="cce_bestpractice_0300__en-us_topic_0249851132_image35211083405" src="en-us_image_0262051194.png"></span></div>
 <p id="cce_bestpractice_0300__p430545215225">You can also specify a user group in the <strong id="cce_bestpractice_0300__b419915110104">subjects</strong> section. In this case, all users in the user group obtain the permissions defined in the Role.</p>
 <pre class="screen" id="cce_bestpractice_0300__screen2269203813232">subjects:
 - kind: Group
diff --git a/docs/cce/umn/cce_bestpractice_0317.html b/docs/cce/umn/cce_bestpractice_0317.html
index db2a1513c..198f9a2fa 100644
--- a/docs/cce/umn/cce_bestpractice_0317.html
+++ b/docs/cce/umn/cce_bestpractice_0317.html
@@ -94,6 +94,9 @@ spec:
 </div>
 <div class="section" id="cce_bestpractice_0317__en-us_topic_0000001226756283_section1730432053118"><h4 class="sectiontitle">Uninstalling web-terminal After Use</h4><p id="cce_bestpractice_0317__en-us_topic_0000001226756283_p18400172813110">The web-terminal add-on can be used to manage CCE clusters. Keep the login password secure and uninstall the add-on when it is no longer needed.</p>
 </div>
+<div class="section" id="cce_bestpractice_0317__en-us_topic_0000001226756283_section93869265136"><h4 class="sectiontitle">Using Physical Multi-Tenancy</h4><p id="cce_bestpractice_0317__en-us_topic_0000001226756283_p11874421317">To ensure that resources of different tenants are isolated and to reduce the attack surface, a separate CCE cluster can be created for each tenant. However, this solution comes with some drawbacks.</p>
+<ul id="cce_bestpractice_0317__en-us_topic_0000001226756283_ul13183446132"><li id="cce_bestpractice_0317__en-us_topic_0000001226756283_li1518174481314">High costs: It may increase the costs as more hardware or VM resources need to be purchased, and more manpower and time need to be spent on managing and maintaining these clusters.</li><li id="cce_bestpractice_0317__en-us_topic_0000001226756283_li1418184419139">Low resource utilization: Each tenant requires separate hardware or VM resources to run their clusters, which may result in low resource utilization and wastage.</li><li id="cce_bestpractice_0317__en-us_topic_0000001226756283_li318744141310">Increased management complexity: Managing and maintaining separate clusters for each tenant increases management complexity and may require more manpower and time.</li></ul>
+</div>
 </div>
 <div>
 <div class="familylinks">
diff --git a/docs/cce/umn/cce_bestpractice_0318.html b/docs/cce/umn/cce_bestpractice_0318.html
index eacf61f7a..3ad8f1811 100644
--- a/docs/cce/umn/cce_bestpractice_0318.html
+++ b/docs/cce/umn/cce_bestpractice_0318.html
@@ -29,7 +29,15 @@ curl 169.254.169.254/openstack/latest/user_data</pre>
 </li><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li973418171252">Run the following commands in the container to access the <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b1440934025718">userdata</strong> and <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b34103401577">metadata</strong> interfaces of OpenStack and check whether the request is intercepted:<pre class="screen" id="cce_bestpractice_0318__en-us_topic_0000001226756285_screen3787166102414">curl 169.254.169.254/openstack/latest/meta_data.json
 curl 169.254.169.254/openstack/latest/user_data</pre>
 </li></ol>
-</li><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li222510111340">CCE Turbo cluster<p id="cce_bestpractice_0318__en-us_topic_0000001226756285_p121461314163415"><a name="cce_bestpractice_0318__en-us_topic_0000001226756285_li222510111340"></a><a name="en-us_topic_0000001226756285_li222510111340"></a>No additional configuration is required.</p>
+</li><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li222510111340">CCE Turbo cluster<p id="cce_bestpractice_0318__en-us_topic_0000001226756285_p121461314163415"><a name="cce_bestpractice_0318__en-us_topic_0000001226756285_li222510111340"></a><a name="en-us_topic_0000001226756285_li222510111340"></a>No additional configuration is required for a cluster of a version earlier than v1.23.13-r0, v1.25.8-r0, v1.27.5-r0, or v1.28.3-r0.</p>
+<div class="p" id="cce_bestpractice_0318__en-us_topic_0000001226756285_p14180194713152">For a cluster of v1.23.13-r0, v1.25.8-r0, v1.27.5-r0, v1.28.3-r0, and later version, log in to the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b1210872619135">Settings</strong>, click the <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b980154512139">Network</strong> tab, and view the value of <span class="uicontrol" id="cce_bestpractice_0318__en-us_topic_0000001226756285_uicontrol1561629161717"><b>Pod Access to Metadata</b></span>.<ul id="cce_bestpractice_0318__en-us_topic_0000001226756285_ul9721740128"><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li142401352511">If <span class="uicontrol" id="cce_bestpractice_0318__en-us_topic_0000001226756285_uicontrol6185125211210"><b>Pod Access to Metadata</b></span> is not enabled, no additional configuration is required. The container has been disabled from obtaining the node metadata.</li><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li16689718201219">If <span class="uicontrol" id="cce_bestpractice_0318__en-us_topic_0000001226756285_uicontrol415362951311"><b>Pod Access to Metadata</b></span> is enabled, take the following steps to disable the container from obtaining the node metadata:<ol type="a" id="cce_bestpractice_0318__en-us_topic_0000001226756285_ol11828145411135"><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li682815441312">Log in to each node in the cluster as user <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b1582515160562">root</strong> and run the following command:<pre class="screen" id="cce_bestpractice_0318__en-us_topic_0000001226756285_screen88281754181310">iptables -I FORWARD -s {container_cidr} -d 169.254.169.254 -j REJECT</pre>
+<p id="cce_bestpractice_0318__en-us_topic_0000001226756285_p382815411320"><em id="cce_bestpractice_0318__en-us_topic_0000001226756285_i718630195616">{container_cidr}</em> indicates the container CIDR block of the cluster, for example, <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b11863010563">10.0.0.0/16</strong>.</p>
+<p id="cce_bestpractice_0318__en-us_topic_0000001226756285_p1882816542133">To ensure configuration persistence, write the command to the <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b145714431564">/etc/rc.local</strong> script.</p>
+</li><li id="cce_bestpractice_0318__en-us_topic_0000001226756285_li582811543136">Run the following commands in the container to access the <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b122661564577">userdata</strong> and <strong id="cce_bestpractice_0318__en-us_topic_0000001226756285_b226676145713">metadata</strong> interfaces of OpenStack and check whether the request is intercepted:<pre class="screen" id="cce_bestpractice_0318__en-us_topic_0000001226756285_screen88281354121310">curl 169.254.169.254/openstack/latest/meta_data.json
+curl 169.254.169.254/openstack/latest/user_data</pre>
+</li></ol>
+</li></ul>
+</div>
 </li></ul>
 </p></li></ol>
 </div>
diff --git a/docs/cce/umn/cce_bestpractice_0319.html b/docs/cce/umn/cce_bestpractice_0319.html
index 9dd8c0e10..8a50c2aca 100644
--- a/docs/cce/umn/cce_bestpractice_0319.html
+++ b/docs/cce/umn/cce_bestpractice_0319.html
@@ -83,6 +83,32 @@ spec:
 </p></li><li id="cce_bestpractice_0319__en-us_topic_0000001181182498_li8454105818194"><span>Run the following command in the container to access kube-apiserver and check whether the request is intercepted:</span><p><pre class="screen" id="cce_bestpractice_0319__en-us_topic_0000001181182498_screen198782045205215">curl -k https://<em id="cce_bestpractice_0319__en-us_topic_0000001181182498_i0393123151412">{Private API server IP}</em>:5443</pre>
 </p></li></ol>
 </div>
+<div class="section" id="cce_bestpractice_0319__en-us_topic_0000001181182498_section1053282084016"><h4 class="sectiontitle">Properly Setting Volume Propagation</h4><p id="cce_bestpractice_0319__en-us_topic_0000001181182498_p1151465341714">When mounting a host path, set the propagation mode to <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b1390755111422">None</strong>. Exercise caution when using the <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b990055574612">Bidirectional</strong> mode.</p>
+<p id="cce_bestpractice_0319__en-us_topic_0000001181182498_p21639579178">The <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b972510624713">mountPropagation</strong> field in <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b20601161144713">Container.volumeMounts</strong> controls the mount propagation feature of a volume. Value options are as follows:</p>
+<ul id="cce_bestpractice_0319__en-us_topic_0000001181182498_ul1516385719175"><li id="cce_bestpractice_0319__en-us_topic_0000001181182498_li1916335711713"><strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b44739474471">None</strong>: the default value, equal to the <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b44537569561">private</strong> mount propagation option described in <a href="https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt" target="_blank" rel="noopener noreferrer">Linux kernel documentation</a>. This volume mount will not receive any subsequent mounts that are mounted to this volume or any of its subdirectories by the host. In similar fashion, no mounts created by the container will be visible on the host.</li></ul>
+<ul id="cce_bestpractice_0319__en-us_topic_0000001181182498_ul216413575174"><li id="cce_bestpractice_0319__en-us_topic_0000001181182498_li201641657121716"><strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b1390293285217">HostToContainer</strong>: equal to the <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b26945118578">rslave</strong> mount propagation option described in <a href="https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt" target="_blank" rel="noopener noreferrer">Linux kernel documentation</a>. This volume mount will receive all subsequent mounts that are mounted to this volume or any of its subdirectories. In other words, if the host mounts anything inside the volume mount, the container will see it mounted there. If a Bidirectional pod mounts anything to the same volume, this change is visible to all HostToContainer pods.</li></ul>
+<ul id="cce_bestpractice_0319__en-us_topic_0000001181182498_ul4164135715172"><li id="cce_bestpractice_0319__en-us_topic_0000001181182498_li11294133204416"><strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b176246112311">Bidirectional</strong>: equal to the <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b1762501116317">rshared</strong> mount propagation option described in <a href="https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt" target="_blank" rel="noopener noreferrer">Linux kernel documentation</a>. All volume mounts created by the container will be propagated back to the host and to all containers of all pods that use the same volume.<p id="cce_bestpractice_0319__en-us_topic_0000001181182498_p141597917447">Bidirectional mount propagation can be dangerous. It can damage the host operating system and therefore it is allowed only in privileged containers. An example is as follows:</p>
+<pre class="screen" id="cce_bestpractice_0319__en-us_topic_0000001181182498_screen15528121124015">apiVersion: v1
+kind: Pod
+metadata:
+    name: security-mount
+    label:
+      app: security-mount
+spec:
+    containers:
+    - name: security-mount
+      image: ...
+      volumeMounts:
+      - name: mount-none
+        mountPath: /opt
+        <strong id="cce_bestpractice_0319__en-us_topic_0000001181182498_b922072091115">mountPropagation: None</strong>
+    volumes:
+    - name: mount-none
+      hostPath:
+        path: /opt/</pre>
+</li></ul>
+<p id="cce_bestpractice_0319__en-us_topic_0000001181182498_p123789335267">For details, see the <a href="https://kubernetes.io/docs/concepts/storage/volumes/" target="_blank" rel="noopener noreferrer">community documentation</a>.</p>
+</div>
 </div>
 <div>
 <div class="familylinks">
diff --git a/docs/cce/umn/cce_bestpractice_0333.html b/docs/cce/umn/cce_bestpractice_0333.html
index 70e831ea0..e74350bad 100644
--- a/docs/cce/umn/cce_bestpractice_0333.html
+++ b/docs/cce/umn/cce_bestpractice_0333.html
@@ -1,11 +1,11 @@
 <a name="cce_bestpractice_0333"></a><a name="cce_bestpractice_0333"></a>
 
 <h1 class="topictitle1">Configuration Suggestions on CCE Workload Identity Security</h1>
-<div id="body8662426"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p8060118">A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK and SK. This helps to minimize security risks.</p>
+<div id="body8662426"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p8060118">A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK/SK. This helps minimize security risks.</p>
 <p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p133991341154613">This section describes how to use workload identities in CCE.</p>
 <div class="section" id="cce_bestpractice_0333__en-us_topic_0000001280331044_section49971247102212"><h4 class="sectiontitle">Notes and Constraints</h4><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p0113115311228">The cluster version must be v1.19.16 or later.</p>
 </div>
-<div class="section" id="cce_bestpractice_0333__en-us_topic_0000001280331044_section7702113994719"><h4 class="sectiontitle">Procedure</h4><ol id="cce_bestpractice_0333__en-us_topic_0000001280331044_ol579915915514"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li779955918512"><span>Obtain the public key of the cluster serviceAccountToken from CCE. For details, see <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section5937204594820">Step 1: Obtain the Public Key for Signature of the CCE Cluster</a>.</span></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li167994591853"><span>Create an identity provider on IAM. For details, see <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013">Step 2: Configure an Identity Provider</a>.</span></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li126302035862"><span>Obtain an IAM token from the workload and simulate an IAM user to access a cloud service. For details, see <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section38531454152611">Step 3: Use a Workload Identity</a>.</span><p><div class="p" id="cce_bestpractice_0333__en-us_topic_0000001280331044_p787014352060">The procedure is as follows:<ol type="a" id="cce_bestpractice_0333__en-us_topic_0000001280331044_ol24641834105515"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1452635010549">Deploy the application pod and obtain the OpenID Connect ID token file by mounting the identity provider.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li94781434556">Use the mounted OpenID Connect ID token file in programs in the pod to access IAM and obtain a temporary IAM token.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li876464142311">Access the cloud service using the IAM token in programs in the pod.</li></ol>
+<div class="section" id="cce_bestpractice_0333__en-us_topic_0000001280331044_section7702113994719"><h4 class="sectiontitle">Procedure</h4><ol id="cce_bestpractice_0333__en-us_topic_0000001280331044_ol579915915514"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li779955918512"><span>Obtain the public key of the cluster service account token from CCE. For details, see <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section5937204594820">Step 1: Obtain the Public Key for Signature of the CCE Cluster</a>.</span></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li167994591853"><span>Create an identity provider on IAM. For details, see <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013">Step 2: Configure an Identity Provider</a>.</span></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li126302035862"><span>Obtain an IAM token from the workload and simulate an IAM user to access a cloud service. For details, see <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section38531454152611">Step 3: Use a Workload Identity</a>.</span><p><div class="p" id="cce_bestpractice_0333__en-us_topic_0000001280331044_p787014352060">The procedure is as follows:<ol type="a" id="cce_bestpractice_0333__en-us_topic_0000001280331044_ol24641834105515"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1452635010549">Deploy the application pod and obtain the OpenID Connect ID token file by mounting the identity provider.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li94781434556">Use the mounted OpenID Connect ID token file in programs in the pod to access IAM and obtain a temporary IAM token.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li876464142311">Access the cloud service using the IAM token in programs in the pod.</li></ol>
 <div class="fignone" id="cce_bestpractice_0333__en-us_topic_0000001280331044_fig20726184218517"><span class="figcap"><b>Figure 1 </b>Workflow</span><br><span><img class="eddx" id="cce_bestpractice_0333__en-us_topic_0000001280331044_image9727114215516" src="en-us_image_0000002101396665.png"></span></div>
 </div>
 </p></li></ol>
@@ -18,7 +18,7 @@
 </div>
 <div class="section" id="cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013"><a name="cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013"></a><a name="en-us_topic_0000001280331044_section18167152865013"></a><h4 class="sectiontitle">Step 2: Configure an Identity Provider</h4><ol id="cce_bestpractice_0333__en-us_topic_0000001280331044_ol169921827125113"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1099232713516"><span>Log in to the IAM console, choose <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b9236174431318">Identity Providers</strong> in the navigation pane, and click <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b167449499132">Create Identity Provider</strong> in the upper right corner. On the displayed page, set <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b15803011146">Protocol</strong> to <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b510665171414">OpenID Connect</strong> and <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b125951516161417">SSO Type</strong> to <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b4189192211413">Virtual user</strong> and click <span class="uicontrol" id="cce_bestpractice_0333__en-us_topic_0000001280331044_uicontrol176618269597"><b>OK</b></span>.</span></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li19516032145116"><span>In the identity provider list, locate the row containing the new identity provider and click <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b156001642101720">Modify</strong> in the <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b118454443177">Operation</strong> column to modify the identity provider information.</span><p><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p192233582812"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b13421111182812">Access Type</strong>: Select <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b10856131974017">Programmatic access</strong>.</p>
 <p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p3372331793"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b513416273402">Configuration Information</strong></p>
-<ul id="cce_bestpractice_0333__en-us_topic_0000001280331044_ul1116031018107"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li10160111091015"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b89401740114010">Identity Provider URL</strong>: Enter <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1367064319400">https://kubernetes.default.svc.cluster.local</strong>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1316010104103"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b19577194911401">Client ID</strong>: Enter an ID, which will be used when you create a container.<div class="caution" id="cce_bestpractice_0333__en-us_topic_0000001280331044_note891311093913"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p491381014392">You are not advised to use a client ID consisting solely of digits. If the client ID consists only of digits, enclose it in double quotation marks ("") when editing the YAML file for the workload. If the client ID is 123456789, it should be entered as <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b0281101716156">"123456789"</strong> in the YAML file.</p>
+<ul id="cce_bestpractice_0333__en-us_topic_0000001280331044_ul1116031018107"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li10160111091015"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b89401740114010">Identity Provider URL</strong>: Enter <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1367064319400">https://kubernetes.default.svc.cluster.local</strong>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1316010104103"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b41062448516">Client ID</strong>: Enter a client ID, which will be used when you create a container.<div class="caution" id="cce_bestpractice_0333__en-us_topic_0000001280331044_note891311093913"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p491381014392">A client ID cannot contain only digits. If the client ID consists only of digits, enclose it in double quotation marks ("") when editing the YAML file for the workload. For example, if the client ID is <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b18623346617">123456789</strong>, it should be entered as <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1797717255611">"123456789"</strong> in the YAML file.</p>
 </div></div>
 </li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li716181081018"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b118391894118">Signing Key</strong>: Enter the JWKS of the CCE cluster obtained in <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section5937204594820">Step 1: Obtain the Public Key for Signature of the CCE Cluster</a>.</li></ul>
 <p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p1473116851817"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b121951410135017">Identity Conversion Rules</strong></p>
@@ -77,7 +77,7 @@ spec:
       - name: container-1
         image: nginx:latest
         volumeMounts:
-        - mountPath: "/var/run/secrets/tokens"     # Mount the serviceAccountToken generated by Kubernetes to the <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b12458612155518">/var/run/secrets/tokens/oidc-token</strong> file.
+        - mountPath: "/var/run/secrets/tokens"     # Mount the service account token generated by Kubernetes to the <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b12458612155518">/var/run/secrets/tokens/oidc-token</strong> file.
           name: oidc-token
       imagePullSecrets:
       - name: default-secret
@@ -92,15 +92,15 @@ spec:
               expirationSeconds: 7200       # Expiry period
               path: oidc-token              # Path name, which can be customized</pre>
 </div>
-</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1597836795"><span>After the creation is complete, log in to the container. The content of the <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b20348529161919">/var/run/secrets/tokens/oidc-token</strong> file is the serviceAccountToken generated by Kubernetes.</span><p><div class="note" id="cce_bestpractice_0333__en-us_topic_0000001280331044_note209921935201012"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p999210357107">If the serviceAccountToken is used for more than 24 hours or 80% of its expiry period, kubelet will automatically rotate the serviceAccountToken.</p>
+</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1597836795"><span>After the creation is complete, log in to the container. The content of the <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b20348529161919">/var/run/secrets/tokens/oidc-token</strong> file is the service account token generated by Kubernetes.</span><p><div class="note" id="cce_bestpractice_0333__en-us_topic_0000001280331044_note209921935201012"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p999210357107">If the service account token is used for more than 24 hours or 80% of its expiry period, kubelet will automatically rotate the service account token.</p>
 </div></div>
-</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li89609511115"><span>Use the OpenID Connect ID token to call the API for <a href="https://docs.otc.t-systems.com/en-us/api/iam/iam_13_0605.html" target="_blank" rel="noopener noreferrer">Obtaining a Token with an OpenID Connect ID Token</a>. The <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b4991929123011">X-Subject-Token</strong> field in the response header is the IAM token. Then, you can use this token to access cloud services.</span><p><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p8607177517">The following shows an example:</p>
+</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li89609511115"><span>Use the OpenID Connect ID token to call the API for <a href="https://docs.otc.t-systems.com/en-us/api/iam/iam_13_0605.html" target="_blank" rel="noopener noreferrer">Obtaining a Token with an OpenID Connect ID Token</a>. The <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b3579155410221">X-Subject-Token</strong> field in the response header is the IAM token. Then, you can use this token to access cloud services.</span><p><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p8607177517">The following shows an example:</p>
 <pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen12632921195416">curl -i --location --request POST 'https://<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b181044375517"><i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname2037412543141">{{iam endpoint}}</span></i></strong>/v3.0/OS-AUTH/id-token/tokens' \
  --header '<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1067820478568">X-Idp-Id: <i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname8889551205611">workload_identity</span></i></strong>' \
  --header 'Content-Type: application/json' \
  --data @<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1830152521417"><i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname216110454146">token_body.json</span></i></strong></pre>
 <p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p467644104113">Specifically:</p>
-<ul id="cce_bestpractice_0333__en-us_topic_0000001280331044_ul1167285918426"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li12672145944213"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1035516205810">{{iam endpoint}}</strong> indicates the endpoint of IAM. For details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li0673259144213"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1014313549424">workload_identity</strong> is the identity provider name, which is the same as that configured in <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013">Step 2: Configure an Identity Provider</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li067305914215"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b756886131510">token_body.json</strong> is a local file and its content is as follows:<pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen16886553181715"> { 
+<ul id="cce_bestpractice_0333__en-us_topic_0000001280331044_ul1167285918426"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li12672145944213"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b385761162317">{{iam endpoint}}</strong> indicates the endpoint of IAM. For details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li0673259144213"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1014313549424">workload_identity</strong> is the identity provider name, which is the same as that configured in <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013">Step 2: Configure an Identity Provider</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li067305914215"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b756886131510">token_body.json</strong> is a local file and its content is as follows:<pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen16886553181715"> { 
    "auth" : { 
      "id_token" : { 
        <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b19576175817239">"id" : <i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname1664085112234">"eyJhbGciOiJSU..."</span></i></strong>
diff --git a/docs/cce/umn/cce_bestpractice_10009.html b/docs/cce/umn/cce_bestpractice_10009.html
index 4e6eef561..ad86aebf2 100644
--- a/docs/cce/umn/cce_bestpractice_10009.html
+++ b/docs/cce/umn/cce_bestpractice_10009.html
@@ -67,8 +67,8 @@ subjects:
 </div>
 <p id="cce_bestpractice_10009__p1886493213502">Run the following command to create the RBAC permission:</p>
 <p id="cce_bestpractice_10009__p1040455212262"><strong id="cce_bestpractice_10009__b1463113420254">kubectl apply -f prometheus_rbac.yaml</strong></p>
-</li><li id="cce_bestpractice_10009__li79009452266">Obtain the <strong id="cce_bestpractice_10009__b71068125484">bearer_token</strong> information of the target cluster.<div class="note" id="cce_bestpractice_10009__note9906457142719"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_ul126619458255"><li id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_li7140417111115">In clusters earlier than v1.21, a token is obtained by mounting the secret of the service account to a pod. Tokens obtained this way are permanent. This approach is no longer recommended starting from version 1.21. Service accounts will stop auto creating secrets in clusters from version 1.25.<p id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_p238119179114"><a name="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_li7140417111115"></a><a name="cce_bestpractice_0070_en-us_topic_0249851131_li7140417111115"></a>In clusters of version 1.21 or later, you can use the <a href="https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-request-v1/" target="_blank" rel="noopener noreferrer">TokenRequest</a> API to <a href="https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/#bound-service-account-token-volume" target="_blank" rel="noopener noreferrer">obtain the token</a> and use the projected volume to mount the token to the pod. Such tokens are valid for a fixed period. When the mounting pod is deleted, the token automatically becomes invalid. </p>
-</li><li id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_li666114512253">If you need a token that never expires, you can also <a href="https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/#manual-secret-management-for-serviceaccounts" target="_blank" rel="noopener noreferrer">manually manage secrets for service accounts</a>. Although a permanent service account token can be manually created, you are advised to use a short-lived token by calling the <a href="https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-request-v1/" target="_blank" rel="noopener noreferrer">TokenRequest</a> API for higher security.</li></ul>
+</li><li id="cce_bestpractice_10009__li79009452266">Obtain the <strong id="cce_bestpractice_10009__b71068125484">bearer_token</strong> information of the target cluster.<div class="note" id="cce_bestpractice_10009__note9906457142719"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_ul126619458255"><li id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_li7140417111115">In clusters earlier than v1.21, tokens are obtained by mounting the secret of a service account to a pod. Such tokens are permanent. However, this approach is not recommended in clusters of v1.21 or later. Starting from v1.25, Kubernetes no longer automatically creates secrets for service accounts as part of its community iteration policy.<p id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_p238119179114"><a name="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_li7140417111115"></a><a name="cce_bestpractice_0070_en-us_topic_0249851131_li7140417111115"></a>Instead, in clusters of v1.21 and later, the recommended approach is to use the <a href="https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-request-v1/" target="_blank" rel="noopener noreferrer">TokenRequest</a> API to <a href="https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/#bound-service-account-token-volume" target="_blank" rel="noopener noreferrer">obtain tokens</a> and mount them via a projected volume to pods. These tokens remain valid only for a fixed period and become invalid once the pods are deleted. </p>
+</li><li id="cce_bestpractice_10009__cce_bestpractice_0070_en-us_topic_0249851131_li666114512253">If you need a token that never expires, you can <a href="https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/#manual-secret-management-for-serviceaccounts" target="_blank" rel="noopener noreferrer">manually manage secrets for service accounts</a>. Although a permanent service account token can be created manually, you are advised to use a short-lived token by calling the <a href="https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-request-v1/" target="_blank" rel="noopener noreferrer">TokenRequest</a> API for better security.</li></ul>
 </div></div>
 <p id="cce_bestpractice_10009__p18188145142714">Obtain the <strong id="cce_bestpractice_10009__b109291416154811">serviceaccount</strong> information.</p>
 <p id="cce_bestpractice_10009__p1250115622719"><strong id="cce_bestpractice_10009__b61071650124115">kubectl describe sa prometheus-test -n kube-system</strong></p>
diff --git a/docs/cce/umn/cce_bestpractice_10016.html b/docs/cce/umn/cce_bestpractice_10016.html
index 0f9b32e97..fdb500369 100644
--- a/docs/cce/umn/cce_bestpractice_10016.html
+++ b/docs/cce/umn/cce_bestpractice_10016.html
@@ -170,7 +170,7 @@
 </div>
 <div class="section" id="cce_bestpractice_10016__section1275621812422"><h4 class="sectiontitle">Service Forwarding Modes</h4><p id="cce_bestpractice_10016__p1954101014316">kube-proxy is a key component of a Kubernetes cluster. It is responsible for load balancing and forwarding between a Service and its backend pod.</p>
 <p id="cce_bestpractice_10016__p6616172092319">CCE supports the iptables and IPVS forwarding modes.</p>
-<ul id="cce_bestpractice_10016__ul4533122413611"><li id="cce_bestpractice_10016__li10533102418367">IPVS allows higher throughput and faster forwarding. It applies to scenarios where the cluster scale is large or the number of Services is large.</li><li id="cce_bestpractice_10016__li2533624123616">iptables is the traditional kube-proxy mode. This mode applies to the scenario where the number of Services is small or there are a large number of short concurrent connections on the client.</li></ul>
+<ul id="cce_bestpractice_10016__ul4533122413611"><li id="cce_bestpractice_10016__li10533102418367">IPVS allows higher throughput and faster forwarding. It applies to scenarios where the cluster scale is large or the number of Services is large.</li><li id="cce_bestpractice_10016__li2533624123616">Iptables: the traditional kube-proxy mode. This mode applies to the scenario where the number of Services is small or there are a large number of short concurrent connections on the client.</li></ul>
 <p id="cce_bestpractice_10016__p3412132524519">If high stability is required and the number of Services is less than 2000, the iptables forwarding mode is recommended. In other scenarios, the IPVS forwarding mode is recommended.</p>
 </div>
 <div class="section" id="cce_bestpractice_10016__section15339746192513"><h4 class="sectiontitle">Node Specifications</h4><div class="p" id="cce_bestpractice_10016__p1738116477271">The minimum specifications of a node are 2 vCPUs and 4 GiB memory. Evaluate based on service requirements before configuring the nodes. However, using many low-specification ECSs is not the optimal choice. The reasons are as follows:<ul id="cce_bestpractice_10016__ul1233904682513"><li id="cce_bestpractice_10016__li12339194642519">The upper limit of network resources is low, which may result in a single-point bottleneck.</li><li id="cce_bestpractice_10016__li23396468253">Resources may be wasted. If each container running on a low-specification node needs a lot of resources, the node cannot run multiple containers and there may be idle resources in it.</li></ul>
diff --git a/docs/cce/umn/cce_bestpractice_10024.html b/docs/cce/umn/cce_bestpractice_10024.html
index 1febfa26e..98758782b 100644
--- a/docs/cce/umn/cce_bestpractice_10024.html
+++ b/docs/cce/umn/cce_bestpractice_10024.html
@@ -55,16 +55,16 @@
 </table>
 </div>
 </div>
-<div class="section" id="cce_bestpractice_10024__section88153516598"><a name="cce_bestpractice_10024__section88153516598"></a><a name="section88153516598"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Upgrading the Cluster Version</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p47508461263">As the CCE cluster version evolves, new overload protection features and optimizations are regularly introduced. It is recommended that you promptly upgrade your clusters to the latest version. For details, see <a href="cce_10_0197.html">Process and Method of Upgrading a Cluster</a>.</p>
+<div class="section" id="cce_bestpractice_10024__section88153516598"><a name="cce_bestpractice_10024__section88153516598"></a><a name="section88153516598"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Upgrading the Cluster Version</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p47508461263">As the CCE cluster version evolves, new overload protection features and optimizations are regularly introduced. It is recommended that you promptly upgrade your clusters to the latest version. For details, see <a href="cce_10_0197.html">Process and Method of Upgrading a Cluster</a>.</p>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section1962889101"><a name="cce_bestpractice_10024__section1962889101"></a><a name="section1962889101"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Overload Control</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p15924344155820">After overload control is enabled, concurrent LIST requests outside the system will be dynamically controlled based on the resource demands received by master nodes to ensure the stable running of the master nodes and the cluster.</p>
+<div class="section" id="cce_bestpractice_10024__section1962889101"><a name="cce_bestpractice_10024__section1962889101"></a><a name="section1962889101"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Overload Control</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p15924344155820">After overload control is enabled, concurrent LIST requests outside the system will be dynamically controlled based on the resource demands received by master nodes to ensure the stable running of the master nodes and the cluster.</p>
 <p id="cce_bestpractice_10024__p42241827131420">For details, see <a href="cce_10_0602.html">Cluster Overload Control</a>.</p>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section128547158020"><a name="cce_bestpractice_10024__section128547158020"></a><a name="section128547158020"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Observability</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p57415233101">Observability is crucial for maintaining the reliability and stability of clusters. By using monitoring, alarms, and logs, administrators can gain a better understanding of the clusters' performance, promptly identify any issues, and take corrective action in a timely manner.</p>
+<div class="section" id="cce_bestpractice_10024__section128547158020"><a name="cce_bestpractice_10024__section128547158020"></a><a name="section128547158020"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Enabling Observability</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p57415233101">Observability is crucial for maintaining the reliability and stability of clusters. By using monitoring, alarms, and logs, administrators can gain a better understanding of the clusters' performance, promptly identify any issues, and take corrective action in a timely manner.</p>
 <p id="cce_bestpractice_10024__p7481401235"><strong id="cce_bestpractice_10024__b019081818243">Monitoring configurations</strong></p>
 <ul id="cce_bestpractice_10024__ul1418162311159"><li id="cce_bestpractice_10024__li73874112716">You can check the monitoring information about master nodes on the <strong id="cce_bestpractice_10024__b167134239451"><span id="cce_bestpractice_10024__text16817546195513">Overview</span></strong> page of the CCE cluster console.</li></ul>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section487713580595"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Controlling Data Volume of Resources</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p53189168012">When the resource data volume in a cluster is too large, it can negatively impact etcd performance, including data read and write latency. Additionally, if the data volume of a single type of resource is too large, the control plane consumes a significant number of resources when a client requests all the resources. To avoid these issues, it is recommended that you keep both the etcd data volume and the data volume of a single type of resources under control.</p>
+<div class="section" id="cce_bestpractice_10024__section487713580595"><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Controlling Data Volume of Resources</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p53189168012">When the resource data volume in a cluster is too large, it can negatively impact etcd performance, including data read and write latency. Additionally, if the data volume of a single type of resource is too large, the control plane consumes a significant number of resources when a client requests all the resources. To avoid these issues, it is recommended that you keep both the etcd data volume and the data volume of a single type of resources under control.</p>
 
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_bestpractice_10024__table7908153214013" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Recommended maximum etcd data volume for different cluster scales</caption><thead align="left"><tr id="cce_bestpractice_10024__row5909132409"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.8.3.2.6.1.1"><p id="cce_bestpractice_10024__p189092324019">Cluster Scale</p>
 </th>
@@ -104,9 +104,9 @@
 </table>
 </div>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section16249619707"><a name="cce_bestpractice_10024__section16249619707"></a><a name="section16249619707"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Clearing Unused Resources</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p1489119915">To prevent a large number of pending pods from consuming extra resources on the control plane, it is recommended that you promptly clear up Kubernetes resources that are no longer in use, such as ConfigMaps, Secrets, and PVCs.</p>
+<div class="section" id="cce_bestpractice_10024__section16249619707"><a name="cce_bestpractice_10024__section16249619707"></a><a name="section16249619707"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Clearing Unused Resources</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p1489119915">To prevent a large number of pending pods from consuming extra resources on the control plane, it is recommended that you promptly clear up Kubernetes resources that are no longer in use, such as ConfigMaps, Secrets, and PVCs.</p>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section203538231209"><a name="cce_bestpractice_10024__section203538231209"></a><a name="section203538231209"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Optimizing the Client Access Mode</h4></div><div class="dropdowncontext"><ul id="cce_bestpractice_10024__ul8912185222716"><li id="cce_bestpractice_10024__li8912195202717">To avoid frequent LIST queries, it is best to use the client cache mechanism when retrieving cluster resource data multiple times. It is recommended that you communicate with clusters using informers and listers. For details, see <a href="https://pkg.go.dev/k8s.io/client-go/tools/cache" target="_blank" rel="noopener noreferrer">client-go documentation</a>.<p id="cce_bestpractice_10024__p191671817111213">If a LIST query must be used, you can:</p>
+<div class="section" id="cce_bestpractice_10024__section203538231209"><a name="cce_bestpractice_10024__section203538231209"></a><a name="section203538231209"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Optimizing the Client Access Mode</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ul id="cce_bestpractice_10024__ul8912185222716"><li id="cce_bestpractice_10024__li8912195202717">To avoid frequent LIST queries, it is best to use the client cache mechanism when retrieving cluster resource data multiple times. It is recommended that you communicate with clusters using informers and listers. For details, see <a href="https://pkg.go.dev/k8s.io/client-go/tools/cache" target="_blank" rel="noopener noreferrer">client-go documentation</a>.<p id="cce_bestpractice_10024__p191671817111213">If a LIST query must be used, you can:</p>
 <ul id="cce_bestpractice_10024__ul1220143621212"><li id="cce_bestpractice_10024__li765543571211">Obtain needed data from the kube-apiserver cache first and avoid making additional queries on etcd data. For clusters earlier than v1.23.8-r0 and v1.25.3-r0, you can set <strong id="cce_bestpractice_10024__b233213464133">resourceVersion</strong> to <strong id="cce_bestpractice_10024__b8724194713135">0</strong>. In clusters of v1.23.8-r0, v1.25.3-r0, and later versions, CCE has improved the way data is retrieved and ensured that the cached data is up to date. By default, you can access the required data from the cache.</li><li id="cce_bestpractice_10024__li916104019120">Accurately define the query scope to avoid retrieving irrelevant data and using unnecessary resources. For example:<pre class="screen" id="cce_bestpractice_10024__screen13522126161311"># client-go Code example for obtaining pods in a specified namespace
 k8sClient.CoreV1().Pods("<i><span class="varname" id="cce_bestpractice_10024__varname14348135131319">&lt;your-namespace&gt;</span></i>").List(metav1.ListOptions{})
 # kubectl Command example for obtaining pods in a specified namespace
@@ -115,11 +115,11 @@ kubectl get pods -n <i><span class="varname" id="cce_bestpractice_10024__varname
 </li></ul>
 <ul id="cce_bestpractice_10024__ul14205145611278"><li id="cce_bestpractice_10024__li202050568275">Use the more efficient Protobuf format instead of the JSON format. By default, Kubernetes returns objects serialized to JSON with content type <strong id="cce_bestpractice_10024__b1129813468545">application/json</strong>. This is the default serialization format for the API. However, clients may request the more efficient Protobuf representation of these objects for better performance. For details, see <a href="https://kubernetes.io/docs/reference/using-api/api-concepts/#alternate-representations-of-resources" target="_blank" rel="noopener noreferrer">Alternate representations of resources</a>.</li></ul>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section148752272013"><a name="cce_bestpractice_10024__section148752272013"></a><a name="section148752272013"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Changing the Cluster Scale</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p188671055111615">If the resource usage on the master nodes in a cluster remains high for a long time, for example, the memory usage is greater than 85%, it is recommended that you promptly increase the cluster management scale. This will prevent the cluster from becoming overloaded during sudden traffic surges. For details, see <a href="cce_10_0403.html">Changing Cluster Scale</a>.</p>
+<div class="section" id="cce_bestpractice_10024__section148752272013"><a name="cce_bestpractice_10024__section148752272013"></a><a name="section148752272013"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Changing the Cluster Scale</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p188671055111615">If the resource usage on the master nodes in a cluster remains high for a long time, for example, the memory usage is greater than 85%, it is recommended that you promptly increase the cluster management scale. This will prevent the cluster from becoming overloaded during sudden traffic surges. For details, see <a href="cce_10_0403.html">Changing Cluster Scale</a>.</p>
 <div class="note" id="cce_bestpractice_10024__note108333358171"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_bestpractice_10024__ul4876164711175"><li id="cce_bestpractice_10024__li887734751719">The performance of the master nodes improves and their specifications become higher as the management scale of a cluster increases.</li><li id="cce_bestpractice_10024__li22514492173">The CCE cluster management scale is the maximum number of nodes that a cluster can manage. It is used as a reference during service deployment planning, and the actual quantity of nodes in use may not reach the maximum number of nodes selected. The actual scale depends on various factors, including the type, quantity, and size of resource objects in the cluster, as well as the number of external accesses to the cluster control plane.</li></ul>
 </div></div>
 </div></div></div>
-<div class="section" id="cce_bestpractice_10024__section136511410151811"><a name="cce_bestpractice_10024__section136511410151811"></a><a name="section136511410151811"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Splitting the Cluster</h4></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p302033151819">The Kubernetes architecture has a performance bottleneck, meaning that the scale of a single cluster cannot be expanded indefinitely. If your cluster has 2,000 worker nodes, it is necessary to split the services and deploy them across multiple clusters. If you encounter any issues with splitting a cluster, submit a service ticket for technical support.</p>
+<div class="section" id="cce_bestpractice_10024__section136511410151811"><a name="cce_bestpractice_10024__section136511410151811"></a><a name="section136511410151811"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Splitting the Cluster</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_bestpractice_10024__p302033151819">The Kubernetes architecture has a performance bottleneck, meaning that the scale of a single cluster cannot be expanded indefinitely. If your cluster has 2,000 worker nodes, it is necessary to split the services and deploy them across multiple clusters. If you encounter any issues with splitting a cluster, submit a service ticket for technical support.</p>
 </div></div></div>
 <div class="section" id="cce_bestpractice_10024__section14426443121815"><h4 class="sectiontitle">Summary</h4><p id="cce_bestpractice_10024__p655935013189">When running services on Kubernetes clusters, their performance and availability are influenced by various factors, including the cluster scale, number and size of resources, and resource access. CCE has optimized cluster performance and availability based on cloud native practices and has developed measures to protect against cluster overload. You can use these measures to ensure that your services run stably and reliably over the long term.</p>
 </div>
diff --git a/docs/cce/umn/cce_bulletin_0027.html b/docs/cce/umn/cce_bulletin_0027.html
index a5b80ff1d..279b86f03 100644
--- a/docs/cce/umn/cce_bulletin_0027.html
+++ b/docs/cce/umn/cce_bulletin_0027.html
@@ -1,6 +1,6 @@
 <a name="cce_bulletin_0027"></a><a name="cce_bulletin_0027"></a>
 
-<h1 class="topictitle1">Kubernetes 1.23 Release Notes</h1>
+<h1 class="topictitle1">Kubernetes 1.23 (EOM) Release Notes</h1>
 <div id="body8662426"><p id="cce_bulletin_0027__en-us_topic_0000001212381758_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">This section describes the updates in CCE Kubernetes 1.23.</p>
 <div class="section" id="cce_bulletin_0027__en-us_topic_0000001212381758_en-us_topic_0000001072975092_section51381161799"><h4 class="sectiontitle">Resource Changes and Deprecations</h4><p id="cce_bulletin_0027__en-us_topic_0000001212381758_p1185317533351"><strong id="cce_bulletin_0027__b1281791545119">Kubernetes v1.23 Release Notes</strong></p>
 <ul id="cce_bulletin_0027__en-us_topic_0000001212381758_ul14465512152614"><li id="cce_bulletin_0027__en-us_topic_0000001212381758_li194651912162616">FlexVolume is deprecated. Use CSI.</li><li id="cce_bulletin_0027__en-us_topic_0000001212381758_li1513453601318">HorizontalPodAutoscaler v2 is promoted to GA, and HorizontalPodAutoscaler API v2 is gradually stable in version 1.23. The HorizontalPodAutoscaler v2beta2 API is not recommended. Use the v2 API.</li><li id="cce_bulletin_0027__en-us_topic_0000001212381758_li868648161616"><a href="https://kubernetes.io/docs/concepts/security/pod-security-admission/" target="_blank" rel="noopener noreferrer">PodSecurity</a> moves to beta, replacing the deprecated PodSecurityPolicy. PodSecurity is an admission controller that enforces pod security standards on pods in the namespace based on specific namespace labels that set the enforcement level. PodSecurity is enabled by default in version 1.23.</li></ul>
diff --git a/docs/cce/umn/cce_bulletin_0058.html b/docs/cce/umn/cce_bulletin_0058.html
index 08803838f..b61a43074 100644
--- a/docs/cce/umn/cce_bulletin_0058.html
+++ b/docs/cce/umn/cce_bulletin_0058.html
@@ -1,6 +1,6 @@
 <a name="cce_bulletin_0058"></a><a name="cce_bulletin_0058"></a>
 
-<h1 class="topictitle1">Kubernetes 1.25 Release Notes</h1>
+<h1 class="topictitle1">Kubernetes 1.25 (EOM) Release Notes</h1>
 <div id="body8662426"><p id="cce_bulletin_0058__en-us_topic_0000001596950457_en-us_topic_0000001389397618_en-us_topic_0000001430891141_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">This section describes the changes made in Kubernetes 1.25 compared with Kubernetes 1.23.</p>
 <div class="section" id="cce_bulletin_0058__en-us_topic_0000001596950457_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0058__en-us_topic_0000001596950457_ul8733155692314"><li id="cce_bulletin_0058__en-us_topic_0000001596950457_li17733195672318"><a href="#cce_bulletin_0058__en-us_topic_0000001596950457_en-us_topic_0000001389397618_en-us_topic_0000001430891141_en-us_topic_0000001072975092_section51381161799">New Features</a></li><li id="cce_bulletin_0058__en-us_topic_0000001596950457_li148111212142418"><a href="#cce_bulletin_0058__en-us_topic_0000001596950457_section1096111394018">Deprecations and Removals</a></li><li id="cce_bulletin_0058__en-us_topic_0000001596950457_li1036516205388"><a href="#cce_bulletin_0058__en-us_topic_0000001596950457_section115291322132513">Enhanced Kubernetes 1.25 on CCE</a></li><li id="cce_bulletin_0058__en-us_topic_0000001596950457_li1076716133914"><a href="#cce_bulletin_0058__en-us_topic_0000001596950457_en-us_topic_0000001389397618_en-us_topic_0000001430891141_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
 </div>
diff --git a/docs/cce/umn/cce_bulletin_0059.html b/docs/cce/umn/cce_bulletin_0059.html
index dc5e3c0a8..52a2cd04c 100644
--- a/docs/cce/umn/cce_bulletin_0059.html
+++ b/docs/cce/umn/cce_bulletin_0059.html
@@ -1,7 +1,7 @@
 <a name="cce_bulletin_0059"></a><a name="cce_bulletin_0059"></a>
 
 <h1 class="topictitle1">Kubernetes 1.27 Release Notes</h1>
-<div id="body8662426"><p id="cce_bulletin_0059__en-us_topic_0000001649273541_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes clusters 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.</p>
+<div id="body8662426"><p id="cce_bulletin_0059__en-us_topic_0000001649273541_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes 1.27 clusters. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.</p>
 <div class="section" id="cce_bulletin_0059__en-us_topic_0000001649273541_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0059__en-us_topic_0000001649273541_ul8733155692314"><li id="cce_bulletin_0059__en-us_topic_0000001649273541_li17733195672318"><a href="#cce_bulletin_0059__en-us_topic_0000001649273541_section14972102702312">New Features</a></li><li id="cce_bulletin_0059__en-us_topic_0000001649273541_li2606144132418"><a href="#cce_bulletin_0059__en-us_topic_0000001649273541_section1898982110241">Deprecations and Removals</a></li><li id="cce_bulletin_0059__en-us_topic_0000001649273541_li1036516205388"><a href="#cce_bulletin_0059__en-us_topic_0000001649273541_section115291322132513">Enhanced Kubernetes 1.27 on CCE</a></li><li id="cce_bulletin_0059__en-us_topic_0000001649273541_li1076716133914"><a href="#cce_bulletin_0059__en-us_topic_0000001649273541_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
 </div>
 <div class="section" id="cce_bulletin_0059__en-us_topic_0000001649273541_section14972102702312"><a name="cce_bulletin_0059__en-us_topic_0000001649273541_section14972102702312"></a><a name="en-us_topic_0000001649273541_section14972102702312"></a><h4 class="sectiontitle">New Features</h4><div class="p" id="cce_bulletin_0059__en-us_topic_0000001649273541_p1404335230"><strong id="cce_bulletin_0059__en-us_topic_0000001649273541_b16877105193917">Kubernetes 1.27</strong><ul id="cce_bulletin_0059__en-us_topic_0000001649273541_ul15117105663918"><li id="cce_bulletin_0059__en-us_topic_0000001649273541_li693144814507">SeccompDefault is stable.<p id="cce_bulletin_0059__en-us_topic_0000001649273541_p877365712152"><a name="cce_bulletin_0059__en-us_topic_0000001649273541_li693144814507"></a><a name="en-us_topic_0000001649273541_li693144814507"></a>To use SeccompDefault, add the <strong id="cce_bulletin_0059__en-us_topic_0000001649273541_b396810398919">--seccomp-default</strong> <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/" target="_blank" rel="noopener noreferrer">command line flag</a> using kubelet on each node. If this feature is enabled, the <strong id="cce_bulletin_0059__en-us_topic_0000001649273541_b67611713481">RuntimeDefault</strong> profile will be used for all workloads by default, instead of the <strong id="cce_bulletin_0059__en-us_topic_0000001649273541_b137781440114314">Unconfined</strong> (seccomp disabled) profile.</p>
diff --git a/docs/cce/umn/cce_bulletin_0068.html b/docs/cce/umn/cce_bulletin_0068.html
index 37315ca56..96d0ddeb4 100644
--- a/docs/cce/umn/cce_bulletin_0068.html
+++ b/docs/cce/umn/cce_bulletin_0068.html
@@ -1,7 +1,7 @@
 <a name="cce_bulletin_0068"></a><a name="cce_bulletin_0068"></a>
 
 <h1 class="topictitle1">Kubernetes 1.28 Release Notes</h1>
-<div id="body8662426"><p id="cce_bulletin_0068__en-us_topic_0000001692158708_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes clusters 1.28. This section describes the changes made in Kubernetes 1.28.</p>
+<div id="body8662426"><p id="cce_bulletin_0068__en-us_topic_0000001692158708_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes 1.28 clusters. This section describes the changes made in Kubernetes 1.28.</p>
 <div class="section" id="cce_bulletin_0068__en-us_topic_0000001692158708_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0068__en-us_topic_0000001692158708_ul8733155692314"><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li144652242261"><a href="#cce_bulletin_0068__en-us_topic_0000001692158708_section611420132265">Important Notes</a></li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li17733195672318"><a href="#cce_bulletin_0068__en-us_topic_0000001692158708_section14972102702312">New and Enhanced Features</a></li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li142311740133412"><a href="#cce_bulletin_0068__en-us_topic_0000001692158708_section1898982110241">API Changes and Removals</a></li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li2606144132418"><a href="#cce_bulletin_0068__en-us_topic_0000001692158708_section7619242123210">Feature Gate and Command Line Parameter Changes and Removals</a></li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li1036516205388"><a href="#cce_bulletin_0068__en-us_topic_0000001692158708_section115291322132513">Enhanced Kubernetes 1.28 on CCE</a></li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li1076716133914"><a href="#cce_bulletin_0068__en-us_topic_0000001692158708_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
 </div>
 <div class="section" id="cce_bulletin_0068__en-us_topic_0000001692158708_section611420132265"><a name="cce_bulletin_0068__en-us_topic_0000001692158708_section611420132265"></a><a name="en-us_topic_0000001692158708_section611420132265"></a><h4 class="sectiontitle">Important Notes</h4><ul id="cce_bulletin_0068__en-us_topic_0000001692158708_ul59237718268"><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li223121362716">In Kubernetes 1.28, the scheduling framework is improved to reduce useless retries. The overall scheduling performance is enhanced. If a custom scheduler plugin is used in a cluster, you can perform the adaptation upgrade following instructions in <a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.28.md#no-really-you-must-read-this-before-you-upgrade" target="_blank" rel="noopener noreferrer">GitHub</a>.</li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li1939772193013">The Ceph FS in-tree plugin has been deprecated in Kubernetes 1.28 and will be removed in Kubernetes 1.31. (The community does not plan to support CSI migration.) Use <a href="https://github.com/ceph/ceph-csi" target="_blank" rel="noopener noreferrer">Ceph CSI driver</a> instead.</li><li id="cce_bulletin_0068__en-us_topic_0000001692158708_li2886314112610">The Ceph RBD in-tree plugin has been deprecated in Kubernetes 1.28 and will be removed in Kubernetes 1.31. (The community does not plan to support CSI migration.) Use RBD <a href="https://github.com/ceph/ceph-csi" target="_blank" rel="noopener noreferrer">Ceph CSI driver</a> instead.</li></ul>
diff --git a/docs/cce/umn/cce_bulletin_0089.html b/docs/cce/umn/cce_bulletin_0089.html
index 9526fa8d9..943593144 100644
--- a/docs/cce/umn/cce_bulletin_0089.html
+++ b/docs/cce/umn/cce_bulletin_0089.html
@@ -1,8 +1,8 @@
 <a name="cce_bulletin_0089"></a><a name="cce_bulletin_0089"></a>
 
 <h1 class="topictitle1">Kubernetes 1.29 Release Notes</h1>
-<div id="body8662426"><p id="cce_bulletin_0089__en-us_topic_0000001802449514_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes clusters 1.29. This section describes the changes made in Kubernetes 1.29.</p>
-<div class="section" id="cce_bulletin_0089__en-us_topic_0000001802449514_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0089__en-us_topic_0000001802449514_ul8733155692314"><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li17733195672318"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section14972102702312">New and Enhanced Features</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li142311740133412"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section1898982110241">API Changes and Removals</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1036516205388"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section115291322132513">Enhanced Kubernetes 1.29 on CCE</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1076716133914"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
+<div id="body8662426"><p id="cce_bulletin_0089__en-us_topic_0000001802449514_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes 1.29 clusters. This section describes the changes made in Kubernetes 1.29.</p>
+<div class="section" id="cce_bulletin_0089__en-us_topic_0000001802449514_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0089__en-us_topic_0000001802449514_ul8733155692314"><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li17733195672318"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section14972102702312">New and Enhanced Features</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li142311740133412"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section1898982110241">API Changes and Removals</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1157117073215"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section1280721172519">Incompatible Changes</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1036516205388"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_section115291322132513">Enhanced Kubernetes 1.29 on CCE</a></li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1076716133914"><a href="#cce_bulletin_0089__en-us_topic_0000001802449514_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
 </div>
 <div class="section" id="cce_bulletin_0089__en-us_topic_0000001802449514_section14972102702312"><a name="cce_bulletin_0089__en-us_topic_0000001802449514_section14972102702312"></a><a name="en-us_topic_0000001802449514_section14972102702312"></a><h4 class="sectiontitle">New and Enhanced Features</h4><ul id="cce_bulletin_0089__en-us_topic_0000001802449514_ul1685574486"><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li26815573481">The load balancer IP mode for Services is in the alpha state.<p id="cce_bulletin_0089__en-us_topic_0000001802449514_p1768416114919"><a name="cce_bulletin_0089__en-us_topic_0000001802449514_li26815573481"></a><a name="en-us_topic_0000001802449514_li26815573481"></a>The load balancer IP mode for Services is promoted to alpha. Kubernetes 1.29 adds the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1940165414012">ipMode</strong> field to the Services' <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1822213191615">status</strong> field for configuring traffic forwarding from Services within a cluster to pods. If <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b183690367310">ipMode</strong> is set to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b18100124314311">VIP</strong>, traffic delivered to a node with the destination set to the load balancer's IP address and port will be redirected to the target node by kube-proxy. If it is set to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1270985912416">Proxy</strong>, traffic delivered to a node will be sent to the load balancer and then redirected to the target node by the load balancer. This feature addresses the issue of load balancer functions being missed due to traffic bypassing it. For details, see <a href="https://kubernetes.io/blog/2023/12/18/kubernetes-1-29-feature-loadbalancer-ip-mode-alpha/" target="_blank" rel="noopener noreferrer">Load Balancer IP Mode for Services</a>.</p>
 </li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li768357124816">The nftables proxy mode is in the alpha state.<p id="cce_bulletin_0089__en-us_topic_0000001802449514_p860017811495"><a name="cce_bulletin_0089__en-us_topic_0000001802449514_li768357124816"></a><a name="en-us_topic_0000001802449514_li768357124816"></a>The nftables proxy mode is promoted to alpha. This feature allows kube-proxy to run in nftables mode. In this mode, kube-proxy configures packet forwarding rules using the nftables API of the kernel netfilter subsystem. For details, see <a href="https://kubernetes.io/docs/reference/networking/virtual-ips/#proxy-mode-nftables" target="_blank" rel="noopener noreferrer">nftables proxy mode</a>.</p>
@@ -32,6 +32,9 @@
 <div class="section" id="cce_bulletin_0089__en-us_topic_0000001802449514_section1898982110241"><a name="cce_bulletin_0089__en-us_topic_0000001802449514_section1898982110241"></a><a name="en-us_topic_0000001802449514_section1898982110241"></a><h4 class="sectiontitle">API Changes and Removals</h4><ul id="cce_bulletin_0089__en-us_topic_0000001802449514_ul84412420517"><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li5441042165118">The time zone of a newly created cron job cannot be configured using <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b0451817101816">TZ</strong> or <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b5221161917183">CRON_TZ</strong> in <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b69211024131810">.spec.schedule</strong>. Use <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b137132921816">.spec.timeZone</strong> instead. Cron jobs that have been created are not affected by this change.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li64444214514">The alpha API <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b5723172745816">ClusterCIDR</strong> is removed.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li844124275119">The startup parameter <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b82990269202">--authentication-config</strong> is added to kube-apiserver to specify the address of the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b119911443102013">AuthenticationConfiguration</strong> file. This startup parameter is mutually exclusive with the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b672218524200">--oidc-*</strong> startup parameter.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li145144220515">The API version <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1410763214910">kubescheduler.config.k8s.io/v1beta3</strong> of <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b19731334292">KubeSchedulerConfiguration</strong> is removed. Migrate <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b080018591498">kube-scheduler</strong> configuration files to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b9267181231013">kubescheduler.config.k8s.io/v1</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li34524216516">The CEL expressions are added to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b95538143419">v1alpha1 AuthenticationConfiguration</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1445042165110">The <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b636140103517">ServiceCIDR</strong> type is added. It allows you to dynamically configure the IP address range used by a cluster to allocate the Service ClusterIPs.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li24513423516">The startup parameters <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b51314515423">--conntrack-udp-timeout</strong> and <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1858798164213">--conntrack-udp-timeout-stream</strong> are added to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b242491417421">kube-proxy</strong>. They are options for configuring the kernel parameters <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b282043610144">nf_conntrack_udp_timeout</strong> and <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1590574220146">nf_conntrack_udp_timeout_stream</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li124516425513">Support for CEL expressions is added to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b169019521457">WebhookMatchCondition</strong> of <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b526595619512">v1alpha1 AuthenticationConfiguration</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li6455421519">The type of <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b10633145113616">PVC.spec.Resource</strong> is changed from <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1690712611372">ResourceRequirements</strong> to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b88179108379">VolumeResourceRequirements</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1445942165111"><strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b13190751144017">onPodConditions</strong> in <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b20674124764111">PodFailurePolicyRule</strong> is marked as optional.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li24534285120">The API version <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b577910011013">flowcontrol.apiserver.k8s.io/v1beta3</strong> of <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b9719521601">FlowSchema</strong> and <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b10559551509">PriorityLevelConfiguration</strong> has been promoted to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b47789263014">flowcontrol.apiserver.k8s.io/v1</strong>, and the following changes have been made:<ul id="cce_bulletin_0089__en-us_topic_0000001802449514_ul94584245115"><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li10451442135112"><strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b14104101117537">PriorityLevelConfiguration</strong>: The <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b0846184394910">.spec.limited.nominalConcurrencyShares</strong> field defaults to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b6518101500">30</strong> if the field is omitted. To ensure compatibility with 1.28 API servers, specifying an explicit <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b84339811549">0</strong> value is not allowed in the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b125505515019">v1</strong> version in 1.29. In 1.30, explicit <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b11231141165415">0</strong> values will be allowed in this field in the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1657374595413">v1</strong> API. The <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b11198720123413">flowcontrol</strong><strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b9198142023412">.apiserver.k8s.io/v1beta3</strong> APIs are deprecated and will no longer be served in 1.32.</li></ul>
 </li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1545104220511">The kube-proxy command line document is updated. kube-proxy does not bind any socket to the IP address specified by <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b34761330117">--bind-address</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li124524215515">The <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b14339754201113">selectorSpread</strong> scheduler plugin is replaced by <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b84122361220">podTopologySpread</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li145174219517">If CSI-Node-Driver is not running, NodeStageVolume calls will be retried.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li64517425511"><strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b15407105415520">ValidatingAdmissionPolicy</strong> type checking now supports CRDs. To use this feature, the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b72971646144820">ValidatingAdmissionPolicy</strong> feature gate must be enabled.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li24614205118">The startup parameter <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b182546208115">--nf-conntrack-tcp-be-liberal</strong> is added to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b10848425131111">kube-proxy</strong>. You can configure it by setting the kernel parameter <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b43275397128">nf_conntrack_tcp_be_liberal</strong>.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li6466422512">The startup parameter <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b91466515133">--init-only</strong> is added to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b19937106191318">kube-proxy</strong>. Setting the flag makes <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1442719316113">kube-proxy</strong> init container run in the privileged mode, perform its initial configuration, and then exit.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li1946342195116">The <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b44617451632">fileSystem</strong> field of container is added to the response body of CRI. It specifies the file system usage of a container. Originally, the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b23653341412">fileSystem</strong> field contains only the file system of the container images.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li134604219512">All built-in cloud providers are disabled by default. If you still need to use them, you can configure the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b182161345171417">DisableCloudProviders</strong> and <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b135665012142">DisableKubeletCloudCredentialProvider</strong> feature gates to disable or enable cloud providers.</li><li id="cce_bulletin_0089__en-us_topic_0000001802449514_li5468423516"><strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b20307718102210">--node-ips</strong> can be used in kubelet to configure IPv4/IPv6 dual-stack. If <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1236931214232">--cloud-provider</strong> is set to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1340151942311">external</strong>, you are allowed to use <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1848622110338">--node-ips</strong> to configure IPv4/IPv6 dual-stack for node IP addresses. To use <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1545495244713">--node-ips</strong>, you need to enable the <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1954162761720">CloudDualStackNodeIPs</strong> feature gate.</li></ul>
 </div>
+<div class="section" id="cce_bulletin_0089__en-us_topic_0000001802449514_section1280721172519"><a name="cce_bulletin_0089__en-us_topic_0000001802449514_section1280721172519"></a><a name="en-us_topic_0000001802449514_section1280721172519"></a><h4 class="sectiontitle">Incompatible Changes</h4><p id="cce_bulletin_0089__en-us_topic_0000001802449514_p3402151782616">In Kubernetes 1.29, the startup behavior of kube-proxy has been modified. This update allows kube-proxy to use a value smaller than the node <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b31421452125919">sysctl</strong> setting. For example, if the kernel value of <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b20949528172212">nf_conntrack_max</strong> on a node is set to <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b1949192816227">1000000</strong>, but kube-proxy calculates a value of <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b18949142810228">131072</strong>, the value <strong id="cce_bulletin_0089__en-us_topic_0000001802449514_b14949328162211">131072</strong> calculated by kube-proxy will be used.</p>
+<p id="cce_bulletin_0089__en-us_topic_0000001802449514_p91349692512">Community PR: <a href="https://github.com/kubernetes/kubernetes/pull/120448" target="_blank" rel="noopener noreferrer">https://github.com/kubernetes/kubernetes/pull/120448</a></p>
+</div>
 <div class="section" id="cce_bulletin_0089__en-us_topic_0000001802449514_section115291322132513"><a name="cce_bulletin_0089__en-us_topic_0000001802449514_section115291322132513"></a><a name="en-us_topic_0000001802449514_section115291322132513"></a><h4 class="sectiontitle">Enhanced Kubernetes 1.29 on CCE</h4><p id="cce_bulletin_0089__en-us_topic_0000001802449514_p10835173722518">During a version maintenance period, CCE periodically updates Kubernetes 1.29 and provides enhanced functions.</p>
 <p id="cce_bulletin_0089__en-us_topic_0000001802449514_p1752116404265">For details about cluster version updates, see <a href="cce_10_0405.html">Patch Versions</a>.</p>
 </div>
diff --git a/docs/cce/umn/cce_bulletin_0095.html b/docs/cce/umn/cce_bulletin_0095.html
index 9f50a9ccd..aa9917414 100644
--- a/docs/cce/umn/cce_bulletin_0095.html
+++ b/docs/cce/umn/cce_bulletin_0095.html
@@ -1,7 +1,7 @@
 <a name="cce_bulletin_0095"></a><a name="cce_bulletin_0095"></a>
 
 <h1 class="topictitle1">Kubernetes 1.30 Release Notes</h1>
-<div id="body8662426"><p id="cce_bulletin_0095__en-us_topic_0000002011393057_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes clusters 1.30. This section describes the changes made in Kubernetes 1.30.</p>
+<div id="body8662426"><p id="cce_bulletin_0095__en-us_topic_0000002011393057_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes 1.30 clusters. This section describes the changes made in Kubernetes 1.30.</p>
 <div class="section" id="cce_bulletin_0095__en-us_topic_0000002011393057_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0095__en-us_topic_0000002011393057_ul8733155692314"><li id="cce_bulletin_0095__en-us_topic_0000002011393057_li17733195672318"><a href="#cce_bulletin_0095__en-us_topic_0000002011393057_section14972102702312">New and Enhanced Features</a></li><li id="cce_bulletin_0095__en-us_topic_0000002011393057_li142311740133412"><a href="#cce_bulletin_0095__en-us_topic_0000002011393057_section1898982110241">API Changes and Removals</a></li><li id="cce_bulletin_0095__en-us_topic_0000002011393057_li1036516205388"><a href="#cce_bulletin_0095__en-us_topic_0000002011393057_section115291322132513">Enhanced Kubernetes 1.30 on CCE</a></li><li id="cce_bulletin_0095__en-us_topic_0000002011393057_li1076716133914"><a href="#cce_bulletin_0095__en-us_topic_0000002011393057_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
 </div>
 <div class="section" id="cce_bulletin_0095__en-us_topic_0000002011393057_section14972102702312"><a name="cce_bulletin_0095__en-us_topic_0000002011393057_section14972102702312"></a><a name="en-us_topic_0000002011393057_section14972102702312"></a><h4 class="sectiontitle">New and Enhanced Features</h4><ul id="cce_bulletin_0095__en-us_topic_0000002011393057_ul765217383916"><li id="cce_bulletin_0095__en-us_topic_0000002011393057_li165213813916">Webhook matching expression is in the GA state.<p id="cce_bulletin_0095__en-us_topic_0000002011393057_p897192710149"><a name="cce_bulletin_0095__en-us_topic_0000002011393057_li165213813916"></a><a name="en-us_topic_0000002011393057_li165213813916"></a>The Webhook matching expression feature is advanced to GA. This feature enables admission webhooks to be matched based on specific conditions, providing control over the triggering conditions of the webhooks in a more precise granularity. For details, see <a href="https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#matching-requests-matchConditions" target="_blank" rel="noopener noreferrer">Dynamic Admission Control</a>.</p>
diff --git a/docs/cce/umn/cce_bulletin_0099.html b/docs/cce/umn/cce_bulletin_0099.html
index b7bab5199..cb9dc5a3a 100644
--- a/docs/cce/umn/cce_bulletin_0099.html
+++ b/docs/cce/umn/cce_bulletin_0099.html
@@ -1,7 +1,7 @@
 <a name="cce_bulletin_0099"></a><a name="cce_bulletin_0099"></a>
 
 <h1 class="topictitle1">Kubernetes 1.31 Release Notes</h1>
-<div id="body8662426"><p id="cce_bulletin_0099__en-us_topic_0000002118120745_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes clusters 1.31. This section describes the changes made in Kubernetes 1.31.</p>
+<div id="body8662426"><p id="cce_bulletin_0099__en-us_topic_0000002118120745_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_p8060118">CCE allows you to create Kubernetes 1.31 clusters. This section describes the changes made in Kubernetes 1.31.</p>
 <div class="section" id="cce_bulletin_0099__en-us_topic_0000002118120745_section1391012495239"><h4 class="sectiontitle">Indexes</h4><ul id="cce_bulletin_0099__en-us_topic_0000002118120745_ul8733155692314"><li id="cce_bulletin_0099__en-us_topic_0000002118120745_li17733195672318"><a href="#cce_bulletin_0099__en-us_topic_0000002118120745_section14972102702312">New and Enhanced Features</a></li><li id="cce_bulletin_0099__en-us_topic_0000002118120745_li142311740133412"><a href="#cce_bulletin_0099__en-us_topic_0000002118120745_section1898982110241">API Changes and Removals</a></li><li id="cce_bulletin_0099__en-us_topic_0000002118120745_li1036516205388"><a href="#cce_bulletin_0099__en-us_topic_0000002118120745_section115291322132513">Enhanced Kubernetes 1.31 on CCE</a></li><li id="cce_bulletin_0099__en-us_topic_0000002118120745_li1076716133914"><a href="#cce_bulletin_0099__en-us_topic_0000002118120745_en-us_topic_0000001072975092_en-us_topic_0261805759_en-us_topic_0261793154_section1272182810583">References</a></li></ul>
 </div>
 <div class="section" id="cce_bulletin_0099__en-us_topic_0000002118120745_section14972102702312"><a name="cce_bulletin_0099__en-us_topic_0000002118120745_section14972102702312"></a><a name="en-us_topic_0000002118120745_section14972102702312"></a><h4 class="sectiontitle">New and Enhanced Features</h4><ul id="cce_bulletin_0099__en-us_topic_0000002118120745_ul765217383916"><li id="cce_bulletin_0099__en-us_topic_0000002118120745_li17374185671819">Start ordinal of StatefulSets is in the General Availability (GA) state.<p id="cce_bulletin_0099__en-us_topic_0000002118120745_p11464204195"><a name="cce_bulletin_0099__en-us_topic_0000002118120745_li17374185671819"></a><a name="en-us_topic_0000002118120745_li17374185671819"></a>StatefulSet start ordinal is advanced to GA. By default, each pod in a StatefulSet is assigned an integer ordinal from 0. With this feature, you can configure a start ordinal for each pod. For details, see <a href="https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#start-ordinal" target="_blank" rel="noopener noreferrer">Start ordinal</a>.</p>
diff --git a/docs/cce/umn/cce_bulletin_0169.html b/docs/cce/umn/cce_bulletin_0169.html
index a8403e129..40ce29ed2 100644
--- a/docs/cce/umn/cce_bulletin_0169.html
+++ b/docs/cce/umn/cce_bulletin_0169.html
@@ -4,6 +4,8 @@
 <div id="body0000001197234813"></div>
 <div>
 <ul class="ullinks">
+<li class="ulchildlink"><strong><a href="CVE-2025-23266.html">Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267)</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="cce_bulletin_0011.html">Vulnerability Fixing Policies</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="CVE-2021-4034.html">Linux Polkit Privilege Escalation Vulnerability (CVE-2021-4034)</a></strong><br>
diff --git a/docs/cce/umn/cce_faq_00020.html b/docs/cce/umn/cce_faq_00020.html
index 278886554..f289f7d93 100644
--- a/docs/cce/umn/cce_faq_00020.html
+++ b/docs/cce/umn/cce_faq_00020.html
@@ -3,7 +3,7 @@
 <h1 class="topictitle1">How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?</h1>
 <div id="body1529474173323"><div class="section" id="cce_faq_00020__section629233718586"><h4 class="sectiontitle">Did a Resource Scheduling Failure Event Occur on a Cluster Node?</h4><p id="cce_faq_00020__p770412286597"><strong id="cce_faq_00020__b116551253111">Symptom</strong></p>
 <p id="cce_faq_00020__p9326151192319">A node is running properly and has GPU resources. However, the following error information is displayed:</p>
-<p id="cce_faq_00020__p7442182515227">0/9 nodes are available: 9 insufficient nvidia.com/gpu</p>
+<p id="cce_faq_00020__p7442182515227">0/9 nodes are available: 9 insufficient nvida.com/gpu</p>
 <p id="cce_faq_00020__p11299340506"><strong id="cce_faq_00020__b84235270620713">Analysis</strong></p>
 <ol id="cce_faq_00020__ol437653629"><li id="cce_faq_00020__li3377163328">Check whether the node is attached with NVIDIA label.<p id="cce_faq_00020__p11731225312"><a name="cce_faq_00020__li3377163328"></a><a name="li3377163328"></a><span><img id="cce_faq_00020__image68028303240" src="en-us_image_0000002218818490.png"></span></p>
 <p id="cce_faq_00020__p18456509215"></p>
diff --git a/docs/cce/umn/cce_faq_00089.html b/docs/cce/umn/cce_faq_00089.html
index de42156f2..0e10669a2 100644
--- a/docs/cce/umn/cce_faq_00089.html
+++ b/docs/cce/umn/cce_faq_00089.html
@@ -1,7 +1,7 @@
 <a name="cce_faq_00089"></a><a name="cce_faq_00089"></a>
 
 <h1 class="topictitle1">Can I Create a CCE Node Without Adding a Data Disk to the Node?</h1>
-<div id="body1528256344715"><ul id="cce_faq_00089__ul3616122982210"><li id="cce_faq_00089__li17617529192217">If <span class="uicontrol" id="cce_faq_00089__uicontrol127216561277"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_faq_00089__uicontrol227255616716"><b>System Disk</b></span>, you do not need to add a data disk.</li><li id="cce_faq_00089__li14336165482216">Data disks are required if <strong id="cce_faq_00089__b278621420369">System Component Storage</strong> is set to <strong id="cce_faq_00089__b1778611143368">Data Disk</strong>.<p id="cce_faq_00089__p0734115164913">A data disk dedicated for kubelet and the container engine will be attached to a new node. By default, CCE uses LVM to manage data disks. With LVM, you can adjust the disk space ratio for different resources on a data disk.</p>
+<div id="body1528256344715"><ul id="cce_faq_00089__ul3616122982210"><li id="cce_faq_00089__li17617529192217">If <span class="uicontrol" id="cce_faq_00089__uicontrol127216561277"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_faq_00089__uicontrol227255616716"><b>System Disk</b></span>, you do not need to add a data disk.</li><li id="cce_faq_00089__li14336165482216">Data disks are required if <strong id="cce_faq_00089__b41476343581">System Component Storage</strong> is set to <strong id="cce_faq_00089__b2014783475818">Data Disk</strong>.<p id="cce_faq_00089__p0734115164913">A data disk dedicated for kubelet and the container engine will be attached to a new node. By default, CCE uses LVM to manage data disks. With LVM, you can adjust the disk space ratio for different resources on a data disk.</p>
 <p id="cce_faq_00089__p97340511492">If the data disk is uninstalled or damaged, the container engine will malfunction and the node becomes unavailable.</p>
 </li></ul>
 </div>
diff --git a/docs/cce/umn/cce_faq_00404.html b/docs/cce/umn/cce_faq_00404.html
index ad19d35f9..e48cc7e88 100644
--- a/docs/cce/umn/cce_faq_00404.html
+++ b/docs/cce/umn/cce_faq_00404.html
@@ -24,7 +24,7 @@
 </div>
 </div>
 <div class="section" id="cce_faq_00404__section87953497530"><h4 class="sectiontitle">Description</h4><p id="cce_faq_00404__p27101061677">The exit code ranges from 0 to 255.</p>
-<ul id="cce_faq_00404__ul463816101776"><li id="cce_faq_00404__li166381610975">If the exit code is 0, the container exits normally.</li><li id="cce_faq_00404__li032116421079">Generally, if the abnormal exit is caused by the program, the exit code ranges from 1 to 128. In special scenarios, the exit code ranges from 129 to 255.</li><li id="cce_faq_00404__li863815109714">When a program exits due to external interrupts, the exit code ranges from 129 to 255. When the operating system sends <a href="#cce_faq_00404__section8671210185117">an interrupt signal</a> to the program, the exist code is the interrupt signal value plus 128. For example, if the interrupt signal value of <strong id="cce_faq_00404__b0942143142615">SIGKILL</strong> is 9, the exit status code is 137 (9 + 128).</li><li id="cce_faq_00404__li163451041101">If the exist code is not in the range of 0 to 255, for example, exit(-1), the exit code is automatically converted to a value that is within this range.<p id="cce_faq_00404__p14541121514218"><a name="cce_faq_00404__li163451041101"></a><a name="li163451041101"></a>If the exist code is a positive number, the conversion formula is as follows:</p>
+<ul id="cce_faq_00404__ul463816101776"><li id="cce_faq_00404__li166381610975">If the exit code is 0, the container exits normally.</li><li id="cce_faq_00404__li032116421079">Generally, if the abnormal exit is caused by the program, the exit code ranges from 1 to 128. In special scenarios, the exit code ranges from 129 to 255.</li><li id="cce_faq_00404__li863815109714">When a program exits due to external interrupts, the exit code ranges from 129 to 255. When the operating system sends <a href="#cce_faq_00404__section8671210185117">an interrupt signal</a> to the program, the exit code is the interrupt signal value plus 128. For example, if the interrupt signal value of <strong id="cce_faq_00404__b0942143142615">SIGKILL</strong> is 9, the exit status code is 137 (9 + 128).</li><li id="cce_faq_00404__li163451041101">If the exit code is not in the range of 0 to 255, for example, exit(-1), the exit code is automatically converted to a value that is within this range.<p id="cce_faq_00404__p14541121514218"><a name="cce_faq_00404__li163451041101"></a><a name="li163451041101"></a>If the exit code is a positive number, the conversion formula is as follows:</p>
 <pre class="screen" id="cce_faq_00404__screen43528422212">code % 256</pre>
 <p id="cce_faq_00404__p776223212214">If the exit code is a negative number, the conversion formula is as follows:</p>
 <pre class="screen" id="cce_faq_00404__screen838174010215">256 - (|code| % 256)</pre>
diff --git a/docs/cce/umn/cce_faq_00468.html b/docs/cce/umn/cce_faq_00468.html
index e4430e4b2..6ac9cc6de 100644
--- a/docs/cce/umn/cce_faq_00468.html
+++ b/docs/cce/umn/cce_faq_00468.html
@@ -4,7 +4,7 @@
 <div id="body0000002033588952"><div class="section" id="cce_faq_00468__section69768441062"><h4 class="sectiontitle">Fault Locating</h4><p id="cce_faq_00468__p61260168710">CCE allows you to locate a node fault using the CCE Node Problem Detector add-on (<a href="#cce_faq_00468__section892614917315">Locating a Node Fault Using the CCE Node Problem Detector Add-on</a>). You can also refer to <a href="#cce_faq_00468__section88261201143">Locating a Node Fault by Performing a Self-Check</a> to locate the fault.</p>
 <p id="cce_faq_00468__p1259819303615">If the fault persists, submit a service ticket.</p>
 </div>
-<div class="section" id="cce_faq_00468__section892614917315"><a name="cce_faq_00468__section892614917315"></a><a name="section892614917315"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Locating a Node Fault Using the CCE Node Problem Detector Add-on</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p1826411654811">CCE provides an add-on called <span id="cce_faq_00468__ph9775240114610">CCE Node Problem Detector</span> for you to locate faults occurred with nodes. In 1.16.0 and later versions of this add-on, a large number of check items have been added. They allow you to detect the exceptions of resources and components on nodes and locate the faults.</p>
+<div class="section" id="cce_faq_00468__section892614917315"><a name="cce_faq_00468__section892614917315"></a><a name="section892614917315"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Locating a Node Fault Using the CCE Node Problem Detector Add-on</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p1826411654811">CCE provides an add-on called <span id="cce_faq_00468__ph9775240114610">CCE Node Problem Detector</span> for you to locate faults occurred with nodes. In 1.16.0 and later versions of this add-on, a large number of check items have been added. They allow you to detect the exceptions of resources and components on nodes and locate the faults.</p>
 <p id="cce_faq_00468__p176054454311">It is strongly recommended that you install this add-on or upgrade it to <strong id="cce_faq_00468__b1984518162432">version 1.16.0 or later</strong>.</p>
 <p id="cce_faq_00468__p1945213540489">With this add-on, if an exception occurs with a node, you can view the abnormal metrics on the console.</p>
 <p id="cce_faq_00468__p853511597512">You can also view the events reported by the add-on in node events and locate the faults based on the events.</p>
@@ -134,7 +134,7 @@
 </table>
 </div>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section88261201143"><a name="cce_faq_00468__section88261201143"></a><a name="section88261201143"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Locating a Node Fault by Performing a Self-Check</h4></div><div class="dropdowncontext"><div class="fignone" id="cce_faq_00468__fig1190804110428"><span class="figcap"><b>Figure 1 </b>Performing a self-check</span><br><span><img class="eddx" id="cce_faq_00468__image1613020446591" src="en-us_image_0000002253778301.png"></span></div>
+<div class="section" id="cce_faq_00468__section88261201143"><a name="cce_faq_00468__section88261201143"></a><a name="section88261201143"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Locating a Node Fault by Performing a Self-Check</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><div class="fignone" id="cce_faq_00468__fig1190804110428"><span class="figcap"><b>Figure 1 </b>Performing a self-check</span><br><span><img class="eddx" id="cce_faq_00468__image1613020446591" src="en-us_image_0000002253778301.png"></span></div>
 <ol id="cce_faq_00468__ol1628885011514"><li id="cce_faq_00468__li2028817507516">Log in to the CCE console.</li><li id="cce_faq_00468__li18288115065112">Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_faq_00468__uicontrol348251534920"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_faq_00468__b448212156497">Nodes</strong> tab.</li><li id="cce_faq_00468__li13411172517511">Locate the row containing the target node, choose <strong id="cce_faq_00468__b1807252102017">More</strong> &gt; <strong id="cce_faq_00468__b11926165402015">View YAML</strong> in the <strong id="cce_faq_00468__b21262155173">Operation</strong> column, and check the <strong id="cce_faq_00468__b188993275172">Status</strong> field of the node.<p id="cce_faq_00468__p1558416024219"><strong id="cce_faq_00468__b75846017428">The node is in the NotReady state.</strong></p>
 <ul id="cce_faq_00468__ul458411016422"><li id="cce_faq_00468__li9584007427">Check the node status and verify whether the value of <strong id="cce_faq_00468__b146564286210">PIDPressure</strong>, <strong id="cce_faq_00468__b119761530202119">DiskPressure</strong>, or <strong id="cce_faq_00468__b15363533112111">MemoryPressure</strong> becomes <strong id="cce_faq_00468__b483463432411">True</strong>. If any of them becomes <strong id="cce_faq_00468__b1554417570243">True</strong>, you can find the appropriate solution based on the exception keyword.</li><li id="cce_faq_00468__li758420020428">Check the key components on the node and the logs of these components. The key components on a node include a kubelet and the node runtime (Docker or containerd). For details, see <a href="#cce_faq_00468__section1969171115149">Checking Key Components of the Node</a>.<ul id="cce_faq_00468__ul175845018420"><li id="cce_faq_00468__li3584130134219">Check the kubelet.<p id="cce_faq_00468__p1962635910214"><a name="cce_faq_00468__li3584130134219"></a><a name="li3584130134219"></a>Check whether the kubelet and its logs are normal. If there is an exception, see <a href="#cce_faq_00468__section157165596254">Abnormal kubelet</a>.</p>
 </li><li id="cce_faq_00468__li458616064210">Check the runtime (Docker or containerd).<ul id="cce_faq_00468__ul158617054212"><li id="cce_faq_00468__li15866044211">Check the runtime of the node. If you are not sure whether the runtime is Docker or containerd, log in to the CCE console and view the runtime of the node.</li><li id="cce_faq_00468__li25867044219">If there is an exception, see <a href="#cce_faq_00468__section35411769262">Abnormal Runtime</a>.</li></ul>
@@ -149,20 +149,20 @@
 </div></div></div>
 <div class="section" id="cce_faq_00468__section133614410112"><h4 class="sectiontitle">Common Problems and Troubleshooting Methods</h4><ul id="cce_faq_00468__ul5281183312298"><li id="cce_faq_00468__li328183362918"><a href="#cce_faq_00468__section199699448112">Checking a Node</a></li><li id="cce_faq_00468__li84031758192920"><a href="#cce_faq_00468__section153218576118">Checking the Node Monitoring Data</a></li><li id="cce_faq_00468__li1254021053013"><a href="#cce_faq_00468__section519231018123">Checking the Node Events</a></li><li id="cce_faq_00468__li984371863016"><a href="#cce_faq_00468__section12601731141210">Verifying Whether the ECS Has Been Deleted or Is Faulty</a></li><li id="cce_faq_00468__li485533017306"><a href="#cce_faq_00468__section17645545111216">Verifying Whether the ECS Can Be Logged In</a></li><li id="cce_faq_00468__li156446558307"><a href="#cce_faq_00468__section48911515161316">Checking the Node Security Group</a></li><li id="cce_faq_00468__li1165055313"><a href="#cce_faq_00468__section14974183916131">Checking the Disks Attached to the Node</a></li><li id="cce_faq_00468__li15378151323113"><a href="#cce_faq_00468__section1969171115149">Checking Key Components of the Node</a></li><li id="cce_faq_00468__li146268256318"><a href="#cce_faq_00468__section9694184382315">Verifying Whether the Node DNS Address Is Properly Configured</a></li></ul>
 </div>
-<div class="section" id="cce_faq_00468__section199699448112"><a name="cce_faq_00468__section199699448112"></a><a name="section199699448112"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking a Node</h4></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol115478319121"><li id="cce_faq_00468__li9547143151211">Log in to the CCE console.</li><li id="cce_faq_00468__li14548133171220">Click the name of the target cluster to access the cluster console.</li><li id="cce_faq_00468__li354843141210">In the navigation pane, choose <strong id="cce_faq_00468__b119621624113516">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00468__b69294419357">Nodes</strong> tab, locate the row containing the unavailable node, and view its status. (If NPD 1.6.10 or a later version is installed in the cluster, you will see a message indicating that the metrics for the unavailable node are abnormal. In this case, you can move the cursor to the upper part to view the specific problem. If the add-on is not installed, you can rectify the fault by referring to the check items.)</li></ol>
+<div class="section" id="cce_faq_00468__section199699448112"><a name="cce_faq_00468__section199699448112"></a><a name="section199699448112"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking a Node</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol115478319121"><li id="cce_faq_00468__li9547143151211">Log in to the CCE console.</li><li id="cce_faq_00468__li14548133171220">Click the name of the target cluster to access the cluster console.</li><li id="cce_faq_00468__li354843141210">In the navigation pane, choose <strong id="cce_faq_00468__b119621624113516">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00468__b69294419357">Nodes</strong> tab, locate the row containing the unavailable node, and view its status. (If NPD 1.6.10 or a later version is installed in the cluster, you will see a message indicating that the metrics for the unavailable node are abnormal. In this case, you can move the cursor to the upper part to view the specific problem. If the add-on is not installed, you can rectify the fault by referring to the check items.)</li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section153218576118"><a name="cce_faq_00468__section153218576118"></a><a name="section153218576118"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Node Monitoring Data</h4></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol134189581215"><li id="cce_faq_00468__li1941817521211">Log in to the CCE console.</li><li id="cce_faq_00468__li24181255121">Click the name of the target cluster to access the cluster console.</li><li id="cce_faq_00468__li4418175131220">In the navigation pane, choose <strong id="cce_faq_00468__b7922181214378">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00468__b1925210320375">Nodes</strong> tab, locate the row containing the abnormal node, and click <strong id="cce_faq_00468__b1359717974016">Monitor</strong> in the <strong id="cce_faq_00468__b144768180404">Operation</strong> column.<p id="cce_faq_00468__p25861401426">On the top of the displayed page, click <strong id="cce_faq_00468__b104451932164010">More Monitoring Data</strong> to go to the AOM console and view historical monitoring records. If the CPU or memory usage of the node is too high, it can lead to high network latency or trigger system OOM, causing the node to be marked as unavailable.</p>
+<div class="section" id="cce_faq_00468__section153218576118"><a name="cce_faq_00468__section153218576118"></a><a name="section153218576118"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Node Monitoring Data</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol134189581215"><li id="cce_faq_00468__li1941817521211">Log in to the CCE console.</li><li id="cce_faq_00468__li24181255121">Click the name of the target cluster to access the cluster console.</li><li id="cce_faq_00468__li4418175131220">In the navigation pane, choose <strong id="cce_faq_00468__b7922181214378">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00468__b1925210320375">Nodes</strong> tab, locate the row containing the abnormal node, and click <strong id="cce_faq_00468__b1359717974016">Monitor</strong> in the <strong id="cce_faq_00468__b144768180404">Operation</strong> column.<p id="cce_faq_00468__p25861401426">On the top of the displayed page, click <strong id="cce_faq_00468__b104451932164010">More Monitoring Data</strong> to go to the AOM console and view historical monitoring records. If the CPU or memory usage of the node is too high, it can lead to high network latency or trigger system OOM, causing the node to be marked as unavailable.</p>
 </li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section519231018123"><a name="cce_faq_00468__section519231018123"></a><a name="section519231018123"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Node Events</h4></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol8442971126"><li id="cce_faq_00468__li1544210719128">Log in to the CCE console.</li><li id="cce_faq_00468__li1144212715125">Click the name of the target cluster to access the cluster console.</li><li id="cce_faq_00468__li844215711129">In the navigation pane, choose <strong id="cce_faq_00468__b76621744164115">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00468__b8662124494112">Nodes</strong> tab, locate the row containing the abnormal node, click <strong id="cce_faq_00468__b06632044124117">View Events</strong> in the <strong id="cce_faq_00468__b666313449417">Operation</strong> column, and check whether any abnormal event is reported. (The NPD add-on must be installed.)</li></ol>
+<div class="section" id="cce_faq_00468__section519231018123"><a name="cce_faq_00468__section519231018123"></a><a name="section519231018123"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Node Events</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol8442971126"><li id="cce_faq_00468__li1544210719128">Log in to the CCE console.</li><li id="cce_faq_00468__li1144212715125">Click the name of the target cluster to access the cluster console.</li><li id="cce_faq_00468__li844215711129">In the navigation pane, choose <strong id="cce_faq_00468__b76621744164115">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00468__b8662124494112">Nodes</strong> tab, locate the row containing the abnormal node, click <strong id="cce_faq_00468__b06632044124117">View Events</strong> in the <strong id="cce_faq_00468__b666313449417">Operation</strong> column, and check whether any abnormal event is reported. (The NPD add-on must be installed.)</li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section12601731141210"><a name="cce_faq_00468__section12601731141210"></a><a name="section12601731141210"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Verifying Whether the ECS Has Been Deleted or Is Faulty</h4></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol1137913379120"><li id="cce_faq_00468__li637933718128">Log in to the CCE console, click the name of the target cluster to access the cluster console, and view the name of the unavailable node.</li><li id="cce_faq_00468__li15379937111215">Log in to the ECS console, search for the node, and check the ECS status.<ul id="cce_faq_00468__ul858650114219"><li id="cce_faq_00468__li13586160194215">If the ECS has been deleted, go back to the CCE console, delete the node from the node list, and create another one.</li><li id="cce_faq_00468__li17586908421">If the ECS is stopped or frozen, restore it first. It takes about 3 minutes to restore the node.</li><li id="cce_faq_00468__li145863020426">If the ECS is faulty, restart it to rectify the fault.</li><li id="cce_faq_00468__li155866024217">If the ECS is available, rectify the fault by referring to <a href="#cce_faq_00468__section1969171115149">Checking Key Components of the Node</a>.</li></ul>
+<div class="section" id="cce_faq_00468__section12601731141210"><a name="cce_faq_00468__section12601731141210"></a><a name="section12601731141210"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Verifying Whether the ECS Has Been Deleted or Is Faulty</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol1137913379120"><li id="cce_faq_00468__li637933718128">Log in to the CCE console, click the name of the target cluster to access the cluster console, and view the name of the unavailable node.</li><li id="cce_faq_00468__li15379937111215">Log in to the ECS console, search for the node, and check the ECS status.<ul id="cce_faq_00468__ul858650114219"><li id="cce_faq_00468__li13586160194215">If the ECS has been deleted, go back to the CCE console, delete the node from the node list, and create another one.</li><li id="cce_faq_00468__li17586908421">If the ECS is stopped or frozen, restore it first. It takes about 3 minutes to restore the node.</li><li id="cce_faq_00468__li145863020426">If the ECS is faulty, restart it to rectify the fault.</li><li id="cce_faq_00468__li155866024217">If the ECS is available, rectify the fault by referring to <a href="#cce_faq_00468__section1969171115149">Checking Key Components of the Node</a>.</li></ul>
 </li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section17645545111216"><a name="cce_faq_00468__section17645545111216"></a><a name="section17645545111216"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Verifying Whether the ECS Can Be Logged In</h4></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol39924881218"><li id="cce_faq_00468__li14995482128">Log in to the ECS console.</li><li id="cce_faq_00468__li1499174817126">Check whether the node name displayed on the ECS console is the same as that on the VM and whether the password or key can be used to log in to the node.<p id="cce_faq_00468__p85871804421"><a name="cce_faq_00468__li1499174817126"></a><a name="li1499174817126"></a>If the node names are inconsistent and the password or key cannot be used to log in to the node, Cloud-Init problems occurred when the ECS was created. In this case, you can restart the node and then <strong id="cce_faq_00468__b16332131313433">submit a service ticket to the ECS personnel</strong> to locate the root cause.</p>
+<div class="section" id="cce_faq_00468__section17645545111216"><a name="cce_faq_00468__section17645545111216"></a><a name="section17645545111216"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Verifying Whether the ECS Can Be Logged In</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ol id="cce_faq_00468__ol39924881218"><li id="cce_faq_00468__li14995482128">Log in to the ECS console.</li><li id="cce_faq_00468__li1499174817126">Check whether the node name displayed on the ECS console is the same as that on the VM and whether the password or key can be used to log in to the node.<p id="cce_faq_00468__p85871804421"><a name="cce_faq_00468__li1499174817126"></a><a name="li1499174817126"></a>If the node names are inconsistent and the password or key cannot be used to log in to the node, Cloud-Init problems occurred when the ECS was created. In this case, you can restart the node and then <strong id="cce_faq_00468__b16332131313433">submit a service ticket to the ECS personnel</strong> to locate the root cause.</p>
 </li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section48911515161316"><a name="cce_faq_00468__section48911515161316"></a><a name="section48911515161316"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Node Security Group</h4></div><div class="dropdowncontext"><ul id="cce_faq_00468__ul4587201424"><li id="cce_faq_00468__li144611223191312">The node security group was changed.<ol id="cce_faq_00468__ol1599182519136"><li id="cce_faq_00468__li6991525121316">Log in to the VPC console. In the navigation pane, choose <strong id="cce_faq_00468__b11390185272518">Access Control</strong> &gt; <strong id="cce_faq_00468__b153901652172519">Security Groups</strong> and find the master node security group of the cluster.</li><li id="cce_faq_00468__li9991125191311">Search for the name of the security group that contains the cluster name and <strong id="cce_faq_00468__b158252517462">-cce-control-</strong>. The name of a master node security group is in the format of <em id="cce_faq_00468__i568645982517">cluster-name</em><strong id="cce_faq_00468__b19687145910252">-cce-control-</strong><em id="cce_faq_00468__i9687135910257">random-ID</em>.</li><li id="cce_faq_00468__li13991162511136">Check whether the security group rules have been changed. For details about security groups, see <a href="cce_faq_00265.html">How Can I Configure a Security Group Rule for a Cluster?</a></li></ol>
+<div class="section" id="cce_faq_00468__section48911515161316"><a name="cce_faq_00468__section48911515161316"></a><a name="section48911515161316"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Node Security Group</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ul id="cce_faq_00468__ul4587201424"><li id="cce_faq_00468__li144611223191312">The node security group was changed.<ol id="cce_faq_00468__ol1599182519136"><li id="cce_faq_00468__li6991525121316">Log in to the VPC console. In the navigation pane, choose <strong id="cce_faq_00468__b11390185272518">Access Control</strong> &gt; <strong id="cce_faq_00468__b153901652172519">Security Groups</strong> and find the master node security group of the cluster.</li><li id="cce_faq_00468__li9991125191311">Search for the name of the security group that contains the cluster name and <strong id="cce_faq_00468__b158252517462">-cce-control-</strong>. The name of a master node security group is in the format of <em id="cce_faq_00468__i568645982517">cluster-name</em><strong id="cce_faq_00468__b19687145910252">-cce-control-</strong><em id="cce_faq_00468__i9687135910257">random-ID</em>.</li><li id="cce_faq_00468__li13991162511136">Check whether the security group rules have been changed. For details about security groups, see <a href="cce_faq_00265.html">How Can I Configure a Security Group Rule for a Cluster?</a></li></ol>
 </li><li id="cce_faq_00468__li94482027151310">The node security group rules must contain a policy that allows the communication between the master nodes and the worker nodes.<ul id="cce_faq_00468__ul135877094218"><li id="cce_faq_00468__li1258720019428">Check whether such a security group policy is present.</li><li id="cce_faq_00468__li35871201426">When adding a node to the cluster, add the security group rules listed in <a href="#cce_faq_00468__table173615012426">Table 2</a> to the <em id="cce_faq_00468__i241752665612">cluster-name</em><strong id="cce_faq_00468__b1041772612564">-cce-control-</strong><em id="cce_faq_00468__i34186268561">random-ID</em> security group to ensure the availability of the added node. This is necessary if a secondary CIDR block is added to the VPC of the node subnet and the subnet is in the secondary CIDR block. However, if a secondary CIDR block has already been added to the VPC during cluster creation, this step is not required.</li><li id="cce_faq_00468__li1358720124214">For details about security groups, see <a href="cce_faq_00265.html">How Can I Configure a Security Group Rule for a Cluster?</a>
 <div class="tablenoborder"><a name="cce_faq_00468__table173615012426"></a><a name="table173615012426"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_faq_00468__table173615012426" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Security group rules to be added</caption><thead align="left"><tr id="cce_faq_00468__row2058719010426"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.10.2.2.1.3.2.2.4.1.1"><p id="cce_faq_00468__p858713034219">Protocol and Port</p>
 </th>
@@ -199,10 +199,10 @@
 </li></ul>
 </li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section14974183916131"><a name="cce_faq_00468__section14974183916131"></a><a name="section14974183916131"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Disks Attached to the Node</h4></div><div class="dropdowncontext"><ul id="cce_faq_00468__ul858715074217"><li id="cce_faq_00468__li5587150184216">By default, a 100-GiB data disk is attached to a node for runtime purposes. You have the option to attach additional data disks to the node if needed. If the data disk is detached or damaged, the runtime becomes abnormal and the node becomes unavailable.</li></ul>
+<div class="section" id="cce_faq_00468__section14974183916131"><a name="cce_faq_00468__section14974183916131"></a><a name="section14974183916131"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking the Disks Attached to the Node</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ul id="cce_faq_00468__ul858715074217"><li id="cce_faq_00468__li5587150184216">By default, a 100-GiB data disk is attached to a node for runtime purposes. You have the option to attach additional data disks to the node if needed. If the data disk is detached or damaged, the runtime becomes abnormal and the node becomes unavailable.</li></ul>
 <ul id="cce_faq_00468__ul65871024214"><li id="cce_faq_00468__li115871014214">You need to check whether the data disks of the node are detached from it. If they are, you are advised to create a node and delete the unavailable node. (To minimize risks, you are not advised to perform operations on the CCE nodes through the ECS console.)</li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section1969171115149"><a name="cce_faq_00468__section1969171115149"></a><a name="section1969171115149"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking Key Components of the Node</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p1058715034220"><strong id="cce_faq_00468__b1634014051215">kubelet</strong></p>
+<div class="section" id="cce_faq_00468__section1969171115149"><a name="cce_faq_00468__section1969171115149"></a><a name="section1969171115149"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Checking Key Components of the Node</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p1058715034220"><strong id="cce_faq_00468__b1634014051215">kubelet</strong></p>
 <ul id="cce_faq_00468__ul8587190134212"><li id="cce_faq_00468__li6587160114218">Check the kubelet.<p id="cce_faq_00468__p458716054217"><a name="cce_faq_00468__li6587160114218"></a><a name="li6587160114218"></a>Log in to the target node, run the following command on it, and check the kubelet:</p>
 <pre class="screen" id="cce_faq_00468__screen1451918123261">systemctl status kubelet</pre>
 <p id="cce_faq_00468__p15588607425">The following shows an example of the expected output.</p>
@@ -238,7 +238,7 @@
 </li></ul>
 </li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section9694184382315"><a name="cce_faq_00468__section9694184382315"></a><a name="section9694184382315"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Verifying Whether the Node DNS Address Is Properly Configured</h4></div><div class="dropdowncontext"><ul id="cce_faq_00468__ul1758815044214"><li id="cce_faq_00468__li15588180164212">Log in to the target node and check whether any domain name resolution failure is recorded in <strong id="cce_faq_00468__b8163191384110">/var/log/cloud-init-output.log</strong>:<pre class="screen" id="cce_faq_00468__screen1074917567275">cat /var/log/cloud-init-output.log | grep resolv</pre>
+<div class="section" id="cce_faq_00468__section9694184382315"><a name="cce_faq_00468__section9694184382315"></a><a name="section9694184382315"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Verifying Whether the Node DNS Address Is Properly Configured</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><ul id="cce_faq_00468__ul1758815044214"><li id="cce_faq_00468__li15588180164212">Log in to the target node and check whether any domain name resolution failure is recorded in <strong id="cce_faq_00468__b8163191384110">/var/log/cloud-init-output.log</strong>:<pre class="screen" id="cce_faq_00468__screen1074917567275">cat /var/log/cloud-init-output.log | grep resolv</pre>
 <p id="cce_faq_00468__p818654142816">If information similar to the following is displayed, the domain name cannot be resolved:</p>
 <pre class="screen" id="cce_faq_00468__screen64076152811">Could not resolve host: xxx ; Unknown error</pre>
 </li><li id="cce_faq_00468__li1358815034217">Ping the domain name that cannot be resolved on the node:<pre class="screen" id="cce_faq_00468__screen1954361722810">ping xxx</pre>
@@ -247,7 +247,7 @@
 </div></div></div>
 <div class="section" id="cce_faq_00468__section15662188132512"><h4 class="sectiontitle">Common Issues and Solutions</h4><ul id="cce_faq_00468__ul1017774314408"><li id="cce_faq_00468__li17177124320408"><a href="#cce_faq_00468__section7917523112516">PID Pressure</a></li><li id="cce_faq_00468__li12371105944016"><a href="#cce_faq_00468__section1587219358259">Memory Pressure</a></li><li id="cce_faq_00468__li51887132414"><a href="#cce_faq_00468__section9667492258">Disk Pressure</a></li><li id="cce_faq_00468__li12390132394119"><a href="#cce_faq_00468__section157165596254">Abnormal kubelet</a></li><li id="cce_faq_00468__li3506331104111"><a href="#cce_faq_00468__section35411769262">Abnormal Runtime</a></li><li id="cce_faq_00468__li1928854074110"><a href="#cce_faq_00468__section385318165266">Abnormal NTP</a></li><li id="cce_faq_00468__li1158351164114"><a href="#cce_faq_00468__section661117235262">Abnormal Node Restart</a></li><li id="cce_faq_00468__li8810162104211"><a href="#cce_faq_00468__section1232652917268">Abnormal Node Network</a></li><li id="cce_faq_00468__li65474914216"><a href="#cce_faq_00468__section8175154116263">Abnormal PLEG</a></li><li id="cce_faq_00468__li54451016114215"><a href="#cce_faq_00468__section2794711161910">Node Overloaded</a></li><li id="cce_faq_00468__li79491225194216"><a href="#cce_faq_00468__section26241627068">Restricted Node Scheduling with the node.kubernetes.io/route-unreachable Taint</a></li><li id="cce_faq_00468__li163410347423"><a href="#cce_faq_00468__section3736518293">Node Unavailable Due to OOM</a></li></ul>
 </div>
-<div class="section" id="cce_faq_00468__section7917523112516"><a name="cce_faq_00468__section7917523112516"></a><a name="section7917523112516"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">PID Pressure</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p1074132912284"><strong id="cce_faq_00468__b19760714114714">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section7917523112516"><a name="cce_faq_00468__section7917523112516"></a><a name="section7917523112516"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">PID Pressure</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p1074132912284"><strong id="cce_faq_00468__b19760714114714">Possible cause</strong></p>
 <p id="cce_faq_00468__p10566432142812">The pods on the node are using up a large number of PIDs, causing a shortage of available PIDs on the node. By default, CCE reserves 10% of the available PIDs for pods.</p>
 <p id="cce_faq_00468__p10883635142810"><strong id="cce_faq_00468__b665283290112550">Symptom</strong></p>
 <p id="cce_faq_00468__p1845143712817">If the number of available PIDs on a node is lower than the specified value of <strong id="cce_faq_00468__b17184135014716">pid.available</strong>, the <strong id="cce_faq_00468__b179711576711">PIDPressure</strong> of the node will be set to <strong id="cce_faq_00468__b040570288">True</strong>, resulting in the eviction of pods running on that node. For details about node eviction, see <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/" target="_blank" rel="noopener noreferrer">Node-pressure Eviction</a>.</p>
@@ -264,7 +264,7 @@ ps -eLf|awk '{print $2}' | sort -rn| head -n 1 #: Check the processes that use t
 <p id="cce_faq_00468__p13511917132915">The first column shows the number of PIDs used by each process, while the second column displays the current process IDs. You can locate the process and associated pods with the given process ID, analyze the reason for excessive PID usage, and optimize the relevant code accordingly.</p>
 </li><li id="cce_faq_00468__li196451018163016">Reduce the load of the node.</li><li id="cce_faq_00468__li835622963010">To restart the node, go to the ECS console and restart it. (<strong id="cce_faq_00468__b1664761873013">Be cautious when restarting the node because it may cause interruptions to your services.</strong>)</li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section1587219358259"><a name="cce_faq_00468__section1587219358259"></a><a name="section1587219358259"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Memory Pressure</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p5837936422"><strong id="cce_faq_00468__b555123616586">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section1587219358259"><a name="cce_faq_00468__section1587219358259"></a><a name="section1587219358259"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Memory Pressure</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p5837936422"><strong id="cce_faq_00468__b555123616586">Possible cause</strong></p>
 <p id="cce_faq_00468__p143011427218">The pods on the node are using up a large amount of memory, causing a shortage of available memory on the node. By default, the available memory of a CCE node is 100 MiB.</p>
 <p id="cce_faq_00468__p18961042922"><strong id="cce_faq_00468__b1031011292112550">Symptom</strong></p>
 <ul id="cce_faq_00468__ul6588160174211"><li id="cce_faq_00468__li185889054210">If the number of available memory resources on a node is lower than the specified value of <strong id="cce_faq_00468__b1952714181385">memory.available</strong>, the <strong id="cce_faq_00468__b552711181482">MemoryPressure</strong> of the node will be set to <strong id="cce_faq_00468__b0528018989">True</strong>, resulting in the eviction of pods running on that node. For details about node eviction, see <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/" target="_blank" rel="noopener noreferrer">Node-pressure Eviction</a>.</li><li id="cce_faq_00468__li1858820204219">If the memory of a node is not enough, the following message will show:<ul id="cce_faq_00468__ul1258870134215"><li id="cce_faq_00468__li658811044218">The value of <strong id="cce_faq_00468__b1792113558597">MemoryPressure</strong> becomes <strong id="cce_faq_00468__b182317321891">True</strong>.</li><li id="cce_faq_00468__li165884074211">When some pods on the node are evicted:<ul id="cce_faq_00468__ul55899013429"><li id="cce_faq_00468__li158914019426">You can see "The node was low on resource: memory" in the events of the evicted pods.</li><li id="cce_faq_00468__li8589130114211">You can see "attempting to reclaim memory" in the node events.</li></ul>
@@ -273,7 +273,7 @@ ps -eLf|awk '{print $2}' | sort -rn| head -n 1 #: Check the processes that use t
 <p id="cce_faq_00468__p174922018313"><strong id="cce_faq_00468__b83606242211263">Solution</strong></p>
 <ul id="cce_faq_00468__ul55891906420"><li id="cce_faq_00468__li125891107429">Check the node memory usage through the node monitoring data, identify the time when the exception occurs, and verify if there is any memory leak in the processes on the node. For details, see <a href="#cce_faq_00468__section153218576118">Checking the Node Monitoring Data</a>.</li><li id="cce_faq_00468__li35899019429">Reduce the load of the node.</li><li id="cce_faq_00468__li13589120104219">To restart the node, go to the ECS console and restart it. (<strong id="cce_faq_00468__b8610103045816">Be cautious when restarting the node because it may cause interruptions to your services.</strong>)</li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section9667492258"><a name="cce_faq_00468__section9667492258"></a><a name="section9667492258"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Disk Pressure</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p181883571867"><strong id="cce_faq_00468__b10291105612116">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section9667492258"><a name="cce_faq_00468__section9667492258"></a><a name="section9667492258"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Disk Pressure</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p181883571867"><strong id="cce_faq_00468__b10291105612116">Possible cause</strong></p>
 <div class="p" id="cce_faq_00468__p1643115211712">The root file system, image file system, or container file system on the node is consuming excessive disk space and inodes, surpassing the eviction threshold. This leads to the <strong id="cce_faq_00468__b1166111472577">nodefs.available</strong>, <strong id="cce_faq_00468__b5320850185719">nodefs.inodesFree</strong>, <strong id="cce_faq_00468__b969015316570">imagefs.available</strong>, or <strong id="cce_faq_00468__b17628155755713">imagefs.inodesFree</strong> metric met the eviction threshold, causing disk pressure. The table below shows the default values for these parameters.
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_faq_00468__table533154622515" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_faq_00468__row3301846172516"><th align="left" class="cellrowborder" valign="top" width="38.41%" id="mcps1.3.17.3.5.1.4.1.1"><p id="cce_faq_00468__p10305464254">Parameter</p>
 </th>
@@ -322,7 +322,7 @@ ps -eLf|awk '{print $2}' | sort -rn| head -n 1 #: Check the processes that use t
 <p id="cce_faq_00468__p959018044211"><strong id="cce_faq_00468__b34045676611263">Solution</strong></p>
 <ul id="cce_faq_00468__ul859010094217"><li id="cce_faq_00468__li1459014064213">View the node disk usage through the node monitoring data, identify the time when the exception occurs, and check if processes on the node are consuming excessive disk space. For details, see <a href="#cce_faq_00468__section153218576118">Checking the Node Monitoring Data</a>.</li><li id="cce_faq_00468__li2059014004214">If a large number of files are not deleted from the node disks, delete these files.</li><li id="cce_faq_00468__li259013014211">Restrict the ephemeral-storage configurations of the pods based on service requirements.</li><li id="cce_faq_00468__li359090164217">Use cloud storage services instead of hostPath volumes.</li><li id="cce_faq_00468__li759016014220">Expand the capacity of the node disks. </li><li id="cce_faq_00468__li2059060134218">Reduce the load of the node.</li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section157165596254"><a name="cce_faq_00468__section157165596254"></a><a name="section157165596254"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal kubelet</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p259011019421"><strong id="cce_faq_00468__b562910219297">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section157165596254"><a name="cce_faq_00468__section157165596254"></a><a name="section157165596254"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal kubelet</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p259011019421"><strong id="cce_faq_00468__b562910219297">Possible cause</strong></p>
 <p id="cce_faq_00468__p1259070204219">The kubelet process is not functioning properly or the kubelet configuration is improper. Typically, CCE has set up health checks for kubelet as a default configuration. There is a greater chance of startup failure if the configuration is incorrect.</p>
 <p id="cce_faq_00468__p75905018422"><strong id="cce_faq_00468__b2112445004112550">Symptom</strong></p>
 <p id="cce_faq_00468__p288015325813">kubelet is inactive.</p>
@@ -334,7 +334,7 @@ ps -eLf|awk '{print $2}' | sort -rn| head -n 1 #: Check the processes that use t
 </li></ol>
 <p id="cce_faq_00468__p125904034210"></p>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section35411769262"><a name="cce_faq_00468__section35411769262"></a><a name="section35411769262"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal Runtime</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p659015011423"><strong id="cce_faq_00468__b45781103110">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section35411769262"><a name="cce_faq_00468__section35411769262"></a><a name="section35411769262"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal Runtime</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p659015011423"><strong id="cce_faq_00468__b45781103110">Possible cause</strong></p>
 <p id="cce_faq_00468__p1059017012429">The Docker or containerd configuration or process is not functioning properly.</p>
 <p id="cce_faq_00468__p75907074211"><strong id="cce_faq_00468__b1337991894112550">Symptom</strong></p>
 <ul id="cce_faq_00468__ul85903034218"><li id="cce_faq_00468__li195901008426">Docker<ul id="cce_faq_00468__ul1959080144217"><li id="cce_faq_00468__li05903013422">Docker is inactive.</li><li id="cce_faq_00468__li185901034212">Docker is active and running, but the node is experiencing issues and not functioning properly, resulting in abnormal behavior. In this case, the <strong id="cce_faq_00468__b45909258517">docker ps</strong> or <strong id="cce_faq_00468__b639616281958">docker exec</strong> command fails to be executed.</li><li id="cce_faq_00468__li1559020194213">The value of <strong id="cce_faq_00468__b1549614581777">RuntimeOffline</strong> of the node becomes <strong id="cce_faq_00468__b7496258877">True</strong>.</li></ul>
@@ -355,7 +355,7 @@ journalctl -u docker
 journalctl -u containerd</pre>
 </li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section385318165266"><a name="cce_faq_00468__section385318165266"></a><a name="section385318165266"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal NTP</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p259018034217"><strong id="cce_faq_00468__b1278916251725">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section385318165266"><a name="cce_faq_00468__section385318165266"></a><a name="section385318165266"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal NTP</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p259018034217"><strong id="cce_faq_00468__b1278916251725">Possible cause</strong></p>
 <p id="cce_faq_00468__p135904014219">The NTP process is abnormal.</p>
 <p id="cce_faq_00468__p165902002429"><strong id="cce_faq_00468__b1155895278112550">Symptom</strong></p>
 <ul id="cce_faq_00468__ul155908084219"><li id="cce_faq_00468__li1259012034212">chronyd is inactive.</li><li id="cce_faq_00468__li9590190144216">The value of <strong id="cce_faq_00468__b8212162710713">NTPProblem</strong> becomes <strong id="cce_faq_00468__b8901203215716">True</strong>.</li></ul>
@@ -365,7 +365,7 @@ journalctl -u containerd</pre>
 </li><li id="cce_faq_00468__li13460122481119">If the chronyd status is still abnormal after the restart, log in to the node and view the chronyd logs:<pre class="screen" id="cce_faq_00468__screen84434018119">journalctl -u chronyd</pre>
 </li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section661117235262"><a name="cce_faq_00468__section661117235262"></a><a name="section661117235262"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal Node Restart</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p115901005422"><strong id="cce_faq_00468__b1664919142914">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section661117235262"><a name="cce_faq_00468__section661117235262"></a><a name="section661117235262"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal Node Restart</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p115901005422"><strong id="cce_faq_00468__b1664919142914">Possible cause</strong></p>
 <p id="cce_faq_00468__p25908011426">The node is experiencing abnormal load.</p>
 <p id="cce_faq_00468__p7590908426"><strong id="cce_faq_00468__b1499834012112550">Symptom</strong></p>
 <p id="cce_faq_00468__p7328155391118">During the restart, the node is in the <strong id="cce_faq_00468__b1278313321499">NotReady</strong> state.</p>
@@ -375,7 +375,7 @@ journalctl -u containerd</pre>
 <p id="cce_faq_00468__p5113121420128"><span><img id="cce_faq_00468__image5739142818390" src="en-us_image_0000002218818398.png"></span></p>
 </li><li id="cce_faq_00468__li15429163461217">View the node monitoring data and locate the abnormal resource based on the restart time of the node. For details, see <a href="#cce_faq_00468__section153218576118">Checking the Node Monitoring Data</a>.</li><li id="cce_faq_00468__li2277113681220">Check the kernel logs and locate the fault based on the restart time.</li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section1232652917268"><a name="cce_faq_00468__section1232652917268"></a><a name="section1232652917268"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal Node Network</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p55911302426"><strong id="cce_faq_00468__b199135511018">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section1232652917268"><a name="cce_faq_00468__section1232652917268"></a><a name="section1232652917268"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal Node Network</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p55911302426"><strong id="cce_faq_00468__b199135511018">Possible cause</strong></p>
 <p id="cce_faq_00468__p1959130174219">The node is experiencing abnormal running status, incorrect security group configuration, or excessive network load.</p>
 <p id="cce_faq_00468__p1059130134218"><strong id="cce_faq_00468__b329081169112550">Symptom</strong></p>
 <ul id="cce_faq_00468__ul85911084216"><li id="cce_faq_00468__li6591130184217">The node cannot be logged in to.</li><li id="cce_faq_00468__li125911700427">The node is in the <strong id="cce_faq_00468__b6228161061119">Unknown</strong> state.</li></ul>
@@ -384,7 +384,7 @@ journalctl -u containerd</pre>
 </li><li id="cce_faq_00468__li959118015423">If the network load of the node is too high, perform the following operations:<ul id="cce_faq_00468__ul359113018424"><li id="cce_faq_00468__li159117054212">View the node networking through the node monitoring data and check whether the pods on the node are consuming excessive network bandwidth.</li><li id="cce_faq_00468__li559190154214">Use network policies to control network traffic of the pods on the node. </li></ul>
 </li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section8175154116263"><a name="cce_faq_00468__section8175154116263"></a><a name="section8175154116263"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal PLEG</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p159150194212"><strong id="cce_faq_00468__b204163619123">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section8175154116263"><a name="cce_faq_00468__section8175154116263"></a><a name="section8175154116263"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Abnormal PLEG</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p159150194212"><strong id="cce_faq_00468__b204163619123">Possible cause</strong></p>
 <p id="cce_faq_00468__p85911709427">The pod lifecycle event generator (PLEG) records different events in the lifecycle of a pod, such as the pod startup and termination. The error "PLEG is not healthy" is usually due to abnormal runtime processes on the node or issues with the systemd version on the node.</p>
 <p id="cce_faq_00468__p75911609426"><strong id="cce_faq_00468__b131323741112550">Symptom</strong></p>
 <ul id="cce_faq_00468__ul12591170184215"><li id="cce_faq_00468__li1559110084214">The node is in the <strong id="cce_faq_00468__b2739172535513">NotReady</strong> state.</li><li id="cce_faq_00468__li1591190164216">You can see the following information in the kubelet logs:<pre class="screen" id="cce_faq_00468__screen27671811173212">skipping pod synchronization - PLEG is not healthy: pleg was last seen active 3m17.028393648s ago; threshold is 3m0s.</pre>
@@ -392,7 +392,7 @@ journalctl -u containerd</pre>
 <p id="cce_faq_00468__p16591190104210"><strong id="cce_faq_00468__b57794596311263">Solution</strong></p>
 <ul id="cce_faq_00468__ul159111016423"><li id="cce_faq_00468__li1059112014423">Restart Docker or containerd and kubelet in sequence and then check whether the node is restored.</li><li id="cce_faq_00468__li459119012424">If the node is not restored after the restart of the key components, restart the node. (<strong id="cce_faq_00468__b185201936105614">Be cautious when restarting the node because it may cause interruptions to your services.</strong>)</li></ul>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section2794711161910"><a name="cce_faq_00468__section2794711161910"></a><a name="section2794711161910"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Node Overloaded</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p18455510193"><strong id="cce_faq_00468__b117013579569">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section2794711161910"><a name="cce_faq_00468__section2794711161910"></a><a name="section2794711161910"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Node Overloaded</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p18455510193"><strong id="cce_faq_00468__b117013579569">Possible cause</strong></p>
 <p id="cce_faq_00468__p1084516531916">The node resources are not enough for pod scheduling.</p>
 <p id="cce_faq_00468__p19845457193"><strong id="cce_faq_00468__b485927456112550">Symptom</strong></p>
 <div class="p" id="cce_faq_00468__p1400111332011">If there are not enough scheduling resources available on the node, pod scheduling will fail and the following error information will be displayed: (Only errors related to common resources are listed.)<ul id="cce_faq_00468__ul17845359191"><li id="cce_faq_00468__li17845145161916">Insufficient CPUs in a cluster: 0/2 nodes are available: 2 Insufficient cpu</li><li id="cce_faq_00468__li14845259198">Insufficient memory in a cluster: 0/2 nodes are available: 2 Insufficient memory</li><li id="cce_faq_00468__li12845653193">Insufficient temporary storage space in a cluster: 0/2 nodes are available: 2 Insufficient ephemeral-storage</li></ul>
@@ -429,7 +429,7 @@ Allocated resources:
 <div class="p" id="cce_faq_00468__p31110792111">If the resources on a node are not enough for pod scheduling, reduce the node load through either of the following ways:<ul id="cce_faq_00468__ul284820515191"><li id="cce_faq_00468__li11846155171914">Delete unnecessary pods.</li><li id="cce_faq_00468__li1284865121917">Restrict the resource configurations of pods based on service requirements.</li><li id="cce_faq_00468__li168488541910">Add more nodes to the cluster.</li></ul>
 </div>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section26241627068"><a name="cce_faq_00468__section26241627068"></a><a name="section26241627068"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Restricted Node Scheduling with the node.kubernetes.io/route-unreachable Taint</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p1399335158"><strong id="cce_faq_00468__b206771311105515">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section26241627068"><a name="cce_faq_00468__section26241627068"></a><a name="section26241627068"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Restricted Node Scheduling with the node.kubernetes.io/route-unreachable Taint</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p1399335158"><strong id="cce_faq_00468__b206771311105515">Possible cause</strong></p>
 <p id="cce_faq_00468__p323954917713">The network infrastructure's route tables allow the container networks in a cluster that uses the VPC network model to be accessible. A newly created CCE node has network isolation support. If the node network is not functioning properly, the system will automatically add the <strong id="cce_faq_00468__b87831335101718">node.kubernetes.io/route-unreachable</strong> taint to the node and remove it once the network is ready. If the <strong id="cce_faq_00468__b515735013185">node.kubernetes.io/route-unreachable</strong> taint remains for an extended period, it indicates abnormal network connectivity for the node.</p>
 <p id="cce_faq_00468__p63034721615"><strong id="cce_faq_00468__b71111565517">Symptom</strong></p>
 <p id="cce_faq_00468__p1586492162">A newly created node is <span class="uicontrol" id="cce_faq_00468__uicontrol4989142710163"><b>restricted for scheduling</b></span> for a long time.</p>
@@ -464,7 +464,7 @@ spec:
 <p id="cce_faq_00468__p12575710912">After the container is started, log in to another normal node and ping the IP address of the container. If the communication is abnormal, go to the next step.</p>
 </p></li><li id="cce_faq_00468__li5352354196"><span>On the <strong id="cce_faq_00468__b9786192918229">Route Tables</strong> page of the VPC console, check whether the node route has been added, whether the next hop type is cloud container, and whether the next hop is the node name. If the node route is present in the route table but the node is still unable to connect to the network, it suggests a potential problem with the underlying network. In such situations, submit a service ticket to the networking team for assistance.</span></li><li id="cce_faq_00468__li15970133711135"><span>If the fault persists, submit a service ticket to CCE for troubleshooting.</span></li></ol>
 </div></div></div>
-<div class="section" id="cce_faq_00468__section3736518293"><a name="cce_faq_00468__section3736518293"></a><a name="section3736518293"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Node Unavailable Due to OOM</h4></div><div class="dropdowncontext"><p id="cce_faq_00468__p92651850346"><strong id="cce_faq_00468__b9936111711617">Possible cause</strong></p>
+<div class="section" id="cce_faq_00468__section3736518293"><a name="cce_faq_00468__section3736518293"></a><a name="section3736518293"></a><div class="dropdownexpand"><div class="dropdowntitle" onclick="ExpandorCollapseNode(this)"><h4 class="sectiontitle">Node Unavailable Due to OOM</h4></div><div class="dropdowncontext"></div><div class="dropdowncontext"><p id="cce_faq_00468__p92651850346"><strong id="cce_faq_00468__b9936111711617">Possible cause</strong></p>
 <p id="cce_faq_00468__p1767105123017">Many containers are scheduled onto a node, using up all its resources and causing an OOM issue. This issue is primarily seen on nodes running the Docker container engine.</p>
 <p id="cce_faq_00468__p121681149134119"><strong id="cce_faq_00468__b117682011370">Symptom</strong></p>
 <p id="cce_faq_00468__p067115511301">If a node in the cluster is assigned too many containers, the node OS might crash, rendering the node unavailable. You may see the information similar to the following after logging in to the node with VNC.</p>
diff --git a/docs/cce/umn/cce_productdesc_0002.html b/docs/cce/umn/cce_productdesc_0002.html
index 64de2ef6d..5e080f88b 100644
--- a/docs/cce/umn/cce_productdesc_0002.html
+++ b/docs/cce/umn/cce_productdesc_0002.html
@@ -411,8 +411,8 @@
 </div>
 </div>
 <div class="section" id="cce_productdesc_0002__section54736241399"><a name="cce_productdesc_0002__section54736241399"></a><a name="section54736241399"></a><h4 class="sectiontitle">Namespace-level Permissions (Assigned by Using Kubernetes RBAC)</h4><p id="cce_productdesc_0002__p293018587113">You can regulate users' or user groups' access to Kubernetes resources in a single namespace based on their Kubernetes RBAC roles. The RBAC API declares four kinds of Kubernetes objects: Role, ClusterRole, RoleBinding, and ClusterRoleBinding, which are described as follows:</p>
-<ul id="cce_productdesc_0002__ul1051101311020"><li id="cce_productdesc_0002__en-us_topic_0249851132_li1481515491386">Role: defines a set of rules for accessing Kubernetes resources in a namespace.</li><li id="cce_productdesc_0002__en-us_topic_0249851132_li1224120528819">RoleBinding: defines the relationship between users and roles.</li><li id="cce_productdesc_0002__en-us_topic_0249851132_li11770153233818">ClusterRole: defines a set of rules for accessing Kubernetes resources in a cluster (including all namespaces).</li><li id="cce_productdesc_0002__en-us_topic_0249851132_li15813127781">ClusterRoleBinding: defines the relationship between users and cluster roles.</li></ul>
-<p id="cce_productdesc_0002__p13511813111010">Role and ClusterRole specify actions that can be performed on specific resources. RoleBinding and ClusterRoleBinding bind roles to specific users, user groups, or ServiceAccounts. See the following figure.</p>
+<ul id="cce_productdesc_0002__ul1051101311020"><li id="cce_productdesc_0002__en-us_topic_0249851132_li1481515491386">Roles: define a set of rules for accessing Kubernetes resources in a namespace.</li><li id="cce_productdesc_0002__en-us_topic_0249851132_li1224120528819">RoleBindings: define the relationship between users and roles.</li><li id="cce_productdesc_0002__en-us_topic_0249851132_li11770153233818">ClusterRoles: define a set of rules for accessing Kubernetes resources in a cluster (including all namespaces).</li><li id="cce_productdesc_0002__en-us_topic_0249851132_li15813127781">ClusterRoleBindings: define the relationship between users and cluster roles.</li></ul>
+<p id="cce_productdesc_0002__p13511813111010">Roles and ClusterRoles specify actions that can be performed on specific resources. RoleBindings and ClusterRoleBindings bind Roles to specific users, user groups, or service accounts.</p>
 <div class="fignone" id="cce_productdesc_0002__fig1751131311103"><span class="figcap"><b>Figure 1 </b>Role binding</span><br><span><img id="cce_productdesc_0002__en-us_topic_0249851132_image19499911182110" src="en-us_image_0261301557.png"></span></div>
 <div class="p" id="cce_productdesc_0002__p18544162681014">On the CCE console, you can assign permissions to a user or user group to access resources in one or multiple namespaces. By default, the CCE console provides the following ClusterRoles:<ul id="cce_productdesc_0002__cce_10_0189_en-us_topic_0084600596_ul12544126191012"><li id="cce_productdesc_0002__cce_10_0189_en-us_topic_0084600596_li1754413268102">view (read-only): read-only permissions on most resources in all or selected namespaces.</li><li id="cce_productdesc_0002__cce_10_0189_en-us_topic_0084600596_li15545182611109">edit (development): read-write permissions on most resources in all or selected namespaces. If this ClusterRole is configured for all namespaces, its capability is the same as the O&amp;M permission.</li><li id="cce_productdesc_0002__cce_10_0189_en-us_topic_0084600596_li14545926101013">admin (O&amp;M): read and write permissions on most resources in all namespaces, and read-only permission on nodes, storage volumes, namespaces, and quota management.</li><li id="cce_productdesc_0002__cce_10_0189_en-us_topic_0084600596_li10545926201011">cluster-admin (administrator): read and write permissions on all resources in all namespaces.</li><li id="cce_productdesc_0002__cce_10_0189_li19771313143717">drainage-editor: drain a node.</li><li id="cce_productdesc_0002__cce_10_0189_li20758163163711">drainage-viewer: view the nodal drainage status but cannot drain a node.</li></ul>
 </div>
diff --git a/docs/cce/umn/cce_productdesc_0003.html b/docs/cce/umn/cce_productdesc_0003.html
index 2c88a440f..ad5645ebf 100644
--- a/docs/cce/umn/cce_productdesc_0003.html
+++ b/docs/cce/umn/cce_productdesc_0003.html
@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Product Advantages</h1>
 <div id="body1511166745671"><div class="section" id="cce_productdesc_0003__section2011513952"><h4 class="sectiontitle">Why CCE?</h4><p id="cce_productdesc_0003__p118653920810">CCE is a container service developed on Docker and Kubernetes. It offers a wide range of features that allow you to run containers on a large scale. CCE containers are highly reliable, have high-performance, and compatible with open-source communities, making them an ideal choice for enterprise needs.</p>
 <p id="cce_productdesc_0003__p717691813612"><strong id="cce_productdesc_0003__b16215635">Easy to Use</strong></p>
-<ul id="cce_productdesc_0003__ul998916336618"><li id="cce_productdesc_0003__li1397163413267">Creating CCE clusters (CCE standard, CCE Turbo, and CCE Autopilot) is a breeze with just a few clicks on the web page. You can deploy VMs in a cluster.</li><li id="cce_productdesc_0003__li203191536152617">CCE automates deployment and O&amp;M of containerized applications throughout their lifecycle.</li><li id="cce_productdesc_0003__li14166163852618">You can resize clusters and workloads by setting auto scaling policies. In-the-moment load spikes are no longer headaches.</li><li id="cce_productdesc_0003__li1687104019261">The console walks you through the steps to upgrade Kubernetes clusters.</li><li id="cce_productdesc_0003__li899011331261">CCE seamlessly integrates with Helm charts and add-ons to provide an out-of-the-box user experience.</li></ul>
+<ul id="cce_productdesc_0003__ul998916336618"><li id="cce_productdesc_0003__li1397163413267">Creating CCE clusters (including CCE standard and Turbo clusters) is a breeze with just a few clicks on the web page. You can deploy VMs in a cluster.</li><li id="cce_productdesc_0003__li203191536152617">CCE automates deployment and O&amp;M of containerized applications throughout their lifecycle.</li><li id="cce_productdesc_0003__li14166163852618">You can resize clusters and workloads by setting auto scaling policies. In-the-moment load spikes are no longer headaches.</li><li id="cce_productdesc_0003__li1687104019261">The console walks you through the steps to upgrade Kubernetes clusters.</li><li id="cce_productdesc_0003__li899011331261">CCE seamlessly integrates with Helm charts and add-ons to provide an out-of-the-box user experience.</li></ul>
 <p id="cce_productdesc_0003__p09271040665"><strong id="cce_productdesc_0003__b1961017591683">High Performance</strong></p>
 <ul id="cce_productdesc_0003__ul138394295913"><li id="cce_productdesc_0003__li429883519152">CCE draws on years of field experience in compute, networking, storage, and heterogeneous infrastructure and provides you high-performance cluster services. You can concurrently launch containers at scale.</li><li id="cce_productdesc_0003__li173831142185916">AI computing is 3x to 5x better with NUMA BMSs and high-speed InfiniBand network cards.</li></ul>
 <p id="cce_productdesc_0003__p124596219711"><strong id="cce_productdesc_0003__b92661562287">Highly Available and Secure</strong></p>
diff --git a/docs/cce/umn/cce_productdesc_0005.html b/docs/cce/umn/cce_productdesc_0005.html
index 1ba0cba77..aa1547802 100644
--- a/docs/cce/umn/cce_productdesc_0005.html
+++ b/docs/cce/umn/cce_productdesc_0005.html
@@ -68,7 +68,7 @@
 <tr id="cce_productdesc_0005__cce_10_0059_row19522163363014"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.2.3.1.1.4.1.1 mcps1.3.3.2.3.1.1.4.2.1 "><p id="cce_productdesc_0005__cce_10_0059_p14522113320305">Supported OS</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.2.3.1.1.4.1.2 mcps1.3.3.2.3.1.1.4.2.2 "><p id="cce_productdesc_0005__cce_10_0059_p36942011103714">EulerOS</p>
-<p id="cce_productdesc_0005__cce_10_0059_p8522163311308">HCE 2.0</p>
+<p id="cce_productdesc_0005__cce_10_0059_p8522163311308">HCE OS 2.0</p>
 </td>
 <td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.3.2.3.1.1.4.1.3 mcps1.3.3.2.3.1.1.4.2.3 "><p id="cce_productdesc_0005__cce_10_0059_p45221033113015">HCE OS 2.0</p>
 </td>
diff --git a/docs/cce/umn/en-us_image_0000002218820614.png b/docs/cce/umn/en-us_image_0000002218820614.png
deleted file mode 100644
index 9e12041d4..000000000
Binary files a/docs/cce/umn/en-us_image_0000002218820614.png and /dev/null differ
diff --git a/docs/cce/umn/en-us_image_0000002365047420.png b/docs/cce/umn/en-us_image_0000002365047420.png
new file mode 100644
index 000000000..64702c0ad
Binary files /dev/null and b/docs/cce/umn/en-us_image_0000002365047420.png differ
diff --git a/docs/cce/umn/en-us_image_0258392378.png b/docs/cce/umn/en-us_image_0258392378.png
index f0282b314..19286cd5f 100644
Binary files a/docs/cce/umn/en-us_image_0258392378.png and b/docs/cce/umn/en-us_image_0258392378.png differ
diff --git a/docs/cce/umn/en-us_image_0261301557.png b/docs/cce/umn/en-us_image_0261301557.png
index 35845e128..0678930e6 100644
Binary files a/docs/cce/umn/en-us_image_0261301557.png and b/docs/cce/umn/en-us_image_0261301557.png differ
diff --git a/docs/cce/umn/en-us_image_0262051194.png b/docs/cce/umn/en-us_image_0262051194.png
index bfa5d1f87..5eb51260f 100644
Binary files a/docs/cce/umn/en-us_image_0262051194.png and b/docs/cce/umn/en-us_image_0262051194.png differ