Free Packages Free

Huawei Cloud Blossom Program

Product Advantages

Why CCE?

CCE is a container service built on Docker and Kubernetes. A wealth of features enable you to run container clusters at scale. CCE eases containerization thanks to its reliability, performance, and open source engagement.

Easy to Use

Creating a Kubernetes cluster is as easy as a few clicks on the web console. You can deploy and manage VMs and BMSs together.

CCE automates deployment and O&M of containerized applications throughout their lifecycle.

You can resize clusters and workloads by setting auto scaling policies. In-the-moment load spikes are no longer headaches.

The console walks you through the steps to upgrade Kubernetes clusters.

CCE supports turnkey Application Service Mesh (ASM) and Helm charts.

High Performance

CCE runs on mature IaaS services and heterogeneous compute resources. You can launch containers at scale.

AI computing is 3x to 5x better with NUMA BMSs and high-speed InfiniBand network cards.

Highly Available and Secure

HA: Three master nodes in different AZs for your cluster control plane. Multi-active DR for your nodes and workloads. All these ensure service continuity when one of the nodes is down or an AZ gets hit by natural disasters.

Secure: Integrating IAM and Kubernetes RBAC, CCE clusters are under your full control. You can set different RBAC permissions for IAM users on the console.

Open and Compatible

CCE runs on Docker that automates container deployment, discovery, scheduling, and scaling.

CCE is compatible with native Kubernetes APIs and kubectl. Updates from Kubernetes and Docker communities are regularly incorporated into CCE.

Comparative Analysis of CCE and On-Premises Kubernetes Cluster Management Systems

CCE clusters versus on-premises Kubernetes clusters

Area of Focus	On-Premises Cluster	CCE
Ease of use	You have to handle all the complexity in deploying and managing Kubernetes clusters. Cluster upgrades are often a heavy burden to O&M personnel.	Easy to manage and use clusters You can create a Kubernetes container cluster in a few clicks. No need to set up Docker or Kubernetes environments. CCE automates deployment and O&M of containerized applications throughout their lifecycle. CCE supports turnkey Helm charts. Using CCE is as simple as choosing a cluster and the workloads that you want to run in the cluster. CCE takes care of cluster management and you focus on app development.
Scalability	You have to assess service loads and cluster health before resizing a cluster.	Managed scaling service CCE auto scales clusters and workloads according to resource metrics and scaling policies.
Reliability	Only one master node is available in a cluster. Once this node is down, the entire cluster is down, as well as all the applications in it.	High availability Enabling HA when creating a cluster will create three master nodes for the control plane. Single points of failure (SPOFs) will not shut down your cluster.
Efficiency	You have to either build an image repository or turn to a third-party one. Images are pulled in serial.	Rapid deployment with images CCE connects to SWR to pull images in parallel. Faster pulls, faster container build.
Cost	Heavy upfront investment in installing, managing, and scaling cluster management infrastructure	Cost effective You only pay for master nodes and the resources used to run and manage applications.

Auto Scaling

Autoscale your computing resources in line with fluctuating demands by adding or reducing cloud servers or containers with zero effort on your end. This allows you to achieve service stability.

Advantages

High Scalability

Make the most of multiple policies to scale your containers in mere seconds.
High Availability

Automatically detect the statuses of pods in your auto-scaling groups to keep your clusters running like clockwork.
Pay-As-You-Go Pricing

Pay only for the cloud servers you use and redirect funds into other avenues of your business.

Related Services

ECS

AOM

DevOps

CCE fits in perfectly with existing continuous integration and continuous delivery (CI/CD) pipelines, allowing you to use source code to automatically compile code, create images, complete grayscale releases, and build containers — all in one place.

Advantages

Streamlined Operations

Stay on top of your work by substantially reducing your scripting workload (over 80%) through streamlined process interaction.
Easy Integration

Utilize various APIs to integrate CCE with your existing CI/CD systems and enjoy the benefits of flexible customization.
Flexible Scheduling

Freely choose how to schedule your tasks with a fully containerized architecture that promotes more efficient execution.

Related Services

OBS

VPN

Hybrid Cloud

Seamlessly orchestrate applications and data both on-premises and on cloud. Collectively manage your containers for flexible resource scheduling and reliable disaster recovery (DR).

Advantages

Reduced Costs

Take advantage of Huawei Cloud's resource pool to rapidly scale during peak hours. Compared to building a private cloud from scratch, the savings are worth writing home about.
High Availability

Protect your service systems from outages using a multi-cloud DR approach. If one cloud is faulty, your system loads will be automatically diverted to other clouds, allowing you to maintain service continuity.
Complementary Technologies

Get the best of both the on-premises system and the cloud. The on-premises system works seamlessly with other Huawei Cloud services, giving you a wide range of added benefits.

Related Services

ECS

SWR

VPN

AI Containers

Run your containers on high-performance GPU-accelerated cloud servers to take your AI computing to the next level. By sharing GPUs between multiple containers, you can minimize idle time and drastically reduce costs.

Advantages

High-performance

Considerably improve your AI computing performance with the bare-metal NUMA architecture and high-speed InfiniBand NICs.
Efficient

Fully utilize your GPUs by sharing and scheduling them between multiple containers. This helps you keep your costs in check.
Tried-and-Tested

Run your AI containers with any mainstream GPU without facing compatibility issues. AI containers have been put into large-scale use and demonstrated their value in Huawei Cloud's Enterprise Intelligence (EI) products.

Related Services

ELB

OBS

User Guide

Buying a CCE Turbo Cluster

Buying a CCE Cluster

Connecting to a Cluster Using kubectl

Creating a Deployment (Nginx) from an Image

Deploying WordPress and MySQL That Depend on Each Other

Deploying an Application from a Chart

Managing Workloads and Jobs

Scaling a Workload

Scaling a Cluster/Node

FAQs

Is HUAWEI CLOUD CCE suitable for users who are not familiar with Kubernetes?

Yes. The CCE console is easy-to-use, and the Getting Started guide helps you quickly understand and use CCE.
Where can I find the instructions on creating Docker images for traditional applications?

For details, see Containerizing an Enterprise Application (ERP) in the CCE Best Practices.
Is CCE suitable for users who have little experience in building images?

Yes. You can select images from Open Source Images, Third-party Images, and Shared Images pages on the CCE console. The My Images page displays only the images created by you. For details, see Creating a Deployment (Nginx) from an Image.
How do I create a workload using CCE?

Create a cluster and then create a workload in the cluster. For details, see Creating a Deployment (Nginx) from an Image.
How do I create a workload accessible to public networks?

CCE provides different workload access types to address diverse scenarios. For details, see Networking Overview.
How can I allow multiple workloads in the same cluster to access each other?

Select the access type ClusterIP, which allows workloads in the same cluster to use their cluster-internal domain names to access each other.
Cluster-internal domain names are in the format of <self-defined service name>.<workload's namespace>.svc.cluster.local:<port number>. For example, nginx.default.svc.cluster.local:80.
Example:
Assume that workload A needs to access workload B in the same cluster. Then, you can create a ClusterIP Service for workload B. After the ClusterIP Service is created, workload B is reachable at <self-defined service name>.<workload B's namespace>.svc.cluster.local:<port number>.

Videos About CCE

CCE Service Introduction