Update content

umn/source/add-ons/autoscaler.rst

@@ -121,7 +121,7 @@ Installing the Add-on
       +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
       | Total Nodes                       | Maximum number of nodes that can be managed by the cluster, within which cluster scale-out is performed.                                                                                                                                                                                                                                                               |
       +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-      | Total Cores                       | Maximum sum of CPU cores of all nodes in a cluster, within which cluster scale-out is performed.                                                                                                                                                                                                                                                                       |
+      | Total CPUs                        | Maximum sum of CPU cores of all nodes in a cluster, within which cluster scale-out is performed.                                                                                                                                                                                                                                                                       |
       +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
       | Total Memory (GB)                 | Maximum sum of memory of all nodes in a cluster, within which cluster scale-out is performed.                                                                                                                                                                                                                                                                          |
       +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

umn/source/add-ons/everest_system_resource_add-on_mandatory.rst

@@ -26,7 +26,7 @@ This add-on has been installed by default. If it is uninstalled due to some reas
 
 #. Log in to the CCE console and access the cluster console. Choose **Add-ons** in the navigation pane, locate **everest** on the right, and click **Install**.
 
-#. Select **Single**, **Custom**, or **HA** for **Add-on Specifications**.
+#. Select **Standalone**, **HA**, or **Custom** for **Add-on Specifications**.
 
    The everest add-on contains the following containers. You can adjust the specifications as required.
 

umn/source/add-ons/gpu-beta.rst

@@ -26,7 +26,7 @@ Installing the Add-on
 
    .. important::
 
-      -  If the download link is a public network address, for example, **https://us.download.nvidia.com/tesla/396.37/NVIDIA-Linux-x86_64-396.37.run**, bind an EIP to each GPU node. For details about how to obtain the driver link, see :ref:`Obtaining the Driver Link from Public Network <cce_10_0141__section95451728192112>`.
+      -  If the download link is a public network address, for example, **https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run**, bind an EIP to each GPU node. For details about how to obtain the driver link, see :ref:`Obtaining the Driver Link from Public Network <cce_10_0141__section95451728192112>`.
       -  If the download link is an OBS URL, you do not need to bind an EIP to GPU nodes.
       -  Ensure that the NVIDIA driver version matches the GPU node.
       -  After the driver version is changed, restart the node for the change to take effect.
@@ -68,7 +68,7 @@ Obtaining the Driver Link from Public Network
 
    .. _cce_10_0141__fig11696366517:
 
-   .. figure:: /_static/images/en-us_image_0000001280547449.png
+   .. figure:: /_static/images/en-us_image_0000001531533921.png
       :alt: **Figure 1** Setting parameters
 
       **Figure 1** Setting parameters
@@ -77,20 +77,20 @@ Obtaining the Driver Link from Public Network
 
    .. _cce_10_0141__fig7873421145213:
 
-   .. figure:: /_static/images/en-us_image_0000001199501252.png
+   .. figure:: /_static/images/en-us_image_0000001531373685.png
       :alt: **Figure 2** Driver information
 
       **Figure 2** Driver information
 
 6. Obtain the driver link in either of the following ways:
 
-   -  Method 1: As shown in :ref:`Figure 3 <cce_10_0141__fig5901194614534>`, find *url=/tesla/396.37/NVIDIA-Linux-x86_64-396.37.run* in the browser address box. Then, supplement it to obtain the driver link https://us.download.nvidia.com/tesla/396.37/NVIDIA-Linux-x86_64-396.37.run. By using this method, you must bind an EIP to each GPU node.
+   -  Method 1: As shown in :ref:`Figure 3 <cce_10_0141__fig5901194614534>`, find *url=/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run* in the browser address box. Then, supplement it to obtain the driver link https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run. By using this method, you must bind an EIP to each GPU node.
 
    -  Method 2: As shown in :ref:`Figure 3 <cce_10_0141__fig5901194614534>`, click **AGREE & DOWNLOAD** to download the driver. Then, upload the driver to OBS and record the OBS URL. By using this method, you do not need to bind an EIP to GPU nodes.
 
       .. _cce_10_0141__fig5901194614534:
 
-      .. figure:: /_static/images/en-us_image_0000001199181292.png
+      .. figure:: /_static/images/en-us_image_0000001531533045.png
          :alt: **Figure 3** Obtaining the link
 
          **Figure 3** Obtaining the link

umn/source/add-ons/overview.rst

@@ -9,18 +9,20 @@ CCE provides multiple types of add-ons to extend cluster functions and meet feat
 
 .. table:: **Table 1** Add-on list
 
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   | Add-on Name                                                             | Introduction                                                                                                                                                                         |
-   +=========================================================================+======================================================================================================================================================================================+
-   | :ref:`coredns (System Resource Add-On, Mandatory) <cce_10_0129>`        | The coredns add-on is a DNS server that provides domain name resolution services for Kubernetes clusters. coredns chains plug-ins to provide additional features.                    |
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   | :ref:`storage-driver (System Resource Add-On, Discarded) <cce_10_0127>` | storage-driver is a FlexVolume driver used to support IaaS storage services such as EVS, SFS, and OBS.                                                                               |
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   | :ref:`everest (System Resource Add-On, Mandatory) <cce_10_0066>`        | Everest is a cloud native container storage system. Based on the Container Storage Interface (CSI), clusters of Kubernetes v1.15.6 or later obtain access to cloud storage services. |
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   | :ref:`autoscaler <cce_10_0154>`                                         | The autoscaler add-on resizes a cluster based on pod scheduling status and resource usage.                                                                                           |
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   | :ref:`metrics-server <cce_10_0205>`                                     | metrics-server is an aggregator for monitoring data of core cluster resources.                                                                                                       |
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-   | :ref:`gpu-beta <cce_10_0141>`                                           | gpu-beta is a device management add-on that supports GPUs in containers. It supports only NVIDIA drivers.                                                                            |
-   +-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | Add-on Name                                                             | Introduction                                                                                                                                                                                                                                                                                 |
+   +=========================================================================+==============================================================================================================================================================================================================================================================================================+
+   | :ref:`coredns (System Resource Add-On, Mandatory) <cce_10_0129>`        | The coredns add-on is a DNS server that provides domain name resolution services for Kubernetes clusters. coredns chains plug-ins to provide additional features.                                                                                                                            |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | :ref:`storage-driver (System Resource Add-On, Discarded) <cce_10_0127>` | storage-driver is a FlexVolume driver used to support IaaS storage services such as EVS, SFS, and OBS.                                                                                                                                                                                       |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | :ref:`everest (System Resource Add-On, Mandatory) <cce_10_0066>`        | Everest is a cloud native container storage system. Based on the Container Storage Interface (CSI), clusters of Kubernetes v1.15.6 or later obtain access to cloud storage services.                                                                                                         |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | :ref:`autoscaler <cce_10_0154>`                                         | The autoscaler add-on resizes a cluster based on pod scheduling status and resource usage.                                                                                                                                                                                                   |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | :ref:`metrics-server <cce_10_0205>`                                     | metrics-server is an aggregator for monitoring data of core cluster resources.                                                                                                                                                                                                               |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | :ref:`gpu-beta <cce_10_0141>`                                           | gpu-beta is a device management add-on that supports GPUs in containers. It supports only NVIDIA drivers.                                                                                                                                                                                    |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+   | :ref:`volcano <cce_10_0193>`                                            | Volcano provides general-purpose, high-performance computing capabilities, such as job scheduling, heterogeneous chip management, and job running management, serving end users through computing frameworks for different industries, such as AI, big data, gene sequencing, and rendering. |
+   +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

umn/source/add-ons/volcano.rst

@@ -101,7 +101,7 @@ Installing the Add-on
       +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+
       | priority                   | The priority plugin schedules pods based on the custom workload priority.                                                                                                                                                   | ``-``                                                                                                                    | ``-``                                                       |
       +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+
-      | overcommit                 | Resources in a cluster are scheduled after being accumulated in a certain multiple to improve the workload enqueuing efficiency. If all workloads are Deployments, remove this plugin or set the raising factor to **2.0**. | **overcommit-factor**: Raising factor. Defaults to is **1.2**.                                                           | .. code-block::                                             |
+      | overcommit                 | Resources in a cluster are scheduled after being accumulated in a certain multiple to improve the workload enqueuing efficiency. If all workloads are Deployments, remove this plugin or set the raising factor to **2.0**. | **overcommit-factor**: Raising factor. Defaults to **1.2**.                                                              | .. code-block::                                             |
       |                            |                                                                                                                                                                                                                             |                                                                                                                          |                                                             |
       |                            |                                                                                                                                                                                                                             |                                                                                                                          |    - plugins:                                               |
       |                            |                                                                                                                                                                                                                             |                                                                                                                          |      - name: overcommit                                     |

umn/source/auto_scaling/index.rst

@@ -7,7 +7,7 @@ Auto Scaling
 
 -  :ref:`Overview <cce_10_0279>`
 -  :ref:`Scaling a Workload <cce_10_0293>`
--  :ref:`Scaling a Cluster/Node <cce_10_0291>`
+-  :ref:`Scaling a Node <cce_10_0291>`
 -  :ref:`Using HPA and CA for Auto Scaling of Workloads and Nodes <cce_10_0300>`
 
 .. toctree::
@@ -16,5 +16,5 @@ Auto Scaling
 
    overview
    scaling_a_workload/index
-   scaling_a_cluster_node/index
+   scaling_a_node/index
    using_hpa_and_ca_for_auto_scaling_of_workloads_and_nodes

umn/source/auto_scaling/scaling_a_node/creating_a_node_scaling_policy.rst

@@ -73,7 +73,7 @@ Procedure
 
       -  **Periodic**:
 
-         **Triggered At**: You can select a specific time point every day, every week, every month, or every year.
+         **Trigger Time**: You can select a specific time point every day, every week, every month, or every year.
 
       **Action**: Set an action to be performed when the trigger condition is met.
 

umn/source/auto_scaling/scaling_a_node/index.rst

@@ -2,8 +2,8 @@
 
 .. _cce_10_0291:
 
-Scaling a Cluster/Node
-======================
+Scaling a Node
+==============
 
 -  :ref:`Node Scaling Mechanisms <cce_10_0296>`
 -  :ref:`Creating a Node Scaling Policy <cce_10_0209>`

umn/source/auto_scaling/scaling_a_node/managing_node_scaling_policies.rst

@@ -17,11 +17,15 @@ You can view the associated node pool, rules, and scaling history of a node scal
 
 #. Log in to the CCE console and access the cluster console.
 #. Choose **Node Scaling** in the navigation pane and click |image1| in front of the policy to be viewed.
-#. In the expanded area, the **Associated Node Pool**, **Execution Rules**, and **Scaling Records** tab pages are displayed. If the policy is abnormal, locate and rectify the fault based on the error information.
+#. In the expanded area, the **Associated Node Pools**, **Rules**, and **Scaling History** tab pages are displayed. If the policy is abnormal, locate and rectify the fault based on the error information.
 
    .. note::
 
-      You can also enable or disable auto scaling in **Node Pools**. Log in to the CCE console. In the navigation pane, choose **Resource Management** > **Node Pools**, and click **Edit** in the upper right corner of the node pool to be operated. In the **Edit Node Pool** dialog box displayed, you can enable **Autoscaler** and set the limits of the number of nodes.
+      You can also disable or enable auto scaling on the **Node Pools** page.
+
+      a. Log in to the CCE console and access the cluster console.
+      b. In the navigation pane, choose **Nodes** and switch to the **Node Pools** tab page.
+      c. Click **Edit** of the node pool to be operated. In the **Edit Node Pool** dialog box that is displayed, set the limits of the number of nodes.
 
 Deleting a Node Scaling Policy
 ------------------------------

umn/source/auto_scaling/scaling_a_workload/managing_workload_scaling_policies.rst

@@ -21,7 +21,11 @@ You can view the rules, status, and events of an HPA policy and handle exception
 
    .. note::
 
-      You can also view the created HPA policy on the workload details page. Log in to the CCE console, choose **Workloads > Deployments** or **Workloads > StatefulSets** in the navigation pane, and choose **More** > **Scaling** in the **Operation** column. On the workload details page, click the **Scaling** tab. You can see the **Auto Scaling-HPA** pane, as well as the HPA policy you have configured on the **Auto Scaling** page.
+      You can also view the created HPA policy on the workload details page.
+
+      a. Log in to the CCE console and access the cluster console.
+      b. In the navigation pane, choose **Workloads**. Click the workload name to view its details.
+      c. On the workload details page, swich to the **Auto Scaling** tab page to view the HPA policies. You can also view the scaling policies you configured in **Workload Scaling**.
 
    .. table:: **Table 1** Event types and names
 

umn/source/auto_scaling/using_hpa_and_ca_for_auto_scaling_of_workloads_and_nodes.rst

@@ -133,7 +133,7 @@ Creating a Node Pool and a Node Scaling Policy
 #. Set node pool parameters, add a node with 2 vCPUs and 4 GB memory, and enable auto scaling.
 
    -  **Nodes**: Set it to **1**, indicating that one node is created by default when a node pool is created.
-   -  Auto Scaling: Enable the option, meaning that nodes will be automatically created or deleted in the node pool based on the cluster loads.
+   -  **Auto Scaling**: Enable the option, meaning that nodes will be automatically created or deleted in the node pool based on the cluster loads.
    -  **Max. Nodes**: Set it to **5**, indicating the maximum number of nodes in a node pool.
    -  **Specifications**: 2 vCPUs \| 4 GiB
 

umn/source/best_practice/auto_scaling/using_hpa_and_ca_for_auto_scaling_of_workloads_and_nodes.rst

@@ -133,7 +133,7 @@ Creating a Node Pool and a Node Scaling Policy
 #. Set node pool parameters, add a node with 2 vCPUs and 4 GB memory, and enable auto scaling.
 
    -  **Nodes**: Set it to **1**, indicating that one node is created by default when a node pool is created.
-   -  Auto Scaling: Enable the option, meaning that nodes will be automatically created or deleted in the node pool based on the cluster loads.
+   -  **Auto Scaling**: Enable the option, meaning that nodes will be automatically created or deleted in the node pool based on the cluster loads.
    -  **Max. Nodes**: Set it to **5**, indicating the maximum number of nodes in a node pool.
    -  **Specifications**: 2 vCPUs \| 4 GiB
 

umn/source/best_practice/migration/migrating_on-premises_kubernetes_clusters_to_cce/migrating_resources_in_a_cluster.rst

@@ -156,4 +156,4 @@ The storage infrastructure of an on-premises cluster is different from that of a
 
 #. After the restoration is complete, check whether the application is running properly. If other adaptation problems may occur, rectify the fault by following the procedure described in :ref:`Updating Resources Accordingly <cce_bestpractice_0312>`.
 
-.. |image1| image:: /_static/images/en-us_image_0000001171703840.png
+.. |image1| image:: /_static/images/en-us_image_0000001480191270.png

umn/source/best_practice/migration/migrating_on-premises_kubernetes_clusters_to_cce/planning_resources_for_the_target_cluster.rst

@@ -18,7 +18,7 @@ CCE allows you to customize cluster resources to meet various service requiremen
    +-----------------+-----------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------+
    | Resource        | Key Performance Parameter                                 | Description                                                                                                                                                                                                                                                                                                                                                                                  | Example Value                                                   |
    +=================+===========================================================+==============================================================================================================================================================================================================================================================================================================================================================================================+=================================================================+
-   | Cluster         | **\***\ Cluster Type                                      | -  CCE cluster: supports VM nodes. You can run your containers in a secure and stable container runtime environment based on a high-performance network model.                                                                                                                                                                                                                               | CCE cluster                                                     |
+   | Cluster         | **\***\ Cluster Type                                      | -  **CCE cluster**: supports VM nodes. You can run your containers in a secure and stable container runtime environment based on a high-performance network model.                                                                                                                                                                                                                           | CCE cluster                                                     |
    |                 |                                                           | -  **CCE Turbo cluster**: runs on a cloud native infrastructure that features software-hardware synergy to support passthrough networking, high security and reliability, intelligent scheduling, and BMS nodes.                                                                                                                                                                             |                                                                 |
    +-----------------+-----------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------+
    |                 | **\***\ Network Model                                     | -  **VPC network**: The container network uses VPC routing to integrate with the underlying network. This network model is applicable to performance-intensive scenarios. The maximum number of nodes allowed in a cluster depends on the route quota in a VPC network.                                                                                                                      | VPC network                                                     |

umn/source/best_practice/migration/migrating_on-premises_kubernetes_clusters_to_cce/updating_resources_accordingly.rst

@@ -20,7 +20,7 @@ The WordPress and MySQL images used in this example can be pulled from SWR. Ther
 
    .. code-block::
 
-      'swr.{Region}.otc.t-systems.com/{Organization name}/{Image name}:{Tag}
+      'swr.{Region}.otc.t-systems.com/{Organization name}/{Image name}:{Tag}'
 
 #. Run the following command to modify the workload and replace the **image** field in the YAML file with the image path:
 

umn/source/charts/deploying_an_application_from_a_chart.rst

@@ -94,7 +94,7 @@ Creating a Release
 
 #. Log in to the CCE console, click the cluster name, and access the cluster console. In the navigation pane, choose **Charts**.
 
-#. In the list of uploaded charts, click **Install Chart**.
+#. In the list of uploaded charts, click **Install**.
 
 #. Set workload installation parameters by referring to :ref:`Table 2 <cce_10_0146__t26bc1c499f114b5185e5edcf61e44d95>`.
 

umn/source/charts/index.rst

@@ -2,8 +2,8 @@
 
 .. _cce_10_0019:
 
-Helms
-=====
+Charts
+======
 
 -  :ref:`Overview <cce_10_0191>`
 -  :ref:`Deploying an Application from a Chart <cce_10_0146>`

umn/source/clusters/cluster_overview/release_notes/cce_kubernetes_1.25_release_notes.rst

@@ -25,7 +25,7 @@ Resource Changes and Deprecations
 **Kubernetes 1.24 Release Notes**
 
 -  Beta APIs are disabled by default. When some long-term beta APIs are removed from Kubernetes, 90% cluster administrators do not care about the beta APIs. Beta features are not recommended in the production environment. However, due to the default enabling policy, these APIs are enabled in the production environment, incurring risks. Therefore, in v1.24 and later versions, beta APIs are disabled by default except for the enabled beta APIs.
--  The LegacyServiceAccountTokenNoAutoGeneration feature is in beta state. By default, this feature is enabled and no more secret token will be automatically generated for the service account. If you want to use a token that never expires, you need to create a secret and mount it. For details, see `Service account token Secrets <https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets>`__.
+-  The LegacyServiceAccountTokenNoAutoGeneration feature is in beta state. By default, this feature is enabled and no more secret token will be automatically generated for the service account. If you want to use a token that never expires, you need to create a secret and mount it. For details, see `Service account token secrets <https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets>`__.
 -  **service.alpha.kubernetes.io/tolerate-unready-endpoints** is replaced by **Service.spec.publishNotReadyAddresses**.
 -  The **Service.Spec.LoadBalancerIP** tag is deprecated and may be removed in later versions. Use a customized annotation.
 

umn/source/clusters/creating_a_cce_cluster.rst

@@ -16,6 +16,7 @@ Notes and Constraints
 -  You can create a maximum of 50 clusters in a single region.
 -  After a cluster is created, the following items cannot be changed:
 
+   -  Cluster type
    -  Number of master nodes in the cluster
    -  AZ of a master node
    -  Network configuration of the cluster, such as the VPC, subnet, container CIDR block, Service CIDR block, and kube-proxy (forwarding) settings
@@ -30,11 +31,11 @@ Procedure
 
    **Basic Settings**
 
-   -  Cluster Name
+   -  **Cluster Name**
 
-   -  Cluster Version: Select the Kubernetes version used by the cluster.
+   -  **Cluster Version**: Select the Kubernetes version used by the cluster.
 
-   -  Cluster Scale: maximum number of nodes that can be managed by the cluster.
+   -  **Cluster Scale**: maximum number of nodes that can be managed by the cluster.
 
    -  **HA**: distribution mode of master nodes. By default, master nodes are randomly distributed in different AZs to improve DR capabilities.
 
@@ -75,6 +76,8 @@ Procedure
             -  The uploaded CA certificate is used for both the authentication proxy and the kube-apiserver aggregation layer configuration. **If the certificate is invalid, the cluster cannot be created**.
             -  Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. You are advised to use the SHA256 algorithm.
 
+   -  **Description**: The value can contain a maximum of 200 English characters.
+
 #. Click **Next: Add-on Configuration**.
 
    By default, :ref:`cordens <cce_10_0129>` and :ref:`everest <cce_10_0066>` add-ons are installed.

umn/source/clusters/creating_a_cce_turbo_cluster.rst

@@ -40,7 +40,7 @@ Procedure
 
    -  **HA**: distribution mode of master nodes. By default, master nodes are randomly distributed in different AZs to improve DR capabilities.
 
-      You can also expand advanced settings and customize the master node distribution mode. The following two modes are supported:
+      You can also expand advanced settings and customize the master node distribution mode. The following modes are supported:
 
       -  **Host**: Master nodes are created on different hosts in the same AZ.
       -  **Custom**: You can determine the location of each master node.
@@ -82,6 +82,8 @@ Procedure
             -  The uploaded CA certificate is used for both the authentication proxy and the kube-apiserver aggregation layer configuration. **If the certificate is invalid, the cluster cannot be created**.
             -  Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. You are advised to use the SHA256 algorithm.
 
+   -  **Description**: The value can contain a maximum of 200 English characters.
+
 #. Click **Next: Add-on Configuration**.
 
    By default, :ref:`cordens <cce_10_0129>` and :ref:`everest <cce_10_0066>` add-ons are installed.