Help Center/ Cloud Container Instance (CCI)/ User Guide/ Using CCI with CCE/ Add-on Overview
Updated on 2026-06-17 GMT+08:00
View PDF
Share

Add-on Overview

This section describes the functions, resource usages, and custom annotations of the CCE Cloud Bursting Engine for CCI add-on (also called the bursting add-on).

This add-on functions as a virtual kubelet to connect Kubernetes clusters to APIs of other platforms. It is mainly used to extend Kubernetes APIs to CCI.

With this add-on, you can schedule Deployments, StatefulSets, jobs, and CronJobs in CCE clusters to CCI 2.0 during peak hours. In this way, you can reduce the consumption caused by cluster scaling.

Functions

When using the CCE Cloud Bursting Engine for CCI add-on, pay attention to the workload delivery and scheduling.

Figure 1 How the add-on schedules extra workloads in a CCE cluster to CCI

Scheduling workloads to CCI is closely related to your workload settings.

Configuration Item

Description

Function

Reference

Scheduling

You can manage pods in a CCE cluster in different ways to control their scheduling to CCI. Workloads can be scheduled to CCI 2.0 to improve resource utilization of clusters.
  • There are three scheduling policies.
  • There are two methods for managing scheduling policies.
  • Multiple virtual nodes can be scheduled.

Configuring a Scheduling Policy

Resource quotas

You can configure fields such as cpu and memory to specify resource requests and limits for containers in a pod. The resource quotas for the add-on are rounded up to meet the requirements of CCI 2.0.

Appropriate pod resource quotas are selected.

Upgrading Pod Resource Specifications

Images

You can configure service images and run your service containers in Huawei Cloud CCE clusters and CCI.
  • The image configuration mode can be changed.
  • Images can be upgraded in-place.

Images

Storage

You can mount storage volumes to workloads for persistent data storage.
  • There are multiple storage volume types.
  • The hostPath volume of a workload can be replaced.

Overview

Networking

You can plan the network topology between CCE clusters and CCI.
  • Pods in CCI can be exposed through a Service.
  • Pods in a CCE cluster can communicate with pods in CCI through a Service.
  • cluster-dns can be specified.
  • Global EIPs can be bound to pods.

Networking

Monitoring

You can install add-ons to connect to Monitoring Center for better O&M of pods for workloads scheduled to CCI.
  • You can view data on the CCI 2.0 console.

Monitoring

Resource Usage Description

The following table describes the Huawei cloud services involved when the CCE Cloud Bursting Engine for CCI add-on is installed in a CCE cluster.

Involved Cloud Service

Resource Description

Remarks

CCI 2.0

A namespace called bursting-{CCE-cluster-ID} will be created for the add-on in CCI 2.0.
  • Do not use this namespace in CCI 2.0. If you need to use CCI 2.0, create a namespace.
  • CCI 2.0 namespaces are free for use.

CCE

Workloads, secrets, ConfigMaps, PVs, and PVCs in CCE are synchronized to CCI and occupy CCE node resources.
  • If there are 1,000 pods and 1,000 ConfigMaps in your CCE cluster, you can apply for 2 cores and 4 GiB of memory.
  • If there are 2,000 pods and 2,000 ConfigMaps in your CCE cluster, you can apply for 4 cores and 8 GiB of memory.
  • If there are 4,000 pods and 4,000 ConfigMaps in your CCE cluster, you can apply for 8 cores and 16 GiB of memory.

ELB

If pods in a CCE cluster can communicate with the pods in CCI through the Service, the CCE Cloud Bursting Engine for CCI add-on automatically creates a shared load balancer.
  • The shared load balancer is named cce-lb-xxx.
  • The load balancer will be automatically deleted if the add-on is uninstalled or the network interconnection is disabled.

VPC

Workloads scheduled to CCI use the same VPC as the CCE cluster.

The CIDR block of the Service in the CCI namespace is 10.247.0.0/16. Do not configure the same CIDR block for the VPC subnet of the CCE cluster.

SWR

When you create a workload in CCE, the image can be pulled from Huawei Cloud SWR.

Ensure that your image has been pushed to SWR.

Pod Annotations

If the CCE Cloud Bursting Engine for CCI add-on is installed in a CCE cluster, custom annotations are required. The following table describes the annotations.

Annotation Key

Description

Reference

scheduling.cci.io/managed-by-profile

Profile that manages the pods of the workloads scheduled to CCI

Configuring a Scheduling Policy

resource.cci.io/size

vCPUs and memory of pods after the workloads are scheduled to CCI

Upgrading Pod Resource Specifications

bursting.cci.io/image-replacement

Annotation for replacing image path prefixes

Images

Release History

Table 1 CCE Cloud Bursting Engine for CCI updates

Add-on Version

Supported Cluster Version

New Feature

1.5.85

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

v1.34

v1.35

Supported clusters v1.35.

1.5.81

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

v1.34
  • Supported obtaining IAM credentials using pod identities.
  • Supported custom agencies.

1.5.72

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

v1.34

Supported clusters v1.34.

1.5.71

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

Pod distribution remains consistent before and after a rolling upgrade.

1.5.67

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

Fixed some issues.

1.5.65

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

Fixed some issues.

1.5.63

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33

ConfigMaps and secrets can be mounted across namespaces.

1.5.58

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

v1.33
  • Supported CCE clusters v1.33.
  • Adapted extensionprofile to AllowHostPath.

1.5.44

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32
  • Supported CCE clusters v1.32.
  • Supported automatic injection of sidecar containers.
  • Supported ARM64 nodes.

1.5.29

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

Specific subnets can be configured for pods.

1.5.28

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

Optimized some functions.

1.5.27

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

Supported CCE clusters v1.31.

1.5.26

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

Fixed some issues.

1.5.24

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

Optimized some functions.

1.5.16

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

Compacted pod CPU and memory resources.

1.5.8

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

Supported CCE clusters v1.29.

1.3.57

v1.21

v1.23

v1.25

v1.27

v1.28

Supported CCE clusters v1.28.

1.3.48

v1.21

v1.23

v1.25

v1.27
  • Clusters v1.25 and v1.27 are supported.
  • Supported JuiceFS.

1.3.25

v1.17

v1.19

v1.21

v1.23
  • Supported Downward API volumes.
  • Supported Projected volumes.
  • Supported custom storage classes.

1.3.19

v1.17

v1.19

v1.21

v1.23

Supported schedule profile.

1.3.7

v1.17

v1.19

v1.21

v1.23

Clusters v1.21 and v1.23 are supported.

1.2.12

v1.13

v1.15

v1.17

v1.19
  • Added some metrics.
  • Supported HPA and CustomHPA.
  • Enabled the hostPath in the pod that is scaled to CCI to be converted to other types of storage.
  • Fixed the issue where Kubernetes Dashboard could not be run from the terminal.

1.2.5

v1.13

v1.15

v1.17

v1.19
  • Automatically cleared CCI resources that are no longer used by pods.
  • Requests and Limits can be set to different values. When pods are scaled to CCI, their resource requests are subject to the resource limits.
  • Fixed the issue where the add-on fails to be uninstalled when the CCI namespace does not exist.
  • Added the function of intercepting creation requests when the pod specifications exceed the CCI limit.

1.2.0

v1.13

v1.15

v1.17

v1.19
  • Supported clusters v1.19.
  • Supported SFS and SFS Turbo storage.
  • Supported CronJobs.
  • Supported envFrom configuration.
  • Supported automatic logs dumping.
  • Shielded TCP socket health check.
  • Supported resource tags (pod-tag).
  • Improved performance and reliability.
  • Resolved some known issues.

1.0.5

v1.13

v1.15

v1.17

Supported clusters v1.17.
Parent Topic: Using CCI with CCE