- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
Developer Guide
- Overview
- Using Native kubectl (Recommended)
- Namespace and Network
- Pod
- Label
- Deployment
- EIPPool
- EIP
- Pod Resource Monitoring Metric
- Collecting Pod Logs
- Managing Network Access Through Service and Ingress
- Using PersistentVolumeClaim to Apply for Persistent Storage
- ConfigMap and Secret
- Creating a Workload Using Job and Cron Job
- YAML Syntax
-
API Reference
- Before You Start
- Calling APIs
- Getting Started
- Proprietary APIs
-
Kubernetes APIs
- ConfigMap
- Pod
- StorageClass
- Service
-
Deployment
- Querying All Deployments
- Deleting All Deployments in a Namespace
- Querying Deployments in a Namespace
- Creating a Deployment
- Deleting a Deployment
- Querying a Deployment
- Updating a Deployment
- Replacing a Deployment
- Querying the Scaling Operation of a Specified Deployment
- Updating the Scaling Operation of a Specified Deployment
- Replacing the Scaling Operation of a Specified Deployment
- Querying the Status of a Deployment
- Ingress
- OpenAPIv2
- VolcanoJob
- Namespace
- ClusterRole
- Secret
- Endpoint
- ResourceQuota
- CronJob
-
API groups
- Querying API Versions
- Querying All APIs of v1
- Querying an APIGroupList
- Querying APIGroup (/apis/apps)
- Querying APIs of apps/v1
- Querying an APIGroup (/apis/batch)
- Querying an APIGroup (/apis/batch.volcano.sh)
- Querying All APIs of batch.volcano.sh/v1alpha1
- Querying All APIs of batch/v1
- Querying All APIs of batch/v1beta1
- Querying an APIGroup (/apis/crd.yangtse.cni)
- Querying All APIs of crd.yangtse.cni/v1
- Querying an APIGroup (/apis/extensions)
- Querying All APIs of extensions/v1beta1
- Querying an APIGroup (/apis/metrics.k8s.io)
- Querying All APIs of metrics.k8s.io/v1beta1
- Querying an APIGroup (/apis/networking.cci.io)
- Querying All APIs of networking.cci.io/v1beta1
- Querying an APIGroup (/apis/rbac.authorization.k8s.io)
- Querying All APIs of rbac.authorization.k8s.io/v1
- Event
- PersistentVolumeClaim
- RoleBinding
- StatefulSet
- Job
- ReplicaSet
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Out-of-Date APIs
- Change History
-
FAQs
- Product Consulting
-
Basic Concept FAQs
- What Is CCI?
- What Are the Differences Between Cloud Container Instance and Cloud Container Engine?
- What Is an Environment Variable?
- What Is a Service?
- What Is Mcore?
- What Are the Relationships Between Images, Containers, and Workloads?
- What Are Kata Containers?
- Can kubectl Be Used to Manage Container Instances?
- What Are Core-Hours in CCI Resource Packages?
- Workload Abnormalities
-
Container Workload FAQs
- Why Service Performance Does Not Meet the Expectation?
- How Do I Set the Quantity of Instances (Pods)?
- How Do I Check My Resource Quotas?
- How Do I Set Probes for a Workload?
- How Do I Configure an Auto Scaling Policy?
- What Do I Do If the Workload Created from the sample Image Fails to Run?
- How Do I View Pods After I Call the API to Delete a Deployment?
- Why an Error Is Reported When a GPU-Related Operation Is Performed on the Container Entered by Using exec?
- Can I Start a Container in Privileged Mode When Running the systemctl Command in a Container in a CCI Cluster?
- Why Does the Intel oneAPI Toolkit Fail to Run VASP Tasks Occasionally?
- Why Are Pods Evicted?
- Why Is the Workload Web-Terminal Not Displayed on the Console?
- Why Are Fees Continuously Deducted After I Delete a Workload?
-
Image Repository FAQs
- Can I Export Public Images?
- How Do I Create a Container Image?
- How Do I Upload Images?
- Does CCI Provide Base Container Images for Download?
- Does CCI Administrator Have the Permission to Upload Image Packages?
- What Permissions Are Required for Uploading Image Packages for CCI?
- What Do I Do If Authentication Is Required During Image Push?
-
Network Management FAQs
- How Do I View the VPC CIDR Block?
- Does CCI Support Load Balancing?
- How Do I Configure the DNS Service on CCI?
- Does CCI Support InfiniBand (IB) Networks?
- How Do I Access a Container from a Public Network?
- How Do I Access a Public Network from a Container?
- What Do I Do If Access to a Workload from a Public Network Fails?
- What Do I Do If Error 504 Is Reported When I Access a Workload?
- What Do I Do If the Connection Timed Out?
- Storage Management FAQs
- Log Collection
- Account
- SDK Reference
- Videos
- General Reference
Copied.
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 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.
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. |
|
|
Resource quotas |
You can configure fields such as cpu and memory to specify resource specifications and limits for containers in a pod. The add-on selects appropriate resource specifications to an integer for better resource utilization. |
Appropriate pod resource quotas are selected. |
|
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 the 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, ConfigMaps, 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 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 |
|
virtual-kubelet.cci.io/burst-pod-cpu |
vCPUs of pods after they are scheduled to CCI |
|
virtual-kubelet.cci.io/burst-pod-memory |
Memory of pods they are 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