What's New

1

Kubernetes 1.28 now available in CCE.

CCE allows you to create clusters of Kubernetes 1.28.

Commercial use

Kubernetes 1.28 Release Notes

2

NGINX Ingress Controller metrics can be monitored.

CCE allows you to use the Cloud Native Cluster Monitoring add-on to gather metrics on the NGINX Ingress Controller. This allows you to monitor the performance and running status of the NGINX Ingress Controller in real time.

Commercial use

Monitoring Metrics of NGINX Ingress Controller

3

Multiple NGINX ingress controllers can be installed in the same cluster.

You can deploy multiple independent NGINX ingress controllers in a cluster. This allows you to customize each controller to meet specific traffic and security needs.

Commercial use

Nginx Ingress Controller

4

CCE Autopilot clusters are in OBT.

CCE Autopilot allows you to create serverless clusters that offer optimized Kubernetes compatibility and free you from O&M. After a CCE Autopilot cluster is created, you can deploy applications without purchasing nodes or maintaining the deployment, management, and security of nodes. You only need to focus on the implementation of application service logic, which greatly reduces your O&M costs and improves the reliability and scalability of applications.

Open beta testing

What Is CCE Autopilot Cluster?

5

ELB blocklists or trustlists are supported for access control.

When creating a Service or ingress, you can add IP addresses to a trustlist or blocklist to control access to a listener of a load balancer to improve security.

Commercial use

Configuring a Blocklist/Trustlist Access Policy for a Service

Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Ingress

1

Kubernetes 1.28 clusters are in OBT.

CCE allows you to create clusters of Kubernetes 1.28.

Open beta testing

Kubernetes 1.28 Release Notes

2

Volcano supports load-aware scheduling for nodes.

Volcano Scheduler offers CPU and memory load-aware scheduling for pods and preferentially schedules pods to the node with the lightest load to balance node loads. This prevents an application or node failure due to heavy loads on a single node.

Commercial use

Load-aware Scheduling

3

Multiple subnet CIDR blocks can be configured for a node pool.

When creating a node pool, you have the option to choose multiple subnet CIDR blocks for more flexible allocation of network resources.

Commercial use

Creating a Node Pool

4

Volcano supports custom workload scale-in priorities.

After the application scaling priority policy is enabled, workload pods can be scaled in or out based on the node priority configured by users. For example, an application pod that runs on a pay-per-use node may be given priority when scaling down.

Commercial use

Application Scaling Priority Policies

5

Ingresses that use dedicated load balancers can interconnect with gRPC backend services.

Ingresses can interconnect with gRPC backend services when dedicated load balancers are used. gRPC is a high-performance general RPC open-source software framework that helps load balancers run over HTTP/2.

Commercial use

Interconnecting LoadBalancer Ingresses with gRPC Backend Services

1

Volcano supports node load-aware rescheduling.

Volcano scheduler can evict pods that do not comply with the configured policy so that pods can be rescheduled. In this way, the cluster load is balanced and resource fragmentation is minimized.

Commercial use

Descheduler

2

Volcano supports node pool affinity scheduling.

Soft affinity scheduling of a node pool is implemented based on labels in the node pool. Each node in the node pool is scored to select the optimal one for pod scheduling.

The rule is to schedule pods to nodes with specified labels as far as possible.

Commercial use

Node Pool Affinity

3

Kubernetes 1.27 now available in CCE.

CCE allows you to create clusters of Kubernetes 1.27.

Commercial use

Kubernetes Release Notes

1

CCE clusters support the dedicated load balancers that use elastic specifications.

Dedicated load balancers are suitable for fluctuating traffic and billed based on the Load Balancer Capacity Units (LCUs) used per hour.

Commercial use

Billing (Dedicated Load Balancers)

2

Custom tags can be added to dynamically created EVS disks.

When dynamically creating EVS PVCs, you can add TMS tags to automatically created EVS disks to classify resources. This facilitates cost management.

Commercial use

Using an EVS Disk Through a Dynamic PV

3

The timeout interval can be configured for a load balancer.

When a LoadBalancer Service or an ELB Ingress is used, the timeout interval can be configured.

Commercial use

Configuring Timeout for a LoadBalancer Service

Configuring Timeout for an ELB Ingress

4

Kubernetes 1.27 OBT

CCE allows you to create clusters of Kubernetes 1.27.

Open beta testing

Kubernetes Release Notes

1

Kubernetes 1.25 now available

CCE allows creating clusters of Kubernetes 1.25.

Commercial use

Buying a CCE Cluster

2

CCE Turbo ENIs support fixed IP addresses.

CCE Turbo clusters support fixed IP addresses for pods (ENIs) of StatefulSets. This is a common practice in access control, service registration, service discovery, and log audit.

Commercial use

Fixed Pod IP Address

3

CCE Turbo ENIs support automatic creation and binding of EIPs.

CCE Turbo clusters can automatically bind an EIP to a StatefulSet. This function works with the automated EIP creation function to assign a fixed EIP (fixed public IP address) to each pod.

Commercial use

Fixed Pod EIP

4

Enhances hybrid deployment of CCE Turbo clusters: Pod network priority restriction is supported.

CCE Turbo clusters balance the egress network bandwidth used by online and offline services to ensure sufficient network bandwidth for online services. When the threshold is reached for online services, the bandwidth usage of offline services will be reduced.

Commercial use

Egress Network Bandwidth Guarantee

5

CCE Turbo clusters support the association between namespaces and container CIDR blocks.

You can set container subnets and security groups by namespace to isolate network.

Commercial use

NetworkAttachmentDefinition

6

CCE Turbo clusters support CPU Burst to prevent CPU traffic limiting from affecting latency-sensitive services.

If a CPU limit is set for a container in the pod, the CPU usage of the container cannot exceed the limit. Frequent CPU traffic limiting affects service performance and increases the long-tail response latency, especially for latency-sensitive services.

CPU Burst is an elastic traffic limiting mechanism that allows temporarily exceeding the CPU limit to reduce the long-tail response time of services.

Commercial use

CPU Burst

1

Kubernetes 1.25 OBT

CCE allows creating clusters of Kubernetes 1.25.

Open beta testing

CCE Kubernetes 1.25 Release Notes

2

Huawei Cloud EulerOS 2.0 is supported.

Nodes running Huawei Cloud EulerOS 2.0 can be created in clusters of v1.23 or later.

Commercial use

Node OS

3

Enhanced CPU core binding management policies are supported.

Based on the Kubernetes static policy, the enhanced CPU core binding management policy (enhanced-static) supports burstable pods (whose requests and limits of CPU are positive integers) and allows certain CPUs to prioritize these pods, enhancing application stability.

Commercial use

Enhanced CPU Core Binding Management Policy

4

CCE clusters support monitoring components of master nodes.

CCE clusters can monitor the kube-apiserver, kube-controller, kube-scheduler and etcd-server components of master nodes.

Commercial use

Monitoring Metrics of the Master Node Component

1

Workload identity

With workload identities, your workloads in a cluster can access cloud services like IAM users without using the AK/SK, reducing security risks.

Commercial use

Workload Identities

2

Resource reservation model V2

For clusters of v1.21.4-r0, v1.23.3-r0, or later, the node memory reservation model is optimized to V2 and can be dynamically adjusted using the node pool parameters kube-reserved-mem and system-reserved-mem.

Commercial use

Formula for Calculating the Reserved Resources of a Node

3

Support for containerd

You can select containerd as the container runtime for CCE clusters.

Commercial use

Node Overview

4

Custom security group for a node pool

You can specify a security group when creating a node pool.

Commercial use

Creating a Node Pool

5

Enhanced npd add-on

CCE enhances the monitoring on component events, OS, network, and storage, and provides fault isolation.

Commercial use

npd

1

CCE Turbo clusters now GA

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 Cluster

2

Kubernetes 1.23 now available

CCE supports creating clusters of Kubernetes 1.23.

Open beta testing

Buying a CCE Cluster

3

Kubernetes 1.21 now available

CCE supports creating clusters of Kubernetes 1.21.

Commercial use

Buying a CCE Cluster

4

Specifying enterprise projects for PVCs

By default, the enterprise project to which a PVC belongs is the same as that to which the cluster belongs. You can now specify an enterprise project.

Commercial use

PersistentVolumeClaims (PVCs)

5

Support for local PVs and ephemeral volumes

Data disks on CCE nodes can be configured as local PVs or ephemeral volumes to provide better data read and write performance.

Commercial use

Local PVs and EVs

1

Kubernetes 1.21 is now available in CCE.

CCE supports creating clusters of Kubernetes 1.21.

Open beta testing

Buying a CCE Cluster

2

Interconnection with Cloud Secret Management Service (CSMS) to mount DEW secrets to pods

The dew-provider add-on is connected to CSMS, allowing users to mount secrets stored outside the cluster, that is, the Data Encryption Workshop (DEW) service dedicated to storing sensitive information, to pods for unified secret management.

Commercial use

dew-provider

3

OverlayFS for Docker storage on CCE cluster nodes that run CentOS 7.6

In CCE clusters of v1.21, the Docker storage mode of CentOS 7.6 nodes is changed from Device Mapper to OverlayFS.

Commercial use

Node Overview

4

ELB layer-7 forwarding for Services

ELB layer-7 forwarding is available for Services.

Commercial use

LoadBalancer

5

Secondary CIDR block for cluster VPC

When creating a cluster, you need to deploy it in a VPC. If the planned VPC is too small and IP addresses are insufficient, you can use a secondary VPC CIDR block to support your service scaling.

Commercial use

Adding a Secondary VPC CIDR Block for a Cluster

6

Multiple container CIDR blocks for a CCE cluster

When creating a CCE cluster, you can specify multiple container CIDR blocks.

Commercial use

Buying a CCE Cluster

1

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.

Commercial use

Upgrading a Cluster

2

CCE clusters of Kubernetes 1.19.10 can be created.

You can create CCE clusters of Kubernetes 1.19.10.

Commercial use

Buying a CCE Cluster

3

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

4

SFS and OBS mount options can be configured.

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

Commercial use

Setting Mount Options

5

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

6

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 of Kubernetes 1.19.

Commercial use

Buying a CCE Cluster

2

Ubuntu 18.04 is supported.

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

Commercial use

Buying a Node

3

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

4

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 Pools

5

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

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

Obtaining Resource Permissions