Elastic Cloud Server (ECS)

An ECS with multiple EVS disks is a node in CCE. You can choose ECS specifications during node creation.

• Buying a Node
• Accepting Existing Nodes into a Cluster

Virtual Private Cloud (VPC)

For security reasons, all clusters created by CCE must run in VPCs. When creating a namespace, you need to create a VPC or bind an existing VPC to the namespace so all containers in the namespace will run in this VPC.

Buying a CCE Cluster

Elastic Load Balance (ELB)

CCE works with ELB to load balance a workload's access requests across multiple pods.

When ELB is used, the load balancer's address, instead of the workload address, is exposed to users. User requests first arrive at ELB via a public network and then routed by ELB to different pods of the workload.

• Creating a Deployment
• Creating a StatefulSet
• LoadBalancer

NAT Gateway

The NAT Gateway service provides source network address translation (SNAT) for container instances in a VPC. The SNAT feature translates private IP addresses of these container instances to the same EIP, which is a public IP address reachable on Internet.

You can define SNAT rules on the NAT gateway to let containers access the Internet.

• Creating a Deployment
• Creating a StatefulSet
• DNAT

Software Repository for Container (SWR)

An image repository is used to store and manage Docker images.

You can create workloads from images in SWR.

• Creating a Deployment
• Creating a StatefulSet

Cloud Container Instance (CCI)

Under the serverless model, CCI allows you to directly create and use containerized workloads on the console or by using kubectl or Kubernetes APIs, and pay only for the resources consumed by these workloads.

Pods can be deployed on CCI when CCE cluster resources are insufficient.

• virtual-kubelet
• Using virtual-kubelet to Schedule CCE Pods to CCI

Elastic Volume Service (EVS)

EVS disks can be attached to cloud servers and scaled to a higher capacity whenever needed.

An ECS with multiple EVS disks is a node in CCE. You can choose ECS specifications during node creation.

Using EVS Volumes

Object Storage Service (OBS)

OBS provides stable, secure, cost-efficient, and object-based cloud storage for data of any size. With OBS, you can create, modify, and delete buckets, as well as uploading, downloading, and deleting objects.

CCE allows you to create an OBS volume and attach it to a path inside a container.

Using OBS Volumes

Scalable File Service (SFS)

SFS is a shared, fully managed file storage service. Compatible with the Network File System protocol, SFS file systems can elastically scale up to petabytes, thereby ensuring top performance of data-intensive and bandwidth-intensive applications.

You can use SFS file systems as persistent storage for containers and attach the file systems to containers when creating a workload.

Using SFS Volumes

Application Operations Management (AOM)

AOM collects container log files in formats like .log from CCE and dumps them to AOM. On the AOM console, you can easily query and view log files. In addition, AOM monitors CCE resource usage. You can define metric thresholds for CCE resource usage to trigger auto scaling.

Collecting Standard Output Logs of Containers

Cloud Trace Service (CTS)

CTS records operations on your cloud resources, allowing you to query, audit, and backtrack resource operation requests initiated from the management console or open APIs as well as responses to these requests.

CCE Operations Supported by CTS