Introduction to CCE Cloud Bursting Engine for CCI
Overview
This section describes the functions, required resources, and custom annotations of CCE Cloud Bursting Engine for CCI (also called as the bursting add-on).
Functions
The figure shows how workloads running in a CCE cluster with the bursting add-on installed are scheduled to CCI. In this process, you only need to take care of workload creation and scheduling.
![](https://support.huaweicloud.com/intl/en-us/usermanual-cci/public_sys-resources/caution_3.0-en-us.png)
Scheduling workloads to CCI is closely related to your workload settings.
Pod Configuration Item |
Description |
Specification |
Reference |
---|---|---|---|
Scheduling |
You can manage pods in a CCE cluster in multiple ways to control their scheduling to CCI. You can also configure scheduling policies to improve cluster resource utilization. |
|
|
Images |
You can configure service images and run your service containers in Huawei Cloud CCE clusters and CCI. |
|
|
Storage |
You can mount storage volumes to workloads for persistent data storage. |
|
|
Networking |
You can plan the network topology between CCE clusters and CCI. |
|
|
Logging |
You can install the Cloud Native Logging and bursting add-ons at the same time to collect pod logs in CCI. |
|
|
Monitoring |
You can install add-ons to connect to Monitoring Center for better O&M of pods scheduled to CCI. |
|
Resource Usage Description
The following table describes Huawei Cloud services involved when the bursting add-on is installed in a CCE cluster.
Involved Cloud Service |
Resource Description |
Remarks |
---|---|---|
CCI |
A namespace called cce-burst-{CCE cluster ID} will be created for the bursting add-on in CCI. |
|
CCE |
Workloads, secrets, CongfigMaps, PVs, and PVCs in CCE are synchronized to CCI and occupy CCE node resources. |
|
ELB |
If pods in a CCE cluster can communicate with the pods CCI through the Service, the bursting add-on automatically creates a shared load balancer. |
|
VPC |
Pods 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 bursting 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 scheduled to CCI |
|
coordinator.cci.io/inject-volumes |
Annotation injected by the cloud native logging add-on for collecting CCI pod logs |
|
logconf.k8s.io/fluent-bit-configmap-reference |
Annotation injected by the cloud native logging add-on for collecting CCI pod logs |
|
logconfigs.logging.openvessel.io |
Annotation injected by the cloud native logging add-on for collecting CCI pod logs |
|
sandbox-volume.openvessel.io/volume-names |
Annotation injected by the cloud native logging add-on for collecting CCI pod logs |
|
coordinator.cci.io/image-replacement |
Annotation for replacing image path prefixes |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot