A200161411/cloud-container-engine
1
0
Fork 0
forked from docs/cloud-container-engine
Code Pull Requests Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2023-01-12 15:30:21 +00:00
parent b24c98e143
commit b5dd7bd40d
22 changed files with 94 additions and 94 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
umn/source/auto_scaling/scaling_a_workload/creating_an_hpa_policy_for_workload_auto_scaling.rst
View File

@ -91,7 +91,7 @@ Procedure
| | When calculating the number of pods to be added or reduced, the HPA policy uses the maximum metrics values in the last 5 minutes. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
#. After the configuration is complete, click **Create**. If the system displays a message indicating that the request to create workload policy \**\* is successfully submitted, click **Back to Workload Scaling**.
#. After the configuration is complete, click **Create**. If the system displays a message indicating that the request to create workload policy ``***`` is successfully submitted, click **Back to Workload Scaling**.
#. On the **Workload Scaling** tab page, you can view the newly created HPA policy.

10
umn/source/charts_helm/my_charts/creating_a_workload_from_a_chart.rst
View File

@ -12,7 +12,7 @@ Creating a Chart-based Workload
#. In the list of uploaded charts, click **Install**.
#. Set the installation parameters listed in :ref:`Table 1 <cce_01_0146__t26bc1c499f114b5185e5edcf61e44d95>`. The parameters marked with an asterisk (*) are mandatory.
#. Set the installation parameters listed in :ref:`Table 1 <cce_01_0146__t26bc1c499f114b5185e5edcf61e44d95>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0146__t26bc1c499f114b5185e5edcf61e44d95:
@ -21,13 +21,13 @@ Creating a Chart-based Workload
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+===========================================================================================================================================================================================+
| \* Release Name | Unique name of the chart release. |
| ``*`` Release Name | Unique name of the chart release. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Chart Version | Chart version by default. |
| ``*`` Chart Version | Chart version by default. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster | Cluster where the workload will be deployed. |
| ``*`` Cluster | Cluster where the workload will be deployed. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Namespace | Namespace to which the workload will be deployed. |
| ``*`` Namespace | Namespace to which the workload will be deployed. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Advanced Settings | You can import and replace the **values.yaml** file or directly edit the chart parameters online. |
| | |

8
umn/source/charts_helm/my_charts/preparing_a_chart.rst
View File

@ -91,7 +91,7 @@ This section uses the redis chart as an example to illustrate the chart specific
Chart.yaml
.helmignore
As listed in :ref:`Table 1 <cce_01_0144__tb7d789a3467e4fe9b4385a51f3460321>`, the parameters marked with \* are mandatory.
As listed in :ref:`Table 1 <cce_01_0144__tb7d789a3467e4fe9b4385a51f3460321>`, the parameters marked with ``*`` are mandatory.
.. _cce_01_0144__tb7d789a3467e4fe9b4385a51f3460321:
@ -100,9 +100,9 @@ This section uses the redis chart as an example to illustrate the chart specific
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+==========================================================================================================================================================================================================================================================================================================================================================================================================================+
| \* templates | Stores all templates. |
| ``*`` templates | Stores all templates. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* values.yaml | Describes configuration parameters required by templates. |
| ``*`` values.yaml | Describes configuration parameters required by templates. |
| | |
| | .. important:: |
| | |
@ -118,7 +118,7 @@ This section uses the redis chart as an example to illustrate the chart specific
| | - Configurations in the **values.yaml** file. |
| | - Information about chart installation and configuration. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Chart.yaml | Basic information about the chart. |
| ``*`` Chart.yaml | Basic information about the chart. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| .helmignore | Files or data that does not need to read templates during workload installation. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

8
umn/source/clusters/creating_a_cce_cluster.rst
View File

@ -26,7 +26,7 @@ Procedure
#. Log in to the CCE console. On the **Dashboard** page, click **Create Cluster**. Alternatively, choose **Resource Management** > **Clusters** in the navigation pane and click **Create** next to **CCE Cluster**.
#. Set cluster parameters by referring to :ref:`Table 1 <cce_01_0028__table8638121213265>`. Pay attention to the parameters marked with an asterisk (*).
#. Set cluster parameters by referring to :ref:`Table 1 <cce_01_0028__table8638121213265>`. Pay attention to the parameters marked with an asterisk (``*``).
.. _cce_01_0028__table8638121213265:
@ -37,7 +37,7 @@ Procedure
+===================================+==========================================================================================================================================================================================================================================================================================================================================================================================================================+
| Region | Select a region near you to ensure the lowest latency possible. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Cluster Name | Name of the new cluster, which cannot be changed after the cluster is created. |
| ``*``\ Cluster Name | Name of the new cluster, which cannot be changed after the cluster is created. |
| | |
| | A cluster name contains 4 to 128 characters starting with a letter and not ending with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@ -66,13 +66,13 @@ Procedure
| | - The multi-master mode cannot be changed after the cluster is created. A single-master cluster cannot be upgraded to a multi-master cluster. For a single-master cluster, if a master node is faulty, services will be affected. |
| | - To ensure reliability, the multi-master mode is enabled by default for a cluster with 1,000 or more nodes. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*VPC | VPC where the cluster is located. The value cannot be changed after the cluster is created. |
| ``*``\ VPC | VPC where the cluster is located. The value cannot be changed after the cluster is created. |
| | |
| | A VPC provides a secure and logically isolated network environment. |
| | |
| | If no VPC is available, click **Create a VPC** to create a VPC. After the VPC is created, click the refresh icon. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Subnet | Subnet where the node VM runs. The value cannot be changed after the cluster is created. |
| ``*``\ Subnet | Subnet where the node VM runs. The value cannot be changed after the cluster is created. |
| | |
| | A subnet provides dedicated network resources that are logically isolated from other networks for network security. |
| | |

38
umn/source/clusters/setting_cluster_auto_scaling.rst
View File

@ -63,17 +63,17 @@ Automatic Cluster Scale-out
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+==============================================================================================================================================================================================================================================================================================+
| \*Metric | Select **Allocated CPU** or **Allocated Memory**. |
| ``*``\ Metric | Select **Allocated CPU** or **Allocated Memory**. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Trigger Condition | Set a condition for triggering a scale-out policy, that is, when the average CPU or memory allocation value is greater than or less than a specified percentage. |
| ``*``\ Trigger Condition | Set a condition for triggering a scale-out policy, that is, when the average CPU or memory allocation value is greater than or less than a specified percentage. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Monitoring Window | Size of the data aggregation window. Select a value from the drop-down list. |
| ``*``\ Monitoring Window | Size of the data aggregation window. Select a value from the drop-down list. |
| | |
| | If you select **15min**, the selected metric is measured every 15 minutes. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Threshold Crossings | Number of consecutive times that the threshold is reached within the monitoring window. The calculation cycle is fixed at one minute. If you set this parameter to **3**, the configured action will be triggered when the metrics meet the specified threshold for three consecutive times. |
| ``*``\ Threshold Crossings | Number of consecutive times that the threshold is reached within the monitoring window. The calculation cycle is fixed at one minute. If you set this parameter to **3**, the configured action will be triggered when the metrics meet the specified threshold for three consecutive times. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Action | Action executed after a policy is triggered. |
| ``*``\ Action | Action executed after a policy is triggered. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- :ref:`Scheduled policy <cce_01_0157__table62540231191540>`: Scale-out is performed at a specified time.
@ -82,13 +82,13 @@ Automatic Cluster Scale-out
.. table:: **Table 3** Parameters for adding a scheduled policy
============== ============================================
Parameter Description
============== ============================================
\*Policy Type Set this parameter to **Scheduled policy**.
\*Trigger Time Time at which the policy is triggered.
\*Action Action executed after a policy is triggered.
============== ============================================
=================== ============================================
Parameter Description
=================== ============================================
``*``\ Policy Type Set this parameter to **Scheduled policy**.
``*``\ Trigger Time Time at which the policy is triggered.
``*``\ Action Action executed after a policy is triggered.
=================== ============================================
- :ref:`Periodic policy <cce_01_0157__table60088509191540>`: Scale-out can be performed by day, week, or month.
@ -96,13 +96,13 @@ Automatic Cluster Scale-out
.. table:: **Table 4** Parameters for adding a periodic policy
============= ============================================
Parameter Description
============= ============================================
\*Policy Type Set the parameter to **Periodic policy**.
\*Time Range Specify the time for triggering the policy.
\*Action Action executed after a policy is triggered.
============= ============================================
================== ============================================
Parameter Description
================== ============================================
``*``\ Policy Type Set the parameter to **Periodic policy**.
``*``\ Time Range Specify the time for triggering the policy.
``*``\ Action Action executed after a policy is triggered.
================== ============================================
#. Click **OK**.

2
umn/source/clusters/upgrading_a_cluster/migrating_services_across_clusters_of_different_versions.rst
View File

@ -10,7 +10,7 @@ Application Scenarios
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-version cluster upgrade is required (for example, upgrade from v1.7.\* or v1.9.\* to 1.17.*) and new clusters can be created for service migration.
This operation is applicable when a cross-version cluster upgrade is required (for example, upgrade from v1.7.\ ``*`` or v1.9.\ ``*`` to 1.17.\ ``*``) and new clusters can be created for service migration.
Prerequisites
-------------

16
umn/source/migrating_data_from_cce_1.0_to_cce_2.0/migrating_clusters.rst
View File

@ -14,7 +14,7 @@ Procedure
#. Log in to the CCE console. In the navigation pane, choose **Resource Management** > **Clusters**. Click **Create Hybrid cluster**.
#. Set cluster parameters. Parameters with \* are mandatory.
#. Set cluster parameters. Parameters with ``*`` are mandatory.
.. figure:: /_static/images/en-us_image_0000001177874150.png
@ -27,22 +27,22 @@ Procedure
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter in CCE 2.0 | Parameter in CCE 1.0 | Configuration |
+===========================+==========================================================================================+===================================================================================================================================================================================================================================================================================================================================================================================================+
| \* Cluster Name | Name | Name of the cluster to be created. |
| ``*`` Cluster Name | Name | Name of the cluster to be created. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Version | This parameter does not exist in CCE 1.0. Retain the default value. | Cluster version, namely, corresponding Kubernetes baseline version. |
| ``*``\ Version | This parameter does not exist in CCE 1.0. Retain the default value. | Cluster version, namely, corresponding Kubernetes baseline version. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Management Scale | This parameter does not exist in CCE 1.0. Set this parameter based on your requirements. | Maximum number of nodes that can be managed by the cluster. |
| ``*``\ Management Scale | This parameter does not exist in CCE 1.0. Set this parameter based on your requirements. | Maximum number of nodes that can be managed by the cluster. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* High Availability | Cluster Type | - **Yes**: The cluster has three master nodes. The cluster is still available even when two master nodes are down. |
| ``*`` High Availability | Cluster Type | - **Yes**: The cluster has three master nodes. The cluster is still available even when two master nodes are down. |
| | | - **No**: The cluster has only one master node. If the master node is down, the whole cluster becomes unavailable, but existing applications are not affected. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*VPC | VPCs created in CCE 1.0 can be used in CCE 2.0. | VPC where the new cluster is located. |
| ``*``\ VPC | VPCs created in CCE 1.0 can be used in CCE 2.0. | VPC where the new cluster is located. |
| | | |
| | | If no VPCs are available, click **Create a VPC**. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Subnet | Subnets created in CCE 1.0 can be used in CCE 2.0. | Subnet in which the cluster will run. |
| ``*``\ Subnet | Subnets created in CCE 1.0 can be used in CCE 2.0. | Subnet in which the cluster will run. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Network Model | This parameter does not exist in CCE 1.0. Set this parameter based on your requirements. | - **Tunnel network**: An independent container network constructed using VXLAN tunnels based on the underlying VPC network. This model is appropriate for typical scenarios. |
| ``*``\ Network Model | This parameter does not exist in CCE 1.0. Set this parameter based on your requirements. | - **Tunnel network**: An independent container network constructed using VXLAN tunnels based on the underlying VPC network. This model is appropriate for typical scenarios. |
| | | - **VPC network**: The VPC routing mode is used to deeply integrate with the underlying network. This mode applies to high-performance scenarios where the number of nodes is limited by the VPC routing quota. Only one cluster using the VPC network model can be created in a single VPC. |
+---------------------------+------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Container Network Segment | This parameter does not exist in CCE 1.0. Set this parameter based on your requirements. | Select a container network segment based on service requirements. Container instances will be assigned with IP addresses within the planned network segment. |

2
umn/source/monitoring_and_logs/container_logs.rst
View File

@ -51,7 +51,7 @@ Setting the Path for Storing Container Logs
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| **Add Container Path** | |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Host Path | Enter the host path, for example, **/var/paas/sys/log/nginx**. |
| ``*``\ Host Path | Enter the host path, for example, **/var/paas/sys/log/nginx**. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Container Path | Container path (for example, **/tmp**) to which the storage resources will be mounted. |
| | |

6
umn/source/namespaces/creating_a_namespace.rst
View File

@ -42,7 +42,7 @@ Creating a Namespace
#. Log in to the CCE console. In the navigation pane, choose **Resource Management** > **Namespaces**. Click **Create Namespace**.
#. Set the parameters listed in :ref:`Table 1 <cce_01_0278__table5523151617575>`. The parameters marked with an asterisk (*) are mandatory.
#. Set the parameters listed in :ref:`Table 1 <cce_01_0278__table5523151617575>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0278__table5523151617575:
@ -51,9 +51,9 @@ Creating a Namespace
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+==========================================================================================================================================================================================================================================================================================================+
| \* Namespace | Unique name of the created namespace. |
| ``*`` Namespace | Unique name of the created namespace. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster | Cluster to which the namespace belongs. |
| ``*`` Cluster | Cluster to which the namespace belongs. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Node Affinity | If this parameter is set to on, workloads in this namespace will be scheduled only to nodes with specified labels. To add labels to a node, choose **Resource Management** > **Nodes** > **Manage Labels**. |
| | |

4
umn/source/networking/ingress/using_elb_ingresses_on_the_console.rst
View File

@ -126,9 +126,9 @@ This section uses an Nginx workload as an example to describe how to add an ELB
#. Access the /healthz interface of the workload, for example, workload **defaultbackend**.
a. Obtain the access address of the /healthz interface of the workload. The access address consists of the load balancer IP address, external port, and mapping URL, for example, 10.**.**.**:80/healthz.
a. Obtain the access address of the /healthz interface of the workload. The access address consists of the load balancer IP address, external port, and mapping URL, for example, 10.\ ``**``.\ ``**``.\ ``**``:80/healthz.
b. Enter the URL of the /healthz interface, for example, http://10.**.**.**:80/healthz, in the address box of the browser to access the workload, as shown in :ref:`Figure 1 <cce_01_0251__fig17115192714367>`.
b. Enter the URL of the /healthz interface, for example, http://10.\ ``**``.\ ``**``.\ ``**``:80/healthz, in the address box of the browser to access the workload, as shown in :ref:`Figure 1 <cce_01_0251__fig17115192714367>`.
.. _cce_01_0251__fig17115192714367:

8
umn/source/networking/ingress/using_kubectl_to_create_an_elb_ingress.rst
View File

@ -243,9 +243,9 @@ The following describes how to run the kubectl command to automatically create a
NAME HOSTS ADDRESS PORTS AGE
ingress-test * 121.**.**.** 80 10s
#. Enter **http://121.**.**.*\*:80** in the address box of the browser to access the workload (for example, :ref:`Nginx workload <cce_01_0047__section155246177178>`).
#. Enter **http://121.\ ``**``.\ ``**``.\ ``**``:80** in the address box of the browser to access the workload (for example, :ref:`Nginx workload <cce_01_0047__section155246177178>`).
**121.**.**.*\*** indicates the IP address of the unified load balancer.
**121.\ ``**``.\ ``**``.\ ``**``** indicates the IP address of the unified load balancer.
.. _cce_01_0252__section32300431736:
@ -467,9 +467,9 @@ Ingress supports TLS certificate configuration and provides security services in
NAME HOSTS ADDRESS PORTS AGE
ingress-test * 121.**.**.** 80 10s
#. Enter **https://121.**.**.*\*:443** in the address box of the browser to access the workload (for example, :ref:`Nginx workload <cce_01_0047__section155246177178>`).
#. Enter **https://121.\ ``**``.\ ``**``.\ ``**``:443** in the address box of the browser to access the workload (for example, :ref:`Nginx workload <cce_01_0047__section155246177178>`).
**121.**.**.*\*** indicates the IP address of the unified load balancer.
**121.\ ``**``.\ ``**``.\ ``**``** indicates the IP address of the unified load balancer.
.. _cce_01_0252__section0555194782414:

2
umn/source/storage_csi/deployment_examples/evs_volumes/using_evs_volumes.rst
View File

@ -43,7 +43,7 @@ Creating an EVS Disk
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+=====================================================================================================================================================================================================================================================================================================================================================================================+
| \* PVC Name | **New PVC Name**: name of the PVC to be created. A storage volume is automatically created when a PVC is created. One PVC corresponds to one storage volume. The storage volume name is automatically generated when the PVC is created. |
| ``*`` PVC Name | **New PVC Name**: name of the PVC to be created. A storage volume is automatically created when a PVC is created. One PVC corresponds to one storage volume. The storage volume name is automatically generated when the PVC is created. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Cluster Name | Cluster where the EVS disk is deployed. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/storage_csi/deployment_examples/obs_volumes/using_obs_volumes.rst
View File

@ -57,7 +57,7 @@ Creating an OBS Volume
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Parameter Description |
+===================================+================================================================================================================================================================================================================================================================================+
| \* PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
| ``*`` PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
| | |
| | The name contains 3 to 55 characters (excluding the prefix). It must contain lowercase letters, digits, and hyphens (-), and cannot start or end with a hyphen (-). |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/storage_csi/deployment_examples/sfs_volumes/using_sfs_volumes.rst
View File

@ -35,7 +35,7 @@ Creating an SFS Volume
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Parameter Description |
+===================================+======================================================================================================================================================================================================================================================================================================================================================================================+
| \* PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
| ``*`` PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Cluster Name | Cluster to which the file system volume belongs. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/storage_flexvolume/using_evs_disks_as_storage_volumes/using_evs_volumes.rst
View File

@ -35,7 +35,7 @@ Buying an EVS Disk
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+=====================================================================================================================================================================================================================================================================================================================================================================================+
| \* PVC Name | **New PVC Name**: name of the PVC to be created. A storage volume is automatically created when a PVC is created. One PVC corresponds to one storage volume. The storage volume name is automatically generated when the PVC is created. |
| ``*`` PVC Name | **New PVC Name**: name of the PVC to be created. A storage volume is automatically created when a PVC is created. One PVC corresponds to one storage volume. The storage volume name is automatically generated when the PVC is created. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Cluster Name | Cluster where the EVS disk is deployed. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/storage_flexvolume/using_obs_buckets_as_storage_volumes/using_obs_volumes.rst
View File

@ -62,7 +62,7 @@ Creating an OBS Volume
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+================================================================================================================================================================================================================================================================================+
| \* PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
| ``*`` PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
| | |
| | The name contains 3 to 55 characters (excluding the prefix). It must contain lowercase letters, digits, and hyphens (-), and cannot start or end with a hyphen (-). |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/storage_flexvolume/using_sfs_file_systems_as_storage_volumes/using_sfs_volumes.rst
View File

@ -35,7 +35,7 @@ Creating an SFS Volume
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Parameter Description |
+===================================+======================================================================================================================================================================================================================================================================================================================================================================================+
| \* PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
| ``*`` PVC Name | Name of the new PVC, which is different from the volume name. The actual volume name is automatically generated when the PV is created by the PVC. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Cluster Name | Cluster to which the file system volume belongs. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

16
umn/source/workloads/creating_a_cron_job.rst
View File

@ -32,7 +32,7 @@ Procedure
#. Log in to the CCE console. In the navigation pane, choose **Workloads** > **Cron Jobs**. Then, click **Create Cron Job**.
#. Configure the basic cron job information listed in :ref:`Table 1 <cce_01_0151__tfadd3a11520b424d9063fe347c9c8c46>`. The parameters marked with an asterisk (*) are mandatory.
#. Configure the basic cron job information listed in :ref:`Table 1 <cce_01_0151__tfadd3a11520b424d9063fe347c9c8c46>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0151__tfadd3a11520b424d9063fe347c9c8c46:
@ -41,13 +41,13 @@ Procedure
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+===========================================================================================================================================================+
| \* Job Name | Name of a new cron job. The name must be unique. |
| ``*`` Job Name | Name of a new cron job. The name must be unique. |
| | |
| | Enter 4 to 52 characters starting with a lowercase letter and ending with a letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster | Cluster to which a new cron job belongs. |
| ``*`` Cluster | Cluster to which a new cron job belongs. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Namespace | Namespace to which a cron job belongs. If you do not specify this parameter, the value **default** is used by default. |
| ``*`` Namespace | Namespace to which a cron job belongs. If you do not specify this parameter, the value **default** is used by default. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Description | Description of a cron job. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
@ -61,13 +61,13 @@ Procedure
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+===========================================================================================================================================================================+
| \* Concurrency Policy | The following policies are supported: |
| ``*`` Concurrency Policy | The following policies are supported: |
| | |
| | - Forbid: A new job cannot be created before the previous job is complete. |
| | - Allow: The cron job allows concurrently running jobs, which preempt cluster resources. |
| | - Replace: A new job replaces the previous job when it is time to create the job but the previous job is not complete. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Schedule | Time when a new cron job is executed. |
| ``*`` Schedule | Time when a new cron job is executed. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Job Records | You can set the number of jobs that are successfully executed or fail to be executed. Setting a limit to **0** corresponds to keeping none of the jobs after they finish. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@ -93,9 +93,9 @@ Procedure
+===================================+==============================================================================================================================================================================================================================================================================================================+
| Image | Name of the image. You can click **Change Image** to update it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Image Version | Select the image tag to be deployed. |
| ``*``\ Image Version | Select the image tag to be deployed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Container Name | Name of the container. You can modify it. |
| ``*``\ Container Name | Name of the container. You can modify it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Container Resources | **CPU** |
| | |

12
umn/source/workloads/creating_a_daemonset.rst
View File

@ -30,7 +30,7 @@ Procedure
#. Log in to the CCE console.
#. In the navigation pane on the left, choose **Workloads** > **DaemonSets**. Click **Create DaemonSet** in the upper right corner of the page. Set basic workload parameters as described in :ref:`Table 1 <cce_01_0216__table18511927357>`. The parameters marked with an asterisk (*) are mandatory.
#. In the navigation pane on the left, choose **Workloads** > **DaemonSets**. Click **Create DaemonSet** in the upper right corner of the page. Set basic workload parameters as described in :ref:`Table 1 <cce_01_0216__table18511927357>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0216__table18511927357:
@ -39,13 +39,13 @@ Procedure
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+===========================================================================================================================================================================================================================================+
| \* Workload Name | Name of the containerized workload to be created. The name must be unique. |
| ``*`` Workload Name | Name of the containerized workload to be created. The name must be unique. |
| | |
| | Enter 4 to 63 characters starting with a letter and ending with a letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster Name | Cluster to which the workload belongs. |
| ``*`` Cluster Name | Cluster to which the workload belongs. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Namespace | In a single cluster, data in different namespaces is isolated from each other. This enables applications to share the services of the same cluster without interfering each other. If no namespace is set, the default namespace is used. |
| ``*`` Namespace | In a single cluster, data in different namespaces is isolated from each other. This enables applications to share the services of the same cluster without interfering each other. If no namespace is set, the default namespace is used. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Time Zone Synchronization | If this parameter is enabled, the container and the node use the same time zone. |
| | |
@ -80,9 +80,9 @@ Procedure
+===================================+==============================================================================================================================================================================================================================================================================================================+
| Image Name | Name of the image. You can click **Change Image** to update it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Image Version | Select the image tag to be deployed. |
| ``*``\ Image Version | Select the image tag to be deployed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Container Name | Name of the container. You can modify it. |
| ``*``\ Container Name | Name of the container. You can modify it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Privileged Container | Programs in a privileged container have certain privileges. |
| | |

16
umn/source/workloads/creating_a_deployment.rst
View File

@ -39,7 +39,7 @@ CCE provides multiple methods for creating a workload. You can use any of the fo
When you click **Create YAML** on the right of the console, do not create multiple YAML files in the YAML definition pane displayed. You need to create them one by one. Otherwise, an error will be reported during the creation.
#. Log in to the CCE console. In the navigation pane, choose **Workloads** > **Deployments**. On the page displayed, click **Create Deployment**. Set basic workload parameters as described in :ref:`Table 1 <cce_01_0047__table12741447488>`. The parameters marked with an asterisk (*) are mandatory.
#. Log in to the CCE console. In the navigation pane, choose **Workloads** > **Deployments**. On the page displayed, click **Create Deployment**. Set basic workload parameters as described in :ref:`Table 1 <cce_01_0047__table12741447488>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0047__table12741447488:
@ -48,19 +48,19 @@ CCE provides multiple methods for creating a workload. You can use any of the fo
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+======================================================================================================================================================================================================================================================+
| \* Workload Name | Name of the workload to be created. The name must be unique. |
| ``*`` Workload Name | Name of the workload to be created. The name must be unique. |
| | |
| | Enter 4 to 63 characters starting with a letter and ending with a letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster Name | Cluster to which the workload belongs. |
| ``*`` Cluster Name | Cluster to which the workload belongs. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Namespace | In a single cluster, data in different namespaces is isolated from each other. This enables applications to share the services of the same cluster without interfering each other. If no namespace is set, the default namespace is used. |
| ``*`` Namespace | In a single cluster, data in different namespaces is isolated from each other. This enables applications to share the services of the same cluster without interfering each other. If no namespace is set, the default namespace is used. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Instances | Number of pods in the workload. A workload can have one or more pods. You can set the number of pods. The default value is **2** and can be set to **1**. |
| ``*`` Instances | Number of pods in the workload. A workload can have one or more pods. You can set the number of pods. The default value is **2** and can be set to **1**. |
| | |
| | Each workload pod consists of the same containers. Configuring multiple pods for a workload ensures that the workload can still run properly even if a pod is faulty. If only one pod is used, a node or pod exception may cause service exceptions. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Container runtime | Select a container runtime, which cannot be changed after creation. **This parameter is available only for CCE Turbo clusters.** |
| ``*`` Container runtime | Select a container runtime, which cannot be changed after creation. **This parameter is available only for CCE Turbo clusters.** |
| | |
| | - **runc**: Common containers will run on the node. |
| | - **kata**: Secure containers will be used and the workload can run only on the node that uses the secure runtime. |
@ -100,9 +100,9 @@ CCE provides multiple methods for creating a workload. You can use any of the fo
+===================================+==============================================================================================================================================================================================================================================================================================================+
| Image Name | Name of the image. You can click **Change Image** to update it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Image Version | Select the image tag to be deployed. |
| ``*``\ Image Version | Select the image tag to be deployed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Container Name | Name of the container. You can modify it. |
| ``*``\ Container Name | Name of the container. You can modify it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Privileged Container | Programs in a privileged container have certain privileges. |
| | |

14
umn/source/workloads/creating_a_job.rst
View File

@ -30,7 +30,7 @@ Procedure
#. Log in to the CCE console. In the navigation pane, choose **Workloads** > **Jobs**. Click **Create Job**.
#. Configure the basic job information listed in :ref:`Table 1 <cce_01_0150__t70ce3a99637a44ce8f7274857fb245b1>`. The parameters marked with an asterisk (*) are mandatory.
#. Configure the basic job information listed in :ref:`Table 1 <cce_01_0150__t70ce3a99637a44ce8f7274857fb245b1>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0150__t70ce3a99637a44ce8f7274857fb245b1:
@ -39,15 +39,15 @@ Procedure
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+==========================================================================================================================================================================+
| \* Job Name | Name of a new job. The name must be unique. |
| ``*`` Job Name | Name of a new job. The name must be unique. |
| | |
| | Enter 4 to 63 characters starting with a lowercase letter and ending with a letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster | Cluster to which a new job belongs. |
| ``*`` Cluster | Cluster to which a new job belongs. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Namespace | Namespace to which the new job belongs. By default, this parameter is set to **default**. |
| ``*`` Namespace | Namespace to which the new job belongs. By default, this parameter is set to **default**. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Instances | Number of pods in this job. A job can have one or more pods. You can specify the number of pods. The default value is **1**. |
| ``*``\ Instances | Number of pods in this job. A job can have one or more pods. You can specify the number of pods. The default value is **1**. |
| | |
| | Each job pod consists of the same containers. Configuring multiple job pods can ensure high availability. The job can continue to run even if one of the pods is faulty. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@ -75,9 +75,9 @@ Procedure
+===================================+==============================================================================================================================================================================================================================================================================================================+
| Image | Name of the image. You can click **Change Image** to update it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Image Version | Select the image tag to be deployed. |
| ``*``\ Image Version | Select the image tag to be deployed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Container Name | Name of the container. You can modify it. |
| ``*``\ Container Name | Name of the container. You can modify it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Container Resources | **CPU** |
| | |

14
umn/source/workloads/creating_a_statefulset.rst
View File

@ -41,7 +41,7 @@ CCE provides multiple methods for creating a workload. You can use any of the fo
When you click **Create YAML** on the right of the console, do not create multiple YAML files in the YAML definition pane displayed. You need to create them one by one. Otherwise, an error will be reported during the creation.
#. Log in to the CCE console. In the navigation pane, choose **Workloads** > **StatefulSets**. On the displayed page, click **Create StatefulSet**. Set basic workload parameters as described in :ref:`Table 1 <cce_01_0048__table12741447488>`. The parameters marked with an asterisk (*) are mandatory.
#. Log in to the CCE console. In the navigation pane, choose **Workloads** > **StatefulSets**. On the displayed page, click **Create StatefulSet**. Set basic workload parameters as described in :ref:`Table 1 <cce_01_0048__table12741447488>`. The parameters marked with an asterisk (``*``) are mandatory.
.. _cce_01_0048__table12741447488:
@ -50,15 +50,15 @@ CCE provides multiple methods for creating a workload. You can use any of the fo
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description |
+===================================+==============================================================================================================================================================================================================================================================================================+
| \* Workload Name | Name of a workload, which must be unique. |
| ``*`` Workload Name | Name of a workload, which must be unique. |
| | |
| | Enter 4 to 52 characters starting with a lowercase letter and ending with a letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Cluster Name | Cluster to which the workload belongs. |
| ``*`` Cluster Name | Cluster to which the workload belongs. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Namespace | In a single cluster, data in different namespaces is isolated from each other. This enables applications to share the services of the same cluster without interfering each other. If no namespace is set, the **default** namespace is used. |
| ``*`` Namespace | In a single cluster, data in different namespaces is isolated from each other. This enables applications to share the services of the same cluster without interfering each other. If no namespace is set, the **default** namespace is used. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \* Instances | Number of pods in a workload. A workload can have one or more pods. The default value is **2**. You can customize the value, for example, setting it to **1**. |
| ``*`` Instances | Number of pods in a workload. A workload can have one or more pods. The default value is **2**. You can customize the value, for example, setting it to **1**. |
| | |
| | Each workload pod consists of the same containers. You can configure multiple pods for a workload to ensure high reliability. For such a workload, if one pod is faulty, the workload can still run properly. If only one pod is used, a node or pod exception may cause service exceptions. |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@ -95,9 +95,9 @@ CCE provides multiple methods for creating a workload. You can use any of the fo
+===================================+==============================================================================================================================================================================================================================================================================================================+
| Image Name | Name of the image. You can click **Change Image** to update it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Image Version | Select the image tag to be deployed. |
| ``*``\ Image Version | Select the image tag to be deployed. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| \*Container Name | Name of the container. You can modify it. |
| ``*``\ Container Name | Name of the container. You can modify it. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Privileged Container | Programs in a privileged container have certain privileges. |
| | |