Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

CCE Cloud Bursting Engine for CCI

Updated on 2025-02-18 GMT+08:00

The bursting add-on 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 schedule Deployments, StatefulSets, jobs, and CronJobs running in CCE clusters to CCI during peak hours. In this way, you can reduce consumption caused by cluster scaling.

Installing the Add-on

  1. Log in to the CCE console.
  2. Click the name of the target CCE cluster to go to the cluster console.
  3. In the navigation pane, choose Add-ons.
  4. Select the CCE Cloud Bursting Engine for CCI add-on and click Install.
  5. 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 running the add-on.

    • If you select Preset, you can select Single or HA.
    • If you select Custom, you can modify the number of replicas, vCPUs, and memory of each add-on component as required.
    NOTE:
    • The bursting add-on 1.5.2 or later uses more node resources. You need to reserve sufficient pods before upgrading the add-on.
      • Single (only one pod for the add-on): There must be a node that has at least seven schedulable pods. If Networking is enabled, eight schedulable pods are required.
      • HA (two pods for the add-on): There must be two nodes, each of which must have at least seven schedulable pods, a total of 14 schedulable pods. If Networking is enabled, eight schedulable pods are required on each node, a total of 16 schedulable pods.
    • The resource usage of the add-on varies depending on the workloads scaled to CCI. The pods, secrets, ConfigMaps, PVs, and PVCs requested by the services occupy VM resources. You are advised to evaluate the service usage and apply for VMs based on the following specifications: For 1,000 pods and 1,000 ConfigMaps (300 KB), nodes with 2 vCPUs and 4-GiB memory are recommended. For 2,000 pods and 2,000 ConfigMaps, nodes with 4 vCPUs and 8-GiB memory are recommended. For 4,000 pods and 4,000 ConfigMaps, nodes with 8 vCPUs and 16-GiB memory are recommended.

    Networking

    If this option is enabled, pods in the CCE cluster can communicate with pods in CCI through Services. The component proxy will be automatically deployed upon add-on installation. For details, see Networking.

Creating a Workload

  1. Log in to the CCE console.
  2. Click the name of the target CCE cluster to go to the cluster console.
  3. In the navigation pane, choose Workloads.
  4. Click Create Workload. For details, see Creating a Workload.
  5. Specify basic information. Set Burst to CCI to Force scheduling. For more information about scheduling policies, see Scheduling Pods to CCI.

    CAUTION:

    When you schedule a workload in a CCE cluster to CCI, TCP probes cannot be used for health check.

  6. Configure the container parameters.
  7. Click Create Workload.
  8. On the Workloads page, click the name of the created workload to go to the workload details page.
  9. 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

  1. Log in to the CCE console.
  2. Click the name of the target CCE cluster to go to the cluster console.
  3. In the navigation pane, choose Add-ons.
  4. 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.

    For more information about the bursting add-on, see CCE Cloud Bursting Engine for CCI.

Change History

Table 3 Release history

Add-on Version

Supported Cluster Version

New Feature

1.5.27

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

CCE clusters 1.31 are supported.

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

CCE clusters 1.29 are supported.

1.3.57

v1.21

v1.23

v1.25

v1.27

v1.28

CCE clusters 1.28 are supported.

1.3.48

v1.21

v1.23

v1.25

v1.27

  • Clusters 1.25 and 1.27 are supported.
  • Supported JuiceFS.

1.3.25

v1.17

v1.19

v1.21

v1.23

  • Supports Downward API volumes.
  • Supports Projected volumes.
  • Supports custom StorageClass.

1.3.19

v1.17

v1.19

v1.21

v1.23

Supports schedule profile.

1.3.7

v1.17

v1.19

v1.21

v1.23

Clusters 1.21 and 1.23 are supported.

1.2.12

v1.13

v1.15

v1.17

v1.19

  • Adds some metrics.
  • Supports HPA and CustomedHPA.
  • Enables the hostPath in the pod that is scaled to CCI to be converted to other types of storage.
  • Fixes an issue that the Kubernetes dashboard cannot run on terminals.

1.2.5

v1.13

v1.15

v1.17

v1.19

  • Automatically clears CCI resources that are no longer used by pods.
  • Requests and Limits can be set to different values. When CCI is scaled, the number of applied resources is subject to Limits.
  • Fixes the issue that the add-on fails to be uninstalled when the CCI namespace does not exist.
  • Adds 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

  • Clusters 1.19 are supported.
  • Supported SFS and SFS Turbo storage.
  • Supported CronJobs.
  • Supported envFrom configuration.
  • Supports automatic logs dumping.
  • Shields TCPSocket health check.
  • Supports resource tags (pod-tag).
  • Improves performance and reliability.
  • Resolves some known issues.

1.0.5

v1.13

v1.15

v1.17

Clusters 1.17 are supported.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback