Using Distributed Cloud Resources in a CCE Turbo Cluster

Core Concepts

CCE introduces partitions to distinguish cloud resources from resources distributed in different edge locations. Partitions are defined as follows:

• From the perspective of computing, a partition is a collection of data center availability zones (AZs) that are physically isolated but close to each other (access latency within 2 ms). Deploying applications in different AZs of a partition ensures high availability.
• From the perspective of networking, nodes and containers in a partition need to use VPC subnets created in AZs of the partition. To facilitate configuration and management, configure the default subnet when creating a partition. If no subnet is specified when you create a node, the node uses the default subnet of the partition.
• Other attributes: Partition types can be center or CloudPond. This classification facilitates application scheduling.

Notes and Constraints

• Nodes: Remote clusters support only x86 VMs. Node migration is unavailable currently.
• Node pools: Random scheduling of a node pool only applies to partitions.
• Storage: You can only create EVS disks in edge partitions.
• Services and ingresses: Only dedicated load balancers are supported.
• Add-ons: The following add-ons are supported by remote clusters and preferentially deployed on cloud servers:
  • CCE Container Storage (Everest)
  • CoreDNS
  • NodeLocal DNSCache
  • CCE Cluster Autoscaler
  • Kubernetes Metrics Server
  • CCE Node Problem Detector
  • Kubernetes Dashboard
  • CCE AI Suite (Ascend NPU)
  • CCE AI Suite (NVIDIA GPU)

Enabling Support for Remote Clouds

When creating a CCE Turbo cluster, you can enable support for distributed clouds (CloudPond).

After distributed clouds are supported, the edge nodes created in the cluster will have the following taint and Kubernetes labels added by default:

• Taint: distribution.io/category=IES:NoSchedule
• Kubernetes labels:
  • distribution.io/category=IES
  • distribution.io/partition=<AZ name>
  • distribution.io/publicbordergroup=<AZ name>

Figure 2 Enabling distributed clouds (CloudPond)