1

Support for V7 BMSs and C7 ECSs

CCE Turbo cluster nodes support V7 BMSs and C7 ECSs.

OBT

Buying a Node

2

Support for yearly/monthly-billed node pools

Yearly/Monthly-billed node pools are now supported.

Commercial use

Creating a Node Pool

3

Resetting nodes by using private images and in batches

You can reset nodes in batches and also by using private images.

Commercial use

Resetting a Node

4

BMS cluster upgrade

Clusters consisting of BMS nodes can be upgraded.

OBT

Upgrading a Cluster

5

Web-based login to containers

You can log in to a container from the web, facilitating debugging.

Commercial use

Logging In to a Container

6

Dedicated ELBs for the nginx-ingress add-on

Dedicated ELBs can be selected when you install the nginx-ingress add-on.

Commercial use

Installing nginx-ingress

1

CCE clusters and CCE Turbo clusters of Kubernetes 1.19.10 can be created.

CCE supports creating CCE clusters and CCE Turbo clusters of Kubernetes 1.19.10.

Commercial use

• Buying a CCE Cluster
• Buying a CCE Turbo Cluster

2

Custom OS images are supported for CCE Turbo clusters.

CCE Turbo clusters support custom OS images.

Commercial use

Creating a Custom CCE Node Image

3

Multiple subnets for a container CIDR Block are allowed for a CCE Turbo cluster.

When creating a CCE Turbo cluster, you can select multiple subnets for the container CIDR Block.

Commercial use

Buying a CCE Turbo Cluster

4

ECS/BMS nodes can be managed and removed in batches.

You can accept and remove ECS/BMS nodes from clusters in batches.

Commercial use

Accepting ECSs/BMSs as Nodes into a Cluster

5

SFS and OBS mount options can be configured.

You can set mount options when mounting SFS and OBS volumes.

Commercial use

Setting Mount Options

6

Custom keys are supported for OBS.

everest 1.2.8 and later versions provide the capability of customizing keys. IAM users can use their own keys to mount OBS volumes, by which you can control access permissions to OBS.

Commercial use

Using a Custom AK/SK to Mount an OBS Volume

7

Clusters can be upgraded from Kubernetes 1.15 and 1.17 to 1.19.

CCE supports cluster upgrades from Kubernetes 1.15 and 1.17 to 1.19.

OBT

Upgrading a Cluster (from v1.15 to v1.19)

8

CloudShell can be used to connect to your clusters.

CloudShell is available in certain regions to replace the web-terminal add-on which will be deprecated soon.

Commercial use

Using CloudShell

9

Released coredns 1.17.7.

coredns 1.17.7 is released, mirroring CoreDNS v1.8.4 in the community upgraded v1.6.5.

For details about the changelog, see 1.6.6 to 1.8.4.

Note: In the community version 1.7.0, there are changes in CoreDNS metric names. If you collect CoreDNS metric data or configure horizontal CoreDNS scaling policies based on the metrics, pay attention to the metric name changes and update the metric names when using the coredns add-on in CCE. After a version earlier than v1.17.7 is upgraded to v1.17.7, the horizontal CoreDNS scaling policies configured on the System Hardening page need to be deleted and configured on the page again.

Commercial use

coredns

1

Kubernetes 1.19 is now available in CCE.

CCE supports creating CCE clusters and CCE Turbo clusters of Kubernetes 1.19.

Commercial use

• Buying a CCE Cluster
• Buying a CCE Turbo Cluster

2

CCE Turbo clusters are commercially available.

CCE Turbo clusters run on a cloud native 2.0 infrastructure that features software-hardware synergy to support passthrough networking, high security and reliability, and intelligent scheduling.

Commercial use

Buying a CCE Turbo Cluster

3

CCE Turbo clusters and BMSs (x86) are compatible with secure containers.

With secure containers, kernels, computing resources, and networks are isolated between different containers to protect pod resources and data from being preempted and stolen by other pods.

Commercial use

• Secure Containers and Common Containers
• Buying a CCE Turbo Cluster

4

Ubuntu 18.04 is supported.

You can select Ubuntu 18.04 as the OS when creating a node in a CCE cluster or CCE Turbo cluster.

Commercial use

• Buying a Node
• Buying a CCE Turbo Cluster

5

VM and BMS system disks can be encrypted.

Data disk encryption provides powerful security protection for your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption function. This function is available only in certain regions.

Commercial use

Buying a Node

6

VM nodes and node pools support common containers, and BMSs support secure containers.

With secure containers, kernels, computing resources, and networks are isolated between different containers to protect pod resources and data from being preempted and stolen by other pods.

Commercial use

• Secure Containers and Common Containers
• Buying a CCE Turbo Cluster
• Creating a Deployment

7

overlayfs2 can be used as the container engine storage driver for CCE Turbo clusters.

Nodes that run on CentOS 7.6 or Ubuntu 18.04 in CCE Turbo clusters and nodes that run on Ubuntu 18.04 in CCE clusters use the Docker OverlayFS2 storage mode, in which you cannot limit the available disk space of a single container by configuring BaseSize.

Commercial use

Creating a Node

8

Enhanced network model (Cloud Native Network 2.0) for CCE Turbo clusters

Cloud Native Network 2.0 is a new container networking solution developed by HUAWEI CLOUD. This network model deeply integrates the VPC-native elastic network interfaces (ENIs), uses the VPC CIDR block to allocate container addresses, and supports passthrough networking to containers through a load balancer.

Commercial use

What Is Cloud Native Network 2.0 and What Scenarios Does It Apply to

9

SecurityGroup for network isolation

To enable CCE to interconnect with VPC security groups in Cloud Native Network 2.0, HUAWEI CLOUD designs SecurityGroup, a new CRD resource object, at the Kubernetes layer. SecurityGroup allows you to customize security groups for workloads with specific requirements to provide services externally.

Commercial use

SecurityGroup

10

Passthrough networking supported by ELB v3 for common containers and secure containers in CCE Turbo clusters

Services and ingresses use dedicated load balancers to forward requests directly to containers, achieving lower latency and zero performance loss.

OBT

/

11

Node pool configuration management parameters are added for clusters of v1.19.

CCE allows you to limit the number of file handles in a container, enable PodPidsLimit by default and modify it, configure the elastic computing period, and mount the F2FS and OverLayFS file systems to containers.

Commercial use

Node Pool Management

12

Add-ons compatible with clusters of v1.19 and their new features

Multiple add-ons in the Add-on Marketplace can be used in clusters of Kubernetes 1.19. Certain add-ons are functionally enhanced.

Commercial use

Add-ons

1

Arm-based bare-metal servers can be added to Kunpeng clusters of v1.15.

Arm-based bare-metal servers can be added to Kunpeng clusters of v1.15. and custom container images can be used.

Commercial use

Buying a Kunpeng Cluster

2

Periodic password update for IAM users

IAM user passwords are periodically updated to ensure the user account security and resource security in CCE.

Commercial use

/

1

Advanced ELB listener configuration is supported when HTTPS is used to create an ingress.

In scenarios with high network security requirements on clients, users can configure ELB listener settings, for example, selecting security policies and two-way authentication.

Commercial use

Creating an Ingress

2

Admission Controller for pod security policies

Admission Controller can be enabled for pod security policies in CCE clusters.

OBT

Submit a service ticket.

1

Creating CCE clusters of v1.17.11

CCE clusters of v1.17.11 can be created.

Commercial use

Buying a CCE Cluster

2

In v1.17.11, advanced ELB listener configuration is supported when HTTPS is used to create an ingress.

In v1.17.11, when HTTPS is used to create an ingress, the default value of the kubernetes.io/elb.tls-ciphers-policy field is tls-1-2, which is the security policy used by the listener and takes effect only when the HTTPS protocol is used.

Commercial use

Using kubectl to Create an Ingress

1

Custom metrics are supported for HPA policies.

Custom metrics are supported for HPA policies in clusters of v1.15 and later. You can set custom metric names, metric sources, expected values, and thresholds.

Commercial use

Scaling a Workload

2

CCE supports a SNI certificate with multiple domain names of ELB v3.

If multiple domain names are required for external access and different domain names use independent certificates, you need to enable the server name indication (SNI) function. After SNI is enabled, the client is allowed to submit the requested domain name information when initiating an SSL handshake request.

Commercial use

LoadBalancer

1

Creating CCE cluster of Kubernetes 1.17

CCE clusters of Kubernetes 1.17 can be created. Kubernetes 1.17.9-r0 is released.

Key features:

• EulerOS 2.5 and CentOS 7.6 are supported.
• Features of Kubernetes v1.17.9 are incorporated.

Commercial use

CCE Kubernetes 1.17 Release Notes

2

Frontend function optimization

• The common task list page is optimized. Information such as the start time, end time, and execution duration of a task is displayed.
• Workloads and cron jobs can be modified in YAML format on the console to facilitate real-time testing.

Commercial use

Creating a Cron Job

3

CCE supports the mounting of OBS buckets of third-party tenants.

CCE clusters can be mounted with OBS buckets of third-party tenants, including OBS parallel file systems (preferred) and OBS object buckets.

Only parallel file systems and object buckets of third-party tenants in the same region can be mounted.

Commercial use

Mounting an Object Storage Bucket of a Third-Party Tenant

4

CCE integrates HUAWEI CLOUD CGS.

CCE integrates Container Guard Service (CGS). CGS scans vulnerabilities and configurations in images, helping enterprises detect the container environment, which cannot be found by the traditional security software. CGS also delivers functions such as process whitelist configuration, read-only file protection, and container escape detection to minimize the security risks for a running container.

Commercial use

Container Guard Service (CGS)

5

Dedicated load balancers can directly access containers.

The native ENI of the VPC is deeply integrated. The VPC CIDR block is used to allocate container addresses. Access requests can directly reach containers through load balancers, providing optimal networking performance.

OBT

Creating a Dedicated Load Balancer

1

Creating CCE clusters and Kunpeng clusters (Arm-based) of v1.15.11

• CCE clusters and Kunpeng clusters (Arm-based) of v1.15.11 can be created.
• The autoscaler, coredns, everest, and dashboard add-ons on the Add-on Marketplace page can be installed in Arm-based clusters and support the dual-architecture to adapt to the x86/Arm hybrid scenario.

Commercial use

• Buying a CCE Cluster
• Buying a Kunpeng Cluster
• Add-ons

2

CCE supports federated users.

EPS fine-grained authorization of CCE supports SAML federated users. Users can access CCE in SAML federated mode.

Commercial use

Introduction to Identity Provider

3

The everest add-on (CSI plug-in) of CCE v1.15 supports the functions of FlexVolume fuxi.

After upgrading CCE clusters earlier than v1.15 to v1.15, you can use the everest add-on to incorporate the functions of FlexVolume fuxi of an earlier version without interrupting services.

Commercial use

• everest
• storage-driver

4

A CCE cluster of v1.15.11 or later can manage a maximum of 2,000 nodes.

The maximum number of nodes that can be managed by a CCE cluster of v1.15.11 is increased to 2,000. You can choose the desired management scale of nodes according to your service requirement during creation.

Commercial use

Buying a CCE Cluster

5

CCE supports upgrading a cluster from a version earlier than v1.15 to v1.15.

Clusters earlier than v1.15 (for example, v1.9, v1.11 and v1.13) can be upgraded to v1.15. Currently, the upgrade cannot be performed on the console. You can submit a service ticket to apply for the upgrade.

Application

Changelog for Upgrading Clusters

1

CCE container storage supports dynamic creation of obsfs data volumes.

If a CCE cluster version is v1.15 or later and the everest add-on version is 1.0.2 or later, parallel file systems that can be mounted by obsfs can be created.

Commercial use

Using OBS Buckets as Storage Volumes

2

Kunpeng cluster supports etcd data backup.

etcd is a distributed k-v database. It is used to manage cluster metadata in Kubernetes. Currently, Kunpeng cluster supports etcd data backup.

Commercial use

/