From af58d555be01b68ebd56321efd0f2539ca4a3612 Mon Sep 17 00:00:00 2001 From: Oliver Date: Thu, 20 Mar 2025 09:48:56 +0000 Subject: [PATCH] Reuploading changes from cce_umn_20250311 due to gitea bug --- docs/cce/umn/ALL_META.TXT.json | 1411 +++++----- docs/cce/umn/CLASS.TXT.json | 2480 +++++++++-------- docs/cce/umn/cce_01_0300.html | 30 +- docs/cce/umn/cce_10_0003.html | 2 +- docs/cce/umn/cce_10_0012.html | 2 +- docs/cce/umn/cce_10_0026.html | 6 +- docs/cce/umn/cce_10_0028.html | 30 +- docs/cce/umn/cce_10_0034.html | 2 +- docs/cce/umn/cce_10_0066.html | 2 +- docs/cce/umn/cce_10_0111.html | 2 + docs/cce/umn/cce_10_0125.html | 2 +- docs/cce/umn/cce_10_0129.html | 14 +- docs/cce/umn/cce_10_0132.html | 8 +- docs/cce/umn/cce_10_0141.html | 8 +- docs/cce/umn/cce_10_0150.html | 2 - docs/cce/umn/cce_10_0154.html | 26 +- docs/cce/umn/cce_10_0182.html | 2 + docs/cce/umn/cce_10_0193.html | 12 +- docs/cce/umn/cce_10_0198.html | 2 +- docs/cce/umn/cce_10_0205.html | 12 +- docs/cce/umn/cce_10_0212.html | 9 +- docs/cce/umn/cce_10_0213.html | 12 +- docs/cce/umn/cce_10_0240.html | 4 +- docs/cce/umn/cce_10_0277.html | 5 + docs/cce/umn/cce_10_0307.html | 4 + docs/cce/umn/cce_10_0337.html | 6 +- docs/cce/umn/cce_10_0342.html | 12 +- docs/cce/umn/cce_10_0363.html | 2 +- docs/cce/umn/cce_10_0364.html | 4 +- docs/cce/umn/cce_10_0378.html | 4 +- docs/cce/umn/cce_10_0380.html | 1 + docs/cce/umn/cce_10_0384.html | 2 +- docs/cce/umn/cce_10_0385.html | 2 +- docs/cce/umn/cce_10_0405.html | 132 +- docs/cce/umn/cce_10_0406.html | 6 +- docs/cce/umn/cce_10_0416.html | 177 ++ docs/cce/umn/cce_10_0476.html | 10 +- docs/cce/umn/cce_10_0553.html | 6 + docs/cce/umn/cce_10_0554.html | 67 + docs/cce/umn/cce_10_0555.html | 83 + docs/cce/umn/cce_10_0557.html | 5 +- docs/cce/umn/cce_10_0605.html | 4 +- docs/cce/umn/cce_10_0616.html | 2 +- docs/cce/umn/cce_10_0617.html | 44 + docs/cce/umn/cce_10_0619.html | 343 ++- docs/cce/umn/cce_10_0620.html | 129 +- docs/cce/umn/cce_10_0624.html | 2 +- docs/cce/umn/cce_10_0652.html | 102 +- docs/cce/umn/cce_10_0653.html | 6 +- docs/cce/umn/cce_10_0659.html | 4 +- docs/cce/umn/cce_10_0695.html | 2 +- docs/cce/umn/cce_10_0704.html | 2 +- docs/cce/umn/cce_10_0705.html | 2 + docs/cce/umn/cce_10_0782.html | 2 +- docs/cce/umn/cce_10_0787.html | 2 +- docs/cce/umn/cce_10_0792.html | 52 + docs/cce/umn/cce_10_0793.html | 57 + docs/cce/umn/cce_10_0799.html | 15 + docs/cce/umn/cce_10_0809.html | 65 + docs/cce/umn/cce_10_0836.html | 2 +- docs/cce/umn/cce_10_0864.html | 2 +- docs/cce/umn/cce_10_0908.html | 2 + docs/cce/umn/cce_10_0914.html | 143 + docs/cce/umn/cce_bestpractice_00253.html | 46 +- docs/cce/umn/cce_bestpractice_00253_0.html | 46 +- docs/cce/umn/cce_bestpractice_00281.html | 1 + docs/cce/umn/cce_bestpractice_0050.html | 2 +- docs/cce/umn/cce_bestpractice_0053.html | 2 +- docs/cce/umn/cce_bestpractice_0333.html | 25 +- docs/cce/umn/cce_bestpractice_10008.html | 2 + docs/cce/umn/cce_bestpractice_10017.html | 4 +- docs/cce/umn/cce_bestpractice_10020.html | 22 +- docs/cce/umn/cce_bestpractice_10020_0.html | 22 +- docs/cce/umn/cce_bestpractice_10021.html | 34 + docs/cce/umn/cce_bulletin_0000.html | 2 - docs/cce/umn/cce_bulletin_0033.html | 182 -- docs/cce/umn/cce_bulletin_0058.html | 4 +- docs/cce/umn/cce_bulletin_0059.html | 2 +- docs/cce/umn/cce_bulletin_0089.html | 2 +- docs/cce/umn/cce_bulletin_0095.html | 2 +- docs/cce/umn/cce_faq_00204.html | 2 +- docs/cce/umn/cce_faq_00265.html | 16 +- docs/cce/umn/cce_faq_00417.html | 2 +- docs/cce/umn/cce_productdesc_0001.html | 14 +- docs/cce/umn/cce_productdesc_0003.html | 2 +- docs/cce/umn/cce_productdesc_0005.html | 2 +- docs/cce/umn/en-us_image_0000001332989461.png | Bin 11864 -> 0 bytes docs/cce/umn/en-us_image_0000002065479094.png | Bin 0 -> 224439 bytes docs/cce/umn/en-us_image_0000002065480294.png | Bin 0 -> 492 bytes docs/cce/umn/en-us_image_0000002065480350.png | Bin 0 -> 172415 bytes docs/cce/umn/en-us_image_0000002065638994.png | Bin 0 -> 492 bytes docs/cce/umn/en-us_image_0000002101595985.png | Bin 0 -> 22235 bytes docs/cce/umn/en-us_image_0000002101597193.png | Bin 0 -> 492 bytes docs/cce/umn/en-us_image_0000002101597545.png | Bin 0 -> 3460 bytes docs/cce/umn/en-us_image_0000002101677473.png | Bin 0 -> 412100 bytes docs/cce/umn/en-us_image_0000002101679033.png | Bin 0 -> 492 bytes docs/cce/umn/en-us_image_0000002194626492.png | Bin 0 -> 4439 bytes 97 files changed, 3526 insertions(+), 2504 deletions(-) create mode 100644 docs/cce/umn/cce_10_0416.html create mode 100644 docs/cce/umn/cce_10_0554.html create mode 100644 docs/cce/umn/cce_10_0555.html create mode 100644 docs/cce/umn/cce_10_0792.html create mode 100644 docs/cce/umn/cce_10_0793.html create mode 100644 docs/cce/umn/cce_10_0799.html create mode 100644 docs/cce/umn/cce_10_0809.html create mode 100644 docs/cce/umn/cce_10_0914.html create mode 100644 docs/cce/umn/cce_bestpractice_10021.html delete mode 100644 docs/cce/umn/cce_bulletin_0033.html delete mode 100644 docs/cce/umn/en-us_image_0000001332989461.png create mode 100644 docs/cce/umn/en-us_image_0000002065479094.png create mode 100644 docs/cce/umn/en-us_image_0000002065480294.png create mode 100644 docs/cce/umn/en-us_image_0000002065480350.png create mode 100644 docs/cce/umn/en-us_image_0000002065638994.png create mode 100644 docs/cce/umn/en-us_image_0000002101595985.png create mode 100644 docs/cce/umn/en-us_image_0000002101597193.png create mode 100644 docs/cce/umn/en-us_image_0000002101597545.png create mode 100644 docs/cce/umn/en-us_image_0000002101677473.png create mode 100644 docs/cce/umn/en-us_image_0000002101679033.png create mode 100644 docs/cce/umn/en-us_image_0000002194626492.png diff --git a/docs/cce/umn/ALL_META.TXT.json b/docs/cce/umn/ALL_META.TXT.json index 1d24509ed..07b25d454 100644 --- a/docs/cce/umn/ALL_META.TXT.json +++ b/docs/cce/umn/ALL_META.TXT.json @@ -27,7 +27,7 @@ "node_id":"cce_productdesc_0001.xml", "product_code":"cce", "code":"2", - "des":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the enter lifecycle of containerized applications and delivers scalable, ", + "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":"What Is CCE?,Service Overview,User Guide", "search_title":"", @@ -240,30 +240,11 @@ "title":"Product Bulletin", "githuburl":"" }, - { - "uri":"cce_bulletin_0033.html", - "node_id":"cce_bulletin_0033.xml", - "product_code":"cce", - "code":"14", - "des":"CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. This section describes the Kubernetes version policy of CCE clusters.The CCE console", - "doc_type":"usermanual2", - "kw":"Kubernetes Version Policy,Product Bulletin,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Kubernetes Version Policy", - "githuburl":"" - }, { "uri":"cce_bulletin_0098.html", "node_id":"cce_bulletin_0098.xml", "product_code":"cce", - "code":"15", + "code":"14", "des":"Released: Oct 23, 2024CentOS has reached its end of maintenance (EOM) date, which means it will no longer receive updates or support. The CentOS public images on CCE are ", "doc_type":"usermanual2", "kw":"EOM of CentOS,Product Bulletin,User Guide", @@ -280,7 +261,7 @@ "uri":"cce_bulletin_0169.html", "node_id":"cce_bulletin_0169.xml", "product_code":"cce", - "code":"16", + "code":"15", "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":"Security Vulnerability Responses", @@ -300,7 +281,7 @@ "uri":"cce_bulletin_0011.html", "node_id":"cce_bulletin_0011.xml", "product_code":"cce", - "code":"17", + "code":"16", "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", @@ -319,7 +300,7 @@ "uri":"CVE-2021-4034.html", "node_id":"cve-2021-4034.xml", "product_code":"cce", - "code":"18", + "code":"17", "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", @@ -339,7 +320,7 @@ "uri":"cce_bulletin_0206.html", "node_id":"cce_bulletin_0206.xml", "product_code":"cce", - "code":"19", + "code":"18", "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", @@ -359,7 +340,7 @@ "uri":"cce_qs_0000.html", "node_id":"cce_qs_0000.xml", "product_code":"cce", - "code":"20", + "code":"19", "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", @@ -379,7 +360,7 @@ "uri":"cce_qs_0001.html", "node_id":"cce_qs_0001.xml", "product_code":"cce", - "code":"21", + "code":"20", "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", @@ -397,7 +378,7 @@ "uri":"cce_qs_0006.html", "node_id":"cce_qs_0006.xml", "product_code":"cce", - "code":"22", + "code":"21", "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", @@ -415,7 +396,7 @@ "uri":"cce_qs_0008.html", "node_id":"cce_qs_0008.xml", "product_code":"cce", - "code":"23", + "code":"22", "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 CCE Sta", "doc_type":"usermanual2", "kw":"Creating a Kubernetes Cluster,Getting Started,User Guide", @@ -433,7 +414,7 @@ "uri":"cce_qs_0003.html", "node_id":"cce_qs_0003.xml", "product_code":"cce", - "code":"24", + "code":"23", "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":"Creating a Deployment (Nginx),Getting Started,User Guide", @@ -451,7 +432,7 @@ "uri":"cce_qs_0007.html", "node_id":"cce_qs_0007.xml", "product_code":"cce", - "code":"25", + "code":"24", "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", @@ -469,7 +450,7 @@ "uri":"cce_qs_0009.html", "node_id":"cce_qs_0009.xml", "product_code":"cce", - "code":"26", + "code":"25", "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", @@ -487,7 +468,7 @@ "uri":"cce_qs_0004.html", "node_id":"cce_qs_0004.xml", "product_code":"cce", - "code":"27", + "code":"26", "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":"Creating a MySQL Workload,Deploying WordPress and MySQL That Depend on Each Other,User Guide", @@ -505,7 +486,7 @@ "uri":"cce_qs_0005.html", "node_id":"cce_qs_0005.xml", "product_code":"cce", - "code":"28", + "code":"27", "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":"Creating a WordPress Workload,Deploying WordPress and MySQL That Depend on Each Other,User Guide", @@ -523,7 +504,7 @@ "uri":"cce_10_0054.html", "node_id":"cce_10_0054.xml", "product_code":"cce", - "code":"29", + "code":"28", "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":"High-Risk Operations,User Guide", @@ -541,7 +522,7 @@ "uri":"cce_10_0091.html", "node_id":"cce_10_0091.xml", "product_code":"cce", - "code":"30", + "code":"29", "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", @@ -559,7 +540,7 @@ "uri":"cce_10_0002.html", "node_id":"cce_10_0002.xml", "product_code":"cce", - "code":"31", + "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":"Cluster Overview", @@ -577,7 +558,7 @@ "uri":"cce_10_0430.html", "node_id":"cce_10_0430.xml", "product_code":"cce", - "code":"32", + "code":"31", "des":"Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of containerized applications.For developers, Kubernetes is", "doc_type":"usermanual2", "kw":"Master Nodes,Basic Cluster Information,Cluster Overview,User Guide", @@ -595,7 +576,7 @@ "uri":"cce_10_0068.html", "node_id":"cce_10_0068.xml", "product_code":"cce", - "code":"33", + "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":"Kubernetes Version Release Notes", @@ -613,7 +594,7 @@ "uri":"cce_bulletin_0095.html", "node_id":"cce_bulletin_0095.xml", "product_code":"cce", - "code":"34", + "code":"33", "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", "doc_type":"usermanual2", "kw":"Kubernetes 1.30 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -631,7 +612,7 @@ "uri":"cce_bulletin_0089.html", "node_id":"cce_bulletin_0089.xml", "product_code":"cce", - "code":"35", + "code":"34", "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", "doc_type":"usermanual2", "kw":"Kubernetes 1.29 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -649,7 +630,7 @@ "uri":"cce_bulletin_0068.html", "node_id":"cce_bulletin_0068.xml", "product_code":"cce", - "code":"36", + "code":"35", "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", "doc_type":"usermanual2", "kw":"Kubernetes 1.28 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -667,8 +648,8 @@ "uri":"cce_bulletin_0059.html", "node_id":"cce_bulletin_0059.xml", "product_code":"cce", - "code":"37", - "des":"CCE allows you to create clusters of Kubernetes 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations an", + "code":"36", + "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", "doc_type":"usermanual2", "kw":"Kubernetes 1.27 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", @@ -685,7 +666,7 @@ "uri":"cce_bulletin_0058.html", "node_id":"cce_bulletin_0058.xml", "product_code":"cce", - "code":"38", + "code":"37", "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", @@ -703,7 +684,7 @@ "uri":"cce_bulletin_0027.html", "node_id":"cce_bulletin_0027.xml", "product_code":"cce", - "code":"39", + "code":"38", "des":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes 1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, and", "doc_type":"usermanual2", "kw":"Kubernetes 1.23 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -721,7 +702,7 @@ "uri":"cce_bulletin_0026.html", "node_id":"cce_bulletin_0026.xml", "product_code":"cce", - "code":"40", + "code":"39", "des":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes 1.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", @@ -739,7 +720,7 @@ "uri":"cce_whsnew_0010.html", "node_id":"cce_whsnew_0010.xml", "product_code":"cce", - "code":"41", + "code":"40", "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", @@ -757,7 +738,7 @@ "uri":"cce_whsnew_0007.html", "node_id":"cce_whsnew_0007.xml", "product_code":"cce", - "code":"42", + "code":"41", "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", @@ -775,8 +756,8 @@ "uri":"cce_10_0405.html", "node_id":"cce_10_0405.xml", "product_code":"cce", - "code":"43", - "des":"dockershim has been removed since Kubernetes v1.24, and Docker is not supported in v1.24 and later versions by default. Use containerd.All nodes in the CCE clusters of ve", + "code":"42", + "des":"All nodes in the CCE clusters of version 1.25, except the ones running EulerOS 2.5, use containerd by default.", "doc_type":"usermanual2", "kw":"Patch Version Release Notes,Cluster Overview,User Guide", "search_title":"", @@ -793,7 +774,7 @@ "uri":"cce_10_0298.html", "node_id":"cce_10_0298.xml", "product_code":"cce", - "code":"44", + "code":"43", "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", @@ -811,7 +792,7 @@ "uri":"cce_10_0342.html", "node_id":"cce_10_0342.xml", "product_code":"cce", - "code":"45", + "code":"44", "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", @@ -829,7 +810,7 @@ "uri":"cce_10_0028.html", "node_id":"cce_10_0028.xml", "product_code":"cce", - "code":"46", + "code":"45", "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", @@ -847,7 +828,7 @@ "uri":"cce_10_0349.html", "node_id":"cce_10_0349.xml", "product_code":"cce", - "code":"47", + "code":"46", "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", @@ -865,7 +846,7 @@ "uri":"cce_10_0140.html", "node_id":"cce_10_0140.xml", "product_code":"cce", - "code":"48", + "code":"47", "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", @@ -883,7 +864,7 @@ "uri":"cce_10_0107.html", "node_id":"cce_10_0107.xml", "product_code":"cce", - "code":"49", + "code":"48", "des":"This section uses a CCE standard cluster as an example to describe how to access a CCE cluster using kubectl.When you access a cluster using kubectl, CCE uses kubeconfig ", "doc_type":"usermanual2", "kw":"kubectl,Intranet access,Two-Way Authentication for Domain Names,Error from server Forbidden,The conn", @@ -901,7 +882,7 @@ "uri":"cce_10_0175.html", "node_id":"cce_10_0175.xml", "product_code":"cce", - "code":"50", + "code":"49", "des":"This section describes how to obtain the cluster certificate from the console and use it to access Kubernetes clusters.The downloaded certificate contains three files: cl", "doc_type":"usermanual2", "kw":"X.509 certificate,Accessing a Cluster Using an X.509 Certificate,Connecting to a Cluster,User Guide", @@ -919,7 +900,7 @@ "uri":"cce_10_0367.html", "node_id":"cce_10_0367.xml", "product_code":"cce", - "code":"51", + "code":"50", "des":"Subject Alternative Name (SAN) allows multiple values (including IP addresses, domain names, and so on) to be associated with certificates. A SAN is usually used by the c", "doc_type":"usermanual2", "kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Gu", @@ -937,7 +918,7 @@ "uri":"cce_10_0864.html", "node_id":"cce_10_0864.xml", "product_code":"cce", - "code":"52", + "code":"51", "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", @@ -955,7 +936,7 @@ "uri":"cce_10_0744.html", "node_id":"cce_10_0744.xml", "product_code":"cce", - "code":"53", + "code":"52", "des":"In multi-tenant scenarios, CCE generates a credential (kubeconfig or X.509 certificate) for you to access the corresponding cluster. The credential contains user identity", "doc_type":"usermanual2", "kw":"Revoking a Cluster Access Credential,Connecting to a Cluster,User Guide", @@ -973,7 +954,7 @@ "uri":"cce_10_0031.html", "node_id":"cce_10_0031.xml", "product_code":"cce", - "code":"54", + "code":"53", "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", @@ -991,7 +972,7 @@ "uri":"cce_10_0213.html", "node_id":"cce_10_0213.xml", "product_code":"cce", - "code":"55", + "code":"54", "des":"CCE allows you to manage cluster parameters, through which you can let core components work under your requirements.kube-apiserverkube-controller-managerkube-scheduler", "doc_type":"usermanual2", "kw":"cluster parameters,kube-apiserver,kube-controller-manager,Modifying Cluster Configurations,Managing ", @@ -1009,7 +990,7 @@ "uri":"cce_10_0602.html", "node_id":"cce_10_0602.xml", "product_code":"cce", - "code":"56", + "code":"55", "des":"After overload control is enabled, the number of simultaneous requests is dynamically regulated according to the resource pressure on the master nodes. This ensures that ", "doc_type":"usermanual2", "kw":"overload control,Enabling Overload Control for a Cluster,Managing a Cluster,User Guide", @@ -1027,7 +1008,7 @@ "uri":"cce_10_0403.html", "node_id":"cce_10_0403.xml", "product_code":"cce", - "code":"57", + "code":"56", "des":"CCE allows you to change the number of nodes managed in a cluster.A cluster that has only one master node supports fewer than 1000 worker nodes.The number of master nodes", "doc_type":"usermanual2", "kw":"Changing Cluster Scale,Managing a Cluster,User Guide", @@ -1045,7 +1026,7 @@ "uri":"cce_10_0426.html", "node_id":"cce_10_0426.xml", "product_code":"cce", - "code":"58", + "code":"57", "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", @@ -1063,7 +1044,7 @@ "uri":"cce_10_0212.html", "node_id":"cce_10_0212.xml", "product_code":"cce", - "code":"59", + "code":"58", "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", @@ -1081,7 +1062,7 @@ "uri":"cce_10_0927.html", "node_id":"cce_10_0927.xml", "product_code":"cce", - "code":"60", + "code":"59", "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", @@ -1099,7 +1080,7 @@ "uri":"cce_10_0214.html", "node_id":"cce_10_0214.xml", "product_code":"cce", - "code":"61", + "code":"60", "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", @@ -1117,7 +1098,7 @@ "uri":"cce_10_0215.html", "node_id":"cce_10_0215.xml", "product_code":"cce", - "code":"62", + "code":"61", "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", @@ -1135,7 +1116,7 @@ "uri":"cce_10_0197.html", "node_id":"cce_10_0197.xml", "product_code":"cce", - "code":"63", + "code":"62", "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,Process and Method of Upgrading a Cluster,Upg", @@ -1153,7 +1134,7 @@ "uri":"cce_10_0302.html", "node_id":"cce_10_0302.xml", "product_code":"cce", - "code":"64", + "code":"63", "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 Process and Method of Upgradi", "doc_type":"usermanual2", "kw":"Deprecated APIs,Before You Start,Upgrading a Cluster,User Guide", @@ -1171,7 +1152,7 @@ "uri":"cce_10_0560.html", "node_id":"cce_10_0560.xml", "product_code":"cce", - "code":"65", + "code":"64", "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", @@ -1189,7 +1170,7 @@ "uri":"cce_10_0568.html", "node_id":"cce_10_0568.xml", "product_code":"cce", - "code":"66", + "code":"65", "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", @@ -1207,7 +1188,7 @@ "uri":"cce_10_0569.html", "node_id":"cce_10_0569.xml", "product_code":"cce", - "code":"67", + "code":"66", "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", @@ -1225,7 +1206,7 @@ "uri":"cce_10_0567.html", "node_id":"cce_10_0567.xml", "product_code":"cce", - "code":"68", + "code":"67", "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", @@ -1243,7 +1224,7 @@ "uri":"cce_10_0561.html", "node_id":"cce_10_0561.xml", "product_code":"cce", - "code":"69", + "code":"68", "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", @@ -1261,7 +1242,7 @@ "uri":"cce_10_0565.html", "node_id":"cce_10_0565.xml", "product_code":"cce", - "code":"70", + "code":"69", "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", @@ -1279,7 +1260,7 @@ "uri":"cce_10_0566.html", "node_id":"cce_10_0566.xml", "product_code":"cce", - "code":"71", + "code":"70", "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", @@ -1297,7 +1278,7 @@ "uri":"cce_10_0210.html", "node_id":"cce_10_0210.xml", "product_code":"cce", - "code":"72", + "code":"71", "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", @@ -1315,7 +1296,7 @@ "uri":"cce_10_0550.html", "node_id":"cce_10_0550.xml", "product_code":"cce", - "code":"73", + "code":"72", "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", @@ -1333,7 +1314,7 @@ "uri":"cce_10_0549.html", "node_id":"cce_10_0549.xml", "product_code":"cce", - "code":"74", + "code":"73", "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", @@ -1351,7 +1332,7 @@ "uri":"cce_10_0431.html", "node_id":"cce_10_0431.xml", "product_code":"cce", - "code":"75", + "code":"74", "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", @@ -1369,7 +1350,7 @@ "uri":"cce_10_0432.html", "node_id":"cce_10_0432.xml", "product_code":"cce", - "code":"76", + "code":"75", "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", @@ -1387,7 +1368,7 @@ "uri":"cce_10_0433.html", "node_id":"cce_10_0433.xml", "product_code":"cce", - "code":"77", + "code":"76", "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", @@ -1405,7 +1386,7 @@ "uri":"cce_10_0434.html", "node_id":"cce_10_0434.xml", "product_code":"cce", - "code":"78", + "code":"77", "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", @@ -1423,7 +1404,7 @@ "uri":"cce_10_0435.html", "node_id":"cce_10_0435.xml", "product_code":"cce", - "code":"79", + "code":"78", "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", @@ -1441,7 +1422,7 @@ "uri":"cce_10_0436.html", "node_id":"cce_10_0436.xml", "product_code":"cce", - "code":"80", + "code":"79", "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", @@ -1459,7 +1440,7 @@ "uri":"cce_10_0437.html", "node_id":"cce_10_0437.xml", "product_code":"cce", - "code":"81", + "code":"80", "des":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group with the source IP address set to the master node ", "doc_type":"usermanual2", "kw":"Security Groups,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1477,7 +1458,7 @@ "uri":"cce_10_0439.html", "node_id":"cce_10_0439.xml", "product_code":"cce", - "code":"82", + "code":"81", "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", @@ -1495,7 +1476,7 @@ "uri":"cce_10_0440.html", "node_id":"cce_10_0440.xml", "product_code":"cce", - "code":"83", + "code":"82", "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", @@ -1513,7 +1494,7 @@ "uri":"cce_10_0441.html", "node_id":"cce_10_0441.xml", "product_code":"cce", - "code":"84", + "code":"83", "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", @@ -1531,7 +1512,7 @@ "uri":"cce_10_0442.html", "node_id":"cce_10_0442.xml", "product_code":"cce", - "code":"85", + "code":"84", "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.cce-agent doe", "doc_type":"usermanual2", "kw":"CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1549,7 +1530,7 @@ "uri":"cce_10_0443.html", "node_id":"cce_10_0443.xml", "product_code":"cce", - "code":"86", + "code":"85", "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", @@ -1567,7 +1548,7 @@ "uri":"cce_10_0444.html", "node_id":"cce_10_0444.xml", "product_code":"cce", - "code":"87", + "code":"86", "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", @@ -1585,7 +1566,7 @@ "uri":"cce_10_0445.html", "node_id":"cce_10_0445.xml", "product_code":"cce", - "code":"88", + "code":"87", "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", @@ -1603,7 +1584,7 @@ "uri":"cce_10_0446.html", "node_id":"cce_10_0446.xml", "product_code":"cce", - "code":"89", + "code":"88", "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", @@ -1621,7 +1602,7 @@ "uri":"cce_10_0447.html", "node_id":"cce_10_0447.xml", "product_code":"cce", - "code":"90", + "code":"89", "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", @@ -1639,7 +1620,7 @@ "uri":"cce_10_0448.html", "node_id":"cce_10_0448.xml", "product_code":"cce", - "code":"91", + "code":"90", "des":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node is unavailable. Restore the nod", "doc_type":"usermanual2", "kw":"kubelet,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1657,7 +1638,7 @@ "uri":"cce_10_0449.html", "node_id":"cce_10_0449.xml", "product_code":"cce", - "code":"92", + "code":"91", "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", @@ -1675,7 +1656,7 @@ "uri":"cce_10_0450.html", "node_id":"cce_10_0450.xml", "product_code":"cce", - "code":"93", + "code":"92", "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", @@ -1693,7 +1674,7 @@ "uri":"cce_10_0451.html", "node_id":"cce_10_0451.xml", "product_code":"cce", - "code":"94", + "code":"93", "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", @@ -1711,7 +1692,7 @@ "uri":"cce_10_0452.html", "node_id":"cce_10_0452.xml", "product_code":"cce", - "code":"95", + "code":"94", "des":"Check and make sure that the master nodes in your cluster have more than 2 CPU cores.The number of CPU cores on the master nodes is 2, which may lead to a cluster upgrade", "doc_type":"usermanual2", "kw":"Node CPU Cores,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1729,7 +1710,7 @@ "uri":"cce_10_0453.html", "node_id":"cce_10_0453.xml", "product_code":"cce", - "code":"96", + "code":"95", "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", @@ -1747,7 +1728,7 @@ "uri":"cce_10_0455.html", "node_id":"cce_10_0455.xml", "product_code":"cce", - "code":"97", + "code":"96", "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", @@ -1765,7 +1746,7 @@ "uri":"cce_10_0456.html", "node_id":"cce_10_0456.xml", "product_code":"cce", - "code":"98", + "code":"97", "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", @@ -1783,7 +1764,7 @@ "uri":"cce_10_0457.html", "node_id":"cce_10_0457.xml", "product_code":"cce", - "code":"99", + "code":"98", "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", @@ -1801,7 +1782,7 @@ "uri":"cce_10_0458.html", "node_id":"cce_10_0458.xml", "product_code":"cce", - "code":"100", + "code":"99", "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", @@ -1819,7 +1800,7 @@ "uri":"cce_10_0459.html", "node_id":"cce_10_0459.xml", "product_code":"cce", - "code":"101", + "code":"100", "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", @@ -1837,7 +1818,7 @@ "uri":"cce_10_0460.html", "node_id":"cce_10_0460.xml", "product_code":"cce", - "code":"102", + "code":"101", "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", @@ -1855,7 +1836,7 @@ "uri":"cce_10_0478.html", "node_id":"cce_10_0478.xml", "product_code":"cce", - "code":"103", + "code":"102", "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", @@ -1873,7 +1854,7 @@ "uri":"cce_10_0479.html", "node_id":"cce_10_0479.xml", "product_code":"cce", - "code":"104", + "code":"103", "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", @@ -1891,7 +1872,7 @@ "uri":"cce_10_0480.html", "node_id":"cce_10_0480.xml", "product_code":"cce", - "code":"105", + "code":"104", "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", @@ -1909,7 +1890,7 @@ "uri":"cce_10_0484.html", "node_id":"cce_10_0484.xml", "product_code":"cce", - "code":"106", + "code":"105", "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", @@ -1927,7 +1908,7 @@ "uri":"cce_10_0485.html", "node_id":"cce_10_0485.xml", "product_code":"cce", - "code":"107", + "code":"106", "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", @@ -1945,7 +1926,7 @@ "uri":"cce_10_0486.html", "node_id":"cce_10_0486.xml", "product_code":"cce", - "code":"108", + "code":"107", "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", @@ -1963,7 +1944,7 @@ "uri":"cce_10_0487.html", "node_id":"cce_10_0487.xml", "product_code":"cce", - "code":"109", + "code":"108", "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", @@ -1981,7 +1962,7 @@ "uri":"cce_10_0488.html", "node_id":"cce_10_0488.xml", "product_code":"cce", - "code":"110", + "code":"109", "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", @@ -1999,7 +1980,7 @@ "uri":"cce_10_0489.html", "node_id":"cce_10_0489.xml", "product_code":"cce", - "code":"111", + "code":"110", "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", @@ -2017,7 +1998,7 @@ "uri":"cce_10_0490.html", "node_id":"cce_10_0490.xml", "product_code":"cce", - "code":"112", + "code":"111", "des":"Check the ID file format.", "doc_type":"usermanual2", "kw":"Node ID File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2035,7 +2016,7 @@ "uri":"cce_10_0491.html", "node_id":"cce_10_0491.xml", "product_code":"cce", - "code":"113", + "code":"112", "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", @@ -2053,7 +2034,7 @@ "uri":"cce_10_0492.html", "node_id":"cce_10_0492.xml", "product_code":"cce", - "code":"114", + "code":"113", "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", @@ -2071,7 +2052,7 @@ "uri":"cce_10_0493.html", "node_id":"cce_10_0493.xml", "product_code":"cce", - "code":"115", + "code":"114", "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", @@ -2089,7 +2070,7 @@ "uri":"cce_10_0494.html", "node_id":"cce_10_0494.xml", "product_code":"cce", - "code":"116", + "code":"115", "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", @@ -2107,7 +2088,7 @@ "uri":"cce_10_0495.html", "node_id":"cce_10_0495.xml", "product_code":"cce", - "code":"117", + "code":"116", "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", @@ -2125,7 +2106,7 @@ "uri":"cce_10_0496.html", "node_id":"cce_10_0496.xml", "product_code":"cce", - "code":"118", + "code":"117", "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", @@ -2143,7 +2124,7 @@ "uri":"cce_10_0497.html", "node_id":"cce_10_0497.xml", "product_code":"cce", - "code":"119", + "code":"118", "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", @@ -2161,7 +2142,7 @@ "uri":"cce_10_0498.html", "node_id":"cce_10_0498.xml", "product_code":"cce", - "code":"120", + "code":"119", "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", @@ -2179,7 +2160,7 @@ "uri":"cce_10_0499.html", "node_id":"cce_10_0499.xml", "product_code":"cce", - "code":"121", + "code":"120", "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", @@ -2197,7 +2178,7 @@ "uri":"cce_10_0500.html", "node_id":"cce_10_0500.xml", "product_code":"cce", - "code":"122", + "code":"121", "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", @@ -2215,7 +2196,7 @@ "uri":"cce_10_0501.html", "node_id":"cce_10_0501.xml", "product_code":"cce", - "code":"123", + "code":"122", "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", @@ -2233,7 +2214,7 @@ "uri":"cce_10_0502.html", "node_id":"cce_10_0502.xml", "product_code":"cce", - "code":"124", + "code":"123", "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", @@ -2251,7 +2232,7 @@ "uri":"cce_10_0503.html", "node_id":"cce_10_0503.xml", "product_code":"cce", - "code":"125", + "code":"124", "des":"The GPU add-on is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The GPU add-on driver needs to be configured by ", "doc_type":"usermanual2", "kw":"GPU Add-on,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2269,7 +2250,7 @@ "uri":"cce_10_0504.html", "node_id":"cce_10_0504.xml", "product_code":"cce", - "code":"126", + "code":"125", "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", @@ -2287,7 +2268,7 @@ "uri":"cce_10_0505.html", "node_id":"cce_10_0505.xml", "product_code":"cce", - "code":"127", + "code":"126", "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", @@ -2305,7 +2286,7 @@ "uri":"cce_10_0506.html", "node_id":"cce_10_0506.xml", "product_code":"cce", - "code":"128", + "code":"127", "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", @@ -2323,7 +2304,7 @@ "uri":"cce_10_0507.html", "node_id":"cce_10_0507.xml", "product_code":"cce", - "code":"129", + "code":"128", "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", @@ -2341,7 +2322,7 @@ "uri":"cce_10_0508.html", "node_id":"cce_10_0508.xml", "product_code":"cce", - "code":"130", + "code":"129", "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 Upgrade,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2359,7 +2340,7 @@ "uri":"cce_10_0510.html", "node_id":"cce_10_0510.xml", "product_code":"cce", - "code":"131", + "code":"130", "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", @@ -2377,7 +2358,7 @@ "uri":"cce_10_0511.html", "node_id":"cce_10_0511.xml", "product_code":"cce", - "code":"132", + "code":"131", "des":"Check whether the configuration of the CCE AI Suite add-on in a cluster has been intrusively modified. If so, upgrading the cluster may fail.", "doc_type":"usermanual2", "kw":"Key GPU Add-on Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2395,7 +2376,7 @@ "uri":"cce_10_0512.html", "node_id":"cce_10_0512.xml", "product_code":"cce", - "code":"133", + "code":"132", "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", @@ -2413,7 +2394,7 @@ "uri":"cce_10_0513.html", "node_id":"cce_10_0513.xml", "product_code":"cce", - "code":"134", + "code":"133", "des":"Check whether ELB listener access control has been configured for the Services in the current cluster using annotations.If so, check whether their configurations are corr", "doc_type":"usermanual2", "kw":"ELB Listener Access Control,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2431,7 +2412,7 @@ "uri":"cce_10_0514.html", "node_id":"cce_10_0514.xml", "product_code":"cce", - "code":"135", + "code":"134", "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", @@ -2449,7 +2430,7 @@ "uri":"cce_10_0515.html", "node_id":"cce_10_0515.xml", "product_code":"cce", - "code":"136", + "code":"135", "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", @@ -2467,7 +2448,7 @@ "uri":"cce_10_0516.html", "node_id":"cce_10_0516.xml", "product_code":"cce", - "code":"137", + "code":"136", "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", @@ -2485,7 +2466,7 @@ "uri":"cce_10_0517.html", "node_id":"cce_10_0517.xml", "product_code":"cce", - "code":"138", + "code":"137", "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", @@ -2503,7 +2484,7 @@ "uri":"cce_10_0518.html", "node_id":"cce_10_0518.xml", "product_code":"cce", - "code":"139", + "code":"138", "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", @@ -2521,7 +2502,7 @@ "uri":"cce_10_0520.html", "node_id":"cce_10_0520.xml", "product_code":"cce", - "code":"140", + "code":"139", "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", @@ -2539,7 +2520,7 @@ "uri":"cce_10_0521.html", "node_id":"cce_10_0521.xml", "product_code":"cce", - "code":"141", + "code":"140", "des":"Make sure that the GPU add-on 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 add-on mus", "doc_type":"usermanual2", "kw":"Compatibility Between the Ubuntu Kernel and GPU Driver,Troubleshooting for Pre-upgrade Check Excepti", @@ -2557,7 +2538,7 @@ "uri":"cce_10_0522.html", "node_id":"cce_10_0522.xml", "product_code":"cce", - "code":"142", + "code":"141", "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", @@ -2575,7 +2556,7 @@ "uri":"cce_10_0523.html", "node_id":"cce_10_0523.xml", "product_code":"cce", - "code":"143", + "code":"142", "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", @@ -2593,7 +2574,7 @@ "uri":"cce_10_0524.html", "node_id":"cce_10_0524.xml", "product_code":"cce", - "code":"144", + "code":"143", "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", @@ -2611,7 +2592,7 @@ "uri":"cce_10_0525.html", "node_id":"cce_10_0525.xml", "product_code":"cce", - "code":"145", + "code":"144", "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", @@ -2629,7 +2610,7 @@ "uri":"cce_10_0526.html", "node_id":"cce_10_0526.xml", "product_code":"cce", - "code":"146", + "code":"145", "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", @@ -2647,7 +2628,7 @@ "uri":"cce_10_0183.html", "node_id":"cce_10_0183.xml", "product_code":"cce", - "code":"147", + "code":"146", "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", @@ -2665,7 +2646,7 @@ "uri":"cce_10_0180.html", "node_id":"cce_10_0180.xml", "product_code":"cce", - "code":"148", + "code":"147", "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", @@ -2683,7 +2664,7 @@ "uri":"cce_10_0462.html", "node_id":"cce_10_0462.xml", "product_code":"cce", - "code":"149", + "code":"148", "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", @@ -2701,7 +2682,7 @@ "uri":"cce_10_0476.html", "node_id":"cce_10_0476.xml", "product_code":"cce", - "code":"150", + "code":"149", "des":"This section describes the mappings between released cluster versions and OS versions.", "doc_type":"usermanual2", "kw":"Node OSs,Nodes,User Guide", @@ -2719,7 +2700,7 @@ "uri":"cce_10_0363.html", "node_id":"cce_10_0363.xml", "product_code":"cce", - "code":"151", + "code":"150", "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", @@ -2737,7 +2718,7 @@ "uri":"cce_10_0198.html", "node_id":"cce_10_0198.xml", "product_code":"cce", - "code":"152", + "code":"151", "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", @@ -2755,7 +2736,7 @@ "uri":"cce_10_0185.html", "node_id":"cce_10_0185.xml", "product_code":"cce", - "code":"153", + "code":"152", "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", @@ -2773,7 +2754,7 @@ "uri":"cce_10_0672.html", "node_id":"cce_10_0672.xml", "product_code":"cce", - "code":"154", + "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":"node labels", @@ -2791,7 +2772,7 @@ "uri":"cce_10_0004.html", "node_id":"cce_10_0004.xml", "product_code":"cce", - "code":"155", + "code":"154", "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", @@ -2809,7 +2790,7 @@ "uri":"cce_10_0352.html", "node_id":"cce_10_0352.xml", "product_code":"cce", - "code":"156", + "code":"155", "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", @@ -2827,7 +2808,7 @@ "uri":"cce_10_0003.html", "node_id":"cce_10_0003.xml", "product_code":"cce", - "code":"157", + "code":"156", "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", @@ -2845,7 +2826,7 @@ "uri":"cce_10_0338.html", "node_id":"cce_10_0338.xml", "product_code":"cce", - "code":"158", + "code":"157", "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", @@ -2863,7 +2844,7 @@ "uri":"cce_10_0184.html", "node_id":"cce_10_0184.xml", "product_code":"cce", - "code":"159", + "code":"158", "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", @@ -2881,7 +2862,7 @@ "uri":"cce_10_0605.html", "node_id":"cce_10_0605.xml", "product_code":"cce", - "code":"160", + "code":"159", "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", @@ -2899,7 +2880,7 @@ "uri":"cce_10_0186.html", "node_id":"cce_10_0186.xml", "product_code":"cce", - "code":"161", + "code":"160", "des":"You can delete a pay-per-use node that is not needed from the node list.Deleting or unsubscribing from a node in a CCE cluster will release the node and services running ", "doc_type":"usermanual2", "kw":"Deleting a Node,Management Nodes,User Guide", @@ -2917,7 +2898,7 @@ "uri":"cce_10_0036.html", "node_id":"cce_10_0036.xml", "product_code":"cce", - "code":"162", + "code":"161", "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", @@ -2935,7 +2916,7 @@ "uri":"cce_10_0276.html", "node_id":"cce_10_0276.xml", "product_code":"cce", - "code":"163", + "code":"162", "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", @@ -2953,7 +2934,7 @@ "uri":"cce_10_0704.html", "node_id":"cce_10_0704.xml", "product_code":"cce", - "code":"164", + "code":"163", "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", @@ -2971,7 +2952,7 @@ "uri":"cce_10_0178.html", "node_id":"cce_10_0178.xml", "product_code":"cce", - "code":"165", + "code":"164", "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", @@ -2989,7 +2970,7 @@ "uri":"cce_10_0341.html", "node_id":"cce_10_0341.xml", "product_code":"cce", - "code":"166", + "code":"165", "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", @@ -3007,7 +2988,7 @@ "uri":"cce_10_0348.html", "node_id":"cce_10_0348.xml", "product_code":"cce", - "code":"167", + "code":"166", "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, specify the number of c", "doc_type":"usermanual2", "kw":"Maximum Number of Pods on a Node,alpha.cce/fixPoolMask,maximum number of pods,Maximum Number of Pods", @@ -3025,7 +3006,7 @@ "uri":"cce_10_0883.html", "node_id":"cce_10_0883.xml", "product_code":"cce", - "code":"168", + "code":"167", "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", @@ -3043,7 +3024,7 @@ "uri":"cce_10_0601.html", "node_id":"cce_10_0601.xml", "product_code":"cce", - "code":"169", + "code":"168", "des":"Kubernetes has removed dockershim from v1.24 and does not support Docker by default. CCE is going to stop the support for Docker. Change the node container engine from Do", "doc_type":"usermanual2", "kw":"Migrating Nodes from Docker to containerd,Node O&M,User Guide", @@ -3061,7 +3042,7 @@ "uri":"cce_10_0659.html", "node_id":"cce_10_0659.xml", "product_code":"cce", - "code":"170", + "code":"169", "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", @@ -3076,10 +3057,10 @@ "githuburl":"" }, { - "uri":"cce_bestpractice_10020_0.html", - "node_id":"cce_bestpractice_10020_0.xml", + "uri":"cce_bestpractice_10020.html", + "node_id":"cce_bestpractice_10020.xml", "product_code":"cce", - "code":"171", + "code":"170", "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", @@ -3097,7 +3078,7 @@ "uri":"cce_10_0035.html", "node_id":"cce_10_0035.xml", "product_code":"cce", - "code":"172", + "code":"171", "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", @@ -3115,7 +3096,7 @@ "uri":"cce_10_0081.html", "node_id":"cce_10_0081.xml", "product_code":"cce", - "code":"173", + "code":"172", "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,", @@ -3133,7 +3114,7 @@ "uri":"cce_10_0012.html", "node_id":"cce_10_0012.xml", "product_code":"cce", - "code":"174", + "code":"173", "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 SettingsCo", "doc_type":"usermanual2", "kw":"Creating a Node Pool,Node Pools,User Guide", @@ -3151,7 +3132,7 @@ "uri":"cce_10_0658.html", "node_id":"cce_10_0658.xml", "product_code":"cce", - "code":"175", + "code":"174", "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.Add or reduce nodes for scali", "doc_type":"usermanual2", "kw":"Scaling a Node Pool,Node Pools,User Guide", @@ -3169,7 +3150,7 @@ "uri":"cce_10_0222.html", "node_id":"cce_10_0222.xml", "product_code":"cce", - "code":"176", + "code":"175", "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", @@ -3187,7 +3168,7 @@ "uri":"cce_10_0653.html", "node_id":"cce_10_0653.xml", "product_code":"cce", - "code":"177", + "code":"176", "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", @@ -3205,7 +3186,7 @@ "uri":"cce_10_0727.html", "node_id":"cce_10_0727.xml", "product_code":"cce", - "code":"178", + "code":"177", "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", @@ -3223,7 +3204,7 @@ "uri":"cce_10_0652.html", "node_id":"cce_10_0652.xml", "product_code":"cce", - "code":"179", + "code":"178", "des":"The default node pool does not support the following management operations.CCE allows you to highly customize Kubernetes parameter settings on core components in a cluste", "doc_type":"usermanual2", "kw":"Modifying Node Pool Configurations,Managing a Node Pool,User Guide", @@ -3241,7 +3222,7 @@ "uri":"cce_10_0886.html", "node_id":"cce_10_0886.xml", "product_code":"cce", - "code":"180", + "code":"179", "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", @@ -3259,7 +3240,7 @@ "uri":"cce_10_0655.html", "node_id":"cce_10_0655.xml", "product_code":"cce", - "code":"181", + "code":"180", "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", @@ -3277,7 +3258,7 @@ "uri":"cce_10_0654.html", "node_id":"cce_10_0654.xml", "product_code":"cce", - "code":"182", + "code":"181", "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", @@ -3295,7 +3276,7 @@ "uri":"cce_10_0660.html", "node_id":"cce_10_0660.xml", "product_code":"cce", - "code":"183", + "code":"182", "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", @@ -3313,7 +3294,7 @@ "uri":"cce_10_0656.html", "node_id":"cce_10_0656.xml", "product_code":"cce", - "code":"184", + "code":"183", "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", @@ -3331,7 +3312,7 @@ "uri":"cce_10_0657.html", "node_id":"cce_10_0657.xml", "product_code":"cce", - "code":"185", + "code":"184", "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", @@ -3349,7 +3330,7 @@ "uri":"cce_10_0046.html", "node_id":"cce_10_0046.xml", "product_code":"cce", - "code":"186", + "code":"185", "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", @@ -3367,7 +3348,7 @@ "uri":"cce_10_0006.html", "node_id":"cce_10_0006.xml", "product_code":"cce", - "code":"187", + "code":"186", "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", @@ -3385,7 +3366,7 @@ "uri":"cce_10_0673.html", "node_id":"cce_10_0673.xml", "product_code":"cce", - "code":"188", + "code":"187", "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", @@ -3403,7 +3384,7 @@ "uri":"cce_10_0047.html", "node_id":"cce_10_0047.xml", "product_code":"cce", - "code":"189", + "code":"188", "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", @@ -3421,7 +3402,7 @@ "uri":"cce_10_0048.html", "node_id":"cce_10_0048.xml", "product_code":"cce", - "code":"190", + "code":"189", "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", @@ -3439,7 +3420,7 @@ "uri":"cce_10_0216.html", "node_id":"cce_10_0216.xml", "product_code":"cce", - "code":"191", + "code":"190", "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", @@ -3457,7 +3438,7 @@ "uri":"cce_10_0150.html", "node_id":"cce_10_0150.xml", "product_code":"cce", - "code":"192", + "code":"191", "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", @@ -3475,7 +3456,7 @@ "uri":"cce_10_0151.html", "node_id":"cce_10_0151.xml", "product_code":"cce", - "code":"193", + "code":"192", "des":"A cron job runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A cron job runs periodically at the specified tim", "doc_type":"usermanual2", "kw":"time synchronization,Creating a Cron Job,Creating a Workload,User Guide", @@ -3493,7 +3474,7 @@ "uri":"cce_10_0130.html", "node_id":"cce_10_0130.xml", "product_code":"cce", - "code":"194", + "code":"193", "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", @@ -3511,7 +3492,7 @@ "uri":"cce_10_0463.html", "node_id":"cce_10_0463.xml", "product_code":"cce", - "code":"195", + "code":"194", "des":"The most significant difference is that each Kata container (pod) runs on an independent micro-VM, has an independent OS kernel, and is securely isolated at the virtualiz", "doc_type":"usermanual2", "kw":"Secure Runtime and Common Runtime,Configuring a Workload,User Guide", @@ -3529,7 +3510,7 @@ "uri":"cce_10_0354.html", "node_id":"cce_10_0354.xml", "product_code":"cce", - "code":"196", + "code":"195", "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", @@ -3547,7 +3528,7 @@ "uri":"cce_10_0353.html", "node_id":"cce_10_0353.xml", "product_code":"cce", - "code":"197", + "code":"196", "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", @@ -3565,7 +3546,7 @@ "uri":"cce_10_0009.html", "node_id":"cce_10_0009.xml", "product_code":"cce", - "code":"198", + "code":"197", "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", @@ -3583,7 +3564,7 @@ "uri":"cce_10_0163.html", "node_id":"cce_10_0163.xml", "product_code":"cce", - "code":"199", + "code":"198", "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", @@ -3601,7 +3582,7 @@ "uri":"cce_10_0105.html", "node_id":"cce_10_0105.xml", "product_code":"cce", - "code":"200", + "code":"199", "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", @@ -3619,7 +3600,7 @@ "uri":"cce_10_0112.html", "node_id":"cce_10_0112.xml", "product_code":"cce", - "code":"201", + "code":"200", "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", @@ -3637,7 +3618,7 @@ "uri":"cce_10_0113.html", "node_id":"cce_10_0113.xml", "product_code":"cce", - "code":"202", + "code":"201", "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", @@ -3655,7 +3636,7 @@ "uri":"cce_10_0397.html", "node_id":"cce_10_0397.xml", "product_code":"cce", - "code":"203", + "code":"202", "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", @@ -3673,7 +3654,7 @@ "uri":"cce_10_0728.html", "node_id":"cce_10_0728.xml", "product_code":"cce", - "code":"204", + "code":"203", "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", @@ -3691,7 +3672,7 @@ "uri":"cce_10_0386.html", "node_id":"cce_10_0386.xml", "product_code":"cce", - "code":"205", + "code":"204", "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", @@ -3709,7 +3690,7 @@ "uri":"cce_10_0889.html", "node_id":"cce_10_0889.xml", "product_code":"cce", - "code":"206", + "code":"205", "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", @@ -3727,7 +3708,7 @@ "uri":"cce_10_0232.html", "node_id":"cce_10_0232.xml", "product_code":"cce", - "code":"207", + "code":"206", "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", @@ -3745,7 +3726,7 @@ "uri":"cce_10_0891.html", "node_id":"cce_10_0891.xml", "product_code":"cce", - "code":"208", + "code":"207", "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", @@ -3763,7 +3744,7 @@ "uri":"cce_10_0892.html", "node_id":"cce_10_0892.xml", "product_code":"cce", - "code":"209", + "code":"208", "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":"Node Affinity,Specified Node Pool Scheduling,Configuring Node Affinity Scheduling (nodeAffinity),Sch", @@ -3781,7 +3762,7 @@ "uri":"cce_10_0893.html", "node_id":"cce_10_0893.xml", "product_code":"cce", - "code":"210", + "code":"209", "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", @@ -3799,7 +3780,7 @@ "uri":"cce_10_00356.html", "node_id":"cce_10_00356.xml", "product_code":"cce", - "code":"211", + "code":"210", "des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.When using CloudShell to access a CCE cluster or container, you c", "doc_type":"usermanual2", "kw":"Logging In to a Container,Workloads,User Guide", @@ -3817,7 +3798,7 @@ "uri":"cce_10_0007.html", "node_id":"cce_10_0007.xml", "product_code":"cce", - "code":"212", + "code":"211", "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", @@ -3835,7 +3816,7 @@ "uri":"cce_10_0833.html", "node_id":"cce_10_0833.xml", "product_code":"cce", - "code":"213", + "code":"212", "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", @@ -3853,7 +3834,7 @@ "uri":"cce_10_0465.html", "node_id":"cce_10_0465.xml", "product_code":"cce", - "code":"214", + "code":"213", "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", @@ -3871,7 +3852,7 @@ "uri":"cce_10_0275.html", "node_id":"cce_10_0275.xml", "product_code":"cce", - "code":"215", + "code":"214", "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", @@ -3889,7 +3870,7 @@ "uri":"cce_10_0466.html", "node_id":"cce_10_0466.xml", "product_code":"cce", - "code":"216", + "code":"215", "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", @@ -3907,7 +3888,7 @@ "uri":"cce_10_0674.html", "node_id":"cce_10_0674.xml", "product_code":"cce", - "code":"217", + "code":"216", "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", @@ -3925,7 +3906,7 @@ "uri":"cce_10_0702.html", "node_id":"cce_10_0702.xml", "product_code":"cce", - "code":"218", + "code":"217", "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", @@ -3943,7 +3924,7 @@ "uri":"cce_10_0551.html", "node_id":"cce_10_0551.xml", "product_code":"cce", - "code":"219", + "code":"218", "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", @@ -3961,7 +3942,7 @@ "uri":"cce_10_0351.html", "node_id":"cce_10_0351.xml", "product_code":"cce", - "code":"220", + "code":"219", "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", @@ -3979,7 +3960,7 @@ "uri":"cce_10_0552.html", "node_id":"cce_10_0552.xml", "product_code":"cce", - "code":"221", + "code":"220", "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", @@ -3997,7 +3978,7 @@ "uri":"cce_10_0720.html", "node_id":"cce_10_0720.xml", "product_code":"cce", - "code":"222", + "code":"221", "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", @@ -4015,7 +3996,7 @@ "uri":"cce_10_0345.html", "node_id":"cce_10_0345.xml", "product_code":"cce", - "code":"223", + "code":"222", "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. During the insta", "doc_type":"usermanual2", "kw":"Default GPU Scheduling in Kubernetes,GPU Scheduling,User Guide", @@ -4033,7 +4014,7 @@ "uri":"cce_10_0423.html", "node_id":"cce_10_0423.xml", "product_code":"cce", - "code":"224", + "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":"Volcano Scheduling", @@ -4051,7 +4032,7 @@ "uri":"cce_10_0721.html", "node_id":"cce_10_0721.xml", "product_code":"cce", - "code":"225", + "code":"224", "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", @@ -4069,7 +4050,7 @@ "uri":"cce_10_0722.html", "node_id":"cce_10_0722.xml", "product_code":"cce", - "code":"226", + "code":"225", "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", @@ -4087,7 +4068,7 @@ "uri":"cce_10_0768.html", "node_id":"cce_10_0768.xml", "product_code":"cce", - "code":"227", + "code":"226", "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", @@ -4105,7 +4086,7 @@ "uri":"cce_10_0773.html", "node_id":"cce_10_0773.xml", "product_code":"cce", - "code":"228", + "code":"227", "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", @@ -4123,7 +4104,7 @@ "uri":"cce_10_0766.html", "node_id":"cce_10_0766.xml", "product_code":"cce", - "code":"229", + "code":"228", "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", @@ -4141,7 +4122,7 @@ "uri":"cce_10_0767.html", "node_id":"cce_10_0767.xml", "product_code":"cce", - "code":"230", + "code":"229", "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", @@ -4159,7 +4140,7 @@ "uri":"cce_10_0789.html", "node_id":"cce_10_0789.xml", "product_code":"cce", - "code":"231", + "code":"230", "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", @@ -4177,7 +4158,7 @@ "uri":"cce_10_0813.html", "node_id":"cce_10_0813.xml", "product_code":"cce", - "code":"232", + "code":"231", "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", @@ -4195,7 +4176,7 @@ "uri":"cce_10_0774.html", "node_id":"cce_10_0774.xml", "product_code":"cce", - "code":"233", + "code":"232", "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", @@ -4213,7 +4194,7 @@ "uri":"cce_10_0775.html", "node_id":"cce_10_0775.xml", "product_code":"cce", - "code":"234", + "code":"233", "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", @@ -4231,7 +4212,7 @@ "uri":"cce_10_0776.html", "node_id":"cce_10_0776.xml", "product_code":"cce", - "code":"235", + "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":"AI Performance-based Scheduling", @@ -4249,7 +4230,7 @@ "uri":"cce_10_0777.html", "node_id":"cce_10_0777.xml", "product_code":"cce", - "code":"236", + "code":"235", "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", @@ -4267,7 +4248,7 @@ "uri":"cce_10_0778.html", "node_id":"cce_10_0778.xml", "product_code":"cce", - "code":"237", + "code":"236", "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", @@ -4285,7 +4266,7 @@ "uri":"cce_10_0425.html", "node_id":"cce_10_0425.xml", "product_code":"cce", - "code":"238", + "code":"237", "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", @@ -4303,7 +4284,7 @@ "uri":"cce_10_0709.html", "node_id":"cce_10_0709.xml", "product_code":"cce", - "code":"239", + "code":"238", "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", @@ -4321,7 +4302,7 @@ "uri":"cce_10_0384.html", "node_id":"cce_10_0384.xml", "product_code":"cce", - "code":"240", + "code":"239", "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", @@ -4339,7 +4320,7 @@ "uri":"cce_10_0020.html", "node_id":"cce_10_0020.xml", "product_code":"cce", - "code":"241", + "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":"Network", @@ -4357,7 +4338,7 @@ "uri":"cce_10_0010.html", "node_id":"cce_10_0010.xml", "product_code":"cce", - "code":"242", + "code":"241", "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", @@ -4375,7 +4356,7 @@ "uri":"cce_10_0280.html", "node_id":"cce_10_0280.xml", "product_code":"cce", - "code":"243", + "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":"Container Network", @@ -4393,7 +4374,7 @@ "uri":"cce_10_0281.html", "node_id":"cce_10_0281.xml", "product_code":"cce", - "code":"244", + "code":"243", "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", @@ -4411,7 +4392,7 @@ "uri":"cce_10_0678.html", "node_id":"cce_10_0678.xml", "product_code":"cce", - "code":"245", + "code":"244", "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", @@ -4429,7 +4410,7 @@ "uri":"cce_10_0284.html", "node_id":"cce_10_0284.xml", "product_code":"cce", - "code":"246", + "code":"245", "des":"Cloud Native 2.0 network model is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network int", "doc_type":"usermanual2", "kw":"Cloud Native 2.0 Network Model,Cloud Native Network 2.0 Settings,User Guide", @@ -4447,7 +4428,7 @@ "uri":"cce_10_0906.html", "node_id":"cce_10_0906.xml", "product_code":"cce", - "code":"247", + "code":"246", "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 Pod Subnets of a Cluster,Cloud Native Network 2.0 Settings,User Guide", @@ -4465,7 +4446,7 @@ "uri":"cce_10_0897.html", "node_id":"cce_10_0897.xml", "product_code":"cce", - "code":"248", + "code":"247", "des":"In Cloud Native 2.0 network mode, 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 i", "doc_type":"usermanual2", "kw":"Binding a Security Group to a Pod Using an Annotation,Cloud Native Network 2.0 Settings,User Guide", @@ -4483,7 +4464,7 @@ "uri":"cce_10_0288.html", "node_id":"cce_10_0288.xml", "product_code":"cce", - "code":"249", + "code":"248", "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", @@ -4501,7 +4482,7 @@ "uri":"cce_10_0196.html", "node_id":"cce_10_0196.xml", "product_code":"cce", - "code":"250", + "code":"249", "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", @@ -4519,7 +4500,7 @@ "uri":"cce_10_0603.html", "node_id":"cce_10_0603.xml", "product_code":"cce", - "code":"251", + "code":"250", "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", @@ -4537,7 +4518,7 @@ "uri":"cce_10_0734.html", "node_id":"cce_10_0734.xml", "product_code":"cce", - "code":"252", + "code":"251", "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", @@ -4555,7 +4536,7 @@ "uri":"cce_10_0651.html", "node_id":"cce_10_0651.xml", "product_code":"cce", - "code":"253", + "code":"252", "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", @@ -4573,7 +4554,7 @@ "uri":"cce_10_0604.html", "node_id":"cce_10_0604.xml", "product_code":"cce", - "code":"254", + "code":"253", "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", @@ -4591,7 +4572,7 @@ "uri":"cce_10_0904.html", "node_id":"cce_10_0904.xml", "product_code":"cce", - "code":"255", + "code":"254", "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", @@ -4609,7 +4590,7 @@ "uri":"cce_10_0283.html", "node_id":"cce_10_0283.xml", "product_code":"cce", - "code":"256", + "code":"255", "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", @@ -4627,7 +4608,7 @@ "uri":"cce_10_0680.html", "node_id":"cce_10_0680.xml", "product_code":"cce", - "code":"257", + "code":"256", "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", @@ -4645,7 +4626,7 @@ "uri":"cce_10_0677.html", "node_id":"cce_10_0677.xml", "product_code":"cce", - "code":"258", + "code":"257", "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", @@ -4663,7 +4644,7 @@ "uri":"cce_10_0282.html", "node_id":"cce_10_0282.xml", "product_code":"cce", - "code":"259", + "code":"258", "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", @@ -4681,7 +4662,7 @@ "uri":"cce_10_0675.html", "node_id":"cce_10_0675.xml", "product_code":"cce", - "code":"260", + "code":"259", "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", @@ -4699,7 +4680,7 @@ "uri":"cce_10_0402.html", "node_id":"cce_10_0402.xml", "product_code":"cce", - "code":"261", + "code":"260", "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", @@ -4717,7 +4698,7 @@ "uri":"cce_10_0382.html", "node_id":"cce_10_0382.xml", "product_code":"cce", - "code":"262", + "code":"261", "des":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure QoS rate limiting for inter-pod acce", "doc_type":"usermanual2", "kw":"Configuring QoS for a Pod,Pod Network Settings,User Guide", @@ -4735,7 +4716,7 @@ "uri":"cce_10_0059.html", "node_id":"cce_10_0059.xml", "product_code":"cce", - "code":"263", + "code":"262", "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", @@ -4753,7 +4734,7 @@ "uri":"cce_10_0247.html", "node_id":"cce_10_0247.xml", "product_code":"cce", - "code":"264", + "code":"263", "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", @@ -4771,7 +4752,7 @@ "uri":"cce_10_0249.html", "node_id":"cce_10_0249.xml", "product_code":"cce", - "code":"265", + "code":"264", "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", "doc_type":"usermanual2", "kw":"Overview,Service,User Guide", @@ -4789,7 +4770,7 @@ "uri":"cce_10_0011.html", "node_id":"cce_10_0011.xml", "product_code":"cce", - "code":"266", + "code":"265", "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 -

2025-02-10

+

2025-03-12

+ +

Add:

+ +

Update:

+ + + +

2025-03-10

+ +

Add:

+ +

Update:

+ +

Delete:

+ + + +

2025-02-28

+ +

Update:

+ + + +

2025-02-10

Add:

@@ -21,7 +45,7 @@

Add:

Update:

- +

Delete:

@@ -78,7 +102,7 @@

2024-06-26

- +

2024-05-30

diff --git a/docs/cce/umn/cce_10_0003.html b/docs/cce/umn/cce_10_0003.html index a1a8f230c..a3ab27df9 100644 --- a/docs/cce/umn/cce_10_0003.html +++ b/docs/cce/umn/cce_10_0003.html @@ -67,7 +67,7 @@

Data Disk

-

At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.

+

At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.

In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, if System Component Storage is set to System Disk, you have the option not to add the default data disk.

Click Expand to configure Data Disk Space Allocation, which is used to allocate space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see Space Allocation of a Data Disk.

For other data disks, a raw disk is created without any processing by default. You can also click Expand and select Mount Disk to mount the data disk to a specified directory.

diff --git a/docs/cce/umn/cce_10_0012.html b/docs/cce/umn/cce_10_0012.html index 935ed1c66..97b06d31f 100644 --- a/docs/cce/umn/cce_10_0012.html +++ b/docs/cce/umn/cce_10_0012.html @@ -92,7 +92,7 @@

Data Disk

-
At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
  • 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.
  • 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.
+
At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
  • 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.
  • 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.

In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, if System Component Storage is set to System Disk, you have the option not to add the 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.

NOTE:
  • If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.
  • 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.
diff --git a/docs/cce/umn/cce_10_0026.html b/docs/cce/umn/cce_10_0026.html index 5605aa3ac..5c902a455 100644 --- a/docs/cce/umn/cce_10_0026.html +++ b/docs/cce/umn/cce_10_0026.html @@ -2,10 +2,8 @@

Viewing CTS Traces in the Trace List

Scenarios

After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.

-

These operation records are retained for seven days on the CTS console and are automatically deleted upon expiration. Manual deletion is not supported.

-
-

Viewing Real-Time Traces

  1. Log in to the management console.
  2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
  3. Choose Trace List in the navigation pane on the left.
  4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
    Figure 1 Filters
    +

    Viewing Real-Time Traces in the Trace List

    1. Log in to the management console.
    2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
    3. Choose Trace List in the navigation pane on the left.
    4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
      Figure 1 Filters
      • Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
        • If you select Resource ID for Search By, specify a resource ID.
        • If you select Trace name for Search By, specify a trace name.
        • If you select Resource name for Search By, specify a resource name.
      • Operator: Select a user.
      • Trace Status: Select All trace statuses, Normal, Warning, or Incident.
      • Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
      @@ -16,7 +14,7 @@

    5. Click View Trace in the Operation column. The trace details are displayed.

      -
    6. For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the CTS User Guide.
    +
  5. For details about key fields in the trace structure, see Trace Structure and Example Traces in the CTS User Guide.
diff --git a/docs/cce/umn/cce_10_0028.html b/docs/cce/umn/cce_10_0028.html index 400b47ffd..17343a826 100644 --- a/docs/cce/umn/cce_10_0028.html +++ b/docs/cce/umn/cce_10_0028.html @@ -163,7 +163,7 @@

Certificate Authentication

-
  • If Automatically generated is selected, the X509-based authentication mode will be enabled by default. X509 is a commonly used certificate format.
  • If Bring your own is selected, the cluster can identify users based on the header in the request body for authentication.

    Upload your CA root certificate, client certificate, and private key.

    +
    • If Automatically generated is selected, the X.509-based authentication mode will be enabled by default. X.509 is a commonly used certificate format.
    • If Bring your own is selected, the cluster can identify users based on the header in the request body for authentication.

      Upload your CA root certificate, client certificate, and private key.

      CAUTION:
      • Upload a file smaller than 1 MB. The CA certificate and client certificate can be in .crt or .cer format. The private key of the client certificate can only be uploaded unencrypted.
      • The validity period of the client certificate must be longer than five years.
      • The uploaded CA root certificate is used by the authentication proxy and for configuring the kube-apiserver aggregation layer. If any of the uploaded certificates is invalid, the cluster cannot be created.
      • Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. The certificate authentication generated using the SHA256 algorithm is supported instead.
    @@ -199,7 +199,7 @@

    Resource Tag

    You can add resource tags to classify resources. A maximum of 20 resource tags can be added.

    -

    You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency.

    +

    You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency.

    Description

    @@ -245,7 +245,17 @@ -

    CCE Node Problem Detector

    +

    Cloud Native Cluster Monitoring

    + +

    (Optional) If selected, this add-on (Cloud Native Cluster Monitoring) will be automatically installed. Cloud Native Cluster Monitoring collects monitoring metrics for your cluster and reports the metrics to AOM. The agent mode does not support HPA based on custom Prometheus statements. If related functions are required, install this add-on manually after the cluster is created.

    + + +

    Cloud Native Log Collection

    + +

    (Optional) If selected, this add-on (Cloud Native Log Collection) will be automatically installed. Cloud Native Log Collection helps report logs to LTS. After the cluster is created, you are allowed to obtain and manage collection rules on the Logging page of the CCE cluster console.

    + + +

    CCE Node Problem Detector

    (Optional) If selected, this add-on (CCE Node Problem Detector) will be automatically installed to detect faults and isolate nodes for prompt cluster troubleshooting.

    @@ -289,7 +299,19 @@ -

    CCE Node Problem Detector

    +

    Cloud Native Cluster Monitoring

    + +

    Select an AOM instance for Cloud Native Cluster Monitoring to report metrics. If no AOM instance is available, click Creating Instance to create one.

    + + +

    Cloud Native Log Collection

    + +

    Select the logs to be collected. If enabled, a log group named k8s-log-{clusterId} will be automatically created, and a log stream will be created for each selected log type.

    +
    • Container log: Standard output logs of containers are collected. The corresponding log stream is named in the format of stdout-{Cluster ID}.
    • Kubernetes Events: Kubernetes logs are collected. The corresponding log stream is named in the format of event-{Cluster ID}.
    • Kubernetes Audit Logs: Audit logs of the master nodes are collected. The corresponding log stream is named in the format of audit-{Cluster ID}.
    • Control Plane Logs: Logs of components like kube-apiserver, kube-controller-manage, and kube-scheduler that run on the master nodes are collected. The corresponding log streams are named in the format of kube-apiserver-{Cluster ID}, kube-controller-manage-{Cluster ID}, and kube-scheduler-{Cluster ID}, respectively.
    +

    If log collection is disabled, choose Logging in the navigation pane of the cluster console after the cluster is created and enable this function.

    + + +

    CCE Node Problem Detector

    This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

    diff --git a/docs/cce/umn/cce_10_0034.html b/docs/cce/umn/cce_10_0034.html index a244294fb..7b5ec0fa4 100644 --- a/docs/cce/umn/cce_10_0034.html +++ b/docs/cce/umn/cce_10_0034.html @@ -19,7 +19,7 @@

    Installing the Add-on

    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons, locate NGINX Ingress Controller on the right, and click Install.
    2. On the Install Add-on page, configure the specifications as needed.

      You can adjust the number of add-on instances 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.

    3. Configure the add-on parameters.

      • Ingress Class: Enter a custom controller name, which uniquely identifies an Ingress controller. The name of each controller in the same cluster must be unique and cannot be set to cce. (cce 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.
      • Namespace for add-on installation: Select a namespace for the ingress controller.
      • Load Balancer: 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.
      • Admission Check: 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 Access Control.
        • Admission check slows down the responses to Ingress requests.
        • Only add-ons of version 2.4.1 or later support admission verification.
        -
      • Nginx Parameters: You can configure the nginx.conf file, which will affect all managed ingresses. You can select GUI or YAML. GUI is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.

        To configure custom parameters supported by the Kubernetes community, choose YAML and find the related parameters in ConfigMaps. For example, you can use the keep-alive-requests parameter to describe how to set the maximum number of requests for keeping active connections to 100.

        +
      • Nginx Parameters: You can configure the nginx.conf file, which will affect all managed ingresses. You can select GUI or YAML. GUI is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.

        To configure custom parameters supported by the Kubernetes community, choose YAML and find the related parameters in ConfigMaps. For example, you can use the keep-alive-requests parameter to describe how to set the maximum number of requests for keeping active connections to 100.

        {
     "keep-alive-requests": "100"
 }
        diff --git a/docs/cce/umn/cce_10_0066.html b/docs/cce/umn/cce_10_0066.html index 1f964de4a..4dd4c17d2 100644 --- a/docs/cce/umn/cce_10_0066.html +++ b/docs/cce/umn/cce_10_0066.html @@ -463,7 +463,7 @@

        v1.27

        v1.28

        -

        CCE clusters 1.28 are supported.

        +

        CCE clusters v1.28 are supported.

        2.1.51

        diff --git a/docs/cce/umn/cce_10_0111.html b/docs/cce/umn/cce_10_0111.html index 9ead90e46..3a5cc846c 100644 --- a/docs/cce/umn/cce_10_0111.html +++ b/docs/cce/umn/cce_10_0111.html @@ -10,6 +10,8 @@
      • Using an SFS File System Through a Dynamic PV
        • +
      • Creating an SFS Subdirectory Using a Dynamic PV
        +
      • Configuring SFS Volume Mount Options
      diff --git a/docs/cce/umn/cce_10_0125.html b/docs/cce/umn/cce_10_0125.html index a10995148..0970fff68 100644 --- a/docs/cce/umn/cce_10_0125.html +++ b/docs/cce/umn/cce_10_0125.html @@ -12,7 +12,7 @@
    4. (Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV
      5. -
    5. Dynamically Creating an SFS Turbo Subdirectory Using StorageClass
      +
    6. Dynamically Creating an SFS Turbo Subdirectory Using StorageClass
diff --git a/docs/cce/umn/cce_10_0129.html b/docs/cce/umn/cce_10_0129.html index 5a13f5d08..99cbb8617 100644 --- a/docs/cce/umn/cce_10_0129.html +++ b/docs/cce/umn/cce_10_0129.html @@ -379,7 +379,7 @@ $configBlock

v1.29

v1.30

-
  • Supported Corefile configurations.
  • CCE clusters 1.30 are supported.
+
  • Supported Corefile configurations.
  • CCE clusters v1.30 are supported.

1.10.1

@@ -393,7 +393,7 @@ $configBlock

v1.28

v1.29

-

CCE clusters 1.29 are supported.

+

CCE clusters v1.29 are supported.

1.10.1

@@ -432,7 +432,7 @@ $configBlock

v1.27

v1.28

-

CCE clusters 1.28 are supported.

+

CCE clusters v1.28 are supported.

1.10.1

@@ -469,7 +469,7 @@ $configBlock

v1.23

v1.25

-

CCE clusters 1.25 are supported.

+

CCE clusters v1.25 are supported.

1.8.4

@@ -495,7 +495,7 @@ $configBlock

v1.21

v1.23

-

CCE clusters 1.23 are supported.

+

CCE clusters v1.23 are supported.

1.8.4

@@ -507,7 +507,7 @@ $configBlock

v1.19

v1.21

-

CCE clusters 1.21 are supported.

+

CCE clusters v1.21 are supported.

1.8.4

@@ -528,7 +528,7 @@ $configBlock

v1.17

v1.19

-

CCE clusters 1.19 are supported.

+

CCE clusters v1.19 are supported.

1.6.5

diff --git a/docs/cce/umn/cce_10_0132.html b/docs/cce/umn/cce_10_0132.html index 2e45a511d..981301ad5 100644 --- a/docs/cce/umn/cce_10_0132.html +++ b/docs/cce/umn/cce_10_0132.html @@ -4,7 +4,7 @@

Introduction

CCE Node Problem Detector (NPD) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. This add-on can run as a DaemonSet or a daemon.

For more information, see node-problem-detector.

-

Notes and Constraints

  • When using this add-on, do not format or partition node disks.
  • Each NPD process occupies 30 m CPU and 100 MiB of memory.
  • If the NPD version is 1.18.45 or later, the EulerOS version of the host machine must be 2.5 or later.
+

Notes and Constraints

  • When using this add-on, do not format or partition node disks.
  • Each NPD process occupies 30m CPUs and 100 MiB of memory.
  • If the NPD version is 1.18.45 or later, the EulerOS version of the host machine must be 2.5 or later.

Permissions

To monitor kernel logs, the NPD add-on needs to read the host /dev/kmsg. Therefore, the privileged mode must be enabled. For details, see privileged.

In addition, CCE mitigates risks according to the least privilege principle. Only the following privileges are available for NPD running:

@@ -100,7 +100,7 @@

Typical scenario: Disk I/O suspension causes process suspension.

Warning event

-

Listening object: /dev/kmsg

+

Listening object: /dev/kmsg

Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."

@@ -112,7 +112,7 @@

Warning event

-

Listening object: /dev/kmsg

+

Listening object: /dev/kmsg

Matching rule: Remounting filesystem read-only

@@ -562,7 +562,7 @@ problem_gauge{reason="CRIIsUp",type="CRIProblem"} 0

v1.27

v1.28

-

CCE clusters 1.28 are supported.

+

CCE clusters v1.28 are supported.

0.8.10

diff --git a/docs/cce/umn/cce_10_0141.html b/docs/cce/umn/cce_10_0141.html index 9b96d0b2e..74f098749 100644 --- a/docs/cce/umn/cce_10_0141.html +++ b/docs/cce/umn/cce_10_0141.html @@ -98,7 +98,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi

v1.29

v1.30

-
  • Supported xGPU configuration by node pool.
  • Supported GPU rendering.
  • Clusters 1.30 are supported.
+
  • Supported xGPU configuration by node pool.
  • Supported GPU rendering.
  • Clusters v1.30 are supported.

2.6.4

@@ -128,7 +128,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi

v1.28

-

Clusters 1.28 are supported.

+

Clusters v1.28 are supported.

2.0.69

@@ -189,7 +189,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi

v1.21

v1.23

-

CCE clusters 1.23 are supported.

+

CCE clusters v1.23 are supported.

1.2.9

@@ -199,7 +199,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi

v1.19

v1.21

-

CCE clusters 1.21 are supported.

+

CCE clusters v1.21 are supported.

1.2.2

diff --git a/docs/cce/umn/cce_10_0150.html b/docs/cce/umn/cce_10_0150.html index 58b21dcd1..19e358215 100644 --- a/docs/cce/umn/cce_10_0150.html +++ b/docs/cce/umn/cce_10_0150.html @@ -174,8 +174,6 @@ myjob-29qlw 0/1 Completed 0 4m5s ...

If the status is Completed, the job is complete.

  • View the pod logs.

    kubectl logs <pod_name>

    -
    # kubectl logs myjob-29qlw
-3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326459958133904780275901

    • Related Operations

    After a one-off job is created, you can perform operations listed in Table 2.

    diff --git a/docs/cce/umn/cce_10_0154.html b/docs/cce/umn/cce_10_0154.html index 91e6e201d..6ab93398a 100644 --- a/docs/cce/umn/cce_10_0154.html +++ b/docs/cce/umn/cce_10_0154.html @@ -76,7 +76,7 @@

    Change History

    -
    Table 3 Release history for the add-on adapted to clusters 1.30

    Add-on Version

    +
    @@ -99,7 +99,7 @@ - @@ -108,7 +108,7 @@
    Table 3 Release history for the add-on adapted to clusters v1.30

    Add-on Version

    Supported Cluster Version

    v1.30

    • Clusters 1.30 are supported.
    • Included the name of the target node pool to the reported event.
    +
    • Clusters v1.30 are supported.
    • Added the name of the target node pool to the events.

    1.30.1

    -
    Table 4 Release history for the add-on adapted to clusters 1.29

    Add-on Version

    +
    @@ -140,7 +140,7 @@ - @@ -149,7 +149,7 @@
    Table 4 Release history for the add-on adapted to clusters v1.29

    Add-on Version

    Supported Cluster Version

    v1.29

    Clusters 1.29 are supported.

    +

    Clusters v1.29 are supported.

    1.29.1

    -
    Table 5 Release history for the add-on adapted to clusters 1.28

    Add-on Version

    +
    @@ -199,7 +199,7 @@
    Table 5 Release history for the add-on adapted to clusters v1.28

    Add-on Version

    Supported Cluster Version

    -
    Table 6 Release history for the add-on adapted to clusters 1.27

    Add-on Version

    +
    @@ -249,7 +249,7 @@
    Table 6 Release history for the add-on adapted to clusters v1.27

    Add-on Version

    Supported Cluster Version

    -
    Table 7 Release history for the add-on adapted to clusters 1.25

    Add-on Version

    +
    @@ -308,7 +308,7 @@ - @@ -317,7 +317,7 @@
    Table 7 Release history for the add-on adapted to clusters v1.25

    Add-on Version

    Supported Cluster Version

    v1.25

    • CCE clusters 1.25 are supported.
    • Modified the memory request and limit of a customized flavor.
    • Enabled to report an event indicating that scaling cannot be performed in a node pool with auto scaling disabled.
    +
    • CCE clusters v1.25 are supported.
    • Modified the memory request and limit of a customized flavor.
    • Enabled to report an event indicating that scaling cannot be performed in a node pool with auto scaling disabled.

    1.25.0

    -
    Table 8 Release history for the add-on adapted to clusters 1.23

    Add-on Version

    +
    @@ -394,7 +394,7 @@
    Table 8 Release history for the add-on adapted to clusters v1.23

    Add-on Version

    Supported Cluster Version

    -
    Table 9 Release history for the add-on adapted to clusters 1.21

    Add-on Version

    +
    @@ -480,7 +480,7 @@
    Table 9 Release history for the add-on adapted to clusters v1.21

    Add-on Version

    Supported Cluster Version

    -
    Table 10 Release history for the add-on adapted to clusters 1.19

    Add-on Version

    +
    @@ -566,7 +566,7 @@
    Table 10 Release history for the add-on adapted to clusters v1.19

    Add-on Version

    Supported Cluster Version

    -
    - - diff --git a/docs/cce/umn/cce_10_0378.html b/docs/cce/umn/cce_10_0378.html index 92a40a8b4..fb0870bce 100644 --- a/docs/cce/umn/cce_10_0378.html +++ b/docs/cce/umn/cce_10_0378.html @@ -170,8 +170,8 @@ metadata: everest.io/reclaim-policy: retain-volume-only name: pv-evs-test labels: - failure-domain.beta.kubernetes.io/region: <your_region> # Region of the node where the application is to be deployed - failure-domain.beta.kubernetes.io/zone: <your_zone> # AZ of the node where the application is to be deployed + failure-domain.beta.kubernetes.io/region: <your_region> # Region of the node where the application is to be deployed + failure-domain.beta.kubernetes.io/zone: <your_zone> # AZ of the node where the application is to be deployed spec: accessModes: - ReadWriteOnce diff --git a/docs/cce/umn/cce_10_0380.html b/docs/cce/umn/cce_10_0380.html index 128872c6d..840fc712f 100644 --- a/docs/cce/umn/cce_10_0380.html +++ b/docs/cce/umn/cce_10_0380.html @@ -48,6 +48,7 @@ NAME PROVISIONER AGE csi-disk everest-csi-provisioner 17d # EVS disk csi-disk-topology everest-csi-provisioner 17d # EVS disks created with delay csi-nas everest-csi-provisioner 17d # SFS 1.0 +csi-sfs everest-csi-provisioner 17d # SFS 3.0 csi-obs everest-csi-provisioner 17d # OBS csi-sfsturbo everest-csi-provisioner 17d # SFS Turbo
    Each StorageClass contains the default parameters used for dynamically creating a PV. The following is an example of StorageClass for EVS disks:
    kind: StorageClass
diff --git a/docs/cce/umn/cce_10_0384.html b/docs/cce/umn/cce_10_0384.html
index 037e1c873..63b96e298 100644
--- a/docs/cce/umn/cce_10_0384.html
+++ b/docs/cce/umn/cce_10_0384.html
@@ -219,7 +219,7 @@ preemptionPolicy: PreemptLowerPriority
 value: -90000
  
 EOF
    -

  • Deploy online and offline jobs and configure priorityClasses for these jobs.

    The volcano.sh/qos-level 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 schedulerName to volcano to enable Volcano.

    +

  • Deploy online and offline jobs and configure priorityClasses for these jobs.

    The volcano.sh/qos-level 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 schedulerName to volcano to enable Volcano.

    The priorities between online jobs and between offline jobs are not differentiated, and the value validity is not verified. If the value of volcano.sh/qos-level of an offline job is not a negative integer ranging from -7 to 0, the job is processed as an online job.

    For an offline job:

    diff --git a/docs/cce/umn/cce_10_0385.html b/docs/cce/umn/cce_10_0385.html index 16be739d1..bc7b85f3a 100644 --- a/docs/cce/umn/cce_10_0385.html +++ b/docs/cce/umn/cce_10_0385.html @@ -507,7 +507,7 @@ spec:
    • diff --git a/docs/cce/umn/cce_10_0405.html b/docs/cce/umn/cce_10_0405.html index 8209815f2..ba86639b4 100644 --- a/docs/cce/umn/cce_10_0405.html +++ b/docs/cce/umn/cce_10_0405.html @@ -53,13 +53,13 @@

    Version 1.29

    -
    Table 11 Release history for the add-on adapted to clusters 1.17

    Add-on Version

    +
    @@ -625,7 +625,7 @@ - diff --git a/docs/cce/umn/cce_10_0182.html b/docs/cce/umn/cce_10_0182.html index a8b1d6324..638a8817e 100644 --- a/docs/cce/umn/cce_10_0182.html +++ b/docs/cce/umn/cce_10_0182.html @@ -4,6 +4,8 @@
    diff --git a/docs/cce/umn/cce_10_0193.html b/docs/cce/umn/cce_10_0193.html index 722d7ec2c..25c01eacc 100644 --- a/docs/cce/umn/cce_10_0193.html +++ b/docs/cce/umn/cce_10_0193.html @@ -929,7 +929,7 @@ tolerations:

    v1.27

    v1.28

    -
    - - - - - diff --git a/docs/cce/umn/cce_10_0198.html b/docs/cce/umn/cce_10_0198.html index 4df16333b..a9d9cde48 100644 --- a/docs/cce/umn/cce_10_0198.html +++ b/docs/cce/umn/cce_10_0198.html @@ -76,7 +76,7 @@ - - @@ -94,7 +94,7 @@

    v1.28

    v1.29

    - @@ -120,7 +120,7 @@

    v1.27

    v1.28

    - @@ -157,7 +157,7 @@

    v1.23

    v1.25

    - @@ -168,7 +168,7 @@

    v1.21

    v1.23

    - @@ -180,7 +180,7 @@

    v1.19

    v1.21

    - diff --git a/docs/cce/umn/cce_10_0212.html b/docs/cce/umn/cce_10_0212.html index 5c9a0855b..5cf63aa47 100644 --- a/docs/cce/umn/cce_10_0212.html +++ b/docs/cce/umn/cce_10_0212.html @@ -26,7 +26,7 @@ - @@ -53,6 +53,13 @@

    If you choose to retain the node, the logical volumes will not be deleted. If you choose to delete or reset the node, the logical volumes will be deleted.

    + + + + - - - @@ -332,7 +332,7 @@ - - - - diff --git a/docs/cce/umn/cce_10_0277.html b/docs/cce/umn/cce_10_0277.html index 0695892ec..07a1ea9cf 100644 --- a/docs/cce/umn/cce_10_0277.html +++ b/docs/cce/umn/cce_10_0277.html @@ -42,6 +42,11 @@ + + + @@ -173,6 +174,7 @@ @@ -184,6 +186,7 @@ @@ -195,6 +198,7 @@ diff --git a/docs/cce/umn/cce_10_0337.html b/docs/cce/umn/cce_10_0337.html index d88642428..567cdd82f 100644 --- a/docs/cce/umn/cce_10_0337.html +++ b/docs/cce/umn/cce_10_0337.html @@ -85,12 +85,13 @@ spec: csi: driver: nas.csi.everest.io # Dependent storage driver for the mounting fsType: nfs - volumeHandle: <your_volume_id> # ID of the SFS Capacity-Oriented volume + volumeHandle: <your_volume_id> # ID of the SFS Capacity-Oriented volume or the SFS volume name when SFS 3.0 is used volumeAttributes: everest.io/share-export-location: <your_location> # Shared path of the SFS volume storage.kubernetes.io/csiProvisionerIdentity: everest-csi-provisioner + everest.io/sfs-version: sfs3.0 # SFS 3.0 is used. persistentVolumeReclaimPolicy: Retain # Reclaim policy - storageClassName: csi-nas # StorageClass name. + storageClassName: csi-nas # Storage class name. csi-nas indicates that SFS Capacity-Oriented is used. csi-sfs indicates that SFS 3.0 is used. mountOptions: # Mount options - vers=3 - nolock @@ -116,6 +117,7 @@ parameters: csi.storage.k8s.io/csi-driver-name: nas.csi.everest.io csi.storage.k8s.io/fstype: nfs everest.io/share-access-to: <your_vpc_id> # VPC ID of the cluster + everest.io/sfs-version: sfs3.0 # SFS 3.0 is used. This parameter is not required for SFS Capacity-Oriented. reclaimPolicy: Delete volumeBindingMode: Immediate mountOptions: # Mount options diff --git a/docs/cce/umn/cce_10_0342.html b/docs/cce/umn/cce_10_0342.html index 871ba54ae..fb0501c0a 100644 --- a/docs/cce/umn/cce_10_0342.html +++ b/docs/cce/umn/cce_10_0342.html @@ -31,7 +31,10 @@ - @@ -63,13 +66,6 @@ - - - -
    Table 11 Release history for the add-on adapted to clusters v1.17

    Add-on Version

    Supported Cluster Version

    v1.17

    Clusters 1.17 are supported.

    +

    Clusters v1.17 are supported.

    1.17.0
    • Supported Kubernetes 1.28.
    • Supported load-aware scheduling.
    • Updated image OS to HCE 2.0.
    • Optimized CSI resource preemption.
    • Optimized load-aware rescheduling.
    • Optimized preemption in hybrid deployment scenarios.
    +
    • Supported Kubernetes v1.28.
    • Supported load-aware scheduling.
    • The image OS is updated to HCE OS 2.0.
    • Optimized CSI resource preemption.
    • Optimized load-aware rescheduling.
    • Optimized preemption in hybrid deployment scenarios.

    1.11.6

    @@ -940,7 +940,7 @@ tolerations:

    v1.25

    v1.27

    • Supported Kubernetes 1.27.
    • Supported rescheduling.
    • Supported affinity scheduling of nodes in the node pool.
    • Optimized the scheduling performance.
    +
    • Supported Kubernetes v1.27.
    • Supported rescheduling.
    • Supported affinity scheduling of nodes in the node pool.
    • Optimized the scheduling performance.

    1.9.1

    @@ -950,7 +950,7 @@ tolerations:

    v1.23

    v1.25

    • Fixes the issue that the counting pipeline pod of the networkresource add-on occupies supplementary network interfaces (Sub-ENI).
    • Fixes the issue where the binpack add-on scores nodes with insufficient resources.
    • Fixes the issue of processing resources in the pod with unknown end status.
    • Optimizes event output.
    • Supports HA deployment by default.
    +
    • Fixed the issue that the counting pipeline pod of the networkresource add-on occupies supplementary network interfaces (sub-ENIs).
    • Fixed the issue where the binpack add-on scores nodes with insufficient resources.
    • Fixed the issue of processing resources in the pod with unknown end status.
    • Optimized event output.
    • Supported HA deployment by default.

    1.7.1

    @@ -960,7 +960,7 @@ tolerations:

    v1.23

    v1.25

    Adapts to clusters 1.25.

    +

    Supported clusters v1.25.

    1.4.5

    @@ -969,7 +969,7 @@ tolerations:

    v1.19

    v1.21

    Changes the deployment mode of volcano-scheduler from statefulset to deployment, and fixes the issue that pods cannot be automatically migrated when the node is abnormal.

    +

    Changed the deployment mode of Volcano Scheduler from StatefulSet to Deployment, and fixed the issue that pods cannot be automatically migrated when the node is abnormal.

    1.3.7

    @@ -979,7 +979,7 @@ tolerations:

    v1.19

    v1.21

    • Supports hybrid deployment of online and offline jobs and resource oversubscription.
    • Optimizes the scheduling throughput for clusters.
    • Fixes the issue where the scheduler panics in certain scenarios.
    • Fixes the issue that the volumes.secret verification of the volcano job in the CCE clusters 1.15 fails.
    • Fixes the issue that jobs fail to be scheduled when volumes are mounted.
    +
    • Supported hybrid deployment of online and offline jobs and resource oversubscription.
    • Optimized the scheduling throughput for clusters.
    • Fixed the issue where the scheduler panics in certain scenarios.
    • Fixed the issue that the volumes.secret verification of the volcano job in the CCE clusters v1.15 fails.
    • Fixed the issue that jobs fail to be scheduled when volumes are mounted.

    Data Disk

    At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.

    +

    At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.

    In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, if System Component Storage is set to System Disk, you have the option not to add the default data disk.

    Click Expand to configure Data Disk Space Allocation, which is used to allocate space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see Space Allocation of a Data Disk.

    For other data disks, a raw disk is created without any processing by default. You can also click Expand and select Mount Disk to mount the data disk to a specified directory.

    diff --git a/docs/cce/umn/cce_10_0205.html b/docs/cce/umn/cce_10_0205.html index 5edfbbb4f..d967824df 100644 --- a/docs/cce/umn/cce_10_0205.html +++ b/docs/cce/umn/cce_10_0205.html @@ -80,7 +80,7 @@

    v1.29

    v1.30

    CCE clusters 1.30 are supported.

    +

    CCE clusters v1.30 are supported.

    0.6.2

    CCE clusters 1.29 are supported.

    +

    CCE clusters v1.29 are supported.

    0.6.2

    CCE clusters 1.28 are supported.

    +

    CCE clusters v1.28 are supported.

    0.6.2

    CCE clusters 1.25 are supported.

    +

    CCE clusters v1.25 are supported.

    0.6.2

    CCE clusters 1.23 are supported.

    +

    CCE clusters v1.23 are supported.

    0.4.4

    CCE clusters 1.21 are supported.

    +

    CCE clusters v1.21 are supported.

    0.4.4

    SFS

    SFS Capacity-Oriented

    +

    SFS Capacity-Oriented or SFS 3.0

    Yes

    SFS 3.0 subdirectory

    +

    A directory in SFS 3.0

    +

    No

    +

    SFS Turbo subdirectory

    A directory in SFS Turbo

    diff --git a/docs/cce/umn/cce_10_0213.html b/docs/cce/umn/cce_10_0213.html index 8c673d41d..499305adf 100644 --- a/docs/cce/umn/cce_10_0213.html +++ b/docs/cce/umn/cce_10_0213.html @@ -170,7 +170,7 @@

    QPS for communicating with kube-apiserver.

    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If the number of nodes in a cluster is 1000 or more, the default value is 200.
    +
    • If the number of nodes in a cluster is less than 1,000, the default value is 100.
    • If the number of nodes in a cluster is 1,000 or more, the default value is 200.

    Burst for communicating with kube-apiserver

    @@ -179,7 +179,7 @@

    Burst for communicating with kube-apiserver.

    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If the number of nodes in a cluster is 1000 or more, the default value is 200.
    +
    • If the number of nodes in a cluster is less than 1,000, the default value is 100.
    • If the number of nodes in a cluster is 1000 or more, the default value is 200.

    Whether to enable GPU sharing

    @@ -224,7 +224,7 @@

    Default: 5

    Concurrent number of garbage collector

    +

    Concurrent number of garbage collectors

    concurrent-gc-syncs

    horizontal-pod-autoscaler-sync-period

    Period for the horizontal pod autoscaler to perform auto scaling on pods. A smaller value will result in a faster auto scaling response and higher CPU load.

    -
    NOTE:

    Make sure to configure this parameter properly as a lengthy period can cause the controller to respond slowly, while a short period may overload the cluster control plane.

    +
    NOTE:

    Make sure to configure this parameter properly as a lengthy period can cause the controller to respond slowly, while a short period may overload the cluster management plane.

    Default: 15 seconds

    @@ -380,7 +380,7 @@

    QPS for communicating with kube-apiserver

    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If the number of nodes in a cluster is 1000 or more, the default value is 200.
    +
    • If the number of nodes in a cluster is less than 1,000, the default value is 100.
    • If the number of nodes in a cluster is 1,000 or more, the default value is 200.

    Burst for communicating with kube-apiserver

    @@ -389,7 +389,7 @@

    Burst for communicating with kube-apiserver

    • If the number of nodes in a cluster is less than 1000, the default value is 100.
    • If the number of nodes in a cluster is 1000 or more, the default value is 200.
    +
    • If the number of nodes in a cluster is less than 1,000, the default value is 100.
    • If the number of nodes in a cluster is 1,000 or more, the default value is 200.

    The maximum number of terminated pods that can be kept before the Pod GC deletes the terminated pod

    diff --git a/docs/cce/umn/cce_10_0240.html b/docs/cce/umn/cce_10_0240.html index 1232fdea7..aa4acc3f5 100644 --- a/docs/cce/umn/cce_10_0240.html +++ b/docs/cce/umn/cce_10_0240.html @@ -119,7 +119,7 @@

    v1.27

    v1.28

    CCE clusters 1.28 are supported.

    +

    CCE clusters v1.28 are supported.

    1.3.14

    @@ -130,7 +130,7 @@

    v1.25

    v1.27

    CCE clusters 1.27 are supported.

    +

    CCE clusters v1.27 are supported.

    This add-on uses Prometheus-operator and Prometheus to provide easy-to-use, end-to-end Kubernetes cluster monitoring.

    Cloud Native Log Collection

    +

    This add-on collects logs and is built based on open-source Fluent Bit and OpenTelemetry. It supports CRD-based log collection policies. It collects and forwards stdout logs, container file logs, node logs, and Kubernetes event logs in a cluster based on configured policies.

    +

    CCE Node Problem Detector

    This add-on monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. It can run as a DaemonSet or a daemon.

    diff --git a/docs/cce/umn/cce_10_0307.html b/docs/cce/umn/cce_10_0307.html index 0b46add07..371978f85 100644 --- a/docs/cce/umn/cce_10_0307.html +++ b/docs/cce/umn/cce_10_0307.html @@ -162,6 +162,7 @@

    TB

    SFS 1.0: PB

    +

    SFS 3.0: EB

    General-purpose: TB

    1–2 ms

    SFS 1.0: 3–20 ms

    +

    SFS 3.0: 10 ms

    General-purpose: 1–5 ms

    2200–256000, depending on flavors

    SFS 1.0: 2000

    +

    SFS 3.0: millions

    General-purpose: up to 100,000

    MB/s

    SFS 1.0: GB/s

    +

    SFS 3.0: TB/s

    General-purpose: up to GB/s

    For users who have higher requirements on performance, resource utilization, and full-scenario coverage

    Specification difference

    +

    Specification difference

    +

    +

    +

    Network model

    • VM-level isolation is supported for secure containers that run only on physical machines.
    • cgroups are used to isolate common containers.

    Edge infrastructure management

    -

    Not supported

    -

    Management of CloudPond edge sites

    -
    diff --git a/docs/cce/umn/cce_10_0363.html b/docs/cce/umn/cce_10_0363.html index db935d251..5b8925fd0 100644 --- a/docs/cce/umn/cce_10_0363.html +++ b/docs/cce/umn/cce_10_0363.html @@ -94,7 +94,7 @@

    Data Disk

    At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
    • 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.
    • 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.
    +
    At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
    • 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.
    • 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.

    In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, if System Component Storage is set to System Disk, you have the option not to add the 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.

    NOTE:
    • If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.
    • 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.
    diff --git a/docs/cce/umn/cce_10_0364.html b/docs/cce/umn/cce_10_0364.html index 3d391b4d8..11f422ce7 100644 --- a/docs/cce/umn/cce_10_0364.html +++ b/docs/cce/umn/cce_10_0364.html @@ -32,7 +32,7 @@ spec: property: ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH pathType: ImplementationSpecific - ingressClassName: nginx # Nginx Ingress is used. If multiple Nginx Ingress controllers are installed in the cluster, replace nginx with the custom name of the controller associated with the ingress. + ingressClassName: nginx # Nginx Ingress is used. If multiple NGINX Ingress Controllers are installed in the cluster, replace nginx with the custom name of the controller associated with the ingress.
    For clusters of v1.21 or earlier:
    apiVersion: networking.k8s.io/v1beta1
 kind: Ingress
@@ -78,7 +78,7 @@ spec:

    String

    nginx: indicates that Nginx Ingress is used. This option is available only after the NGINX Ingress Controller add-on is installed. If multiple NGINX Ingress Controllers are installed in the cluster, replace nginx with the custom name of the controller associated with the ingress.

    +

    nginx: indicates that Nginx Ingress is used. This option is available only after the NGINX Ingress Controller add-on is installed. If multiple NGINX Ingress Controllers are installed in the cluster, replace nginx with the custom name of the controller associated with the ingress.

    Multiple NGINX Ingress Controller add-ons can be installed in one cluster if the add-on version is 2.5.4 or later. In this case, the value of this parameter must be the controller name customized during controller installation, which indicates that the ingress is managed by the controller.

    This parameter is mandatory when an ingress is created by calling the API.

    If the pod uses hostNetwork, the ELB forwards the request to the host network after this annotation is used.

    Options:

    -
    • true: enabled
    • false (default): disabled
    +
    • true: enabled
    • false (default): disabled

    v1.9 or later
    Table 2 Release notes for the v1.29 patch

    CCE Cluster Patch Version

    +
    - - - @@ -103,13 +103,13 @@

    Version 1.28

    -
    Table 2 Release notes for the v1.29 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing
    Table 3 Release notes for the v1.28 patch

    CCE Cluster Patch Version

    +
    - - - @@ -188,98 +188,96 @@

    -

    Version 1.27

    dockershim has been removed since Kubernetes v1.24, and Docker is not supported in v1.24 and later versions by default. Use containerd.

    -
    - -
    Table 3 Release notes for the v1.28 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing
    Table 4 Release notes for the v1.27 patch

    CCE Cluster Patch Version

    +

    Version 1.27

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -289,13 +287,13 @@

    Version 1.25

    All nodes in the CCE clusters of version 1.25, except the ones running EulerOS 2.5, use containerd by default.

    -
    Table 4 Release notes for the v1.27 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing

    +

    Vulnerability Fixing

    v1.27.16-r0

    +

    v1.27.16-r0

    v1.27.16

    +

    v1.27.16

    • LoadBalancer ingresses can forward requests based on parameters such as HTTP request methods, HTTP request headers, query strings, CIDR blocks, and cookies.
    +
    • LoadBalancer ingresses can forward requests based on parameters such as HTTP request methods, HTTP request headers, query strings, CIDR blocks, and cookies.
    • You can change a node password when updating its node pool.
    • A node can be attached with no data disks.
    • When updating a LoadBalancer ingress, you can modify the configuration of redirecting HTTP requests to HTTPS requests.
    • The default image address can be customized for Docker node pools.
    +
    • You can change a node password when updating its node pool.
    • A node can be attached with no data disks.
    • When updating a LoadBalancer ingress, you can modify the configuration of redirecting HTTP requests to HTTPS requests.
    • The default image address can be customized for Docker node pools.

    Fixed some security issues.

    +

    Fixed some security issues.

    v1.27.8-r0

    +

    v1.27.8-r0

    v1.27.12

    +

    v1.27.12

    • CCE ingresses support traffic distribution based on custom HTTP headers.
    • Scaling priority policies can be configured for third-party workloads.
    • You can configure a security group for a pod using annotations. This feature is only available for CCE Turbo clusters.
    • You can bind an existing EIP to a pod. This feature is only available for CCE Turbo clusters.
    +
    • CCE ingresses support traffic distribution based on custom HTTP headers.
    • Scaling priority policies can be configured for third-party workloads.
    • You can configure a security group for a pod using annotations. This feature is only available for CCE Turbo clusters.
    • You can bind an existing EIP to a pod. This feature is only available for CCE Turbo clusters.
    • An in-progress node drainage can be canceled.
    • When updating a node pool, you can change its agency name, prefix, and suffix.
    • Kubernetes labels and taints of a node are retained after the node is reset.
    • Both the Kubernetes service account token volume projection and the load scaling controller can be configured.
    +
    • An in-progress node drainage can be canceled.
    • When updating a node pool, you can change its agency name, prefix, and suffix.
    • Kubernetes labels and taints of a node are retained after the node is reset.
    • Both the Kubernetes service account token volume projection and the load scaling controller can be configured.

    Fixed some security issues.

    +

    Fixed some security issues.

    v1.27.5-r0

    +

    v1.27.5-r0

    v1.27.4

    +

    v1.27.4

    LoadBalancer Services and ingresses allow you to:
    • Configure SNI.
    • Enable HTTP/2.
    • Configure idle timeout, request timeout, and response timeout.
    +
    LoadBalancer Services and ingresses allow you to:
    • Configure SNI.
    • Enable HTTP/2.
    • Configure idle timeout, request timeout, and response timeout.

    None

    +

    None

    Fixed some security issues.

    +

    Fixed some security issues.

    v1.27.3-r4

    +

    v1.27.3-r4

    v1.27.4

    +

    v1.27.4

    None

    +

    None

    None

    +

    None

    Fixed CVE-2024-21626 issues.

    +

    Fixed CVE-2024-21626 issues.

    v1.27.2-r0

    +

    v1.27.2-r0

    v1.27.2

    +

    v1.27.2

    • Volcano supports node pool affinity scheduling.
    • Volcano supports workload rescheduling.
    +
    • Volcano supports node pool affinity scheduling.
    • Volcano supports workload rescheduling.

    None

    +

    None

    Fixed some security issues.

    +

    Fixed some security issues.

    v1.27.1-r10

    +

    v1.27.1-r10

    v1.27.2

    +

    v1.27.2

    None

    +

    None

    Optimized the events generated during node pool scaling.

    +

    Optimized the events generated during node pool scaling.

    Fixed some security issues.

    +

    Fixed some security issues.

    v1.27.1-r0

    +

    v1.27.1-r0

    v1.27.2

    +

    v1.27.2

    CCE clusters of v1.27 are released for the first time. For more information, see Kubernetes 1.27 Release Notes.

    +

    CCE clusters of v1.27 are released for the first time. For more information, see Kubernetes 1.27 Release Notes.

    • Both soft eviction and hard eviction are supported in node pool configurations.

    None

    +

    None

    None

    +

    None
    Table 5 Release notes for the v1.25 patch

    CCE Cluster Patch Version

    +
    - - - @@ -417,13 +415,13 @@

    Version 1.23

    -
    Table 5 Release notes for the v1.25 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing
    Table 6 Release notes for the v1.23 patch

    CCE Cluster Patch Version

    +
    - - - @@ -557,13 +555,13 @@

    Version 1.21

    -
    Table 6 Release notes for the v1.23 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing
    Table 7 Release notes for the v1.21 patch

    CCE Cluster Patch Version

    +
    - - - @@ -674,13 +672,13 @@

    Version 1.19

    -
    Table 7 Release notes for the v1.21 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing
    - @@ -96,7 +96,7 @@ - @@ -107,7 +107,7 @@ - @@ -118,7 +118,7 @@ - @@ -129,7 +129,7 @@ - diff --git a/docs/cce/umn/cce_10_0553.html b/docs/cce/umn/cce_10_0553.html index 737b9b8fe..b7c837d5e 100644 --- a/docs/cce/umn/cce_10_0553.html +++ b/docs/cce/umn/cce_10_0553.html @@ -8,6 +8,12 @@
  • Collecting Container Logs
    • +
  • Collecting Kubernetes Events
    +
    • +
  • Collecting Control Plane Component Logs
    +
    • +
  • Collecting Audit Logs
    +
    • diff --git a/docs/cce/umn/cce_10_0554.html b/docs/cce/umn/cce_10_0554.html new file mode 100644 index 000000000..cbc84702f --- /dev/null +++ b/docs/cce/umn/cce_10_0554.html @@ -0,0 +1,67 @@ + + +

    Collecting Control Plane Component Logs

    +

    CCE supports logging for master nodes. On the Logging page, you can select one or more control plane components (kube-controller-manager, kube-apiserver, and kube-scheduler) whose logs need to be reported.

    +

    Constraints

    • The cluster version must be v1.21.7-r0 or later, v1.23.5-r0 or later, or 1.25.
    • There is required LTS resource quota.
    +
    +

    Control Plane Components

    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 Kubernetes Components.

    + +
    Table 8 Release notes for the v1.19 patch

    CCE Cluster Patch Version

    +
    - - - diff --git a/docs/cce/umn/cce_10_0406.html b/docs/cce/umn/cce_10_0406.html index 980daf48d..991c1643e 100644 --- a/docs/cce/umn/cce_10_0406.html +++ b/docs/cce/umn/cce_10_0406.html @@ -16,8 +16,8 @@
    • cap_dac_override: reads the Docker info data.

    Installing the Add-on

    The Cloud Native Cluster Monitoring add-on automatically selects a deployment mode based on Data Storage Configuration. This is supported by Cloud Native Cluster Monitoring 3.7.1 or later.

    -
    • Original agent mode: Disable Local data storage and enable at least one of Report Monitoring Data to AOM and Report Monitoring Data to a Third-Party Platform.
    -
    • Original server mode: Enable Local data storage and Report Monitoring Data to AOM or Report Monitoring Data to a Third-Party Platform.
    +
    • Original agent mode: Disable Local data storage and enable at least one of Report Monitoring Data to AOM and Report Monitoring Data to a Third-Party Platform.
    +
    • Original server mode: Enable Local data storage and Report Monitoring Data to AOM or Report Monitoring Data to a Third-Party Platform.
    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons, locate Cloud Native Cluster Monitoring on the right, and click Install.
    2. On the Install Add-on page, enable at least one item in the Data Storage Configuration area.

      • Reporting Monitoring Data to AOM: Report Prometheus data to AOM. After this function is enabled, you can select the corresponding AOM instance. The collected basic metrics are free of charge. Custom metrics are charged by AOM. To interconnect with AOM, you must have certain permissions. Only users in the admin user group can perform this operation.
      • Reporting Monitoring Data to a Third-Party Platform: To report Prometheus data to a third-party monitoring system, you need to enter the address and token of the third-party monitoring system and determine whether to skip certificate authentication.
      • Local data storage: Select the type and size of a disk for storing monitoring data to store Prometheus data in PVCs in the cluster. Storage volumes are not deleted along with the add-on. If local data storage is enabled, all components will be deployed. For details, see Components.

        An available PVC named pvc-prometheus-server exists in namespace monitoring and will be used as the storage source.

        @@ -226,7 +226,7 @@ custom-metrics-apiserver-d4f556ff9-l2j2m 38m 44Mi

        v1.29

        v1.30

        -
    diff --git a/docs/cce/umn/cce_10_0416.html b/docs/cce/umn/cce_10_0416.html new file mode 100644 index 000000000..30b9e5718 --- /dev/null +++ b/docs/cce/umn/cce_10_0416.html @@ -0,0 +1,177 @@ + + +

    Cloud Native Log Collection

    +

    Introduction

    Cloud Native Log Collection is built based on Fluent Bit and OpenTelemetry. It collects logs and Kubernetes events. This add-on supports CRD-based log collection policies. It collects and forwards standard output logs, container file logs, node logs, and Kubernetes event logs in a cluster based on configured policies. It also reports Kubernetes events to AOM for configuring event alarms. By default, all abnormal events and some normal events are reported.

    +

    In 1.3.2 and later versions, Cloud Native Log Collection reports all warning events and some normal events to AOM by default. The reported events can be used to configure alarms. If the cluster version is 1.19.16, 1.21.11, 1.23.9, 1.25.4, or later, after Cloud Native Log Collection is installed, events are reported to AOM by this add-on instead of the control plane component. After Cloud Native Log Collection is uninstalled, events will not be reported to AOM.

    +
    +
    +

    Notes and Constraints

    This add-on is available only in clusters v1.17 or later.

    +
    +

    Add-on Performance

    +
    Table 8 Release notes for the v1.19 patch

    CCE Cluster Patch Version

    Kubernetes Version

    +

    Kubernetes Version

    Feature Updates

    +

    Feature Updates

    Optimization

    +

    Optimization

    Vulnerability Fixing

    CCE clusters 1.30 are supported.

    +

    CCE clusters v1.30 are supported.

    2.37.8

    + + + + + + + + + + + + + + + + + + + + + +

    Item

    +

    Description

    +

    Remarks

    +

    Size of a log

    +

    Each individual log must not exceed 512 KB in size. In the case of multi-line logs, the length of each line will be calculated separately.

    +

    None

    +

    Maximum number of collected files

    +

    On a single node, the total number of files that can be listened by all log collection rules is limited to 4,095.

    +

    None

    +

    Log collection rate

    +
    • If the add-on version is earlier than 1.5.0, in each cluster, no more than 10,000 single-line logs can be collected per second, and no more than 2000 multi-line logs can be collected per second.
    • If the add-on version is 1.5.0 or later, on each node, no more than 20,000 logs or 10 MB of logs can be collected per second.
    +

    Service quality cannot be ensured if any of these limits is exceeded.

    +

    Configuration update

    +

    Configuration updates take effect in 1 to 3 minutes.

    +

    None

    +
    +
    + +

    Permissions

    The fluent-bit component of the log-agent add-on reads and collects the stdout logs on each node, file logs in pods, and node logs based on the collection configuration.

    +

    The following permissions are required for running the fluent-bit component:

    +
    • CAP_DAC_OVERRIDE: ignores the discretionary access control (DAC) restrictions on files.
    • CAP_FOWNER: ignores the restrictions that the file owner ID must match the process user ID.
    • DAC_READ_SEARCH: ignores the DAC restrictions on file reading and catalog research.
    • SYS_PTRACE: allows all processes to be traced.
    +
    +

    Installing the Add-on

    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons, locate Cloud Native Log Collection on the right, and click Install.
    2. On the Install Add-on page, configure the specifications as needed.

      • If you selected Preset, you can choose between Small or Large depending on the number of logs on nodes. The system will automatically set the number of add-on pods and resource quotas according to the preset specifications. You can see the configurations on the console.

        You can select the Small option for clusters where the logs of a single node are less than 5000/s or 5 MB/s, and select the Large option for clusters where the logs on a single node are less than 10000/s or 10 MB/s.

        +
      • If you selected Custom, you can adjust the number of pods and resource quotas as needed. 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.
      +

    3. Configure deployment policies for the add-on pods.

      Scheduling policies do not take effect on add-on instances of the DaemonSet type.

      +
      + +
      + + + + + + + +
      Table 1 Configurations for add-on scheduling

      Parameter

      +

      Description

      +

      Multi AZ

      +
      • Preferred: Deployment pods of the add-on will be preferentially scheduled to nodes in different AZs. If all the nodes in the cluster are deployed in the same AZ, the pods will be scheduled to different nodes in that AZ.
      • Forcible: Deployment pods of the add-on are forcibly scheduled to nodes in different AZs. There can be at most one pod in each AZ. If nodes in a cluster are not in different AZs, some add-on pods cannot run properly. If a node is faulty, add-on pods on it may fail to be migrated.
      +
      +
      +

    4. Click Install.
    +
    +

    Components

    +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Add-on components

    Component

    +

    Description

    +

    Resource Type

    +

    fluent-bit

    +

    Lightweight log collector and forwarder deployed on each node to collect logs

    +

    DaemonSet

    +

    cop-logs

    +

    Used to generate soft links for collected files and run in the same pod as fluent-bit

    +

    DaemonSet

    +

    log-operator

    +

    Used to generate internal configuration files

    +

    Deployment

    +

    otel-collector

    +

    Used to collect logs from applications and services and report the logs to LTS

    +

    Deployment

    +
    +
    +
    +

    Add-on Usage

    This add-on can collect container standard output logs, container file logs, node logs, and Kubernetes events. You can use LTS or AOM to store the collected logs. These services support different types of logs. For details, see Table 3.

    + +
    + + + + + + + + + + + + + +
    Table 3 Log storage description

    Log Storage Location

    +

    Supported Log Types

    +

    How to Use

    +

    LTS

    +
    • Container standard output logs
    • Container file logs
    • Node logs
    • Kubernetes events
    +

    Go to Logging to create a policy. For details, see Collecting Container Logs Using Cloud Native Log Collection.

    +

    AOM

    +

    Kubernetes events

    +

    If the cluster version is 1.19.16, 1.21.11, 1.23.9, 1.25.4, or later, all abnormal events and some normal events will be reported by default. For details, see Reporting Kubernetes Events to AOM.

    +
    +
    +
    +

    Change History

    +
    + + + + + + + + + +
    Table 4 Release history

    Add-on Version

    +

    Supported Cluster Version

    +

    New Feature

    +

    1.6.0

    +

    v1.21

    +

    v1.23

    +

    v1.25

    +

    v1.27

    +

    v1.28

    +

    v1.29

    +

    v1.30

    +
    • Clusters v1.30 are supported.
    • Security hardening: The permissions of the add-on for accessing secrets are limited to the monitoring namespace.
    +
    +
    +
    + + + diff --git a/docs/cce/umn/cce_10_0476.html b/docs/cce/umn/cce_10_0476.html index fe07e7189..a92683326 100644 --- a/docs/cce/umn/cce_10_0476.html +++ b/docs/cce/umn/cce_10_0476.html @@ -85,7 +85,7 @@

    √

    x

    +

    ×

    √

    √

    x

    +

    ×

    √

    √

    x

    +

    ×

    √

    √

    x

    +

    ×

    √

    √

    x

    +

    ×

    √
    + + + + + + + + + + + + + + + + + + + +
    Table 1 Control plane components

    Log Type

    +

    Component

    +

    Log Stream

    +

    Description

    +

    Control plane component logs

    +

    kube-apiserver

    +

    kube-apiserver-{{clusterID}}

    +

    It exposes Kubernetes APIs. For more information, see kube-apiserver.

    +

    kube-controller-manager

    +

    kube-controller-manager-{{clusterID}}

    +

    It manages controllers and embeds the core control loops shipped with Kubernetes. For more information, see kube-controller-manager.

    +

    kube-scheduler

    +

    kube-scheduler-{{clusterID}}

    +

    It manages when and where to run Pods in your cluster. For more information, see kube-scheduler.

    +
    +
    + +

    Enabling Control Plane Logging

    Enabling control plane logging during cluster creation

    +
    1. Log in to the CCE console.
    2. In the upper right corner, click Create Cluster. Then, configure the parameters and click Next: Select Add-on.
    3. On the displayed page, select Cloud Native Log Collection and click Next: Add-on Configuration.
    4. On the displayed page, select Control Plane Logs for Cloud Native Log Collection.
    5. Click Next: Confirm configuration.
    +
    Enabling control plane logging for an existing cluster
    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
    2. Click the Control Plane Logs tab and modify the settings in Logging Settings.
      Figure 1 Modifying logging settings
      +
    3. Determine whether to enable logging for each component. If yes, click .
    +
    +
    +

    Viewing Control Plane Component Logs of the Target Cluster

    Viewing control plane component logs of the target cluster on the CCE console

    +
    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
    2. Click the Control Plane Logs tab and select the topic of logs to be viewed. For details about available control plane log types, see Control Plane Components. For details about related operations, see LTS User Guide.
    +

    Viewing control plane component logs of the target cluster on the LTS console

    +
    1. Log in to the LTS console and choose Log Management.
    2. Search for the log group by cluster ID and click the log group name to view the log streams. For details, see LTS User Guide.
    +
    +

    Disabling Control Plane Logging

    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
    2. Click the Control Plane Logs tab. Then, modify the log setting.
    3. Determine whether to enable logging for each component. If yes, click .

      After you disable control plane logging, logs are no longer written to the original log stream, but the existing logs will not be deleted and expenses may be incurred for this.

      +
      +
    +
    + +
    +
    +
    Parent topic: Logging
    +
    +
    + diff --git a/docs/cce/umn/cce_10_0555.html b/docs/cce/umn/cce_10_0555.html new file mode 100644 index 000000000..eeb97dc48 --- /dev/null +++ b/docs/cce/umn/cce_10_0555.html @@ -0,0 +1,83 @@ + + +

    Collecting Container Logs Using Cloud Native Log Collection

    +

    The Cloud Native Log Collection add-on (Cloud Native Log Collection) is built based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This add-on supports CRD-based log collection policies. It collects and forwards stdout logs, container file logs, node logs, and Kubernetes events in a cluster based on configured policies.

    +

    Constraints

    • A maximum of 50 log rules can be created for each cluster.
    • The Cloud Native Log Collection add-on cannot collect .gz, .tar, and .zip logs and cannot access symbolic links of logs.
    • If the node storage driver is Device Mapper, container file logs must be collected from the path where the data disk is attached to the node.
    • 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.)
    • If a volume is attached to the data 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.
    • 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.
    +
    +

    Configuring Log Collection on the Console

    1. Enable log collection.

      Enabling log collection during cluster creation

      +
      1. Log in to the CCE console.
      2. Click Create Cluster from the top menu.
      3. On the Select Add-on page, select Cloud Native Log Collection.
      4. Click Next: Add-on Configuration in the lower right corner and select the required logs.
        • Container logs: A log collection policy named default-stdout will be created, and stdout logs in all namespaces will be reported to LTS.
        • Kubernetes events: A log collection policy named default-event will be created, and Kubernetes events in all namespaces will be reported to LTS.
        +
      5. Click Next: Confirm configuration in the lower right corner. On the displayed page, click Submit.
      +

    2. View and configure log collection policies.

      1. On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose Logging.

      2. In the upper right corner, click View Log Collection Policies.

        +

        All log collection policies reported to LTS are displayed.

        +
      3. In the upper right corner, click Create Log Collection Policy.
        • To avoid log disorder, you are advised to select different log streams for reporting logs in the log collection policies of various log types.
        • The following are requirements for configuring the container and node file log paths:
          • Log directory: Enter an absolute path, for example, /log. The path must start with a slash (/) and contain a maximum of 512 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), slashes (/), asterisks (*), and question marks (?) are allowed.
          • Log file name: It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), asterisks (*), question marks (?), and periods (.). Logs in the format of .gz, .tar, and .zip are not supported.
          +

          The directory and file names must be complete and support asterisks (*) and question marks (?) as wildcards. A maximum of three levels of directories can be matched using wildcards. The level-1 directory does not support wildcards. An asterisk (*) can match multiple characters. A question mark (?) can match only one character. For example:

          +
          • If the directory is /var/logs/* and the file name is *.log, the match expression is /var/logs/*/*.log, indicating that any files with the extension .log in all level-1 directories in the /var/logs directory are matched. Note that this expression cannot match any files with the extension .log in the /var/logs directory and multi-level directories in the /var/logs directory.
          • If the directory is /var/logs/app_* and the file name is *.log, any log files with the extension .log in all directories that match app_* in the /var/logs directory will be reported.
          +
        +
        + +
        + + + + + + + + + + + + + + + + + + + + + + +
        Table 1 Custom policy parameters

        Parameter

        +

        Description

        +

        Log Type

        +

        Container standard output: used to collect container stdout logs. You can create a log collection policy by namespace, workload name, or instance label.

        +

        Container file log: used to collect text logs. You can specify a workload or instance label to create a log collection policy.

        +

        Node file log: used to collect logs from a node. Only one file path can be configured for a log collection policy.

        +

        Kubernetes Events: used to collect Kubernetes events. You can configure collection policies by namespace.

        +

        Log Source

        +
        • All containers: You can specify all containers in a namespace. If this parameter is not specified, logs of containers in all namespaces will be collected.
        • Workload: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.
        • Workload with target label: 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.
        +
        • Workload: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.
        • Workload with target label: 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.
        +

        You also need to specify the log collection path. For details, see the log path configuration requirements.

        +

        Collection Path: used to configure the log collection path. For details, see the log path configuration requirements.

        +

        You can specify a namespace whose Kubernetes events are to be collected. If no namespace is specified, Kubernetes events in all namespaces are collected.

        +

        Log Format

        +
        • Single-line

          Each log contains only one line of text. The newline character \n denotes the start of a new log.

          +
        • Multi-line

          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 Multi-line, configure Log Matching Format.

          +

          For example, if logs need to be collected by line and each log starts with a date and occupies three lines, you can set Log Matching Format to the regular expression of the date, for example, \d{4}-\d{2}-\d{2} \d{2}\:\d{2}\:\d{2}.*.

          +
          The three lines starting with the date are regarded as a log.
          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)
          +
          +
        +

        +

        LTS Collection

        +

        This parameter is used to configure the log group and log stream for log reporting.

        +
        • Centralized: The default log group (k8s-log-{Cluster ID}) and default log stream (stdout-{Cluster ID}) are automatically selected.
        • Custom: You can select any log group and log stream.
          • Log Group: 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 k8s-log-{Cluster ID}, for example, k8s-log-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3.
          • Log Stream: 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:

            - stdout-{Cluster ID} for container logs, for example, stdout-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3

            +

            - event-{Cluster ID} for Kubernetes events, for example, event-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3

            +
          +
        +

        +
        +
        +
      +

    3. View the logs.

      1. On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose Logging.
      2. View different types of logs:
      3. Click View Log Collection Policies in the upper right corner. Locate the log collection policy and click View Log to go to the log list.
      +

    +
    +
    +
    +
    +
    Parent topic: Collecting Container Logs
    +
    +
    + diff --git a/docs/cce/umn/cce_10_0557.html b/docs/cce/umn/cce_10_0557.html index 9b0061973..534e4d2f4 100644 --- a/docs/cce/umn/cce_10_0557.html +++ b/docs/cce/umn/cce_10_0557.html @@ -1,8 +1,9 @@

    Overview

    -

    Kubernetes logs allow you to locate and rectify faults. This section describes how you can manage Kubernetes logs generated for CCE.

    - +

    Kubernetes logs allow you to locate and rectify faults. This section describes methods for managing Kubernetes logs.

    +

    Kubernetes log management methods:

    +
    diff --git a/docs/cce/umn/cce_10_0605.html b/docs/cce/umn/cce_10_0605.html index 6d0d8428b..f89d7ad78 100644 --- a/docs/cce/umn/cce_10_0605.html +++ b/docs/cce/umn/cce_10_0605.html @@ -111,7 +111,7 @@ status:

    Drainage Through APIs

    1. Obtain the token in the region where the cluster is located.
    2. Based on the API format, find the URL for the node drainage API.

      URL of the API for draining a node:
      https://{clusterid}.Endpoint/apis/node.cce.io/v1/drainages
      -
      • {clusterid}: cluster ID, which can be obtained on the Overview page of the CCE console.
      • Endpoint: endpoint of CCE in the region where the cluster is located.

        For details about the value, see Regions and Endpoints.

        +
        • {clusterid}: cluster ID, which can be obtained on the Overview page of the CCE console.
        • Endpoint: endpoint of CCE in the region where the cluster is located.

          For details about its value, see Regions and Endpoints.

    3. Use the POST request method and configure request header parameters.

      curl --location --request POST 'https://{clusterid}.Endpoint/apis/node.cce.io/v1/drainages' \
@@ -218,7 +218,7 @@ status:

    Cancellation Through APIs

    1. Obtain the token in the region where the cluster is located.
    2. Based on the API format, find the URL for the node drainage API.

      URL of the API for canceling node drainage:
      https://{clusterid}.Endpoint/apis/node.cce.io/v1/drainages/{drainageName}
      -
      • {clusterid}: cluster ID, which can be obtained on the Overview page of the CCE console.
      • Endpoint: endpoint of CCE in the region where the cluster is located.

        For details about the value, see Regions and Endpoints.

        +
        • {clusterid}: cluster ID, which can be obtained on the Overview page of the CCE console.
        • Endpoint: endpoint of CCE in the region where the cluster is located.

          For details about its value, see Regions and Endpoints.

        • {drainageName}: name of the drainage resource, which can be obtained by running the kubectl get drainages command.

    3. Use the PATCH request method and configure request header parameters.

      curl --location --request PATCH 'https://{clusterid}.Endpoint/apis/node.cce.io/v1/drainages/{drainageName}' \
diff --git a/docs/cce/umn/cce_10_0616.html b/docs/cce/umn/cce_10_0616.html
index f94e3deb0..7582b9bcd 100644
--- a/docs/cce/umn/cce_10_0616.html
+++ b/docs/cce/umn/cce_10_0616.html
@@ -72,7 +72,7 @@

    Resource Tag

    You can add resource tags to classify resources, which is supported only when the Everest version in the cluster is 2.1.39 or later.

    -

    You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency.

    +

    You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency.

    CCE automatically creates system tags CCE-Cluster-ID={Cluster ID}, CCE-Cluster-Name={Cluster name}, and CCE-Namespace={Namespace name}. These tags cannot be modified.

    NOTE:

    After a dynamic PV of the EVS type is created, the resource tags cannot be updated on the CCE console. To update these resource tags, go to the EVS console.

    diff --git a/docs/cce/umn/cce_10_0617.html b/docs/cce/umn/cce_10_0617.html index 5aab99a27..373b95ac9 100644 --- a/docs/cce/umn/cce_10_0617.html +++ b/docs/cce/umn/cce_10_0617.html @@ -5,6 +5,50 @@

    Expandable to petabytes, SFS provides fully hosted shared file storage, highly available and stable to handle data- and bandwidth-intensive applications

    • Standard file protocols: You can mount file systems as volumes to servers, the same as using local directories.
    • Data sharing: The same file system can be mounted to multiple servers, so that data can be shared.
    • Private network: Users can access data only in private networks of data centers.
    • Capacity and performance: The capacity of a single file system is high (PB level) and the performance is excellent (ms-level I/O latency).
    • Use cases: Deployments/StatefulSets in the ReadWriteMany mode and jobs created for high-performance computing (HPC), media processing, content management, web services, big data analysis, and workload process analysis
    +

    Performance

    CCE supports SFS Capacity-Oriented and SFS 3.0. For details about file system types, see File System Types .
    • SFS Capacity-Oriented file systems are sold out and cannot be used to create PVs on the CCE console. However, you can still create PVs using existing SFS Capacity-Oriented file systems through kubectl.
    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Performance

    Parameter

    +

    SFS Capacity-Oriented

    +

    SFS 3.0

    +

    Maximum bandwidth

    +

    2 GB/s

    +

    1.25 TB/s

    +

    Maximum IOPS

    +

    2000

    +

    Million

    +

    Latency

    +

    3–20 ms

    +

    10 ms

    +

    Maximum capacity

    +

    4 PB

    +

    EB

    +
    +
    +

    Application Scenarios

    SFS supports the following mounting modes based on application scenarios:

    • Using an Existing SFS File System Through a Static PV: static creation mode, where you use an existing SFS volume to create a PV and then mount storage to the workload through a PVC. This mode applies if the underlying storage is available.
    • Using an SFS File System Through a Dynamic PV: dynamic creation mode, in which you do not need to create SFS file systems beforehand. Instead, specify a StorageClass when creating a PVC. Then, a file system and PV will be created automatically. This mode applies to scenarios where no underlying storage is available.
    diff --git a/docs/cce/umn/cce_10_0619.html b/docs/cce/umn/cce_10_0619.html index 87659773c..8a9419de1 100644 --- a/docs/cce/umn/cce_10_0619.html +++ b/docs/cce/umn/cce_10_0619.html @@ -2,10 +2,10 @@

    Using an Existing SFS File System Through a Static PV

    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 services. This section describes how to use an existing SFS file system to statically create PVs and PVCs for data persistence and sharing in workloads.

    -

    Prerequisites

    +

    Prerequisites

    • You have created a cluster and installed the CCE Container Storage (Everest) add-on in the cluster.
    • To create a cluster using commands, ensure kubectl is used. For details, see Connecting to a Cluster Using kubectl.
    • You have created an SFS file system that is in the same VPC as the cluster.
    • Before using SFS 3.0 for storage, ensure a VPC endpoint has been created in the VPC where the cluster is located for the cluster to access the SFS 3.0 file system. For details, see Configure a VPC Endpoint.

    Notes and Constraints

    • Multiple PVs can use the same SFS or SFS Turbo file system with the following restrictions:
      • Do not mount the PVCs/PVs that use the same underlying SFS or SFS Turbo volume to one pod. This will lead to a pod startup failure because not all PVCs can be mounted to the pod due to the same volumeHandle value.
      • The persistentVolumeReclaimPolicy parameter in the PVs must be set to Retain. Otherwise, when a PV is deleted, the associated underlying volume may be deleted. In this case, other PVs associated with the underlying volume malfunction.
      • When the underlying volume is repeatedly used, enable isolation and protection for ReadWriteMany at the application layer to prevent data overwriting and loss.
      -
    +
  • If SFS 3.0 is used, the CCE Container Storage (Everest) add-on of v2.0.9 or later must be installed in the cluster.
  • If SFS 3.0 is used, the owner group and permission of the mount point cannot be modified. The default owner of the mount point is user root.
  • If the reclamation policy of SFS 3.0 is set to Delete, PVs and PVCs can be properly deleted only after all files are manually deleted from the mounted SFS system.

    • Using an Existing SFS File System on the Console

    1. Log in to the CCE console and click the cluster name to access the cluster console.
    2. Statically create a PVC and PV.

      1. Choose Storage in the navigation pane. In the right pane, click the PVCs tab. Click Create PVC in the upper right corner. In the dialog box displayed, configure PVC parameters.

        Parameter

        @@ -39,6 +39,8 @@

        SFSb

        Click Select SFS. On the displayed page, select the SFS file system that meets your requirements and click OK.

        +
        NOTE:

        Only SFS 3.0 is supported.

        +

        PV Nameb

        @@ -111,157 +113,158 @@

        -

        Using an Existing SFS Capacity-Oriented File System Through kubectl

        1. Use kubectl to access the cluster.
        2. Create a PV.

          1. Create the pv-sfs.yaml file.
            Example:
            apiVersion: v1
+
            Using an Existing SFS 3.0 File System Through kubectl
            1. Use kubectl to access the cluster.
            2. Create a PV.
              1. Create the pv-sfs.yaml file.
                Example:
                apiVersion: v1
 kind: PersistentVolume
 metadata:
   annotations:
     pv.kubernetes.io/provisioned-by: everest-csi-provisioner
     everest.io/reclaim-policy: retain-volume-only      # (Optional) The underlying volume is retained when the PV is deleted.
-  name: pv-sfs    # PV name
+  name: pv-sfs    # PV name
 spec:
   accessModes:
-  - ReadWriteMany      # Access mode. The value must be ReadWriteMany for SFS.
+  - ReadWriteMany      # Access mode. The value must be ReadWriteMany for SFS.
   capacity:
-    storage: 1Gi     # SFS volume capacity
+    storage: 1Gi     # SFS volume capacity
   csi:
     driver: nas.csi.everest.io    # Dependent storage driver for the mounting
     fsType: nfs
-    volumeHandle: <your_volume_id>   # SFS Capacity-Oriented volume ID
+    volumeHandle: <sfs30_name>   # Enter the file system name when SFS 3.0 is used.
     volumeAttributes:
-      everest.io/share-export-location: <your_location>  # Shared path of the SFS volume
+      everest.io/share-export-location: <your_location>  # Shared path of the SFS volume
       storage.kubernetes.io/csiProvisionerIdentity: everest-csi-provisioner
+      everest.io/sfs-version: sfs3.0       # SFS 3.0 is used.
   persistentVolumeReclaimPolicy: Retain    # Reclaim policy
-  storageClassName: csi-nas               # StorageClass name. csi-nas indicates that SFS Capacity-Oriented is used.
+  storageClassName: csi-sfs               # StorageClass name, where csi-sfs indicates SFS 3.0
   mountOptions: []                         # Mount options
                
 
                
 
-
                Table 2 Key parameters
                Parameter
                
+
                
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                Table 2 Key parameters
                Parameter
                
 
                Mandatory
                
+
                Mandatory
                
 
                Description
                
+
                Description
                
                 		
 
                
 
                everest.io/reclaim-policy
                
+
                everest.io/reclaim-policy
                
 
                No
                
+
                No
                
 
                Only retain-volume-only is supported.
                
-
                This parameter is valid only when the Everest version is 1.2.9 or later and the reclaim policy is Delete. If the reclaim policy is Delete and the current value is retain-volume-only, the associated PV is deleted while the underlying storage volume is retained, when a PVC is deleted.
                
+
                Only retain-volume-only is supported.
                
+
                This parameter is valid only when the Everest version is 1.2.9 or later and the reclaim policy is Delete. If the reclaim policy is Delete and the current value is retain-volume-only, the associated PV is deleted while the underlying storage volume is retained, when a PVC is deleted.
                
                 		
 
                volumeHandle
                
+
                volumeHandle
                
 
                Yes
                
+
                Yes
                
 
                Volume ID if SFS Capacity-Oriented is used.
                
-
                Log in to the CCE console, choose Service List > Storage > Scalable File Service, and select SFS Capacity-Oriented. In the list, click the name of the target SFS file system. On the details page, copy the content following ID.
                
+
                If SFS 3.0 is used, enter the name of the file system.
                
                 		
 
                everest.io/share-export-location
                
+
                everest.io/share-export-location
                
 
                Yes
                
+
                Yes
                
 
                Shared path of the file system.
                
-
                On the management console, choose Service List > Storage > Scalable File Service. You can obtain the shared path of the file system from the Mount Address column.
                
+
                Shared path of SFS 3.0.
                
+
                A shared path is in the following format:
                
+
                {your_sfs30_name}.sfs3.{region}.******.com:/{your_sfs30_name}
                
                 		
 
                mountOptions
                
+
                mountOptions
                
 
                Yes
                
+
                No
                
 
                Mount options.
                
-
                If not specified, the following configurations are used by default. For details, see Configuring SFS Volume Mount Options.
                
-
                mountOptions:
+
                Mount options.
                
+
                If not specified, the following configurations are used by default. For details, see Configuring SFS Volume Mount Options.
                
+
                mountOptions:
 - vers=3
 - timeo=600
 - nolock
 - hard
                
                 		
 
                persistentVolumeReclaimPolicy
                
+
                persistentVolumeReclaimPolicy
                
 
                Yes
                
+
                Yes
                
 
                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.
                
-
                The Delete and Retain reclaim policies are supported. For details, see PV Reclaim Policy. If multiple PVs use the same SFS volume, use Retain to prevent the underlying volume from being deleted with a PV.
                
-
                Retain: 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 Released state and cannot be bound to a PVC again.
                
-
                Delete: When a PVC is deleted, its PV will also be deleted.
                
+
                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.
                
+
                The Delete and Retain reclaim policies are supported. For details, see PV Reclaim Policy. If multiple PVs use the same SFS volume, use Retain to prevent the underlying volume from being deleted with a PV.
                
+
                Retain: 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 Released state and cannot be bound to a PVC again.
                
+
                Delete: When a PVC is deleted, its PV will also be deleted.
                
                 		
 
                storage
                
+
                storage
                
 
                Yes
                
+
                Yes
                
 
                Requested capacity in the PVC, in Gi.
                
-
                For SFS, this field is used only for verification (cannot be empty or 0). Its value is fixed at 1, and any value you set does not take effect for SFS file systems.
                
+
                Requested capacity in the PVC, in Gi.
                
+
                For SFS, this field is used only for verification (cannot be empty or 0). Its value is fixed at 1, and any value you set does not take effect for SFS file systems.
                
                 		
 
                storageClassName
                
+
                storageClassName
                
 
                Yes
                
+
                Yes
                
 
                StorageClass name csi-nas, indicating that SFS 1.0 Capacity-Oriented is used for storage.
                
+
                StorageClass name. Enter csi-sfs, indicating that SFS 3.0 is used.
                
                 		
 
                
                 
 
                
 
                
-
              2. Run the following command to create a PV:
                kubectl apply -f pv-sfs.yaml
                
+
              3. Run the following command to create a PV:
                kubectl apply -f pv-sfs.yaml
                
 
                4. 
-
              4. Create a PVC.
                1. Create the pvc-sfs.yaml file.
                  apiVersion: v1
+
                2. Create a PVC.
                  1. Create the pvc-sfs.yaml file.
                    apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
-  name: pvc-sfs
+  name: pvc-sfs
   namespace: default
   annotations:
     volume.beta.kubernetes.io/storage-provisioner: everest-csi-provisioner
 spec:
   accessModes:
-  - ReadWriteMany               # The value must be ReadWriteMany for SFS.
+  - ReadWriteMany               # The value must be ReadWriteMany for SFS.
   resources:
     requests:
-      storage: 1Gi               # SFS volume capacity
-  storageClassName: csi-nas     # StorageClass name, which must be the same as that of the PV
-  volumeName: pv-sfs    # PV name
                    
+      storage: 1Gi               # SFS volume capacity
+   storageClassName: csi-sfs     # StorageClass name, which must be the same as that of the PV
+  volumeName: pv-sfs    # PV name
 
-
                    Table 3 Key parameters
                    Parameter
                    
+
                    
-
-
-
-
-
-
-
-
-
-
-
                    Table 3 Key parameters
                    Parameter
                    
 
                    Mandatory
                    
+
                    Mandatory
                    
 
                    Description
                    
+
                    Description
                    
                     		
 
                    
 
                    storage
                    
+
                    storage
                    
 
                    Yes
                    
+
                    Yes
                    
 
                    Requested capacity in the PVC, in Gi.
                    
-
                    The value must be the same as the storage size of the existing PV.
                    
+
                    Requested capacity in the PVC, in Gi.
                    
+
                    The value must be the same as the storage size of the existing PV.
                    
                     		
 
                    storageClassName
                    
+
                    storageClassName
                    
 
                    Yes
                    
+
                    Yes
                    
 
                    StorageClass name csi-nas, which must be the same as the StorageClass of the PV specified in 1. This indicates that SFS 1.0 Capacity-Oriented is used for storage.
                    
+
                    StorageClass name. Enter csi-sfs, indicating that SFS 3.0 is used. The value of this parameter must be the sames as the PV StorageClass specified in 1.
                    
                     		
 
                    volumeName
                    
+
                    volumeName
                    
 
                    Yes
                    
+
                    Yes
                    
 
                    PV name, which must be the same as the PV name in 1.
                    
+
                    PV name, which must be the same as the PV name in 1.
                    
                     		
 
                    
                     
 
                    
 
                    
-
                  2. Run the following command to create a PVC:
                    kubectl apply -f pvc-sfs.yaml
                    
+
                  3. Run the following command to create a PVC:
                    kubectl apply -f pvc-sfs.yaml
                    
 
                    4. 
-
                  4. Create an application.
                    1. Create a file named web-demo.yaml. In this example, the SFS volume is mounted to the /data path.
                      apiVersion: apps/v1
+
                    2. Create an application.
                      1. Create a file named web-demo.yaml. In this example, the SFS volume is mounted to the /data path.
                        apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: web-demo
@@ -280,14 +283,196 @@ spec:
       - name: container-1
         image: nginx:latest
         volumeMounts:
-        - name: pvc-sfs-volume    # Volume name, which must be the same as the volume name in the volumes field
+        - name: pvc-sfs-volume    # Volume name, which must be the same as the volume name in the volumes field
           mountPath: /data  # Location where the storage volume is mounted
       imagePullSecrets:
         - name: default-secret
       volumes:
         - name: pvc-sfs-volume    # Volume name, which can be customized
           persistentVolumeClaim:
-            claimName: pvc-sfs    # Name of the created PVC
                        
+            claimName: pvc-sfs    # Name of the created PVC
+
                      2. Run the following command to create a workload to which the SFS volume is mounted:
                        kubectl apply -f web-demo.yaml
                        
+
                        After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence and Sharing.
                        
+
                      
+
                    
+
+
                    Using an Existing SFS Capacity-Oriented File System Through kubectl
                    1. Use kubectl to access the cluster.
                    2. Create a PV.
                      1. Create the pv-sfs.yaml file.
                        Example:
                        apiVersion: v1
+kind: PersistentVolume
+metadata:
+  annotations:
+    pv.kubernetes.io/provisioned-by: everest-csi-provisioner
+    everest.io/reclaim-policy: retain-volume-only      # (Optional) The underlying volume is retained when the PV is deleted.
+  name: pv-sfs    # PV name
+spec:
+  accessModes:
+  - ReadWriteMany      # Access mode. The value must be ReadWriteMany for SFS.
+  capacity:
+    storage: 1Gi     # SFS volume capacity
+  csi:
+    driver: nas.csi.everest.io    # Dependent storage driver for the mounting
+    fsType: nfs
+    volumeHandle: <your_volume_id>   # SFS Capacity-Oriented volume ID
+    volumeAttributes:
+      everest.io/share-export-location: <your_location>  # Shared path of the SFS volume
+      storage.kubernetes.io/csiProvisionerIdentity: everest-csi-provisioner
+  persistentVolumeReclaimPolicy: Retain    # Reclaim policy
+  storageClassName: csi-nas               # Storage class name. csi-nas indicates that SFS Capacity-Oriented is used.
+  mountOptions: []                         # Mount options
                        
+
                        
+
+
                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                        Table 4 Key parameters
                        Parameter
                        
+
                        Mandatory
                        
+
                        Description
                        
+
                        everest.io/reclaim-policy
                        
+
                        No
                        
+
                        Only retain-volume-only is supported.
                        
+
                        This parameter is valid only when the Everest version is 1.2.9 or later and the reclaim policy is Delete. If the reclaim policy is Delete and the current value is retain-volume-only, the associated PV is deleted while the underlying storage volume is retained, when a PVC is deleted.
                        
+
                        volumeHandle
                        
+
                        Yes
                        
+
                        Volume ID if SFS Capacity-Oriented is used.
                        
+
                        Log in to the CCE console, choose Service List > Storage > Scalable File Service, and select SFS Capacity-Oriented. In the list, click the name of the target SFS file system. On the details page, copy the content following ID.
                        
+
                        everest.io/share-export-location
                        
+
                        Yes
                        
+
                        Shared path of the file system.
                        
+
                        On the management console, choose Service List > Storage > Scalable File Service. You can obtain the shared path of the file system from the Mount Address column.
                        
+
                        mountOptions
                        
+
                        Yes
                        
+
                        Mount options.
                        
+
                        If not specified, the following configurations are used by default. For details, see Configuring SFS Volume Mount Options.
                        
+
                        mountOptions:
+- vers=3
+- timeo=600
+- nolock
+- hard
                        
+
                        persistentVolumeReclaimPolicy
                        
+
                        Yes
                        
+
                        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.
                        
+
                        The Delete and Retain reclaim policies are supported. For details, see PV Reclaim Policy. If multiple PVs use the same SFS volume, use Retain to prevent the underlying volume from being deleted with a PV.
                        
+
                        Retain: 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 Released state and cannot be bound to a PVC again.
                        
+
                        Delete: When a PVC is deleted, its PV will also be deleted.
                        
+
                        storage
                        
+
                        Yes
                        
+
                        Requested capacity in the PVC, in Gi.
                        
+
                        For SFS, this field is used only for verification (cannot be empty or 0). Its value is fixed at 1, and any value you set does not take effect for SFS file systems.
                        
+
                        storageClassName
                        
+
                        Yes
                        
+
                        StorageClass name csi-nas, indicating that SFS 1.0 Capacity-Oriented is used for storage.
                        
+
                        
+
                        
+
                      2. Run the following command to create a PV:
                        kubectl apply -f pv-sfs.yaml
                        
+
                      
+
                    3. Create a PVC.
                      1. Create the pvc-sfs.yaml file.
                        apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: pvc-sfs
+  namespace: default
+  annotations:
+    volume.beta.kubernetes.io/storage-provisioner: everest-csi-provisioner
+spec:
+  accessModes:
+  - ReadWriteMany               # The value must be ReadWriteMany for SFS.
+  resources:
+    requests:
+      storage: 1Gi               # SFS volume capacity
+  storageClassName: csi-nas     # StorageClass name, which must be the same as that of the PV
+  volumeName: pv-sfs    # PV name
                        
+
+
                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                        Table 5 Key parameters
                        Parameter
                        
+
                        Mandatory
                        
+
                        Description
                        
+
                        storage
                        
+
                        Yes
                        
+
                        Requested capacity in the PVC, in Gi.
                        
+
                        The value must be the same as the storage size of the existing PV.
                        
+
                        storageClassName
                        
+
                        Yes
                        
+
                        StorageClass name csi-nas, which must be the same as the StorageClass of the PV specified in 1. This indicates that SFS 1.0 Capacity-Oriented is used for storage.
                        
+
                        volumeName
                        
+
                        Yes
                        
+
                        PV name, which must be the same as the PV name in 1.
                        
+
                        
+
                        
+
                      2. Run the following command to create a PVC:
                        kubectl apply -f pvc-sfs.yaml
                        
+
                      
+
                    4. Create an application.
                      1. Create a file named web-demo.yaml. In this example, the SFS volume is mounted to the /data path.
                        apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: web-demo
+  namespace: default
+spec:
+  replicas: 2
+  selector:
+    matchLabels:
+      app: web-demo
+  template:
+    metadata:
+      labels:
+        app: web-demo
+    spec:
+      containers:
+      - name: container-1
+        image: nginx:latest
+        volumeMounts:
+        - name: pvc-sfs-volume    # Volume name, which must be the same as the volume name in the volumes field
+          mountPath: /data  # Location where the storage volume is mounted
+      imagePullSecrets:
+        - name: default-secret
+      volumes:
+        - name: pvc-sfs-volume    # Volume name, which can be customized
+          persistentVolumeClaim:
+            claimName: pvc-sfs    # Name of the created PVC
                        
 
                      2. Run the following command to create a workload to which the SFS volume is mounted:
                        kubectl apply -f web-demo.yaml
                        
 
                        After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence and Sharing.
                        
 
                      
@@ -336,37 +521,37 @@ static
 
                    
 
                    5. 
 
-
                    Related Operations
                    You can also perform the operations listed in Table 4.
-
                    Table 4 Related operations
                    Operation
                    
+
                    Related Operations
                    You can also perform the operations listed in Table 6.
+
                    
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/cce/umn/cce_10_0620.html b/docs/cce/umn/cce_10_0620.html
index f32232d68..6c80738a1 100644
--- a/docs/cce/umn/cce_10_0620.html
+++ b/docs/cce/umn/cce_10_0620.html
@@ -2,57 +2,49 @@
 
 
                    Using an SFS File System Through a Dynamic PV
                    This section describes how to use storage classes to dynamically create PVs and PVCs for data persistence and sharing in workloads.
                    
-
                    Prerequisites
                    
+
                    Prerequisites
                    • You have created a cluster and installed the CCE Container Storage (Everest) add-on in the cluster.
                    • To create a cluster using commands, ensure kubectl is used. For details, see Connecting to a Cluster Using kubectl.
                    • You have created an SFS file system that is in the same VPC as the cluster.
                    • Before using SFS 3.0 for storage, ensure a VPC endpoint has been created in the VPC where the cluster is located for the cluster to access the SFS 3.0 file system. For details, see Configure a VPC Endpoint.
                    
+
                    
+
                    Notes and Constraints
                    • If SFS 3.0 is used, the CCE Container Storage (Everest) add-on of v2.0.9 or later must be installed in the cluster.
                    • If SFS 3.0 is used, the owner group and permission of the mount point cannot be modified. The default owner of the mount point is user root.
                    • If the reclamation policy of SFS 3.0 is set to Delete, PVs and PVCs can be properly deleted only after all files are manually deleted from the mounted SFS system.
                    
 
                    
 
                    Automatically Creating an SFS File System on the Console
                    1. Log in to the CCE console and click the cluster name to access the cluster console.
                    2. Dynamically create a PVC and PV.
                      1. Choose Storage in the navigation pane. In the right pane, click the PVCs tab. Click Create PVC in the upper right corner. In the dialog box displayed, configure PVC parameters.
-
                    Table 6 Related operations
                    Operation
                    
 
                    Description
                    
+
                    Description
                    
 
                    Procedure
                    
+
                    Procedure
                    
                     		
 
                    
 
                    Creating a storage volume (PV)
                    
+
                    Creating a storage volume (PV)
                    
 
                    Create a PV on the CCE console.
                    
+
                    Create a PV on the CCE console.
                    
 
                    1. Choose Storage in the navigation pane. In the right pane, click the PVs tab. Click Create PersistentVolume in the upper right corner. In the dialog box displayed, configure parameters.
                      • Volume Type: Select SFS.
                      • SFS: Click Select SFS. On the displayed page, select the SFS file system that meets your requirements and click OK.
                      • PV Name: Enter the PV name, which must be unique in a cluster.
                      • Access Mode: SFS volumes support only ReadWriteMany, indicating that a storage volume can be mounted to multiple nodes in read/write mode. For details, see Volume Access Modes.
                      • Reclaim Policy: Delete or Retain is supported. For details, see PV Reclaim Policy.
                         NOTE: 
                        If multiple PVs use the same underlying storage volume, use Retain to prevent the underlying volume from being deleted with a PV.
                        
+
                    1. Choose Storage in the navigation pane. In the right pane, click the PVs tab. Click Create PersistentVolume in the upper right corner. In the dialog box displayed, configure parameters.
                      • Volume Type: Select SFS.
                      • SFS: Click Select SFS. On the displayed page, select the SFS file system that meets your requirements and click OK.
                      • PV Name: Enter the PV name, which must be unique in a cluster.
                      • Access Mode: SFS volumes support only ReadWriteMany, indicating that a storage volume can be mounted to multiple nodes in read/write mode. For details, see Volume Access Modes.
                      • Reclaim Policy: Delete or Retain is supported. For details, see PV Reclaim Policy.
                         NOTE: 
                        If multiple PVs use the same underlying storage volume, use Retain to prevent the underlying volume from being deleted with a PV.
                        
 
                        
 
                      • Mount Options: Enter the mounting parameter key-value pairs. For details, see Configuring SFS Volume Mount Options.
                      
 
                    2. Click Create.
                    
                     		
 
                    Viewing events
                    
+
                    Viewing events
                    
 
                    View event names, event types, number of occurrences, Kubernetes events, first occurrence time, and last occurrence time of the PVC or PV.
                    
+
                    View event names, event types, number of occurrences, Kubernetes events, first occurrence time, and last occurrence time of the PVC or PV.
                    
 
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View Events in the Operation column of the target PVC or PV to view events generated within one hour (events are retained for one hour).
                    
+
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View Events in the Operation column of the target PVC or PV to view events generated within one hour (events are retained for one hour).
                    
                     		
 
                    Viewing a YAML file
                    
+
                    Viewing a YAML file
                    
 
                    View, copy, or download the YAML file of a PVC or PV.
                    
+
                    View, copy, or download the YAML file of a PVC or PV.
                    
 
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View YAML in the Operation column of the target PVC or PV to view or download the YAML.
                    
+
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View YAML in the Operation column of the target PVC or PV to view or download the YAML.
                    
                     		
 
                    
                     
 
                    Parameter
                    
+
                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -61,33 +53,33 @@
 
                  5. Click Create to create a PVC and a PV.
                    You can choose Storage in the navigation pane and view the created PVC and PV on the PVCs and PVs tab pages, respectively.
                    
 
                  6. Create an application.
                    1. Choose Workloads in the navigation pane. In the right pane, click the Deployments tab.
                    2. Click Create Workload in the upper right corner. On the displayed page, click Data Storage in the Container Settings area and click Add Volume to select PVC.
                      Mount and use storage volumes, as shown in Table 1. For details about other parameters, see Workloads.
-
                    7. Parameter
                    
 
                    Description
                    
+
                    Description
                    
                     		
 
                    
 
                    PVC Type
                    
+
                    PVC Type
                    
 
                    In this example, select SFS.
                    
+
                    In this example, select SFS.
                    
                     		
 
                    PVC Name
                    
+
                    PVC Name
                    
 
                    Enter the PVC name, which must be unique in a namespace.
                    
+
                    Enter the PVC name, which must be unique in a namespace.
                    
                     		
 
                    Creation Method
                    
+
                    Creation Method
                    
 
                    • If no underlying storage is available, select Dynamically provision to create a PVC, PV, and underlying storage on the console in cascading mode.
                    • If underlying storage is available, create a PV or use an existing PV to statically create a PVC. For details, see Using an Existing SFS File System Through a Static PV.
                    
+
                    • If no underlying storage is available, select Dynamically provision to create a PVC, PV, and underlying storage on the console in cascading mode.
                    • If underlying storage is available, create a PV or use an existing PV to statically create a PVC. For details, see Using an Existing SFS File System Through a Static PV.
                    
 
                    In this document, Dynamically provision is selected.
                    
                     		
 
                    Storage Classes
                    
+
                    Storage Classes
                    
 
                    The default StorageClass for SFS volumes is csi-nas.
                    
+
                    The default storage class for SFS volumes is csi-sfs.
                    
 
                    You can customize a StorageClass and configure its reclaim policy and binding mode. For details, see Creating a StorageClass Using the CCE Console.
                    
                     		
 
                    (Optional) Storage Volume Name Prefix
                    
+
                    (Optional) Storage Volume Name Prefix
                    
 
                    Available only when the cluster version is v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later, and Everest of v2.4.15 or later is installed in the cluster.
                    
+
                    Available only when the cluster version is v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later, and Everest of v2.4.15 or later is installed in the cluster.
                    
 
                    This parameter specifies the name of the underlying storage that is automatically created. The actual underlying storage name is in the format of "Storage volume name prefix + PVC UID". If this parameter is left blank, the default prefix pvc will be used.
                    
 
                    For example, if the storage volume name prefix is set to test, the actual underlying storage name is test-{UID}.
                    
                     		
 
                    Capacity (GiB)
                    
+
                    Access Mode
                    
 
                    The value cannot be less than 10.
                    
-
                    Access Mode
                    
-
                    SFS volumes support only ReadWriteMany, indicating that a storage volume can be mounted to multiple nodes in read/write mode. For details, see Volume Access Modes.
                    
-
                    Encryption
                    
-
                    Configure whether to encrypt underlying storage if the storage class is csi-nas. If you select Enabled (key), an encryption key must be configured.
                    
+
                    SFS volumes support only ReadWriteMany, indicating that a storage volume can be mounted to multiple nodes in read/write mode. For details, see Volume Access Modes.
                    
                     		
 
                    
                     
 
                    Table 1 Mounting a storage volume
                    Parameter
                    
+
                    
-
-
-
-
-
-
-
-
-
@@ -106,11 +98,8 @@ metadata:
   name: pvc-sfs-auto
   namespace: default
   annotations: 
-    everest.io/crypt-key-id: <your_key_id>      # (Optional) ID of the key for encrypting file systems
 
-    everest.io/crypt-alias: sfs/default         # (Optional) Key name. Mandatory for encrypting volumes.
 
-    everest.io/crypt-domain-id: <your_domain_id>   # (Optional) ID of the tenant to which an encrypted volume belongs. Mandatory for encrypting volumes.
 
     everest.io/csi.volume-name-prefix: test  # (Optional) Storage volume name prefix of the automatically created underlying storage
 spec:
@@ -119,54 +108,62 @@ spec:
   resources:
     requests:
       storage: 1Gi             # SFS volume capacity
-  storageClassName: csi-nas    # StorageClass is SFS. 
+  storageClassName: csi-sfs    # The storage class is SFS. csi-sfs indicates that SFS 3.0 is used.
 
-
                    Table 1 Mounting a storage volume
                    Parameter
                    
 
                    Description
                    
+
                    Description
                    
                     		
 
                    
 
                    PVC
                    
+
                    PVC
                    
 
                    Select an existing SFS volume.
                    
+
                    Select an existing SFS volume.
                    
                     		
 
                    Mount Path
                    
+
                    Mount Path
                    
 
                    Enter a mount path, for example, /tmp.
                    
+
                    Enter a mount path, for example, /tmp.
                    
 
                    This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as / or /var/run. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, leading to container startup failures or workload creation failures.
                     NOTICE: 
                    If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.
                    
 
                    
 
                    
                     		
 
                    Subpath
                    
+
                    Subpath
                    
 
                    Enter the subpath of the storage volume and mount a path in the storage volume to the container. In this way, different folders of the same storage volume can be used in a single pod. tmp, for example, indicates that data in the mount path of the container is stored in the tmp folder of the storage volume. If this parameter is left blank, the root path will be used by default.
                    
+
                    Enter the subpath of the storage volume and mount a path in the storage volume to the container. In this way, different folders of the same storage volume can be used in a single pod. tmp, for example, indicates that data in the mount path of the container is stored in the tmp folder of the storage volume. If this parameter is left blank, the root path will be used by default.
                    
                     		
 
                    Permission
                    
+
                    Permission
                    
 
                    • Read-only: You can only read the data in the mounted volumes.
                    • Read-write: You can modify the data volumes mounted to the path. Newly written data will not be migrated if the container is migrated, which may cause data loss.
                    
+
                    • Read-only: You can only read the data in the mounted volumes.
                    • Read-write: You can modify the data volumes mounted to the path. Newly written data will not be migrated if the container is migrated, which may cause data loss.
                    
                     		
 
                    
 
                    Table 2 Key parameters
                    Parameter
                    
+
                    
-
-
-
-
-
-
-
-
+
+
+
+
-
-
-
-
-
-
-
-
-
                    Table 2 Key parameters
                    Parameter
                    
 
                    Mandatory
                    
+
                    Mandatory
                    
 
                    Description
                    
+
                    Description
                    
                     		
 
                    
 
                    storage
                    
+
                    storage
                    
 
                    Yes
                    
+
                    Yes
                    
 
                    Requested capacity in the PVC, in Gi.
                    
+
                    Requested capacity in the PVC, in Gi.
                    
 
                    For SFS, this field is used only for verification (cannot be empty or 0). Its value is fixed at 1, and any value you set does not take effect for SFS file systems.
                    
                     		
 
                    everest.io/crypt-key-id
                    
+
                    storageClassName
                    
 
                    No
                    
+
                    Yes
                    
 
                    If StorageClass is csi-nas, you can determine whether to encrypt the underlying storage.
                    
+
                    Name of a storage class.
                    
+
                    • csi-sfs (recommended): indicates that SFS 3.0 is used.
                    • csi-nas: indicates that an SFS 1.0 Capacity-Oriented file system is used.
                    
+
                    everest.io/crypt-key-id
                    
+
                    No
                    
+
                    If StorageClass is csi-nas, you can determine whether to encrypt the underlying storage.
                    
 
                    This parameter is mandatory when an SFS system is encrypted. Enter the encryption key ID selected during SFS system creation. You can use a custom key or the default key named sfs/default.
                    
 
                    To obtain a key ID, log in to the DEW console, locate the key to be encrypted, and copy the key ID.
                    
                     		
 
                    everest.io/crypt-alias
                    
+
                    everest.io/crypt-alias
                    
 
                    No
                    
+
                    No
                    
 
                    Key name, which is mandatory when you create an encrypted volume.
                    
+
                    Key name, which is mandatory when you create an encrypted volume.
                    
 
                    To obtain a key name, log in to the DEW console, locate the key to be encrypted, and copy the key name.
                    
                     		
 
                    everest.io/crypt-domain-id
                    
+
                    everest.io/crypt-domain-id
                    
 
                    No
                    
+
                    No
                    
 
                    ID of the tenant to which the encrypted volume belongs. This parameter is mandatory for creating an encrypted volume.
                    
+
                    ID of the tenant to which the encrypted volume belongs. This parameter is mandatory for creating an encrypted volume.
                    
 
                    To obtain a tenant ID, hover the cursor over the username in the upper right corner of the ECS console, choose My Credentials, and copy the account ID.
                    
                     		
 
                    everest.io/csi.volume-name-prefix
                    
+
                    everest.io/csi.volume-name-prefix
                    
 
                    No
                    
+
                    No
                    
 
                    (Optional) This parameter is available only when the cluster version is v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later, and Everest of v2.4.15 or later is installed in the cluster.
                    
+
                    (Optional) This parameter is available only when the cluster version is v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later, and Everest of v2.4.15 or later is installed in the cluster.
                    
 
                    This parameter specifies the name of the underlying storage that is automatically created. The actual underlying storage name is in the format of "Storage volume name prefix + PVC UID". If this parameter is left blank, the default prefix pvc will be used.
                    
 
                    Enter 1 to 26 characters that cannot start or end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.
                    
 
                    For example, if the storage volume name prefix is set to test, the actual underlying storage name is test-{UID}.
                    
@@ -253,26 +250,26 @@ static
 
                    
 
 
                    Related Operations
                    You can also perform the operations listed in Table 3.
-
                    Table 3 Related operations
                    Operation
                    
+
                    
-
-
-
-
-
-
-
-
diff --git a/docs/cce/umn/cce_10_0624.html b/docs/cce/umn/cce_10_0624.html
index 478a7795e..bf2740c52 100644
--- a/docs/cce/umn/cce_10_0624.html
+++ b/docs/cce/umn/cce_10_0624.html
@@ -6,7 +6,7 @@
 
                    • Standard file protocols: You can mount file systems as volumes to servers, the same as using local directories.
                    • Data sharing: The same file system can be mounted to multiple servers, so that data can be shared.
                    • Private network: Users can access data only in private networks of data centers.
                    • Data isolation: The on-cloud storage service provides exclusive cloud file storage, which delivers data isolation and ensures IOPS performance.
                    • Use cases: Deployments/StatefulSets in the ReadWriteMany mode, DaemonSets, and jobs created for high-traffic websites, log storage, DevOps, and enterprise OA applications
                    Application Scenarios
                    SFS Turbo supports the following mounting modes:
                    
-
+
 
                    
diff --git a/docs/cce/umn/cce_10_0652.html b/docs/cce/umn/cce_10_0652.html
index 8ae075729..b16f4f8bf 100644
--- a/docs/cce/umn/cce_10_0652.html
+++ b/docs/cce/umn/cce_10_0652.html
@@ -10,9 +10,9 @@
 
                  7. Click OK.
                    8. 
 
                    kubelet
                    
-
                    Table 3 Related operations
                    Operation
                    
 
                    Description
                    
+
                    Description
                    
 
                    Procedure
                    
+
                    Procedure
                    
                     		
 
                    
 
                    Viewing events
                    
+
                    Viewing events
                    
 
                    View event names, event types, number of occurrences, Kubernetes events, first occurrence time, and last occurrence time of the PVC or PV.
                    
+
                    View event names, event types, number of occurrences, Kubernetes events, first occurrence time, and last occurrence time of the PVC or PV.
                    
 
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View Events in the Operation column of the target PVC or PV to view events generated within one hour (events are retained for one hour).
                    
+
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View Events in the Operation column of the target PVC or PV to view events generated within one hour (events are retained for one hour).
                    
                     		
 
                    Viewing a YAML file
                    
+
                    Viewing a YAML file
                    
 
                    View, copy, or download the YAML file of a PVC or PV.
                    
+
                    View, copy, or download the YAML file of a PVC or PV.
                    
 
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View YAML in the Operation column of the target PVC or PV to view or download the YAML.
                    
+
                    1. Choose Storage in the navigation pane. In the right pane, click the PVCs or PVs tab.
                    2. Click View YAML in the Operation column of the target PVC or PV to view or download the YAML.
                    
                     		
 
                    
                     
 
 
 
 
 
                    
-
-
-
@@ -366,9 +366,9 @@
 
-
-
-
@@ -559,9 +559,9 @@
 
-
-
-
@@ -67,13 +70,6 @@
 
-
-
-
-
                    Item
                    
+
                    
-
@@ -22,9 +22,9 @@
 
-
-
-
-
@@ -46,9 +46,9 @@
 
-
-
@@ -57,9 +57,9 @@
 
-
-
@@ -68,9 +68,9 @@
 
-
-
@@ -79,9 +79,9 @@
 
-
-
@@ -90,9 +90,9 @@
 
-
-
@@ -101,9 +101,9 @@
 
-
-
@@ -112,9 +112,9 @@
 
-
-
-
-
-
-
-
-
-
-
@@ -183,9 +183,9 @@
 
-
-
@@ -194,9 +194,9 @@
 
-
-
-
-
@@ -218,9 +218,9 @@
 
-
-
@@ -230,9 +230,9 @@
 
-
-
@@ -242,9 +242,9 @@
 
-
-
@@ -254,9 +254,9 @@
 
-
-
@@ -267,9 +267,9 @@
 
                    This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.28.4-r0, or later versions.
                    
-
-
@@ -280,9 +280,9 @@
 
                    This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.28.4-r0, or later versions.
                    
-
-
@@ -297,7 +297,7 @@
 
-
-
@@ -590,12 +590,12 @@
 
-
@@ -611,7 +611,7 @@
 
diff --git a/docs/cce/umn/cce_10_0653.html b/docs/cce/umn/cce_10_0653.html
index 2da85ef45..02dfb122c 100644
--- a/docs/cce/umn/cce_10_0653.html
+++ b/docs/cce/umn/cce_10_0653.html
@@ -95,7 +95,7 @@
 
-
@@ -81,7 +81,7 @@
 
diff --git a/docs/cce/umn/cce_10_0695.html b/docs/cce/umn/cce_10_0695.html
index f376347d2..ad0c41744 100644
--- a/docs/cce/umn/cce_10_0695.html
+++ b/docs/cce/umn/cce_10_0695.html
@@ -226,7 +226,7 @@
 
-
diff --git a/docs/cce/umn/cce_10_0704.html b/docs/cce/umn/cce_10_0704.html
index c472b4bc3..c48a48b7d 100644
--- a/docs/cce/umn/cce_10_0704.html
+++ b/docs/cce/umn/cce_10_0704.html
@@ -20,7 +20,7 @@
 
                  8. Configuring Node Fault Detection Policies
                    
 
                    9. 
-
                  9. Executing the Pre- or Post-installation Commands During Node Creation
                    
+
                  10. Executing the Pre- or Post-installation Commands During Node Creation
                    
 
                    11. 
 
diff --git a/docs/cce/umn/cce_10_0705.html b/docs/cce/umn/cce_10_0705.html
index b7e81f7fe..4dcfe6f29 100644
--- a/docs/cce/umn/cce_10_0705.html
+++ b/docs/cce/umn/cce_10_0705.html
@@ -8,6 +8,8 @@
 
                  11. Log Auditing
                    
 
                    12. 
+
                  12. FAQ
                    
+
                  13. Best Practices
                    
 
                    14. 
diff --git a/docs/cce/umn/cce_10_0782.html b/docs/cce/umn/cce_10_0782.html
index 9b2fa1aba..2ab05a5ea 100644
--- a/docs/cce/umn/cce_10_0782.html
+++ b/docs/cce/umn/cce_10_0782.html
@@ -5,7 +5,7 @@
 
                    Accessing the Settings
                    1. Log in to the CCE console and click the cluster name to access the cluster console.
                    2. In the navigation pane, choose Settings and click the Dashboard tab.
                    
 
                    Cluster Information
                    It includes:
                    
-
                    • ID: uniquely identifies a cluster resource. It is automatically generated after a cluster is created and can be used in scenarios such as API calling.
                    • Current Name: After a cluster is created, you can click  to change its name.
                    • Original Name: specifies a cluster's original name after its current name is changed. The current name of a cluster must be unique.
                    • Status: specifies the status of a cluster. For details, see Cluster Lifecycle.
                    • Type: specifies whether a cluster is a CCE standard or a CCE Turbo cluster. For details about the differences between CCE standard and CCE Turbo clusters, see Comparison Between Cluster Types.
                    • Created On: specifies the time when a cluster was created. You will be billed based on the creation time of clusters.
                    
+
                    • ID: uniquely identifies a cluster resource. It is automatically generated after a cluster is created and can be used in scenarios such as API calling.
                    • Current Name: After a cluster is created, you can click  to change its name.
                    • Original Name: specifies a cluster's original name after its current name is changed. The current name of a cluster must be unique.
                    • Status: specifies the status of a cluster. For details, see Cluster Lifecycle.
                    • Type: specifies whether a cluster is a CCE standard cluster or a CCE Turbo cluster. For details about the differences between CCE standard and CCE Turbo clusters, see Comparison Between Cluster Types.
                    • Created On: specifies the time when a cluster was created. You will be billed based on the creation time of clusters.
                    
 
                    Cluster Settings
                    After a cluster is created, you can modify the following items for it:
                    
 
                    • Cluster Scale: specifies how many nodes a cluster can manage at most. You can change the cluster scale as needed. For details, see Changing Cluster Scale.
                    • Cluster Version | Patch Version: specifies the Kubernetes version and CCE patch version of a cluster.
                    • Network Model: specifies the network model of a cluster, which cannot be changed. For details about network models, see Container Network.
                    • Resource Tag: You can add resource tags to classify resources.
                    • Cluster Description: specifies the description that you entered for a cluster. A maximum of 200 characters are allowed.
                    • Cluster Deletion Protection: A measure taken to prevent accidental deletion of clusters through the console or APIs. After this function is enabled, you will not be able to delete or unsubscribe from clusters on CCE.
                    
diff --git a/docs/cce/umn/cce_10_0787.html b/docs/cce/umn/cce_10_0787.html
index 8c550f560..763daadbe 100644
--- a/docs/cce/umn/cce_10_0787.html
+++ b/docs/cce/umn/cce_10_0787.html
@@ -397,7 +397,7 @@
 
                    
-
-
diff --git a/docs/cce/umn/cce_bestpractice_10020.html b/docs/cce/umn/cce_bestpractice_10020.html
index 84c9fdd9a..34694c652 100644
--- a/docs/cce/umn/cce_bestpractice_10020.html
+++ b/docs/cce/umn/cce_bestpractice_10020.html
@@ -1,25 +1,25 @@
 
                    Executing the Pre- or Post-installation Commands During Node Creation
                    
-
                    Background
                    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 correctly use the pre- or post-installation scripts. 
                    
+
                    Background
                    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 correctly use the pre- or post-installation scripts. 
                    
 
                    
-
                    Precautions
                    • Do not use pre- or post-installation scripts that take a long time to execute.
                      The pre-installation script has a 15-minute time limit, while the post-installation script has a 30-minute time limit. If the node is not available within the designated time, the node reclaim process will be initiated. Therefore, do not use pre- or post-installation scripts that take a long time to execute.
                      
-
                    • Do not directly use reboot in the script.
                      CCE executes the post-installation command after installing mandatory components on a node. The node will be available only after the post-installation command is executed. If you run reboot directly, the node may be restarted before its status is reported. As a result, it cannot reach the running state within 30 minutes, and a rollback due to timeout will be triggered. Therefore, do not use reboot.
                      
-
                      If you need to restart a node, perform the following operations:
                      
-
                      • Run shutdown -r <time > in the script to delay the restart. For example, you can run shutdown -r 1 to delay the restart for 1 minute.
                      • After the node is available, manually restart it.
                      
+
                      Precautions
                      • Do not use pre- or post-installation scripts that take a long time to execute.
                        The pre-installation script has a 15-minute time limit, while the post-installation script has a 30-minute time limit. If the node is not available within the designated time, the node reclaim process will be initiated. Therefore, do not use pre- or post-installation scripts that take a long time to execute.
                        
+
                      • Do not directly use reboot in the script.
                        CCE executes the post-installation command after installing mandatory components on a node. The node will be available only after the post-installation command is executed. If you run reboot directly, the node may be restarted before its status is reported. As a result, it cannot reach the running state within 30 minutes, and a rollback due to timeout will be triggered. Therefore, do not use reboot.
                        
+
                        If you need to restart a node, perform the following operations:
                        
+
                        • Run shutdown -r <time > in the script to delay the restart. For example, you can run shutdown -r 1 to delay the restart for 1 minute.
                        • After the node is available, manually restart it.
                        
 
                      
 
                      
-
                      Procedure
                      1. Log in to the CCE console. In the navigation pane, choose Clusters. Click the target cluster name to access the cluster console.
                      2. Choose Nodes in the navigation pane, click the Nodes tab, click Create Node in the right corner, and configure the parameters.
                      3. In the Advanced Settings area, enter pre- or post-installation commands.
                        
-
                        For example, you can create iptables rules by running a post-installation command to allow a maximum of 25 TCP data packets to be addressed to port 80 per minute and allow a maximum of 100 data packets to be addressed to the port when the limit is exceeded to prevent DDoS attacks.
                        
-
                        iptables -A INPUT -p tcp --dport 80 -m limit --limit 25/minute --limit-burst 100 -j ACCEPT
                        
-
                         
                        The command example here is for reference only.
                        
+
                        Procedure
                        1. Log in to the CCE console. In the navigation pane, choose Clusters. Click the target cluster name to access the cluster console.
                        2. Choose Nodes in the navigation pane, click the Nodes tab, click Create Node in the right corner, and configure the parameters.
                        3. In the Advanced Settings area, enter pre- or post-installation commands.
                          
+
                          For example, you can create iptables rules by running a post-installation command to allow a maximum of 25 TCP data packets to be addressed to port 80 per minute and allow a maximum of 100 data packets to be addressed to the port when the limit is exceeded to prevent DDoS attacks.
                          
+
                          iptables -A INPUT -p tcp --dport 80 -m limit --limit 25/minute --limit-burst 100 -j ACCEPT
                          
+
                           
                          The command example here is for reference only.
                          
 
                          
-
                        4. After the configuration, enter the number of nodes to be created and click Next: Confirm.
                        5. Click Submit.
                        
+
                      4. After the configuration, enter the number of nodes to be created and click Next: Confirm.
                      5. Click Submit.
                      
 
                      
 
                    
 
                    
 
                    
-
                    Parent topic: Cluster
                    
+
                    Parent topic: Node O&M
                    
 
                    
 
                    
 
diff --git a/docs/cce/umn/cce_bestpractice_10020_0.html b/docs/cce/umn/cce_bestpractice_10020_0.html
index 922f473ca..4cc0bc4ed 100644
--- a/docs/cce/umn/cce_bestpractice_10020_0.html
+++ b/docs/cce/umn/cce_bestpractice_10020_0.html
@@ -1,25 +1,25 @@
 
 
 
                    Executing the Pre- or Post-installation Commands During Node Creation
                    
-
                    Background
                    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 correctly use the pre- or post-installation scripts. 
                    
+
                    Background
                    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 correctly use the pre- or post-installation scripts. 
                    
 
                    
-
                    Precautions
                    • Do not use pre- or post-installation scripts that take a long time to execute.
                      The pre-installation script has a 15-minute time limit, while the post-installation script has a 30-minute time limit. If the node is not available within the designated time, the node reclaim process will be initiated. Therefore, do not use pre- or post-installation scripts that take a long time to execute.
                      
-
                    • Do not directly use reboot in the script.
                      CCE executes the post-installation command after installing mandatory components on a node. The node will be available only after the post-installation command is executed. If you run reboot directly, the node may be restarted before its status is reported. As a result, it cannot reach the running state within 30 minutes, and a rollback due to timeout will be triggered. Therefore, do not use reboot.
                      
-
                      If you need to restart a node, perform the following operations:
                      
-
                      • Run shutdown -r <time > in the script to delay the restart. For example, you can run shutdown -r 1 to delay the restart for 1 minute.
                      • After the node is available, manually restart it.
                      
+
                      Precautions
                      • Do not use pre- or post-installation scripts that take a long time to execute.
                        The pre-installation script has a 15-minute time limit, while the post-installation script has a 30-minute time limit. If the node is not available within the designated time, the node reclaim process will be initiated. Therefore, do not use pre- or post-installation scripts that take a long time to execute.
                        
+
                      • Do not directly use reboot in the script.
                        CCE executes the post-installation command after installing mandatory components on a node. The node will be available only after the post-installation command is executed. If you run reboot directly, the node may be restarted before its status is reported. As a result, it cannot reach the running state within 30 minutes, and a rollback due to timeout will be triggered. Therefore, do not use reboot.
                        
+
                        If you need to restart a node, perform the following operations:
                        
+
                        • Run shutdown -r <time > in the script to delay the restart. For example, you can run shutdown -r 1 to delay the restart for 1 minute.
                        • After the node is available, manually restart it.
                        
 
                      
 
                      
-
                      Procedure
                      1. Log in to the CCE console. In the navigation pane, choose Clusters. Click the target cluster name to access the cluster console.
                      2. Choose Nodes in the navigation pane, click the Nodes tab, click Create Node in the right corner, and configure the parameters.
                      3. In the Advanced Settings area, enter pre- or post-installation commands.
                        
-
                        For example, you can create iptables rules by running a post-installation command to allow a maximum of 25 TCP data packets to be addressed to port 80 per minute and allow a maximum of 100 data packets to be addressed to the port when the limit is exceeded to prevent DDoS attacks.
                        
-
                        iptables -A INPUT -p tcp --dport 80 -m limit --limit 25/minute --limit-burst 100 -j ACCEPT
                        
-
                         
                        The command example here is for reference only.
                        
+
                        Procedure
                        1. Log in to the CCE console. In the navigation pane, choose Clusters. Click the target cluster name to access the cluster console.
                        2. Choose Nodes in the navigation pane, click the Nodes tab, click Create Node in the right corner, and configure the parameters.
                        3. In the Advanced Settings area, enter pre- or post-installation commands.
                          
+
                          For example, you can create iptables rules by running a post-installation command to allow a maximum of 25 TCP data packets to be addressed to port 80 per minute and allow a maximum of 100 data packets to be addressed to the port when the limit is exceeded to prevent DDoS attacks.
                          
+
                          iptables -A INPUT -p tcp --dport 80 -m limit --limit 25/minute --limit-burst 100 -j ACCEPT
                          
+
                           
                          The command example here is for reference only.
                          
 
                          
-
                        4. After the configuration, enter the number of nodes to be created and click Next: Confirm.
                        5. Click Submit.
                        
+
                      4. After the configuration, enter the number of nodes to be created and click Next: Confirm.
                      5. Click Submit.
                      
 
                      
 
                    
 
                    
 
                    
-
                    Parent topic: Node O&M
                    
+
                    Parent topic: Cluster
                    
 
                    
 
                    
 
diff --git a/docs/cce/umn/cce_bestpractice_10021.html b/docs/cce/umn/cce_bestpractice_10021.html
new file mode 100644
index 000000000..b44e099d8
--- /dev/null
+++ b/docs/cce/umn/cce_bestpractice_10021.html
@@ -0,0 +1,34 @@
+
+
+
                    Reporting Prometheus Monitoring Data to a Third-Party Monitoring Platform
                    
+
                    Application Scenarios
                    The Cloud Native Cluster Monitoring add-on can report Prometheus metrics collected from clusters to a specified platform, for example, AOM or a third-party platform that supports Prometheus metrics. This section explains how to configure settings for Cloud Native Cluster Monitoring to send collected metrics to a third-party's Prometheus instance.
                    
+
                    
+
                    Step 1: Obtain the Data Reporting Address
                    Prometheus provides standard Remote Write APIs. You can enter the source address (Remote Write URL) in the Cloud Native Cluster Monitoring add-on for storing the locally collected monitoring data in a Prometheus instance remotely.
                    
+
                    • If the Prometheus instance for receiving data is provided by a third-party vendor, view the Remote Write URL on the vendor's console.
                    • If the Prometheus instance for receiving data is an on-premises one, the Remote Write URL is https:// {prometheus_addr} /api/v1/write, where {prometheus_addr} indicates the IP address and port number for external access.
                    
+
                    
+
                    Step 2: Obtain the Authentication Mode
                    • If the Prometheus instance for receiving data is provided by a third-party vendor, view the token or account password used for authorized access on the vendor's console.
                    • For the on-premises Prometheus instance, take the following steps to obtain a token:
                      1. If this Prometheus instance is deployed in a Kubernetes cluster, view the token in the corresponding container. If this Prometheus instance is deployed on a VM, skip this step.
                        kubectl exec -ti -n monitoring prometheus-server-0 sh
                        
+
                        Replace the variables in the command as needed:
                        
+
                        • monitoring: indicates the namespace where a Prometheus pod is in.
                        • prometheus-server-0: indicates the name of a Prometheus pod.
                        
+
                      2. Check the location of the configuration file.
                        ps -aux | grep prometheus
                        
+
                        Information similar to the following is displayed:
                        
+
                        
+
                      3. View and record the token information in prometheus.env.yaml.
                        cat /etc/prometheus/config_out/prometheus.env.yaml
                        
+
                        
+
                      
+
                    
+
                    
+
                    Step 3: Connect to a Third-Party Monitoring Platform
                    1. Log in to the CCE console, click the name of a cluster with the Cloud Native Cluster Monitoring add-on installed to access the cluster console.
                    2. In the navigation pane, choose Add-ons, locate the Cloud Native Cluster Monitoring add-on, and click Edit.
                    3. Enable Report Monitoring Data to a Third-Party Platform so that the data collected by Cloud Native Cluster Monitoring can be reported to a third-party monitoring platform.
                      • Source Address: Remote Write URL obtained in step 1, for example, https://127.0.0.1:9090/api/v1/write.
                      • Authentication method: Select the authentication method supported by the third-party monitoring platform in step 2.
                        • Basic Auth: Enter the user name and password.
                        • Bearer Token: Enter the identity credential (token).
                        
+
                      
+
                      
+
                    4. After the modification is complete, click OK.
                    
+
                    
+
                    Step 4: Check the Data Sending and Receiving Statuses
                    After the preceding configuration is complete, log in to the Prometheus console supported by the third-party platform and view the Prometheus metrics with remote write on the Graph page.
                    
+
                    
+
                    
+
                    
+
                    
+
                    
+
                    Parent topic: Monitoring
                    
+
                    
+
                    
+
diff --git a/docs/cce/umn/cce_bulletin_0000.html b/docs/cce/umn/cce_bulletin_0000.html
index 5c3a01a8a..18346db6f 100644
--- a/docs/cce/umn/cce_bulletin_0000.html
+++ b/docs/cce/umn/cce_bulletin_0000.html
@@ -4,8 +4,6 @@
 
                    
 
                    
 
                      
-
                    • Kubernetes Version Policy
                      
-
                      • 
 
                    • EOM of CentOS
                      
 
                      • 
 
                    • Security Vulnerability Responses
                      
diff --git a/docs/cce/umn/cce_bulletin_0033.html b/docs/cce/umn/cce_bulletin_0033.html
deleted file mode 100644
index 1e403bd37..000000000
--- a/docs/cce/umn/cce_bulletin_0033.html
+++ /dev/null
@@ -1,182 +0,0 @@
-
-
-
                      Kubernetes Version Policy
                      
-
                      CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. This section describes the Kubernetes version policy of CCE clusters.
                      
-
                      Lifecycle of CCE Cluster Versions
                      
-
                    Item
                    
 
                    Parameter
                    
+
                    Parameter
                    
                     		
 
                    Description
                    
                     		
 
                    
 
                    CPU management policy
                    
+
                    CPU management policy
                    
 
                    cpu-manager-policy
                    
+
                    cpu-manager-policy
                    
                     		
 
                    CPU management policy configuration. For details, see CPU Scheduling.
                    
 
                    • none: disables pods from exclusively occupying CPUs. Select this value if you want a large pool of shareable CPU cores.
                    • static: enables pods to exclusively occupy CPUs. Select this value if your workload is sensitive to latency in CPU cache and scheduling.
                    
@@ -35,9 +35,9 @@
 
                    None
                    
                     		
 
                    QPS for requests to kube-apiserver
                    
+
                    QPS for requests to kube-apiserver
                    
 
                    kube-api-qps
                    
+
                    kube-api-qps
                    
                     		
 
                    Number of queries per second for communication with the API server.
                    
 
                    None
                    
                     		
 
                    Burst for requests to kube-apiserver
                    
+
                    Burst for requests to kube-apiserver
                    
 
                    kube-api-burst
                    
+
                    kube-api-burst
                    
                     		
 
                    Maximum number of burst requests sent to the API server per second.
                    
 
                    None
                    
                     		
 
                    Limit on the pods managed by kubelet
                    
+
                    Limit on the pods managed by kubelet
                    
 
                    max-pods
                    
+
                    max-pods
                    
                     		
 
                    Maximum number of pods that can run on a node.
                    
 
                    None
                    
                     		
 
                    Limited number of processes in a pod
                    
+
                    Limited number of processes in a pod
                    
 
                    pod-pids-limit
                    
+
                    pod-pids-limit
                    
                     		
 
                    Maximum number of PIDs that can be used in each pod.
                    
 
                    None
                    
                     		
 
                    Whether to use a local IP address as a node's ClusterDNS
                    
+
                    Whether to use a local IP address as a node's ClusterDNS
                    
 
                    with-local-dns
                    
+
                    with-local-dns
                    
                     		
 
                    The default ENI IP address of the node will be automatically added to the node's kubelet configuration as the preferred DNS address.
                    
 
                    None
                    
                     		
 
                    QPS limit on creating events
                    
+
                    QPS limit on creating events
                    
 
                    event-qps
                    
+
                    event-qps
                    
                     		
 
                    Number of events that can be generated per second.
                    
 
                    None
                    
                     		
 
                    Upper Limit for Burst Events
                    
+
                    Upper Limit for Burst Events
                    
 
                    event-burst
                    
+
                    event-burst
                    
                     		
 
                    Upper limit for burst event creation. The number of burst events can be temporarily increased to the specified value.
                    
 
                    None
                    
                     		
 
                    Allowed unsafe sysctls
                    
+
                    Allowed unsafe sysctls
                    
 
                    allowed-unsafe-sysctls
                    
+
                    allowed-unsafe-sysctls
                    
                     		
 
                    Insecure system configuration allowed.
                    
 
                    Starting from v1.17.17, CCE enables pod security policies for kube-apiserver. Add corresponding configurations to allowedUnsafeSysctls of a pod security policy to make the policy take effect. (This configuration is not required for clusters earlier than v1.17.17.) For details, see Example of Enabling Unsafe Sysctls in Pod Security Policy.
                    
@@ -124,9 +124,9 @@
 
                    None
                    
                     		
 
                    Node oversubscription
                    
+
                    Node oversubscription
                    
 
                    over-subscription-resource
                    
+
                    over-subscription-resource
                    
                     		
 
                    Whether to enable node oversubscription.
                    
 
                    If this parameter is set to true, node oversubscription is enabled on nodes. For details, see Dynamic Resource Oversubscription.
                    
@@ -136,9 +136,9 @@
 
                    None
                    
                     		
 
                    Hybrid deployment
                    
+
                    Hybrid deployment
                    
 
                    colocation
                    
+
                    colocation
                    
                     		
 
                    Whether to enable hybrid deployment on nodes.
                    
 
                    If this parameter is set to true, hybrid deployment is enabled on nodes. For details, see Dynamic Resource Oversubscription.
                    
@@ -148,9 +148,9 @@
 
                    None
                    
                     		
 
                    Topology management policy
                    
+
                    Topology management policy
                    
 
                    topology-manager-policy
                    
+
                    topology-manager-policy
                    
                     		
 
                    Set the topology management policy.
                    
 
                    Valid values are as follows:
                    
@@ -172,9 +172,9 @@
 
                    Default: container
                    
                     		
 
                    Specified DNS configuration file
                    
+
                    Specified DNS configuration file
                    
 
                    resolv-conf
                    
+
                    resolv-conf
                    
                     		
 
                    DNS resolution configuration file specified by the container
                    
 
                    None
                    
                     		
 
                    Timeout for all runtime requests except long-running requests
                    
+
                    Timeout for all runtime requests except long-running requests
                    
 
                    runtime-request-timeout
                    
+
                    runtime-request-timeout
                    
                     		
 
                    Timeout interval of all runtime requests except long-running requests (pull, logs, exec, and attach).
                    
 
                    This parameter is available only in clusters of v1.21.10-r0, v1.23.8-r0, v1.25.3-r0, or later versions.
                    
                     		
 
                    Whether to allow kubelet to pull only one image at a time
                    
+
                    Whether to allow kubelet to pull only one image at a time
                    
 
                    serialize-image-pulls
                    
+
                    serialize-image-pulls
                    
                     		
 
                    Pull an image in serial mode.
                    
 
                    • false: recommended configuration so that an image can be pulled in parallel mode to improve pod startup.
                    • true: allows images to be pulled in serial mode.
                    
@@ -206,9 +206,9 @@
 
                    This parameter is available only in clusters of v1.21.10-r0, v1.23.8-r0, v1.25.3-r0, or later versions.
                    
                     		
 
                    Image repository pull limit per second
                    
+
                    Image repository pull limit per second
                    
 
                    registry-pull-qps
                    
+
                    registry-pull-qps
                    
                     		
 
                    QPS upper limit of an image repository.
                    
 
                    This parameter is available only in clusters of v1.21.10-r0, v1.23.8-r0, v1.25.3-r0, or later versions.
                    
                     		
 
                    Upper limit of burst image pull
                    
+
                    Upper limit of burst image pull
                    
 
                    registry-burst
                    
+
                    registry-burst
                    
                     		
 
                    Maximum number of burst image pulls.
                    
 
                    This parameter is available only in clusters of v1.21.10-r0, v1.23.8-r0, v1.25.3-r0, or later versions.
                    
                     		
 
                    Maximum Number of Container Log Files
                    
+
                    Maximum Number of Container Log Files
                    
 
                    container-log-max-files
                    
+
                    container-log-max-files
                    
                     		
 
                    Maximum number of container log files. When the number of existing log files exceeds this value, the earliest log file will be deleted to release space for new log files.
                    
 
                    This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.28.4-r0, or later versions.
                    
                     		
 
                    Maximum Container Log File Size
                    
+
                    Maximum Container Log File Size
                    
 
                    container-log-max-size
                    
+
                    container-log-max-size
                    
                     		
 
                    Maximum size of a single container log file. When the size of a log file reaches this value, the current log file will be closed and a new log file will be created to continue logging.
                    
 
                    This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.28.4-r0, or later versions.
                    
                     		
 
                    Upper Limit for Image Garbage Collection
                    
+
                    Upper Limit for Image Garbage Collection
                    
 
                    image-gc-high-threshold
                    
+
                    image-gc-high-threshold
                    
                     		
 
                    When the kubelet disk usage reaches this value, kubelet starts to collect image garbage.
                    
                     		
 
 
                    Lower Limit for Image Garbage Collection
                    
+
                    Lower Limit for Image Garbage Collection
                    
 
                    image-gc-low-threshold
                    
+
                    image-gc-low-threshold
                    
                     		
 
                    When the disk usage reduces to this value, image garbage collection stops.
                    
                     		
 
 
                    Node memory reservation
                    
+
                    Node memory reservation
                    
 
                    system-reserved-mem
                    
+
                    system-reserved-mem
                    
                     		
 
                    System memory reservation reserves memory resources for OS system daemons such as sshd and udev.
                    
 
                    Kubernetes memory reservation reserves memory resources for Kubernetes daemons such kubelet and container runtime.
                    
                     		
 
                    Hard eviction
                    
+
                    Hard eviction
                    
 
                    
 
                    
 
                    
@@ -305,7 +305,7 @@
 
                    
 
                    
 
                    memory.available
                    
+
                    memory.available
                    
                     		
 
                    Available memory on a node.
                    
                     		
 
                    
 
                    Maximum size of a container core file
                    
+
                    Maximum size of a container core file
                    
                     		
 
                    limitcore
                    
                     		
 
                    Maximum size of a core file in a container. The unit is byte.
                    
-
                    If not specified, the value is infinity.
                    
+
                    If not specified, the value is infinity.
                    
                     		
 
                    Default: 5368709120
                    
 
                    Default: 1048576
                    
                     		
 
                    The value cannot exceed the value of the kernel parameter nr_open and cannot be a negative number.
                    
-
                    You can run the following command to obtain the kernel parameter nr_open:
                    
+
                    You can run the following command to obtain the kernel parameter nr_open:
                    
 
                    sysctl -a | grep nr_open
                    
                     		
 
                    
 
                    Data Disk
                    
 
                    At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
                    • 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.
                    • 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.
                    
+
                    At least one data disk is required for the container runtime and kubelet components in 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
                    • 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.
                    • 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.
                    
 
                    
 
                     NOTE: 
                    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.
                    
 
                    
@@ -103,8 +103,8 @@
 
                    Expand the area and configure the following parameters:
                    
 
                    • Data Disk Space Allocation: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see Space Allocation of a Data Disk.
                       NOTE: 
                      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.
                      
 
                      
-
                    • Enabled: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. 
                      • Not encrypted is selected by default.
                      • After setting Data Disk Encryption to Enabled, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the key text box.
                      
-
                       NOTE: 
                      After the Data Disk Encryption is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.
                      
+
                    • Enabled: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. 
                      • Not encrypted is selected by default.
                      • After setting Data Disk Encryption to Enabled, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the key text box.
                      
+
                       NOTE: 
                      After the Data Disk Encryption is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.
                      
 
                      
 
                    
 
                    Adding data disks
                    
diff --git a/docs/cce/umn/cce_10_0659.html b/docs/cce/umn/cce_10_0659.html
index 52bab6dfe..fe84166fc 100644
--- a/docs/cce/umn/cce_10_0659.html
+++ b/docs/cce/umn/cce_10_0659.html
@@ -69,7 +69,7 @@
 
                    Typical scenario: Disk I/O suspension causes process suspension.
                    
                     		
 
                    Warning event
                    
-
                    Listening object: /dev/kmsg
                    
+
                    Listening object: /dev/kmsg
                    
 
                    Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."
                    
                     		
 
                    
 
 
                    Warning event
                    
-
                    Listening object: /dev/kmsg
                    
+
                    Listening object: /dev/kmsg
                    
 
                    Matching rule: Remounting filesystem read-only
                    
                     		
 
                    
 
                    String
                    
 
                    To interconnect with HTTPS backend services, set this parameter to https.
                    
+
                    To interconnect with HTTPS backend services, set this parameter to https.
                    
                     		
 
                    v1.23.8, v1.25.3, or later
                    
                     		
 
 
 
 
 
 
 
                    horizontal-pod-autoscaler-sync-period
                    
                     		
 
                    Period for the horizontal pod autoscaler to perform elastic scaling on pods. A smaller value will result in a faster auto scaling response and higher CPU load.
                    
-
                     NOTE: 
                    Make sure to configure this parameter properly as a lengthy period can cause the controller to respond slowly, while a short period may overload the cluster control plane.
                    
+
                     NOTE: 
                    Make sure to configure this parameter properly as a lengthy period can cause the controller to respond slowly, while a short period may overload the cluster management plane.
                    
 
                    
 
                    		
 
                    Default: 15s
                    
diff --git a/docs/cce/umn/cce_10_0792.html b/docs/cce/umn/cce_10_0792.html
new file mode 100644
index 000000000..fa2e518e0
--- /dev/null
+++ b/docs/cce/umn/cce_10_0792.html
@@ -0,0 +1,52 @@
+
+
+
                    Collecting Audit Logs
                    
+
                    CCE supports logging for master nodes. On the Kubernetes Audit Logs tab of Logging, you can determine whether to report audit logs to LTS.
                    
+
                    Constraints
                    • The cluster version must be v1.21.7-r0 or later, v1.23.5-r0 or later, or 1.25.
                    • There is required LTS resource quota.
                    
+
                    
+
                    Audit Logs
                    
+
                    
+
+
+
+
+
+
+
+
+
+
+
+
                    Table 1 Audit logs
                    Log Type
                    
+
                    Component
                    
+
                    Log Stream
                    
+
                    Description
                    
+
                    Audit logs
                    
+
                    audit
                    
+
                    audit-{{clusterID}}
                    
+
                    An audit log is a chronological record of user operations on Kubernetes APIs and control plane activities for security.
                    
+
                    
+
                    
+
                    
+
                    Enabling Audit Logging
                    Enabling audit logging during cluster creation
                    
+
                    1. Log in to the CCE console.
                    2. In the upper right corner, click Create Cluster. Then, configure the parameters and click Next: Select Add-on.
                    3. On the displayed page, select Cloud Native Log Collection and click Next: Add-on Configuration.
                    4. On the displayed page, select Kubernetes Audit Logs for Cloud Native Log Collection.
                    5. Click Next: Confirm configuration.
                    
+
                    Enabling audit logging for an existing cluster
                    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
                    2. Click the Kubernetes Audit Logs tab and modify the settings in Logging Settings.
                      Figure 1 Enabling audit logging for an existing cluster
                      
+
                    3. Determine whether to enable logging for the audit component. If yes, click .
                    
+
                    
+
                    
+
                    Viewing Audit Logs
                    Viewing audit logs on the CCE console
                    
+
                    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
                    2. Click the Kubernetes Audit Logs tab to view audit logs in the cluster. For details about related operations, see LTS User Guide.
                    
+
                    Viewing audit logs on the TLS console
                    
+
                    1. Log in to the LTS console and choose Log Management.
                    2. Search for the log group by cluster ID and click the log group name to view the log streams. For details, see LTS User Guide.
                    
+
                    
+
                    Disabling Audit Logging
                    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
                    2. Click the Kubernetes Audit Logs tab.
                    3. Disable the audit component and click .
                       
                      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.
                      
+
                      
+
                    
+
                    
+
                    
+
                    
+
                    
+
                    Parent topic: Logging
                    
+
                    
+
                    
+
diff --git a/docs/cce/umn/cce_10_0793.html b/docs/cce/umn/cce_10_0793.html
new file mode 100644
index 000000000..a26ca7275
--- /dev/null
+++ b/docs/cce/umn/cce_10_0793.html
@@ -0,0 +1,57 @@
+
+
+
                    Collecting Kubernetes Events
                    
+
                    The Cloud Native Log Collection add-on works with LTS to collect and store Kubernetes events and works with AOM to generate alarms.
                    
+
                    Reporting Kubernetes Events to LTS
                    To enable Kubernetes event collection in different scenarios, take the following steps.
                    
+
                    
+
                    Logging Has Been Enabled for a Cluster
                    If logging has been enabled for a cluster but Kubernetes event collection has not been enabled, or the corresponding log collection policy has been deleted, you can manually create a log collection policy by taking the following steps:
                    
+
                    1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging.
                    2. In the upper right corner, click View Log Collection Policies.
                      
+
                      All log collection policies are displayed.
                      
+
                    3. Click Create Log Collection Policy. Then, select Kubernetes events and click OK.
                      
+
                    4. (After the creation is complete, you can view logs on the Logging page.) Select the log stream configured in the log collection policy to view the events reported to LTS.
                      
+
                    
+
                    
+
                    Reporting Kubernetes Events to AOM
                    In 1.3.2 and later versions, the Cloud Native Log Collection add-on reports all warning events and some normal events to AOM by default. The reported events can be used to configure alarms. If the cluster version is 1.19.16, 1.21.11, 1.23.9, 1.25.4, or later, after the Cloud Native Log Collection add-on is installed, events will be reported to AOM by this add-on instead of the control plane component. After the Cloud Native Log Collection add-on is uninstalled, events will not be reported to AOM.
                    
+
                    Custom Event Reporting
                    
+
                    If the reported events cannot meet requirements, you can modify the settings for the events.
                    
+
                    
+
                    Using kubectl
                    1. Run the following command on the cluster to modify the event collection settings:
                      kubectl edit logconfig -n kube-system default-event-aom
                      
+
                    2. Modify the event collection settings as required.
                      apiVersion: logging.openvessel.io/v1
+kind: LogConfig
+metadata:
+  annotations:
+    helm.sh/resource-policy: keep
+  name: default-event-aom
+  namespace: kube-system
+spec:
+  inputDetail:    # Settings on CCE from which events are collected
+    type: event    # Type of logs to be collected from CCE. Do not change the value.
+    event:
+      normalEvents:    # Used to configure normal events
+        enable: true    # Whether to enable normal event collection
+        includeNames:    # Names of events to be collected. If this parameter is not specified, all events will be collected.
+        - NotTriggerScaleUp
+        excludeNames:    # Names of events that are not collected. If this parameter is not specified, all events will be collected.
+        - ScaleDown
+      warningEvents:    # Used to configure warning events
+        enable: true    # Whether to enable warning event collection
+        includeNames:    # Names of events to be collected. If this parameter is not specified, all events will be collected.
+        - NotTriggerScaleUp
+        excludeNames:    # Names of events that are not collected. If this parameter is not specified, all events will be collected.
+        - ScaleDown
+  outputDetail:
+    type: AOM    # Type of the system that receives the events. Do not change the value.
+    AOM:
+      events:
+      - name: DeleteNodeWithNoServer    # Event name. This parameter is mandatory.
+        resourceType: Namespace    # Type of the resource that operations are performed on.
+        severity: Major    # Event severity after an event is reported to AOM, which can be Critical, Major, Minor, or Info. The default value is Major.
                      
+
                    
+
                    
+
                    
+
                    
+
                    
+
                    Parent topic: Logging
                    
+
                    
+
                    
+
diff --git a/docs/cce/umn/cce_10_0799.html b/docs/cce/umn/cce_10_0799.html
new file mode 100644
index 000000000..91b0723f4
--- /dev/null
+++ b/docs/cce/umn/cce_10_0799.html
@@ -0,0 +1,15 @@
+
+
+
                    FAQ
                    
+
                    
+
                    
+
+
+
                    
+
                    Parent topic: Observability
                    
+
                    
+
                    
+
diff --git a/docs/cce/umn/cce_10_0809.html b/docs/cce/umn/cce_10_0809.html
new file mode 100644
index 000000000..89731e854
--- /dev/null
+++ b/docs/cce/umn/cce_10_0809.html
@@ -0,0 +1,65 @@
+
+
+
                    Logging FAQ
                    
+
                    Indexes
                    
+
                    
+
                    How Do I Disable Logging?
                    Disabling container log and Kubernetes event collection
                    
+
                    Method 1: Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Logging. In the upper right corner, click View Log Collection Policies. Then, locate and delete the corresponding log collection policy. 
                    
+
                    Method 2: Access the Add-ons page and uninstall the Cloud Native Log Collection add-on. Note: Once you uninstall this add-on, it will no longer report Kubernetes events to AOM.
                    
+
                    
+
                    Disabling the log collection of control plane components
                    
+
                    Choose Logging > Control Plane Logs and deselect one or more components whose logs do not need to be collected.
                    
+
                    Disabling Kubernetes audit log collection
                    
+
                    Choose Logging > Kubernetes Audit Logs and deselect the component whose logs do not need to be collected.
                    
+
                    
+
                    All Components Except log-operator Are Not Ready
                    Symptom: All components except log-operator are not ready, and the volume failed to be attached to the node.
                    
+
                    Solution: 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.
                    
+
                    The log information is as follows:
                    
+
                    MountVolume.SetUp failed for volume "otel-collector-config-vol":configmap "log-agent-otel-collector-config" not found
                    
+
                    
+
                    There Is an Error in Stdout Logs of log-operator
                    Symptom:
                    
+
                    2023/05/05 12:17:20.799 [E] call 3 times failed, reason: create group failed, projectID: xxx, groupName: k8s-log-xxx, err: create groups status code: 400, response: {"error_code":"LTS.0104","error_msg":"Failed to create log group, the number of log groups exceeds the quota"}, url: https://lts.***.com/v2/xxx/groups, process will retry after 45s
                    
+
                    Solution: On the LTS console, delete unnecessary log groups. 
                    
+
                    
+
                    Container File Logs Cannot Be Collected When Docker Is Used as the Container Engine
                    Symptom:
                    
+
                    A container file path is configured but is not mounted to the container, and Docker is used as the container engine. As a result, logs cannot be collected.
                    
+
                    Solution:
                    
+
                    Check whether Device Mapper is used for the node where the workload resides. Device Mapper does not support text log collection. (This restriction is displayed when you create a log collection policy.) To check this, perform the following operations:
                    
+
                    1. Go to the node where the workload resides.
                    2. Run the docker info | grep "Storage Driver" command.
                    3. If the value of Storage Driver is Device Mapper, text logs cannot be collected.
                    
+
                    
+
                    Container File Logs Cannot Be Collected Due to the Wildcard in the Collection Directory
                    Troubleshooting: Check the volume mounting status in the workload configuration. If a volume is attached to the data directory of a service container, this add-on cannot collect data from the parent directory. In this case, you need to set the collection directory to a complete data directory. For example, if the data volume is attached to the /var/log/service directory, logs cannot be collected from the /var/log or /var/log/* directory. In this case, you need to set the collection directory to /var/log/service.
                    
+
                    Solution: If the log generation directory is /application/logs/{Application name}/*.log, attach the data volume to the /application/logs directory and set the collection directory in the log collection policy to /application/logs/*/*.log.
                    
+
                    
+
                    fluent-bit Pod Keeps Restarting
                    Troubleshooting: Run the kubectl describe pod command. The output shows that the pod was restarted due to OOM. There are a large number of evicted pods on the node where the fluent-bit resides. As a result, resources are occupied, causing OOM.
                    
+
                    Solution: Delete the evicted pods from the node.
                    
+
                    
+
                    Job Logs Cannot Be Collected
                    Troubleshooting: Check the job lifetime. If the job lifetime is less than 1 minute, the pod will be destroyed before logs are collected. In this case, logs cannot be collected.
                    
+
                    Solution: Prolong the job lifetime.
                    
+
                    
+
                    Cloud Native Log Collection is Running Normally, but Some Log Collection Policies Do Not Take Effect
                    Solution:
                    
+
                    • If the log collection policy of the event type does not take effect or the add-on version is earlier than 1.5.0, check the stdout of the log-agent-otel-collector workload.
                      Go to the Add-ons page and click the name of Cloud Native Log Collection. Then, click the Pods tab, locate log-agent-otel-collector, and choose More > View Log in the Operation column.
                      
+
                    • If the log collection policy of the other type does not take effect and the add-on version is later than 1.5.0, check the log of the log-agent-fluent-bit instance on the node where the container to be monitored resides.
                      Go to the Add-ons page and click the name of Cloud Native Log Collection. Then, click the Pods tab, locate log-agent-fluent-bit of the corresponding node, and choose More > View Log in the Operation column.
                      
+
                      Select the fluent-bit container, search for the keyword "fail to push {event/log} data via lts exporter" in the log, and view the error message.
                      
+
                      1. If the error message "The log streamId does not exist." is displayed, the log group or log stream does not exist. In this case, choose Logging > View Log Collection Policies, edit or delete the log collection policy, and recreate a log collection policy to update the log group or log stream.
                      2. For other errors, go to LTS to search for the error code and view the cause. 
                      
+
                      
+
                    
+
                    
+
                    Some Pod Information Is Missing During Log Collection Due to Excessive Node Load
                    When the Cloud Native Log Collection add-on version is later than 1.5.0, some pod information, such as the pod ID and name, is missing from container file logs or stdout logs.
                    
+
                    Troubleshooting:
                    
+
                    Go to the Add-ons page and click the name of Cloud Native Log Collection. Then, click the Pods tab, locate log-agent-fluent-bit of the corresponding node, and choose More > View Log in the Operation column.
                    
+
                    Select the fluent-bit container and search for the keyword "cannot increase buffer: current=512000 requested=*** max=512000" in the log.
                    
+
                    Solution:
                    
+
                    Run the kubectl edit deploy -n monitoring log-agent-log-operator command on the node and add --kubernetes-buffer-size=20MB to the command lines of the log-operator container. The default value is 16MB. You can estimate the value based on the total size of pod information on the node. 0 indicates no limits.
                    
+
                     
                    If the Cloud Native Log Collection add-on is upgraded, you need to reconfigure kubernetes-buffer-size.
                    
+
                    
+
                    Figure 1 Modifying the command line parameter of the log-operator container
                    
+
                    
+
                    How Do I Change the Log Storage Period on Logging?
                    1. On the Clusters page, hover the cursor over the cluster name to view the current cluster ID.
                    2. Log in to the LTS console. In the navigation pane, choose Log Management. In Log Groups, select a search criterion. Query the log group and log stream by cluster ID.
                    3. Locate the log group and click Modify to configure the log storage period.
                    
+
                    
+
                    
+
                    
+
                    
+
                    Parent topic: FAQ
                    
+
                    
+
                    
+
diff --git a/docs/cce/umn/cce_10_0836.html b/docs/cce/umn/cce_10_0836.html
index 9edfa4896..62cf96c49 100644
--- a/docs/cce/umn/cce_10_0836.html
+++ b/docs/cce/umn/cce_10_0836.html
@@ -3,7 +3,7 @@
 
                    Monitoring
                    
 
                    CCE monitors applications and resources and collects metrics and events to analyze application health status. You can choose Settings from the navigation pane, click the Monitoring tab, and change monitoring parameters on the console.
                    
 
                    Log Configuration
                    Collection configuration
                    
-
                    Send stdout Logs to AOM 1.0 (No more evolution): Logging in AOM 1.0 has not been improved, so you are advised to disable this function and use LTS logging instead. 
                    
+
                    Send stdout Logs to AOM 1.0 (No more evolution): Logging in AOM 1.0 has not been improved, so you are advised to disable this function and use LTS logging instead. 
                    
 
                    
 
                    
 
                    
diff --git a/docs/cce/umn/cce_10_0864.html b/docs/cce/umn/cce_10_0864.html
index 26504e237..584b2128a 100644
--- a/docs/cce/umn/cce_10_0864.html
+++ b/docs/cce/umn/cce_10_0864.html
@@ -8,7 +8,7 @@
 
                    
 
                    Configuring Access Policies for an API Server
                    To ensure the security of a cluster's API server, it is important to modify the security group rules for the master nodes. This is because the EIP, which is exposed to the Internet, is at risk of being attacked.
                    
 
                    1. Log in to the CCE console and click the cluster name to access the cluster console. On the Overview page, copy the cluster ID in the Basic Info area.
                    2. Log in to the VPC console. In the navigation pane, choose Access Control > Security Groups.
                    3. Select Description as the filter criterion and paste the cluster ID to search for the target security group.
                    4. Locate the row that contains the security group (starting with {CCE cluster name}-cce-control) of the master node and click Manage Rules in the Operation column.
                    5. On the page displayed, locate the row that contains port 5443 and click Modify in the Operation column to modify its inbound rules.
                      
-
                    6. Change the source IP address that can be accessed as required. For example, if the IP address used by the client to access the API Server is 100.*.*.*, you can add an inbound rule for port 5443 and set the source IP address to 100.*.*.*.
                       
                      In addition to the client IP address, the port must allow traffic from the CIDR blocks of the VPC, container, and the control plane of the hosted service mesh to ensure that the API Server can be accessed from within the cluster.
                      
+
                    7. Change the source IP address that can be accessed as required. For example, if the IP address used by the client to access the API Server is 100.*.*.*, you can add an inbound rule for port 5443 and set the source IP address to 100.*.*.*.
                       
                      In addition to the client IP address, the port must allow traffic from the CIDR blocks of the VPC, container, and the management plane of the hosted service mesh to ensure that the API Server can be accessed from within the cluster.
                      
 
                      
 
                      
 
                    8. Click Confirm.
                    
diff --git a/docs/cce/umn/cce_10_0908.html b/docs/cce/umn/cce_10_0908.html
index 9e775ee40..328952f14 100644
--- a/docs/cce/umn/cce_10_0908.html
+++ b/docs/cce/umn/cce_10_0908.html
@@ -10,6 +10,8 @@
 
                      
 
                    • Cloud Native Cluster Monitoring
                      
 
                      • 
+
                    • Cloud Native Log Collection
                      
+
                      • 
 
                    • CCE Node Problem Detector
                      
 
                      • 
 
                    • Kubernetes Metrics Server
                      
diff --git a/docs/cce/umn/cce_10_0914.html b/docs/cce/umn/cce_10_0914.html
new file mode 100644
index 000000000..06c9bfb75
--- /dev/null
+++ b/docs/cce/umn/cce_10_0914.html
@@ -0,0 +1,143 @@
+
+
+
                      Creating an SFS Subdirectory Using a Dynamic PV
                      
+
                      When an SFS volume is mounted to a workload container, the root directory is mounted to the container by default. To properly use the storage capacity, CCE allows you to dynamically create an SFS subdirectory when creating a PVC so that different workloads can share one SFS volume.
                      
+
                       
                      Only SFS 3.0 supports dynamic creation of subdirectories.
                      
+
                      
+
                      Prerequisites
                      • You have created a cluster and installed the CCE Container Storage (Everest) add-on of v2.4.41 or later in the cluster.
                      • To create a cluster using commands, ensure kubectl is used. For details, see Connecting to a Cluster Using kubectl.
                      • You have created an available SFS file system, and the SFS file system and the cluster are in the same VPC. Before using SFS 3.0 for storage, ensure a VPC endpoint has been created in the VPC where the cluster is located for the cluster to access the SFS 3.0 file system. For details, see Configure a VPC Endpoint.
                      
+
                      
+
                      Dynamically Creating an SFS Subdirectory on the Console
                      1. Log in to the CCE console and click the cluster name to access the cluster console.
                      2. Choose Storage in the navigation pane. In the right pane, click the PVCs tab. Click Create PVC in the upper right corner. In the dialog box displayed, configure PVC parameters.
                        
+
                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                        Parameter
                        
+
                        Description
                        
+
                        PVC Type
                        
+
                        In this example, select SFS.
                        
+
                        PVC Name
                        
+
                        Enter the PVC name, which must be unique in a namespace.
                        
+
                        Creation Method
                        
+
                        Select New subdirectory.
                        
+
                        Storage Classes
                        
+
                        Select csi-sfs for SFS.
                        
+
                        You can customize a StorageClass and configure its reclaim policy and binding mode. For details, see Creating a StorageClass Using the CCE Console.
                        
+
                        Access Mode
                        
+
                        SFS volumes support only ReadWriteMany, indicating that a storage volume can be mounted to multiple nodes in read/write mode. For details, see Volume Access Modes.
                        
+
                        SFS
                        
+
                        Click Select SFS. On the displayed page, select the SFS file system that meets your requirements and click OK.
                        
+
                        Subdirectory
                        
+
                        Enter the absolute path of a subdirectory, for example, /a/b.
                        
+
                        Subdirectory Reclaim Policy
                        
+
                        Whether to retain subdirectories when a PVC is deleted.
                        
+
                        • Retain: If a PVC is deleted, the PV will be deleted, but the subdirectories associated with the PV will be retained.
                        • Delete: After a PVC is deleted, the PV and its associated subdirectories will also be deleted.
                           NOTE: 
                          When a subdirectory is deleted, only the absolute path of the subdirectory configured in the PVC will be deleted. The upper-layer directory will not be deleted.
                          
+
                          
+
                        
+
                        
+
                        
+
                      3. Click Create to create a PVC and a PV.
                        You can choose Storage in the navigation pane and view the created PVC and PV on the PVCs and PVs tab pages, respectively.
                        
+
                      
+
                      
+
                      Dynamically Creating an SFS Subdirectory Using kubectl
                      1. Use kubectl to access the cluster.
                      2. Create the pvc-sfs-subpath.yaml file.
                        apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: pvc-sfs-subpath    # PVC name
+  namespace: default
+  annotations:
+    everest.io/csi.volume-as: absolute-path                # An SFS subdirectory is used.
+    everest.io/csi.sfs30-name: <sfs_name>                    # Name of the SFS instance
+    everest.io/csi.path: /a                                # Subdirectory that is automatically created, which must be an absolute path
+    everest.io/csi.reclaim-policy: retain-volume-only      # When a PVC is deleted, the PV will be deleted, but the subdirectories associated with the PV will be retained.
+spec:
+  accessModes:
+    - ReadWriteMany      # ReadWriteMany must be selected for SFS.
+  resources:
+    requests:
+      storage: 1Gi      # This parameter is only used for verification for the PVCs of the SFS subdirectory type. The value cannot be empty or 0.
+  storageClassName: csi-sfs     # StorageClass name of SFS 3.0
                        
+
+
                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                        Table 1 Key parameters
                        Parameter
                        
+
                        Mandatory
                        
+
                        Description
                        
+
                        everest.io/csi.volume-as
                        
+
                        Yes
                        
+
                        When a dynamically created SFS subdirectory is used, the value of this parameter is consistently absolute-path.
                        
+
                        everest.io/csi.sfs30-name
                        
+
                        Yes
                        
+
                        SFS instance name.
                        
+
                        everest.io/csi.path
                        
+
                        Yes
                        
+
                        Subdirectory that is automatically created, which must be an absolute path.
                        
+
                        everest.io/csi.reclaim-policy
                        
+
                        Yes
                        
+
                        Whether to retain subdirectories when deleting a PVC. This parameter must be used with PV Reclaim Policy. This parameter is available only when the PV reclaim policy is Delete. Options:
                        
+
                        • retain-volume-only: If a PVC is deleted, the PV will be deleted, but the subdirectories associated with the PV will be retained.
                        • delete: After a PVC is deleted, the PV and its associated subdirectories will also be deleted.
                           NOTE: 
                          When a subdirectory is deleted, only the absolute path of the subdirectory configured in the PVC will be deleted. The upper-layer directory will not be deleted.
                          
+
                          
+
                        
+
                        storage
                        
+
                        Yes
                        
+
                        Requested capacity in the PVC, in Gi.
                        
+
                        This parameter is only used for verification for the PVCs of the SFS subdirectory type. The value cannot be empty or 0, and can be fixed at 1 because any value you set does not take effect.
                        
+
                        
+
                        
+
                      3. Run the following command to create a PVC:
                        kubectl apply -f pvc-sfs-subpath.yaml
                        
+
                      
+
                      
+
                      
+
                      
+
                      
+
                      Parent topic: Scalable File Service
                      
+
                      
+
                      
+
diff --git a/docs/cce/umn/cce_bestpractice_00253.html b/docs/cce/umn/cce_bestpractice_00253.html
index b0d09513e..a3ff084b2 100644
--- a/docs/cce/umn/cce_bestpractice_00253.html
+++ b/docs/cce/umn/cce_bestpractice_00253.html
@@ -1,14 +1,14 @@
 
 
 
                      Dynamically Creating an SFS Turbo Subdirectory Using StorageClass
                      
-
                      Background
                      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, does not require such a large capacity.
                      
-
                      The everest add-on allows you to dynamically create subdirectories in an SFS Turbo file system and mount these subdirectories to containers. In this way, an SFS Turbo file system can be shared by multiple containers to increase storage efficiency.
                      
+
                      Background
                      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, does not require such a large capacity.
                      
+
                      The everest add-on allows you to dynamically create subdirectories in an SFS Turbo file system and mount these subdirectories to containers. In this way, an SFS Turbo file system can be shared by multiple containers to increase storage efficiency.
                      
 
                      
-
                      Constraints
                      • Only clusters of v1.15 or later are supported.
                      • The cluster must use the everest add-on of version 1.1.13 or later.
                      • Kata containers are not supported.
                      • When the everest add-on earlier than 1.2.69 or 2.1.11 is used, a maximum of 10 PVCs can be created concurrently at a time by using the subdirectory function. everest of 1.2.69 or later or of 2.1.11 or later is recommended.
                      • A subPath volume is a subdirectory of an SFS Turbo file system. Increasing the capacity of a PVC of this type only changes the resource range specified by the PVC, but does not change the total capacity of the SFS Turbo file system. If the SFS Turbo file system's total resource capacity is not enough, the available capacity of the subPath volume will be restricted. To fix this, you must increase the resource capacity of the SFS Turbo file system on the SFS Turbo console.
                        Deleting the subPath volume does not result in the deletion of the resources of the SFS Turbo file system.
                        
+
                        Constraints
                        • Only clusters of v1.15 or later are supported.
                        • The cluster must use the everest add-on of version 1.1.13 or later.
                        • Kata containers are not supported.
                        • When the everest add-on earlier than 1.2.69 or 2.1.11 is used, a maximum of 10 PVCs can be created concurrently at a time by using the subdirectory function. everest of 1.2.69 or later or of 2.1.11 or later is recommended.
                        • A subPath volume is a subdirectory of an SFS Turbo file system. Increasing the capacity of a PVC of this type only changes the resource range specified by the PVC, but does not change the total capacity of the SFS Turbo file system. If the SFS Turbo file system's total resource capacity is not enough, the available capacity of the subPath volume will be restricted. To fix this, you must increase the resource capacity of the SFS Turbo file system on the SFS Turbo console.
                          Deleting the subPath volume does not result in the deletion of the resources of the SFS Turbo file system.
                          
 
                        
 
                        
-
                        Creating an SFS Turbo Volume of the subPath Type
                        1. Create an SFS Turbo file system in the same VPC and subnet as the cluster.
                        2. Create a YAML file of StorageClass, for example, sfsturbo-subpath-sc.yaml.
                          The following is an example:
                          
-
                          apiVersion: storage.k8s.io/v1
+
                          Creating an SFS Turbo Volume of the subPath Type
                          1. Create an SFS Turbo file system in the same VPC and subnet as the cluster.
                          2. Create a YAML file of StorageClass, for example, sfsturbo-subpath-sc.yaml.
                            The following is an example:
                            
+
                            apiVersion: storage.k8s.io/v1
 allowVolumeExpansion: true
 kind: StorageClass
 metadata:
@@ -29,16 +29,16 @@ parameters:
 provisioner: everest-csi-provisioner
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
                            
-
                            In this example:
                            
-
                            • name: indicates the name of the StorageClass.
                            • mountOptions: indicates the mount options. This field is optional.
                              • In versions later than everest 1.1.13 and earlier than everest 1.2.8, only the nolock parameter can be configured. By default, the nolock parameter is used for the mount operation and does not need to be configured. If nolock is set to false, the lock field is used.
                              • Starting from everest 1.2.8, more mount options are supported. For details, see Configuring SFS Volume Mount Options. Do not set nolock to true. Otherwise, the mount operation will fail.
                                mountOptions:
+
                                In this example:
                                
+
                                • name: indicates the name of the StorageClass.
                                • mountOptions: indicates the mount options. This field is optional.
                                  • In versions later than everest 1.1.13 and earlier than everest 1.2.8, only the nolock parameter can be configured. By default, the nolock parameter is used for the mount operation and does not need to be configured. If nolock is set to false, the lock field is used.
                                  • Starting from everest 1.2.8, more mount options are supported. For details, see Configuring SFS Volume Mount Options. Do not set nolock to true. Otherwise, the mount operation will fail.
                                    mountOptions:
 - vers=3
 - timeo=600
 - nolock
 - hard
                                    
 
                                  
-
                                • everest.io/volume-as: This parameter is set to subpath to use the subPath volume.
                                • everest.io/share-access-to: This parameter is optional. In a subPath volume, set this parameter to the ID of the VPC where the SFS Turbo file system is located.
                                • everest.io/share-expand-type: This parameter is optional. If the type of the SFS Turbo file system is SFS Turbo Standard – Enhanced or SFS Turbo Performance – Enhanced, set this parameter to bandwidth.
                                • everest.io/share-export-location: This parameter indicates the mount directory. It consists of the SFS Turbo shared path and sub-directory. The shared path can be obtained on the SFS Turbo console. The sub-directory is user-defined. The PVCs created using the StorageClass are located in this sub-directory.
                                • everest.io/share-volume-type: This parameter is optional. It specifies the SFS Turbo file system type. The value can be STANDARD or PERFORMANCE. For enhanced types, this parameter must be used together with everest.io/share-expand-type (whose value should be bandwidth).
                                • everest.io/zone: This parameter is optional. Set it to the AZ where the SFS Turbo file system is located.
                                • everest.io/volume-id: This parameter indicates the ID of the SFS Turbo volume. You can obtain the volume ID on the SFS Turbo page.
                                • everest.io/archive-on-delete: If this parameter is set to true and Delete is selected for Reclaim Policy, the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted. If this parameter is set to false, the SFS Turbo subdirectory of the corresponding PV will be deleted. The default value is true, indicating that the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted.
                                
-
                          1. Run kubectl create -f sfsturbo-subpath-sc.yaml.
                          2. Create a PVC YAML file named sfs-turbo-test.yaml.
                            The following is an example:
                            
-
                            apiVersion: v1
+
                          3. everest.io/volume-as: This parameter is set to subpath to use the subPath volume.
                          4. everest.io/share-access-to: This parameter is optional. In a subPath volume, set this parameter to the ID of the VPC where the SFS Turbo file system is located.
                          5. everest.io/share-expand-type: This parameter is optional. If the type of the SFS Turbo file system is SFS Turbo Standard – Enhanced or SFS Turbo Performance – Enhanced, set this parameter to bandwidth.
                          6. everest.io/share-export-location: This parameter indicates the mount directory. It consists of the SFS Turbo shared path and sub-directory. The shared path can be obtained on the SFS Turbo console. The sub-directory is user-defined. The PVCs created using the StorageClass are located in this sub-directory.
                          7. everest.io/share-volume-type: This parameter is optional. It specifies the SFS Turbo file system type. The value can be STANDARD or PERFORMANCE. For enhanced types, this parameter must be used together with everest.io/share-expand-type (whose value should be bandwidth).
                          8. everest.io/zone: This parameter is optional. Set it to the AZ where the SFS Turbo file system is located.
                          9. everest.io/volume-id: This parameter indicates the ID of the SFS Turbo volume. You can obtain the volume ID on the SFS Turbo page.
                          10. everest.io/archive-on-delete: If this parameter is set to true and Delete is selected for Reclaim Policy, the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted. If this parameter is set to false, the SFS Turbo subdirectory of the corresponding PV will be deleted. The default value is true, indicating that the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted.
                      
+
                      1. Run kubectl create -f sfsturbo-subpath-sc.yaml.
                      2. Create a PVC YAML file named sfs-turbo-test.yaml.
                        The following is an example:
                        
+
                        apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
   name: sfs-turbo-test
@@ -51,13 +51,13 @@ spec:
       storage: 50Gi
   storageClassName: sfsturbo-subpath-sc
   volumeMode: Filesystem
                        
-
                        In this example:
                        
-
                        • name: indicates the name of the PVC.
                        • storageClassName: specifies the name of the StorageClass.
                        • storage: In a subPath volume, modifying the value of this parameter does not impact the resource capacity of the SFS Turbo file system. A subPath volume is essentially a file path within an SFS Turbo file system. As a result, increasing the capacity of the subPath volume in a PVC does not lead to an increase in the resources of the SFS Turbo file system.
                           
                          The capacity of a subPath volume is restricted by the overall resource capacity of the corresponding SFS Turbo file system. If the resources of the SFS Turbo file system are inadequate, you can adjust the resource capacity via the SFS Turbo console.
                          
+
                          In this example:
                          
+
                          • name: indicates the name of the PVC.
                          • storageClassName: specifies the name of the StorageClass.
                          • storage: In a subPath volume, modifying the value of this parameter does not impact the resource capacity of the SFS Turbo file system. A subPath volume is essentially a file path within an SFS Turbo file system. As a result, increasing the capacity of the subPath volume in a PVC does not lead to an increase in the resources of the SFS Turbo file system.
                             
                            The capacity of a subPath volume is restricted by the overall resource capacity of the corresponding SFS Turbo file system. If the resources of the SFS Turbo file system are inadequate, you can adjust the resource capacity via the SFS Turbo console.
                            
 
                            
 
                          
-
                      1. Run kubectl create -f sfs-turbo-test.yaml.
                      
+
                      1. Run kubectl create -f sfs-turbo-test.yaml.
                      
 
                    
-
                    Creating a Deployment and Mounting an Existing Volume
                    1. Create a YAML file for the Deployment, for example, deployment-test.yaml.
                      The following is an example:
                      apiVersion: apps/v1
+
                      Creating a Deployment and Mounting an Existing Volume
                      1. Create a YAML file for the Deployment, for example, deployment-test.yaml.
                        The following is an example:
                        apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: test-turbo-subpath-example
@@ -89,13 +89,13 @@ spec:
         persistentVolumeClaim: 
           claimName: sfs-turbo-test
                        
 
                        
-
                        In this example:
                        
-
                        • name: indicates the name of the created workload.
                        • image: specifies the image used by the workload.
                        • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                        • claimName: indicates the name of an existing PVC.
                        
-
                      1. Create the Deployment.
                        kubectl create -f deployment-test.yaml
                        
+
                        In this example:
                        
+
                        • name: indicates the name of the created workload.
                        • image: specifies the image used by the workload.
                        • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                        • claimName: indicates the name of an existing PVC.
                        
+
                      1. Create the Deployment.
                        kubectl create -f deployment-test.yaml
                        
 
                      
 
                      
-
                      Dynamically Creating a subPath Volume for a StatefulSet
                      1. Create a YAML file for a StatefulSet, for example, statefulset-test.yaml.
                        The following is an example:
                        
-
                        apiVersion: apps/v1
+
                        Dynamically Creating a subPath Volume for a StatefulSet
                        1. Create a YAML file for a StatefulSet, for example, statefulset-test.yaml.
                          The following is an example:
                          
+
                          apiVersion: apps/v1
 kind: StatefulSet
 metadata:
   name: test-turbo-subpath
@@ -151,15 +151,15 @@ spec:
   updateStrategy:
     type: RollingUpdate
   revisionHistoryLimit: 10
                          
-
                          In this example:
                          
-
                          • name: indicates the name of the created workload.
                          • image: specifies the image used by the workload.
                          • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                          • spec.template.spec.containers.volumeMounts.name and spec.volumeClaimTemplates.metadata.name: must be consistent because they have a mapping relationship.
                          • storageClassName: specifies the name of an on-premises StorageClass.
                          
-
                        1. Create the StatefulSet.
                          kubectl create -f statefulset-test.yaml
                          
+
                          In this example:
                          
+
                          • name: indicates the name of the created workload.
                          • image: specifies the image used by the workload.
                          • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                          • spec.template.spec.containers.volumeMounts.name and spec.volumeClaimTemplates.metadata.name: must be consistent because they have a mapping relationship.
                          • storageClassName: specifies the name of an on-premises StorageClass.
                          
+
                        1. Create the StatefulSet.
                          kubectl create -f statefulset-test.yaml
                          
 
                        
 
                        
 
                      
 
                      
 
                      
-
                      Parent topic: Storage
                      
+
                      Parent topic: SFS Turbo
                      
 
                      
 
                      
 
diff --git a/docs/cce/umn/cce_bestpractice_00253_0.html b/docs/cce/umn/cce_bestpractice_00253_0.html
index 58192ce19..8d5b44b0e 100644
--- a/docs/cce/umn/cce_bestpractice_00253_0.html
+++ b/docs/cce/umn/cce_bestpractice_00253_0.html
@@ -1,14 +1,14 @@
 
 
 
                      Dynamically Creating an SFS Turbo Subdirectory Using StorageClass
                      
-
                      Background
                      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, does not require such a large capacity.
                      
-
                      The everest add-on allows you to dynamically create subdirectories in an SFS Turbo file system and mount these subdirectories to containers. In this way, an SFS Turbo file system can be shared by multiple containers to increase storage efficiency.
                      
+
                      Background
                      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, does not require such a large capacity.
                      
+
                      The everest add-on allows you to dynamically create subdirectories in an SFS Turbo file system and mount these subdirectories to containers. In this way, an SFS Turbo file system can be shared by multiple containers to increase storage efficiency.
                      
 
                      
-
                      Constraints
                      • Only clusters of v1.15 or later are supported.
                      • The cluster must use the everest add-on of version 1.1.13 or later.
                      • Kata containers are not supported.
                      • When the everest add-on earlier than 1.2.69 or 2.1.11 is used, a maximum of 10 PVCs can be created concurrently at a time by using the subdirectory function. everest of 1.2.69 or later or of 2.1.11 or later is recommended.
                      • A subPath volume is a subdirectory of an SFS Turbo file system. Increasing the capacity of a PVC of this type only changes the resource range specified by the PVC, but does not change the total capacity of the SFS Turbo file system. If the SFS Turbo file system's total resource capacity is not enough, the available capacity of the subPath volume will be restricted. To fix this, you must increase the resource capacity of the SFS Turbo file system on the SFS Turbo console.
                        Deleting the subPath volume does not result in the deletion of the resources of the SFS Turbo file system.
                        
+
                        Constraints
                        • Only clusters of v1.15 or later are supported.
                        • The cluster must use the everest add-on of version 1.1.13 or later.
                        • Kata containers are not supported.
                        • When the everest add-on earlier than 1.2.69 or 2.1.11 is used, a maximum of 10 PVCs can be created concurrently at a time by using the subdirectory function. everest of 1.2.69 or later or of 2.1.11 or later is recommended.
                        • A subPath volume is a subdirectory of an SFS Turbo file system. Increasing the capacity of a PVC of this type only changes the resource range specified by the PVC, but does not change the total capacity of the SFS Turbo file system. If the SFS Turbo file system's total resource capacity is not enough, the available capacity of the subPath volume will be restricted. To fix this, you must increase the resource capacity of the SFS Turbo file system on the SFS Turbo console.
                          Deleting the subPath volume does not result in the deletion of the resources of the SFS Turbo file system.
                          
 
                        
 
                        
-
                        Creating an SFS Turbo Volume of the subPath Type
                        1. Create an SFS Turbo file system in the same VPC and subnet as the cluster.
                        2. Create a YAML file of StorageClass, for example, sfsturbo-subpath-sc.yaml.
                          The following is an example:
                          
-
                          apiVersion: storage.k8s.io/v1
+
                          Creating an SFS Turbo Volume of the subPath Type
                          1. Create an SFS Turbo file system in the same VPC and subnet as the cluster.
                          2. Create a YAML file of StorageClass, for example, sfsturbo-subpath-sc.yaml.
                            The following is an example:
                            
+
                            apiVersion: storage.k8s.io/v1
 allowVolumeExpansion: true
 kind: StorageClass
 metadata:
@@ -29,16 +29,16 @@ parameters:
 provisioner: everest-csi-provisioner
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
                            
-
                            In this example:
                            
-
                            • name: indicates the name of the StorageClass.
                            • mountOptions: indicates the mount options. This field is optional.
                              • In versions later than everest 1.1.13 and earlier than everest 1.2.8, only the nolock parameter can be configured. By default, the nolock parameter is used for the mount operation and does not need to be configured. If nolock is set to false, the lock field is used.
                              • Starting from everest 1.2.8, more mount options are supported. For details, see Configuring SFS Volume Mount Options. Do not set nolock to true. Otherwise, the mount operation will fail.
                                mountOptions:
+
                                In this example:
                                
+
                                • name: indicates the name of the StorageClass.
                                • mountOptions: indicates the mount options. This field is optional.
                                  • In versions later than everest 1.1.13 and earlier than everest 1.2.8, only the nolock parameter can be configured. By default, the nolock parameter is used for the mount operation and does not need to be configured. If nolock is set to false, the lock field is used.
                                  • Starting from everest 1.2.8, more mount options are supported. For details, see Configuring SFS Volume Mount Options. Do not set nolock to true. Otherwise, the mount operation will fail.
                                    mountOptions:
 - vers=3
 - timeo=600
 - nolock
 - hard
                                    
 
                                  
-
                                • everest.io/volume-as: This parameter is set to subpath to use the subPath volume.
                                • everest.io/share-access-to: This parameter is optional. In a subPath volume, set this parameter to the ID of the VPC where the SFS Turbo file system is located.
                                • everest.io/share-expand-type: This parameter is optional. If the type of the SFS Turbo file system is SFS Turbo Standard – Enhanced or SFS Turbo Performance – Enhanced, set this parameter to bandwidth.
                                • everest.io/share-export-location: This parameter indicates the mount directory. It consists of the SFS Turbo shared path and sub-directory. The shared path can be obtained on the SFS Turbo console. The sub-directory is user-defined. The PVCs created using the StorageClass are located in this sub-directory.
                                • everest.io/share-volume-type: This parameter is optional. It specifies the SFS Turbo file system type. The value can be STANDARD or PERFORMANCE. For enhanced types, this parameter must be used together with everest.io/share-expand-type (whose value should be bandwidth).
                                • everest.io/zone: This parameter is optional. Set it to the AZ where the SFS Turbo file system is located.
                                • everest.io/volume-id: This parameter indicates the ID of the SFS Turbo volume. You can obtain the volume ID on the SFS Turbo page.
                                • everest.io/archive-on-delete: If this parameter is set to true and Delete is selected for Reclaim Policy, the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted. If this parameter is set to false, the SFS Turbo subdirectory of the corresponding PV will be deleted. The default value is true, indicating that the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted.
                                
-
                          1. Run kubectl create -f sfsturbo-subpath-sc.yaml.
                          2. Create a PVC YAML file named sfs-turbo-test.yaml.
                            The following is an example:
                            
-
                            apiVersion: v1
+
                          3. everest.io/volume-as: This parameter is set to subpath to use the subPath volume.
                          4. everest.io/share-access-to: This parameter is optional. In a subPath volume, set this parameter to the ID of the VPC where the SFS Turbo file system is located.
                          5. everest.io/share-expand-type: This parameter is optional. If the type of the SFS Turbo file system is SFS Turbo Standard – Enhanced or SFS Turbo Performance – Enhanced, set this parameter to bandwidth.
                          6. everest.io/share-export-location: This parameter indicates the mount directory. It consists of the SFS Turbo shared path and sub-directory. The shared path can be obtained on the SFS Turbo console. The sub-directory is user-defined. The PVCs created using the StorageClass are located in this sub-directory.
                          7. everest.io/share-volume-type: This parameter is optional. It specifies the SFS Turbo file system type. The value can be STANDARD or PERFORMANCE. For enhanced types, this parameter must be used together with everest.io/share-expand-type (whose value should be bandwidth).
                          8. everest.io/zone: This parameter is optional. Set it to the AZ where the SFS Turbo file system is located.
                          9. everest.io/volume-id: This parameter indicates the ID of the SFS Turbo volume. You can obtain the volume ID on the SFS Turbo page.
                          10. everest.io/archive-on-delete: If this parameter is set to true and Delete is selected for Reclaim Policy, the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted. If this parameter is set to false, the SFS Turbo subdirectory of the corresponding PV will be deleted. The default value is true, indicating that the original documents of the PV will be archived to the directory named archived-{$PV name.timestamp} before the PVC is deleted.
                      
+
                    1. Run kubectl create -f sfsturbo-subpath-sc.yaml.
                    2. Create a PVC YAML file named sfs-turbo-test.yaml.
                      The following is an example:
                      
+
                      apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
   name: sfs-turbo-test
@@ -51,13 +51,13 @@ spec:
       storage: 50Gi
   storageClassName: sfsturbo-subpath-sc
   volumeMode: Filesystem
                      
-
                      In this example:
                      
-
                      • name: indicates the name of the PVC.
                      • storageClassName: specifies the name of the StorageClass.
                      • storage: In a subPath volume, modifying the value of this parameter does not impact the resource capacity of the SFS Turbo file system. A subPath volume is essentially a file path within an SFS Turbo file system. As a result, increasing the capacity of the subPath volume in a PVC does not lead to an increase in the resources of the SFS Turbo file system.
                         
                        The capacity of a subPath volume is restricted by the overall resource capacity of the corresponding SFS Turbo file system. If the resources of the SFS Turbo file system are inadequate, you can adjust the resource capacity via the SFS Turbo console.
                        
+
                        In this example:
                        
+
                        • name: indicates the name of the PVC.
                        • storageClassName: specifies the name of the StorageClass.
                        • storage: In a subPath volume, modifying the value of this parameter does not impact the resource capacity of the SFS Turbo file system. A subPath volume is essentially a file path within an SFS Turbo file system. As a result, increasing the capacity of the subPath volume in a PVC does not lead to an increase in the resources of the SFS Turbo file system.
                           
                          The capacity of a subPath volume is restricted by the overall resource capacity of the corresponding SFS Turbo file system. If the resources of the SFS Turbo file system are inadequate, you can adjust the resource capacity via the SFS Turbo console.
                          
 
                          
 
                        
-
                    1. Run kubectl create -f sfs-turbo-test.yaml.
                    
+
                    1. Run kubectl create -f sfs-turbo-test.yaml.
                    
 
                    
-
                    Creating a Deployment and Mounting an Existing Volume
                    1. Create a YAML file for the Deployment, for example, deployment-test.yaml.
                      The following is an example:
                      apiVersion: apps/v1
+
                      Creating a Deployment and Mounting an Existing Volume
                      1. Create a YAML file for the Deployment, for example, deployment-test.yaml.
                        The following is an example:
                        apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: test-turbo-subpath-example
@@ -89,13 +89,13 @@ spec:
         persistentVolumeClaim: 
           claimName: sfs-turbo-test
                        
 
                        
-
                        In this example:
                        
-
                        • name: indicates the name of the created workload.
                        • image: specifies the image used by the workload.
                        • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                        • claimName: indicates the name of an existing PVC.
                        
-
                      1. Create the Deployment.
                        kubectl create -f deployment-test.yaml
                        
+
                        In this example:
                        
+
                        • name: indicates the name of the created workload.
                        • image: specifies the image used by the workload.
                        • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                        • claimName: indicates the name of an existing PVC.
                        
+
                      1. Create the Deployment.
                        kubectl create -f deployment-test.yaml
                        
 
                      
 
                      
-
                      Dynamically Creating a subPath Volume for a StatefulSet
                      1. Create a YAML file for a StatefulSet, for example, statefulset-test.yaml.
                        The following is an example:
                        
-
                        apiVersion: apps/v1
+
                        Dynamically Creating a subPath Volume for a StatefulSet
                        1. Create a YAML file for a StatefulSet, for example, statefulset-test.yaml.
                          The following is an example:
                          
+
                          apiVersion: apps/v1
 kind: StatefulSet
 metadata:
   name: test-turbo-subpath
@@ -151,15 +151,15 @@ spec:
   updateStrategy:
     type: RollingUpdate
   revisionHistoryLimit: 10
                          
-
                          In this example:
                          
-
                          • name: indicates the name of the created workload.
                          • image: specifies the image used by the workload.
                          • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                          • spec.template.spec.containers.volumeMounts.name and spec.volumeClaimTemplates.metadata.name: must be consistent because they have a mapping relationship.
                          • storageClassName: specifies the name of an on-premises StorageClass.
                          
-
                        1. Create the StatefulSet.
                          kubectl create -f statefulset-test.yaml
                          
+
                          In this example:
                          
+
                          • name: indicates the name of the created workload.
                          • image: specifies the image used by the workload.
                          • mountPath: indicates the mount path of the container. In this example, the volume is mounted to the /tmp directory.
                          • spec.template.spec.containers.volumeMounts.name and spec.volumeClaimTemplates.metadata.name: must be consistent because they have a mapping relationship.
                          • storageClassName: specifies the name of an on-premises StorageClass.
                          
+
                        1. Create the StatefulSet.
                          kubectl create -f statefulset-test.yaml
                          
 
                        
 
                        
 
                      
 
                      
 
                      
-
                      Parent topic: SFS Turbo
                      
+
                      Parent topic: Storage
                      
 
                      
 
                      
 
diff --git a/docs/cce/umn/cce_bestpractice_00281.html b/docs/cce/umn/cce_bestpractice_00281.html
index fc4a36ce5..7c9647e9f 100644
--- a/docs/cce/umn/cce_bestpractice_00281.html
+++ b/docs/cce/umn/cce_bestpractice_00281.html
@@ -42,6 +42,7 @@ NAME                PROVISIONER                     AGE
 csi-disk            everest-csi-provisioner         17d          # EVS disk
 csi-disk-topology   everest-csi-provisioner         17d          # EVS disks created with delay
 csi-nas             everest-csi-provisioner         17d          # SFS 1.0
+csi-sfs             everest-csi-provisioner         17d          # SFS 3.0
 csi-obs             everest-csi-provisioner         17d          # OBS
 csi-sfsturbo        everest-csi-provisioner         17d          # SFS Turbo
                      
 
                      Each StorageClass contains the default parameters used for dynamically creating a PV. The following is an example of StorageClass for EVS disks:
                      kind: StorageClass
diff --git a/docs/cce/umn/cce_bestpractice_0050.html b/docs/cce/umn/cce_bestpractice_0050.html
index f57946ad9..7dec0cdbc 100644
--- a/docs/cce/umn/cce_bestpractice_0050.html
+++ b/docs/cce/umn/cce_bestpractice_0050.html
@@ -9,7 +9,7 @@
 
                      2. 
 
                    2. Creating an IPv4/IPv6 Dual-Stack Cluster in CCE
                      
 
                      3. 
-
                    3. Executing the Pre- or Post-installation Commands During Node Creation
                      
+
                    4. Executing the Pre- or Post-installation Commands During Node Creation
                      
 
                      5. 
 
                    5. Connecting to Multiple Clusters Using kubectl
                      
 
                      6. 
diff --git a/docs/cce/umn/cce_bestpractice_0053.html b/docs/cce/umn/cce_bestpractice_0053.html
index 3a2f673c4..3575cb33e 100644
--- a/docs/cce/umn/cce_bestpractice_0053.html
+++ b/docs/cce/umn/cce_bestpractice_0053.html
@@ -8,7 +8,7 @@
 
 
                    6. Mounting Object Storage Across Accounts
                      
 
                      7. 
-
                    7. Dynamically Creating an SFS Turbo Subdirectory Using StorageClass
                      
+
                    8. Dynamically Creating an SFS Turbo Subdirectory Using StorageClass
                      
 
                      9. 
 
                    9. Changing the Storage Class Used by a Cluster of v1.15 from FlexVolume to CSI Everest
                      
 
                      10. 
diff --git a/docs/cce/umn/cce_bestpractice_0333.html b/docs/cce/umn/cce_bestpractice_0333.html
index f56c6deb3..b38e189c1 100644
--- a/docs/cce/umn/cce_bestpractice_0333.html
+++ b/docs/cce/umn/cce_bestpractice_0333.html
@@ -3,26 +3,29 @@
 
                      Configuration Suggestions on CCE Workload Identity Security
                      
 
                      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.
                      
 
                      This section describes how to use workload identities in CCE.
                      
-
                      Notes and Constraints
                      The cluster version must be 1.19.16 or later.
                      
+
                      Notes and Constraints
                      The cluster version must be v1.19.16 or later.
                      
 
                      
-
                      Procedure
                      1. Obtain the public key of the cluster serviceAccountToken from CCE. For details, see Step 1: Obtain the Public Key for Signature of the CCE Cluster.
                      2. Create an identity provider on IAM. For details, see Step 2: Configure an Identity Provider.
                      3. Obtain an IAM token from the workload to simulate an IAM user to access a cloud service. For details, see Step 3: Use a Workload Identity.
                        The procedure is as follows:
                        1. Deploy the application pod and obtain the OpenID Connect ID token file by mounting the identity provider.
                        2. Use the mounted OpenID Connect ID token file in programs in the pod to access IAM and obtain a temporary IAM token.
                        3. Access the cloud service using the IAM token in programs in the pod.
                        
+
                        Procedure
                        1. Obtain the public key of the cluster serviceAccountToken from CCE. For details, see Step 1: Obtain the Public Key for Signature of the CCE Cluster.
                        2. Create an identity provider on IAM. For details, see Step 2: Configure an Identity Provider.
                        3. Obtain an IAM token from the workload and simulate an IAM user to access a cloud service. For details, see Step 3: Use a Workload Identity.
                          The procedure is as follows:
                          1. Deploy the application pod and obtain the OpenID Connect ID token file by mounting the identity provider.
                          2. Use the mounted OpenID Connect ID token file in programs in the pod to access IAM and obtain a temporary IAM token.
                          3. Access the cloud service using the IAM token in programs in the pod.
                          
 
                          Figure 1 Workflow
                          
 
                          
 
                        
 
                        
-
                        Step 1: Obtain the Public Key for Signature of the CCE Cluster
                        1. Use kubectl to access the target cluster.
                        2. Obtain the public key:
                          kubectl get --raw /openid/v1/jwks
                          
+
                          Step 1: Obtain the Public Key for Signature of the CCE Cluster
                          1. Use kubectl to access the target cluster.
                          2. Obtain the public key:
                            kubectl get --raw /openid/v1/jwks
                            
+
                            The returned result is the public key of the cluster. The following is an example of the command output:
                            
 
                            # kubectl get --raw /openid/v1/jwks
 {"keys":[{"use":"sig","kty":"RSA","kid":"*****","alg":"RS256","n":"*****","e":"AQAB"}]}
                            
-
                            The returned field is the public key of the cluster.
                            
 
                          
 
                          
 
                          Step 2: Configure an Identity Provider
                          1. Log in to the IAM console, choose Identity Providers in the navigation pane, and click Create Identity Provider in the upper right corner. On the displayed page, set Protocol to OpenID Connect and SSO Type to Virtual user and click OK.
                          2. In the identity provider list, locate the row containing the new identity provider and click Modify in the Operation column to modify the identity provider information.
                            Access Type: Select Programmatic access.
                            
 
                            Configuration Information
                            
-
+
                            • Identity Provider URL: Enter https://kubernetes.default.svc.cluster.local.
                            • Client ID: Enter an ID, which will be used when you create a container.
                               
                              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 "123456789" in the YAML file.
                              
+
                              
+
                            • Signing Key: Enter the JWKS of the CCE cluster obtained in Step 1: Obtain the Public Key for Signature of the CCE Cluster.
                            
 
                            Identity Conversion Rules
                            
-
                            An identity conversion rule maps the ServiceAccount of a workload to IAM user.
                            
-
                            For example, create a ServiceAccount named oidc-token in namespace default of the cluster and map it to user group demo. If you use the identity provider ID to access cloud services, you have the permissions of the demo user group. The attribute must be sub. The value format is system:serviceaccount:Namespace:ServiceAccountName.
                            
-
                            
+
                            An identity conversion rule maps the ServiceAccount of a workload to an IAM user.
                            
+
                            For example, create a ServiceAccount named oidc-token in namespace default of the cluster and map it to user group demo. If you use the identity provider ID to access cloud services, you have the permissions of the demo user group. The attribute must be sub. The value is in the format of system:serviceaccount:Namespace:ServiceAccountName.
                            
+
                            
+
 
                            Rules are in the JSON format as follows:
                            
 
                            [
     {
@@ -91,13 +94,13 @@ spec:
 
                          
 
                        3. After the creation is complete, log in to the container. The content of the /var/run/secrets/tokens/oidc-token file is the serviceAccountToken generated by Kubernetes.
                           
                          If the serviceAccountToken is used for more than 24 hours or 80% of its expiry period, kubelet will automatically rotate the serviceAccountToken.
                          
 
                          
-
                        4. Use the OpenID Connect ID token to call the API for Obtaining a Token with an OpenID Connect ID Token. The X-Subject-Token field in the response header is the IAM token. Then, you can use this token to access cloud services.
                          The following shows an example:
                          
+
                        5. Use the OpenID Connect ID token to call the API for Obtaining a Token with an OpenID Connect ID Token. The X-Subject-Token field in the response header is the IAM token. Then, you can use this token to access cloud services.
                          The following shows an example:
                          
 
                          curl -i --location --request POST 'https://{{iam endpoint}}/v3.0/OS-AUTH/id-token/tokens' \
  --header 'X-Idp-Id: workload_identity' \
  --header 'Content-Type: application/json' \
  --data @token_body.json
                          
 
                          Specifically:
                          
-
                          • {{iam endpoint}} indicates the endpoint of IAM. For details, see Regions and Endpoints.
                          • workload_identity is the identity provider name, which is the same as that configured in Step 2: Configure an Identity Provider.
                          • token_body.json is a local file and its content is as follows:
                             { 
+
                            • {{iam endpoint}} indicates the endpoint of IAM. For details, see Regions and Endpoints.
                            • workload_identity is the identity provider name, which is the same as that configured in Step 2: Configure an Identity Provider.
                            • token_body.json is a local file and its content is as follows:
                               { 
    "auth" : { 
      "id_token" : { 
        "id" : "eyJhbGciOiJSU..."
@@ -110,7 +113,7 @@ spec:
      } 
    } 
  }
                              
-
                              • $.auth.id_token.id: The value is the content of the /var/run/secrets/tokens/oidc-token file in the container.
                              • $.auth.scope.project.id: indicates the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
                              • $.auth.scope.project.name: indicates the project name.
                              
+
                              • $.auth.id_token.id: The value is the content of the /var/run/secrets/tokens/oidc-token file in the container.
                              • $.auth.scope.project.id: indicates the project ID. To obtain the value, see Obtaining a Project ID.
                              • $.auth.scope.project.name: indicates the project name.
                              
 
                            
 
                        
 
                        
diff --git a/docs/cce/umn/cce_bestpractice_10008.html b/docs/cce/umn/cce_bestpractice_10008.html
index 6d46ca708..e062b6bd1 100644
--- a/docs/cce/umn/cce_bestpractice_10008.html
+++ b/docs/cce/umn/cce_bestpractice_10008.html
@@ -7,6 +7,8 @@
 
 
 
                        
diff --git a/docs/cce/umn/cce_bestpractice_10017.html b/docs/cce/umn/cce_bestpractice_10017.html
index 6e0ea15ce..c3e9b3fcc 100644
--- a/docs/cce/umn/cce_bestpractice_10017.html
+++ b/docs/cce/umn/cce_bestpractice_10017.html
@@ -11,9 +11,9 @@
 
 
                    
 
                    Master node
                    
+
                    Cluster management plane
                    
 
                    CCE is a hosted Kubernetes cluster service. You do not need to perform O&M on the master nodes. You can configure your cluster specifications to improve the stability and reliability.
                    
+
                    CCE is a hosted Kubernetes cluster service. You do not need to perform O&M on the management plane (master nodes). You can use some settings to improve the stability and reliability of your cluster.
                    
                     		
 
 
 
 
                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                    Kubernetes Version
                    
-
                    Status
                    
-
                    Community Release In
                    
-
                    Commercial Use of CCE Clusters
                    
-
                    EOS of CCE Clusters
                    
-
                    v1.30
                    
-
                    In commercial usea
                    
-
                    April 2024
                    
-
                    October 2024
                    
-
                    October 2026
                    
-
                    v1.29
                    
-
                    In commercial usea
                    
-
                    November 2023
                    
-
                    June 2024
                    
-
                    June 2026
                    
-
                    v1.28
                    
-
                    In commercial useb
                    
-
                    August 2023
                    
-
                    February 2024
                    
-
                    February 2026
                    
-
                    v1.27
                    
-
                    In commercial useb
                    
-
                    April 2023
                    
-
                    October 2023
                    
-
                    October 2025
                    
-
                    v1.25
                    
-
                    In commercial useb
                    
-
                    August 2022
                    
-
                    March 2023
                    
-
                    March 2025
                    
-
                    v1.23
                    
-
                    In commercial useb
                    
-
                    December 2021
                    
-
                    September 2022
                    
-
                    September 2024
                    
-
                    v1.21
                    
-
                    End of service (EOS)
                    
-
                    April 2021
                    
-
                    April 2022
                    
-
                    April 2024
                    
-
                    v1.19
                    
-
                    EOS
                    
-
                    August 2020
                    
-
                    March 2021
                    
-
                    September 2023
                    
-
                    v1.17
                    
-
                    EOS
                    
-
                    December 2019
                    
-
                    July 2020
                    
-
                    January 2023
                    
-
                    v1.15
                    
-
                    EOS
                    
-
                    June 2019
                    
-
                    December 2019
                    
-
                    September 2022
                    
-
                    v1.13
                    
-
                    EOS
                    
-
                    December 2018
                    
-
                    June 2019
                    
-
                    March 2022
                    
-
                    v1.11
                    
-
                    EOS
                    
-
                    August 2018
                    
-
                    October 2018
                    
-
                    March 2021
                    
-
                    v1.9
                    
-
                    EOS
                    
-
                    December 2017
                    
-
                    March 2018
                    
-
                    December 2020
                    
-
                    
-
                    
-
                     
                    The CCE console supports clusters of the latest two commercially used versions:
                    
-
                    • a: Clusters created using the console or APIs
                    • b: Clusters created only using APIs
                    
-
                    
-
-
                    Phases of CCE Cluster Versions
                    • In commercial use: The cluster version has been fully verified and is stable and reliable. You can use clusters of this version in the production environment, and the CCE SLA is valid for such clusters.
                    • EOS: After the cluster version EOS, CCE does not support the creation of new clusters or provide technical support including new feature updates, vulnerability or issue fixes, new patches, work order guidance, and online checks for the EOS cluster version. The CCE SLA is not valid for such clusters.
                    
-
                    
-
                    CCE Cluster Versions
                    CCE clusters are updated according to the versions available in the Kubernetes community. This means that a CCE cluster version is made up of both the Kubernetes community version number and the CCE patch version number. The CCE cluster version is in the format for vX.Y.Z-rN, such as v1.30.4-r0.
                    
-
                    • A Kubernetes version is in the format of X.Y.Z, which inherits the community version policy. The major Kubernetes version is represented by X, the minor Kubernetes version is represented by Y, and the Kubernetes patch version is represented by Z. For details, see the Kubernetes version policies. For details about the Kubernetes versions supported by CCE, see Kubernetes Version Release Notes.
                    • A CCE patch version is in the format of, for example, v1.30.4-rN. New patches are released on an irregular basis for Kubernetes versions that are still in the maintenance period. If a new patch version provides new features, bug fixes, vulnerability fixes, or scenario optimizations compared with the previous version, the N version number increases. For details about the patch versions, see Patch Versions.
                    
-
                    
-
                    Cluster Upgrade
                    Periodically upgrade CCE clusters for better user experience. Using an EOS version, you cannot obtain technical support and CCE SLA assurance. Upgrade CCE clusters in a timely manner.
                    
-
                    On the CCE console, you can easily upgrade clusters in a visualized manner, improving the stability and reliability of clusters. For details, see Upgrade Overview.
                    
-
                    
-
-
                    
-
                    
-
                    Parent topic: Product Bulletin
                    
-
                    
-
                    
-
diff --git a/docs/cce/umn/cce_bulletin_0058.html b/docs/cce/umn/cce_bulletin_0058.html
index c1228642d..08803838f 100644
--- a/docs/cce/umn/cce_bulletin_0058.html
+++ b/docs/cce/umn/cce_bulletin_0058.html
@@ -5,7 +5,7 @@
 
                    Indexes
                    
 
                    
 
                    New Features
                    Kubernetes 1.25
                    • Pod Security Admission is stable. PodSecurityPolicy is deprecated.
                      PodSecurityPolicy is replaced by Pod Security Admission. For details about the migration, see Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller.
                      
-
                    • The ephemeral container is stable.
                      An ephemeral container is a container that runs temporarily in an existing pod. It is useful for troubleshooting, especially when kubectl exec cannot be used to check a container that breaks down or its image lacks a debugging tool.
                      
+
                    • The ephemeral containers are stable.
                      An ephemeral container runs temporarily in an existing pod. It is useful for troubleshooting, especially when kubectl exec cannot be used to check a container that breaks down or its image lacks a debugging tool.
                      
 
                    • Support for cgroups v2 enters the stable phase.
                      Kubernetes supports cgroups v2. cgroups v2 provides some improvements over cgroup v1. For details, see About cgroup v2.
                      
 
                    • SeccompDefault moves to beta.
                      To enable this feature, add the startup parameter --seccomp-default=true to kubelet. In this way, seccomp is set to RuntimeDefault by default, improving system security. Clusters of v1.25 no longer support seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io/annotation. Replace them with the securityContext.seccompProfile field in pods or containers. For details, see Configure a Security Context for a Pod or Container.
                       
                      After this feature is enabled, the system calls required by the application may be restricted by the runtime. Ensure that the debugging is performed in the test environment, so that application is not affected.
                      
 
                      
@@ -24,7 +24,7 @@
 
                    
 
                  14. Beta APIs are disabled by default.
                    The Kubernetes community found 90% cluster administrators did not care about the beta APIs and left them enabled. However, the beta features are not recommended because these APIs enabled in the production environment by default incur risks. Therefore, in 1.24 and later versions, beta APIs are disabled by default, but the existing beta APIs will retain the original settings.
                    
 
                  15. OpenAPI v3 is supported.
                    In Kubernetes 1.24 and later versions, OpenAPI V3 is enabled by default.
                    
-
                  16. Storage capacity tracking is stable.
                    In Kubernetes 1.24 and later versions, the CSIStorageCapacity API supports exposing the available storage capacity. This ensures that pods are scheduled to nodes with sufficient storage capacity, which reduces pod scheduling delay caused by volume creation and mounting failures. For details, see Storage Capacity.
                    
+
                  17. Storage capacity tracking is stable.
                    In Kubernetes 1.24 and later versions, the CSIStorageCapacity API supports exposing the available storage capacity. This ensures that pods are scheduled to nodes with enough storage capacity, which reduces pod scheduling delay caused by volume creation and mounting failures. For details, see Storage Capacity.
                    
 
                  18. gRPC container probe moves to beta.
                    In Kubernetes 1.24 and later versions, the gRPC probe goes to beta. The feature gate GRPCContainerProbe is available by default. For details about how to use this probe, see Configure Probes.
                    
 
                  19. LegacyServiceAccountTokenNoAutoGeneration is enabled by default.
                    LegacyServiceAccountTokenNoAutoGeneration moves to beta. By default, this feature is enabled, where no secret token is automatically generated for a service account. To use a token that never expires, create a secret to hold the token. For details, see Service account token Secrets.
                    
 
                  20. IP address conflict is prevented.
                    In Kubernetes 1.24, an IP address pool is soft reserved for the static IP addresses of Services. After you manually enable this function, Service IP addresses will be automatically from the IP address pool to minimize IP address conflict.
                    
diff --git a/docs/cce/umn/cce_bulletin_0059.html b/docs/cce/umn/cce_bulletin_0059.html
index 9e75fa0e7..dc5e3c0a8 100644
--- a/docs/cce/umn/cce_bulletin_0059.html
+++ b/docs/cce/umn/cce_bulletin_0059.html
@@ -1,7 +1,7 @@
 
 
 
                    Kubernetes 1.27 Release Notes
                    
-
                    CCE allows you to create clusters of Kubernetes 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.
                    
+
                    CCE allows you to create Kubernetes clusters 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.
                    
 
                    Indexes
                    
 
                    
 
                    New Features
                    Kubernetes 1.27
                    • SeccompDefault is stable.
                      To use SeccompDefault, add the --seccomp-default command line flag using kubelet on each node. If this feature is enabled, the RuntimeDefault profile will be used for all workloads by default, instead of the Unconfined (seccomp disabled) profile.
                      
diff --git a/docs/cce/umn/cce_bulletin_0089.html b/docs/cce/umn/cce_bulletin_0089.html
index 6879a7887..9526fa8d9 100644
--- a/docs/cce/umn/cce_bulletin_0089.html
+++ b/docs/cce/umn/cce_bulletin_0089.html
@@ -20,7 +20,7 @@
 
                    • The legacy ServiceAccount token cleaner is in the beta state.
                      Legacy ServiceAccount token cleaner is promoted to beta. It runs as part of kube-controller-manager and checks every 24 hours to see if any auto-generated legacy ServiceAccount token has not been used in a specific amount of time (one year by default, specified by --legacy-service-account-token-clean-up-period). If so, the cleaner marks those tokens as invalid and adds the kubernetes.io/legacy-token-invalid-since label whose value is the current date. If an invalid token is not used for a specific period of time (one year by default, specified by --legacy-service-account-token-clean-up-period), the cleaner deletes it. For details, see Legacy ServiceAccount token cleaner.
                      
 
                    • DevicePluginCDIDevices is in the beta state.
                      DevicePluginCDIDevices moves to beta. With this feature enabled, plugin developers can use the CDIDevices field added to DeviceRunContainerOptions to pass CDI device names directly to CDI enabled runtimes.
                      
 
                    • PodHostIPs is in the beta state.
                      The PodHostIPs feature moves to beta. With this feature enabled, Kubernetes adds the hostIPs field to Status of pods and downward API to expose node IP addresses to workloads. This field specifies the dual-stack protocol version of the host IP address. The first IP address is always the same as the host IP address.
                      
-
                    • The API Priority and Fairness feature (APF) is in the GA state.
                      APF moves to GA. APF classifies and isolates requests in a more fine-grained way. It improves max-inflight limitations. It also introduces a limited amount of queuing, so that the API server does not reject any request in cases of very brief bursts. Requests are dispatched from queues using a fair queuing technique so that, for example, a poorly-behaved controller does not cause others (even at the same priority level) to become abnormal. For details, see API Priority and Fairness.
                      
+
                    • The API Priority and Fairness (APF) feature is in the GA state.
                      APF moves to GA. APF classifies and isolates requests in a more fine-grained way. It improves max-inflight limitations. It also introduces a limited amount of queuing, so that the API server does not reject any request in cases of very brief bursts. Requests are dispatched from queues using a fair queuing technique so that, for example, a poorly-behaved controller does not cause others (even at the same priority level) to become abnormal. For details, see API Priority and Fairness.
                      
 
                    • APIListChunking is in the GA state.
                      The APIListChunking feature moves to GA. This feature allows clients to perform pagination in List requests to avoid performance problems caused by returning too much data at a time.
                      
 
                    • ServiceNodePortStaticSubrange is in the GA state.
                      The ServiceNodePortStaticSubrange feature moves to GA. With this feature enabled, kubelet calculates the size of reserved IP addresses based on the ranges of the NodePort Services and divides node ports into static band and dynamic band. During automatic node port assignment, dynamic band is preferentially assigned, which helps avoid port conflicts during static band assignment. For details, see ServiceNodePortStaticSubrange.
                      
 
                    • The phase transition timestamp of PersistentVolume (PV) is in the beta state.
                      The PV phase transition timestamp moves to beta. With this feature enabled, Kubernetes adds the lastPhaseTransitionTime field to the status field of a PV to indicate the time when the PV phase changes last time. Cluster administrators are now able to track the last time a PV transitioned to a different phase, allowing for more efficient and informed resource management. For details, see PersistentVolume Last Phase Transition Time in Kubernetes.
                      
diff --git a/docs/cce/umn/cce_bulletin_0095.html b/docs/cce/umn/cce_bulletin_0095.html
index c9ed28e05..9f50a9ccd 100644
--- a/docs/cce/umn/cce_bulletin_0095.html
+++ b/docs/cce/umn/cce_bulletin_0095.html
@@ -12,7 +12,7 @@
 
                    • The minimum domain in the pod topology spread is in the GA state.
                      The minimum domain feature in pod topology spread is advanced to GA. This feature allows you to configure a minimum number of domains that meet specific conditions by using the minDomains field in the pod configuration. If the number of domains that match the load topology constraints exceeds the minDomains value, this field will not affect the settings. However, if the number of domains that match the load topology constraints is less than the minDomains value, the global minimum value is set to 0, which represents the minimum number of matched pods in domains that meet the conditions. To prevent pods from being scheduled when topology constraints are not met, this field must be used together with whenUnsatisfiable: DoNotSchedule. For details, see Spread constraint definition.
                      
 
                    
 
                    
-
                    API Changes and Removals
                    • kubectl removes the prune-whitelist parameter of the apply command and replaces it with prune-allowlist.
                    • SecurityContextDeny, which has been deprecated in Kubernetes 1.27, is replaced by Pod Security admission.
                    
+
                    API Changes and Removals
                    • kubectl removes the prune-whitelist parameter of the apply command and replaces it with prune-allowlist.
                    • SecurityContextDeny, which has been deprecated in Kubernetes 1.27, is replaced by Pod Security admission controller.
                    
 
                    
 
                    Enhanced Kubernetes 1.30 on CCE
                    During a version maintenance period, CCE periodically updates Kubernetes 1.30 and provides enhanced functions.
                    
 
                    For details about cluster version updates, see Patch Versions.
                    
diff --git a/docs/cce/umn/cce_faq_00204.html b/docs/cce/umn/cce_faq_00204.html
index 0a7f0537a..6a5430188 100644
--- a/docs/cce/umn/cce_faq_00204.html
+++ b/docs/cce/umn/cce_faq_00204.html
@@ -2,7 +2,7 @@
 
 
                    What Should I Do If a Container Fails to Access the Internet?
                    
 
                    If a container cannot access the Internet, check whether the node where the container is located can access the Internet. Then check whether the network configuration of the container is correct. For example, check whether the DNS configuration can resolve the domain name.
                    
-
                    Check Item 1: Whether the Node Can Access the Internet
                    1. Log in to the ECS console.
                    2. Check whether an EIP has been bound to the ECS (node) or whether the ECS has a NAT gateway configured.
                      The following figure shows that an EIP has been bound. If no EIP is displayed, bind an EIP to the ECS.
                      
+
                      Check Item 1: Whether the Node Can Access the Internet
                      1. Log in to the ECS console.
                      2. Check whether an EIP has been bound to the ECS (node) or whether the ECS has a NAT gateway configured.
                        The following figure shows that an EIP has been bound to an ECS. If no EIP is displayed, bind an EIP to the ECS.
                        
 
                        Figure 1 Node with an EIP bound
                        
 
                      
 
                      
diff --git a/docs/cce/umn/cce_faq_00265.html b/docs/cce/umn/cce_faq_00265.html
index 6923490b8..523704474 100644
--- a/docs/cce/umn/cce_faq_00265.html
+++ b/docs/cce/umn/cce_faq_00265.html
@@ -166,9 +166,9 @@
 
 
                    21. Allow kube-apiserver of the master nodes to listen to the worker nodes.
                    
 
                    Recommended
                    
+
                    Recommended
                    
 
                    The port must allow traffic from the CIDR blocks of the VPC, the control plane of the hosted service mesh, and container.
                    
+
                    The port must allow traffic from the CIDR blocks of the VPC, the management plane of the hosted service mesh, and container.
                    
                     		
 
                    
 
                    TCP port 8445
                    
@@ -271,7 +271,7 @@
                     		
 
                    Allow SSH access to Linux ECSs.
                    
 
                    Recommended
                    
+
                    Recommended
                    
                     		
 
                    N/A
                    
                     		
 
                    Allow kube-apiserver of the master nodes to listen to the worker nodes.
                    
 
                    Recommended
                    
+
                    Recommended
                    
 
                    The port must allow traffic from the CIDR blocks of the VPC, the control plane of the hosted service mesh, and container.
                    
+
                    The port must allow traffic from the CIDR blocks of the VPC, the management plane of the hosted service mesh, and container.
                    
                     		
 
                    
 
                    TCP port 8445
                    
@@ -460,7 +460,7 @@
                     		
 
                    Allow SSH access to Linux ECSs.
                    
 
                    Recommended
                    
+
                    Recommended
                    
                     		
 
                    N/A
                    
                     		
 
                    Allow kube-apiserver of the master nodes to listen to the worker nodes.
                    
 
                    Recommended
                    
+
                    Recommended
                    
 
                    The port must allow traffic from the CIDR blocks of the VPC, the control plane of the hosted service mesh, and container.
                    
+
                    The port must allow traffic from the CIDR blocks of the VPC, the management plane of the hosted service mesh, and container.
                    
                     		
 
                    
 
                    TCP port 8445
                    
diff --git a/docs/cce/umn/cce_faq_00417.html b/docs/cce/umn/cce_faq_00417.html
index 173ed57c7..3ba33680c 100644
--- a/docs/cce/umn/cce_faq_00417.html
+++ b/docs/cce/umn/cce_faq_00417.html
@@ -3,7 +3,7 @@
 
                    How Do I Configure an Access Policy for a Cluster?
                    
 
                    After the public API Server address is bound to the cluster, modify the security group rules of port 5443 on the master node to harden the access control policy of the cluster.
                    
 
                    1. Log in to the CCE console and click the cluster name to access the cluster console. On the Overview page, copy the cluster ID in the Basic Info area.
                    2. Log in to the VPC console. In the navigation pane, choose Access Control > Security Groups.
                    3. Select Description as the filter criterion and paste the cluster ID to search for the target security group.
                    4. Locate the row that contains the security group (starting with {CCE cluster name}-cce-control) of the master node and click Manage Rules in the Operation column.
                    5. On the page displayed, locate the row that contains port 5443 and click Modify in the Operation column to modify its inbound rules.
                      
-
                    6. Change the source IP address that can be accessed as required. For example, if the IP address used by the client to access the API Server is 100.*.*.*, you can add an inbound rule for port 5443 and set the source IP address to 100.*.*.*.
                       
                      In addition to the client IP address, the port must allow traffic from the CIDR blocks of the VPC, container, and the control plane of the hosted service mesh to ensure that the API Server can be accessed from within the cluster.
                      
+
                    7. Change the source IP address that can be accessed as required. For example, if the IP address used by the client to access the API Server is 100.*.*.*, you can add an inbound rule for port 5443 and set the source IP address to 100.*.*.*.
                       
                      In addition to the client IP address, the port must allow traffic from the CIDR blocks of the VPC, container, and the management plane of the hosted service mesh to ensure that the API Server can be accessed from within the cluster.
                      
 
                      
 
                      
 
                    8. Click Confirm.
                    
diff --git a/docs/cce/umn/cce_productdesc_0001.html b/docs/cce/umn/cce_productdesc_0001.html
index 5d07494f7..7c0dbae5a 100644
--- a/docs/cce/umn/cce_productdesc_0001.html
+++ b/docs/cce/umn/cce_productdesc_0001.html
@@ -1,7 +1,7 @@
 
 
 
                    What Is CCE?
                    
-
                    Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the enter lifecycle of containerized applications and delivers scalable, high-performance solutions for deploying and managing cloud native applications.
                    
+
                    Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the entire lifecycle of containerized applications and delivers scalable, high-performance solutions for deploying and managing cloud native applications.
                    
 
                    Why CCE?
                    CCE is a one-stop platform integrating compute (ECS), networking (VPC, EIP, and ELB), storage (EVS, OBS, and SFS), and many other services. Multi-AZ, multi-region disaster recovery (DR) ensures high availability (HA) of Kubernetes clusters.
                    
 
                    For more information, see Product Advantages and Application Scenarios.
                    
 
                    
@@ -35,7 +35,10 @@
 
                    For users who have higher requirements on performance, resource utilization, and full-scenario coverage
                    
                     		
 
                    Specification difference
                    
+
                    Specification difference
                    
+
                    
+
                    
+
                    
                     		
 
                    Network model
                    
 
                    • VM-level isolation is supported for secure containers that run only on physical machines.
                    • cgroups are used to isolate common containers.
                    
                     		
 
                    Edge infrastructure management
                    
-
                    Not supported
                    
-
                    Management of CloudPond edge sites
                    
-
                    
 
 
                    
 
                    
diff --git a/docs/cce/umn/cce_productdesc_0003.html b/docs/cce/umn/cce_productdesc_0003.html
index 90dd65f91..0c43c32ee 100644
--- a/docs/cce/umn/cce_productdesc_0003.html
+++ b/docs/cce/umn/cce_productdesc_0003.html
@@ -7,7 +7,7 @@
 
                    High Performance
                    
 
                    • 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.
                    • AI computing is 3x to 5x better with NUMA BMSs and high-speed InfiniBand network cards.
                    
 
                    Highly Available and Secure
                    
-