Updated on 2024-07-02 GMT+08:00

CCE Cloud Bursting Engine for 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 schedule 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

  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 on the left, 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 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

  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 on the left, 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.

    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 on the left, 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.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

Supports clusters of v1.21 and v1.23.

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

  • Supported clusters 1.19.
  • 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.