Overview

Scheduling

You can manage pods in a CCE cluster in different ways to control their scheduling to CCI 2.0. 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.

Scheduling Workloads to CCI 2.0

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.

Rounding Up Pod Resources

Images

You can configure service images and run your service containers in Huawei Cloud CCE clusters and CCI 2.0.

• 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.

Storage

Networking

You can plan the network topology between CCE clusters and CCI 2.0.

• Pods in CCI 2.0 can be exposed by the Service.
• Pods in a CCE cluster can communicate with pods in CCI 2.0 through the 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 2.0.

• View data on the CCI 2.0 console.

Monitoring

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 pod and 1,000 ConfigMaps in your CCE cluster, you can apply for 2 cores and 4 GiB of memory.
• If there are 2,000 pod and 2,000 ConfigMaps in your CCE cluster, you can apply for 4 cores and 8 GiB of memory.
• If there are 4,000 pod 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 SWR.

Ensure that your image has been pushed to SWR.

scheduling.cci.io/managed-by-profile

Profile that manages the pods of the workloads scheduled to CCI

Scheduling Workloads to CCI 2.0

resource.cci.io/size

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

Rounding Up Pod Resources

bursting.cci.io/image-replacement

Annotation for replacing image path prefixes

Images

1.5.44

v1.21

v1.23

v1.25

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

• CCE clusters v1.32 are supported.
• 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

CCE clusters v1.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 v1.29 are supported.

1.3.57

v1.21

v1.23

v1.25

v1.27

v1.28

CCE clusters v1.28 are supported.

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 an issue that the Kubernetes Dashboard cannot run on terminals.

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 that 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

• Clusters v1.19 are supported.
• 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

Clusters v1.17 are supported.