Enabling Cloud Native Hybrid Deployment

Prerequisites

• A CCE standard or Turbo cluster is available and the cluster version meets the following requirements:
  • v1.23: v1.23.9-r0 or later
  • v1.25: v1.25.4-r0 or later
• Volcano of v1.10.0 or later has been installed in the cluster.

Notes and Constraints

• After cloud native hybrid deployment is enabled, the Volcano scheduler will automatically enable the oversubscription add-on. Ensure the add-on remains enabled during the usage of cloud native hybrid deployment.
• The hybrid deployment agent is deployed in affinity mode as a DaemonSet only on an x86 node that runs Huawei Cloud EulerOS 2.0.
• The default node pool does not allow the modification of hybrid configurations.

Procedure

Cloud native hybrid deployment is managed by node pool. You need to enable hybrid deployment in the target node pool and configure it accordingly. By default, all hybrid deployment capabilities are enabled and default parameter values are used in the configuration. You can modify the configuration as needed.

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. Choose Nodes in the navigation pane and choose More > Mixed configuration in the Operation column of the target node pool.

   

3. If Volcano does not have hybrid deployment of online and offline services enabled, you can enable this function on the configuration page that is displayed and continue with the configuration after installing or updating Volcano.

   

4. On the Mixed configuration page, enable hybrid deployment.

   

   You can configure the parameters listed in the following table.

   Parameter	Default Setting	Description
   CPU burst elastic traffic limiting	Enabled	After this function is enabled, the CPU usage of a pod can temporarily exceed the CPU limit when there are enough node resources. This reduces response latency for long-tail services. For details, see CPU Burst.
   Egress network bandwidth	Enabled	In CCE Turbo clusters, networks of online and offline services can be isolated. For details, see Guaranteed Egress Network Bandwidth.
   Resource Oversubscription	Enabled	Node resources can be oversubscribed by collecting node load information in real time and detecting the resources that have been allocated but not used by the nodes. Select the resource type that requires oversubscription. By default, oversubscription is enabled for both CPU and memory. For details, see Dynamic Resource Oversubscription. NOTE: If the cluster version does not meet specific requirements, resource oversubscription will not take effect. For details, see Table 1. When you modify the resource oversubscription configuration: You can add oversubscribed resources (such as CPU and memory) at any time. You can reduce oversubscribed resource types, for example, from CPU and memory to only CPU, only when the resource allocation rate does not exceed 100%.

5. Click OK.