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-03-11 16:50:26 +00:00
parent e9b73b536f
commit a1b7cd047d
115 changed files with 1558 additions and 705 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
umn/source/_static/images/en-us_image_0000001171703840.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 285 KiB

BIN
umn/source/_static/images/en-us_image_0000001199021274.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 9.5 KiB

BIN
umn/source/_static/images/en-us_image_0000001199021280.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 673 B

BIN
umn/source/_static/images/en-us_image_0000001199181292.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 124 KiB

BIN
umn/source/_static/images/en-us_image_0000001199341268.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 643 B

BIN
umn/source/_static/images/en-us_image_0000001199501182.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 22 KiB

BIN
umn/source/_static/images/en-us_image_0000001199501252.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 35 KiB

BIN
umn/source/_static/images/en-us_image_0000001207036074.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 35 KiB

BIN
umn/source/_static/images/en-us_image_0000001207511384.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 48 KiB

BIN
umn/source/_static/images/en-us_image_0000001217183707.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 43 KiB

After

Width:  |  Height:  |  Size: 47 KiB

BIN
umn/source/_static/images/en-us_image_0000001276433425.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 174 KiB

BIN
umn/source/_static/images/en-us_image_0000001280547449.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 70 KiB

BIN
umn/source/_static/images/en-us_image_0000001378942548.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 39 KiB

0
umn/source/_static/images/en-us_image_0000001248666457.png → umn/source/_static/images/en-us_image_0000001464878016.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 164 B

After

Width:  |  Height:  |  Size: 164 B

0
umn/source/_static/images/en-us_image_0000001248946053.png → umn/source/_static/images/en-us_image_0000001465197524.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 164 B

After

Width:  |  Height:  |  Size: 164 B

BIN
umn/source/_static/images/en-us_image_0000001480191270.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 220 KiB

BIN
umn/source/_static/images/en-us_image_0000001482546084.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 24 KiB

BIN
umn/source/_static/images/en-us_image_0000001482796460.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

0
umn/source/_static/images/en-us_image_0000001248946421.png → umn/source/_static/images/en-us_image_0000001515838557.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 164 B

After

Width:  |  Height:  |  Size: 164 B

0
umn/source/_static/images/en-us_image_0000001249026401.png → umn/source/_static/images/en-us_image_0000001515917789.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 164 B

After

Width:  |  Height:  |  Size: 164 B

BIN
umn/source/_static/images/en-us_image_0000001528627005.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BIN
umn/source/_static/images/en-us_image_0000001531373685.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

BIN
umn/source/_static/images/en-us_image_0000001531533045.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 289 KiB

BIN
umn/source/_static/images/en-us_image_0000001531533921.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 48 KiB

BIN
umn/source/_static/images/en-us_image_0000001533585325.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
umn/source/_static/images/en-us_image_0000001533586881.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 231 B

2
umn/source/add-ons/autoscaler.rst
View File

@ -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 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. | | Total Memory (GB) | Maximum sum of memory of all nodes in a cluster, within which cluster scale-out is performed. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

14
umn/source/add-ons/coredns_system_resource_add-on_mandatory.rst
View File

@ -40,17 +40,17 @@ This add-on has been installed by default. If it is uninstalled due to some reas
.. table:: **Table 1** coredns add-on parameters .. table:: **Table 1** coredns add-on parameters
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description | | Parameter | Description |
+===================================+===========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ +===================================+=========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+
| Add-on Specifications | Concurrent domain name resolution ability. Select add-on specifications that best fit your needs. | | Add-on Specifications | Concurrent domain name resolution ability. Select add-on specifications that best fit your needs. |
| | | | | |
| | If you select **Custom qps**, the domain name resolution QPS provided by CoreDNS is positively correlated with the CPU consumption. Adjust the number of pods and container CPU/memory quotas as required. | | | If you select **Custom qps**, the domain name resolution QPS provided by CoreDNS is positively correlated with the CPU consumption. Adjust the number of pods and container CPU/memory quotas as required. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Pods | Number of pods that will be created to match the selected add-on specifications. | | Pods | Number of pods that will be created to match the selected add-on specifications. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Containers | CPU and memory quotas of the container allowed for the selected add-on specifications. | | Containers | CPU and memory quotas of the container allowed for the selected add-on specifications. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameters | - **parameterSyncStrategy**: indicates whether to configure consistency check when an add-on is upgraded. | | Parameters | - **parameterSyncStrategy**: indicates whether to configure consistency check when an add-on is upgraded. |
| | | | | |
| | - **ensureConsistent**: indicates that the configuration consistency check is enabled. If the configuration recorded in the cluster is inconsistent with the actual configuration, the add-on cannot be upgraded. | | | - **ensureConsistent**: indicates that the configuration consistency check is enabled. If the configuration recorded in the cluster is inconsistent with the actual configuration, the add-on cannot be upgraded. |
@ -60,7 +60,7 @@ This add-on has been installed by default. If it is uninstalled due to some reas
| | | | | |
| | - **upstream_nameservers**: IP address of the upstream DNS server. | | | - **upstream_nameservers**: IP address of the upstream DNS server. |
| | | | | |
| | - **servers**: The servers configuration is available since coredns 1.23.1. You can customize the servers configuration. For details, see `dns-custom-nameservers <https://kubernetes.io/zh/docs/tasks/administer-cluster/dns-custom-nameservers>`__. **plugins** indicates the configuration of each component in coredns (https://coredns.io/manual/plugins/). You are advised to retain the default configurations in common scenarios to prevent CoreDNS from being unavailable due to configuration errors. Each plugin component contains **name**, **parameters** (optional), and **configBlock** (optional). The format of the generated Corefile is as follows: | | | - **servers**: The servers configuration is available since coredns 1.23.1. You can customize the servers configuration. For details, see `dns-custom-nameservers <https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/>`__. **plugins** indicates the configuration of each component in coredns (https://coredns.io/manual/plugins/). You are advised to retain the default configurations in common scenarios to prevent CoreDNS from being unavailable due to configuration errors. Each plugin component contains **name**, **parameters** (optional), and **configBlock** (optional). The format of the generated Corefile is as follows: |
| | | | | |
| | $name $parameters { | | | $name $parameters { |
| | | | | |
@ -134,7 +134,7 @@ This add-on has been installed by default. If it is uninstalled due to some reas
| | }, | | | }, |
| | "upstream_nameservers": ["8.8.8.8", "8.8.4.4"] | | | "upstream_nameservers": ["8.8.8.8", "8.8.4.4"] |
| | } | | | } |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. _cce_10_0129__table1420814384015: .. _cce_10_0129__table1420814384015:

2
umn/source/add-ons/everest_system_resource_add-on_mandatory.rst
View File

@ -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**. #. 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. The everest add-on contains the following containers. You can adjust the specifications as required.

10
umn/source/add-ons/gpu-beta.rst
View File

@ -26,7 +26,7 @@ Installing the Add-on
.. important:: .. 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. - 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. - 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. - 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: .. _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 :alt: **Figure 1** Setting parameters
**Figure 1** Setting parameters **Figure 1** Setting parameters
@ -77,20 +77,20 @@ Obtaining the Driver Link from Public Network
.. _cce_10_0141__fig7873421145213: .. _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 :alt: **Figure 2** Driver information
**Figure 2** Driver information **Figure 2** Driver information
6. Obtain the driver link in either of the following ways: 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. - 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: .. _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 :alt: **Figure 3** Obtaining the link
**Figure 3** Obtaining the link **Figure 3** Obtaining the link

18
umn/source/add-ons/overview.rst
View File

@ -9,18 +9,20 @@ CCE provides multiple types of add-ons to extend cluster functions and meet feat
.. table:: **Table 1** Add-on list .. table:: **Table 1** Add-on list
+-------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Add-on Name | Introduction | | 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:`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:`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:`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:`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:`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:`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. |
+-------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/add-ons/volcano.rst
View File

@ -101,7 +101,7 @@ Installing the Add-on
+----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+ +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+
| priority | The priority plugin schedules pods based on the custom workload priority. | ``-`` | ``-`` | | 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: | | | | | - plugins: |
| | | | - name: overcommit | | | | | - name: overcommit |

4
umn/source/auto_scaling/index.rst
View File

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

2
umn/source/auto_scaling/scaling_a_cluster_node/creating_a_node_scaling_policy.rst → umn/source/auto_scaling/scaling_a_node/creating_a_node_scaling_policy.rst
View File

@ -73,7 +73,7 @@ Procedure
- **Periodic**: - **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. **Action**: Set an action to be performed when the trigger condition is met.

4
umn/source/auto_scaling/scaling_a_cluster_node/index.rst → umn/source/auto_scaling/scaling_a_node/index.rst
View File

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

8
umn/source/auto_scaling/scaling_a_cluster_node/managing_node_scaling_policies.rst → umn/source/auto_scaling/scaling_a_node/managing_node_scaling_policies.rst
View File

@ -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. #. 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. #. 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:: .. 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 Deleting a Node Scaling Policy
------------------------------ ------------------------------

0
umn/source/auto_scaling/scaling_a_cluster_node/node_scaling_mechanisms.rst → umn/source/auto_scaling/scaling_a_node/node_scaling_mechanisms.rst
View File

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

@ -17,7 +17,7 @@ Notes and Constraints
- HPA policies can be created only for clusters of v1.13 or later. - HPA policies can be created only for clusters of v1.13 or later.
- Only one policy can be created for each workload. That is, if you have created an HPA policy, you cannot create other HPA policies for the workload. You can delete the created HPA policy and create a new one. - Only one policy can be created for each workload. You can create an HPA policy.
- For clusters earlier than v1.19.10, if an HPA policy is used to scale out a workload with EVS volumes mounted, the existing pods cannot be read or written when a new pod is scheduled to another node. - For clusters earlier than v1.19.10, if an HPA policy is used to scale out a workload with EVS volumes mounted, the existing pods cannot be read or written when a new pod is scheduled to another node.
@ -36,60 +36,60 @@ Procedure
.. table:: **Table 1** HPA policy parameters .. table:: **Table 1** HPA policy parameters
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description | | Parameter | Description |
+===================================+===========================================================================================================================================================================================================================+ +==============================================================+===========================================================================================================================================================================================================================+
| Policy Name | Name of the policy to be created. Set this parameter as required. | | Policy Name | Name of the policy to be created. Set this parameter as required. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Namespace | Namespace to which the workload belongs. | | Namespace | Namespace to which the workload belongs. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Associated Workload | Workload with which the HPA policy is associated. | | Associated Workload | Workload with which the HPA policy is associated. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Pod Range | Minimum and maximum numbers of pods. | | Pod Range | Minimum and maximum numbers of pods. |
| | | | | |
| | When a policy is triggered, the workload pods are scaled within this range. | | | When a policy is triggered, the workload pods are scaled within this range. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Cooldown Period | Interval between a scale-in and a scale-out. The unit is minute. **The interval cannot be shorter than 1 minute.** | | Cooldown Period | Interval between a scale-in and a scale-out. The unit is minute. **The interval cannot be shorter than 1 minute.** |
| | | | | |
| | **This parameter is available only for clusters of v1.15 and later. It is not supported in clusters of v1.13 or earlier.** | | | **This parameter is available only for clusters of v1.15 and later. It is not supported in clusters of v1.13 or earlier.** |
| | | | | |
| | This parameter indicates the interval between consecutive scaling operations. The cooldown period ensures that a scaling operation is initiated only when the previous one is completed and the system is running stably. | | | This parameter indicates the interval between consecutive scaling operations. The cooldown period ensures that a scaling operation is initiated only when the previous one is completed and the system is running stably. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Rules | Policy rules can be based on system metrics or custom metrics. | | System Policy | - **Metric**: You can select **CPU usage** or **Memory usage**. |
| | |
| | **System Policy** |
| | |
| | - **Metric**: You can select **CPU usage** or **Memory usage**. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | Usage = CPUs or memory used by pods/Requested CPUs or memory. | | | Usage = CPUs or memory used by pods/Requested CPUs or memory. |
| | | | | |
| | - **Expected Value**: Enter the expected average resource usage. | | | - **Desired Value**: Enter the desired average resource usage. |
| | | | | |
| | This parameter indicates the expected value of the selected metric. The number of new pods required (rounded up) = Current metric value/Expected value x Number of current pods | | | This parameter indicates the desired value of the selected metric. Number of pods to be scaled (rounded up) = (Current metric value/Desired value) x Number of current pods |
| | | | | |
| | - **Threshold**: Enter the scaling thresholds. | | | .. note:: |
| | |
| | When calculating the number of pods to be added or reduced, the HPA policy uses the maximum number of pods in the last 5 minutes. |
| | |
| | - **Tolerance Range**: Scaling is not triggered when the metric value is within the tolerance range. The desired value must be within the tolerance range. |
| | | | | |
| | If the metric value is greater than the scale-in threshold and less than the scale-out threshold, no scaling is triggered. **This parameter is supported only in clusters of v1.15 or later.** | | | If the metric value is greater than the scale-in threshold and less than the scale-out threshold, no scaling is triggered. **This parameter is supported only in clusters of v1.15 or later.** |
+--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Custom Policy (supported only in clusters of v1.15 or later) | .. note:: |
| | | | | |
| | **Custom policy (supported only in clusters of v1.15 or later)** | | | Before setting a custom policy, you need to install an add-on that supports custom metric collection in the cluster, for example, prometheus add-on. |
| | | | | |
| | - **Metric Name**: name of the custom metric. You can select a name as prompted. | | | - **Metric Name**: name of the custom metric. You can select a name as prompted. |
| | | | | |
| | For details, see :ref:`Custom Monitoring <cce_10_0201>`. | | | For details, see :ref:`Custom Monitoring <cce_10_0201>`. |
| | | | | |
| | - **Source**: Select an object type from the drop-down list. You can select **Pod**. | | | - **Metric Source**: Select an object type from the drop-down list. You can select **Pod**. |
| | | | | |
| | - **Expected Value**: the average metric value of all pods. | | | - **Desired Value**: the average metric value of all pods. Number of pods to be scaled (rounded up) = (Current metric value/Desired value) x Number of current pods |
| | |
| | - **Threshold**: Triggers scaling only when the metric value is within the thresholds. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | When calculating the number of pods to be added or reduced, the HPA policy uses the maximum number of pods in the last 5 minutes. | | | When calculating the number of pods to be added or reduced, the HPA policy uses the maximum number of pods in the last 5 minutes. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| | - **Tolerance Range**: Scaling is not triggered when the metric value is within the tolerance range. The desired value must be within the tolerance range. |
+--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
#. 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**. #. Click **Create**.
#. On the **Workload Scaling** tab page, you can view the newly created HPA policy.

6
umn/source/auto_scaling/scaling_a_workload/managing_workload_scaling_policies.rst
View File

@ -21,7 +21,11 @@ You can view the rules, status, and events of an HPA policy and handle exception
.. note:: .. 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 .. table:: **Table 1** Event types and names

2
umn/source/auto_scaling/using_hpa_and_ca_for_auto_scaling_of_workloads_and_nodes.rst
View File

@ -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. #. 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. - **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. - **Max. Nodes**: Set it to **5**, indicating the maximum number of nodes in a node pool.
- **Specifications**: 2 vCPUs \| 4 GiB - **Specifications**: 2 vCPUs \| 4 GiB

2
umn/source/best_practice/auto_scaling/using_hpa_and_ca_for_auto_scaling_of_workloads_and_nodes.rst
View File

@ -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. #. 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. - **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. - **Max. Nodes**: Set it to **5**, indicating the maximum number of nodes in a node pool.
- **Specifications**: 2 vCPUs \| 4 GiB - **Specifications**: 2 vCPUs \| 4 GiB

2
umn/source/best_practice/migration/migrating_on-premises_kubernetes_clusters_to_cce/migrating_resources_in_a_cluster.rst
View File

@ -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>`. #. 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

2
umn/source/best_practice/migration/migrating_on-premises_kubernetes_clusters_to_cce/planning_resources_for_the_target_cluster.rst
View File

@ -18,7 +18,7 @@ CCE allows you to customize cluster resources to meet various service requiremen
+-----------------+-----------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------+ +-----------------+-----------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------+
| Resource | Key Performance Parameter | Description | Example Value | | 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. | | | | | - **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 | | | **\***\ 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 |

2
umn/source/best_practice/migration/migrating_on-premises_kubernetes_clusters_to_cce/updating_resources_accordingly.rst
View File

@ -20,7 +20,7 @@ The WordPress and MySQL images used in this example can be pulled from SWR. Ther
.. code-block:: .. 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: #. Run the following command to modify the workload and replace the **image** field in the YAML file with the image path:

2
umn/source/helms/deploying_an_application_from_a_chart.rst → umn/source/charts/deploying_an_application_from_a_chart.rst
View File

@ -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**. #. 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>`. #. Set workload installation parameters by referring to :ref:`Table 2 <cce_10_0146__t26bc1c499f114b5185e5edcf61e44d95>`.

4
umn/source/helms/index.rst → umn/source/charts/index.rst
View File

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

0
umn/source/helms/overview.rst → umn/source/charts/overview.rst
View File

2
umn/source/clusters/cluster_overview/release_notes/cce_kubernetes_1.25_release_notes.rst
View File

@ -25,7 +25,7 @@ Resource Changes and Deprecations
**Kubernetes 1.24 Release Notes** **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. - 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**. - **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. - The **Service.Spec.LoadBalancerIP** tag is deprecated and may be removed in later versions. Use a customized annotation.

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

@ -16,6 +16,7 @@ Notes and Constraints
- You can create a maximum of 50 clusters in a single region. - You can create a maximum of 50 clusters in a single region.
- After a cluster is created, the following items cannot be changed: - After a cluster is created, the following items cannot be changed:
- Cluster type
- Number of master nodes in the cluster - Number of master nodes in the cluster
- AZ of a master node - 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 - 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** **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. - **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**. - 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. - 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**. #. Click **Next: Add-on Configuration**.
By default, :ref:`cordens <cce_10_0129>` and :ref:`everest <cce_10_0066>` add-ons are installed. By default, :ref:`cordens <cce_10_0129>` and :ref:`everest <cce_10_0066>` add-ons are installed.

4
umn/source/clusters/creating_a_cce_turbo_cluster.rst
View File

@ -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. - **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. - **Host**: Master nodes are created on different hosts in the same AZ.
- **Custom**: You can determine the location of each master node. - **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**. - 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. - 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**. #. Click **Next: Add-on Configuration**.
By default, :ref:`cordens <cce_10_0129>` and :ref:`everest <cce_10_0066>` add-ons are installed. By default, :ref:`cordens <cce_10_0129>` and :ref:`everest <cce_10_0066>` add-ons are installed.

Some files were not shown because too many files have changed in this diff Show More