Elastic Scaling of CCE Pods to CCI

CCE Cloud Bursting Engine for CCI functions as a virtual kubelet to connect Kubernetes clusters to APIs of other platforms. This add-on is mainly used to extend Kubernetes APIs to serverless container services such as Huawei Cloud CCI.

With this add-on, you can scale Deployments, StatefulSets, Jobs, and CronJobs running in CCE clusters to Cloud Container Instance (CCI) during peak hours. In this way, you can reduce consumption caused by cluster scaling.

Installing the Add-on

Log in to the CCE console.
Click the name of the target CCE cluster to go to the cluster console.
In the navigation pane on the left, choose Add-ons.
Select the CCE Cloud Bursting Engine for CCI add-on and click Install.

Configure the add-on parameters.

**Table 1** Add-on parameters
Parameter	Description
Version	Add-on version. There is a mapping between add-on versions and CCE cluster versions. For more details, see "Change History" in CCE Cloud Bursting Engine for CCI.
Specifications	Number of pods required for a workload.
Networking	If this option is enabled, pods in a CCE cluster can communicate with the pods in CCI. For details, see Networking.

Creating a Workload

Log in to the CCE console.
Click the name of the target CCE cluster to go to the cluster console.
In the navigation pane on the left, choose Workloads.
Click Create Workload. For details, see Creating a Workload.
Specify basic information. Set Burst to CCI to Force scheduling. For more information about scheduling policies, see Scaling Pods to CCI.
Configure the container parameters.
Click Create Workload.
On the Workloads page, click the name of the created workload to go to the workload details page.
View the node where the workload is running. If the workload is running on a CCI node, it has been scheduled to CCI.

Uninstalling the Add-on

Log in to the CCE console.
Click the name of the target CCE cluster to go to the cluster console.
In the navigation pane on the left, choose Add-ons.

Select the CCE Cloud Bursting Engine for CCI add-on and click Uninstall.

**Table 2** Special scenarios for uninstalling the add-on
Scenario	Symptom	Description
There are no nodes in the CCE cluster that the bursting add-on needs to be uninstalled from.	Failed to uninstall the bursting add-on.	If the bursting add-on is uninstalled from the cluster, a job for clearing resources will be started in the cluster. To ensure that the job can be started, there is at least one node in the cluster that can be scheduled.
The CCE cluster is deleted, but the bursting add-on is not uninstalled.	There are residual resources in the namespace on CCI. If the resources are not free, additional expenditures will be generated.	The cluster is deleted, but the resource clearing job is not executed. You can manually clear the namespace and residual resources.