Updated on 2026-08-29 GMT+08:00

DataPlane V2

DataPlane V2 can be enabled in clusters that use a VPC network or Cloud Native Network 2.0. This feature uses eBPF redirection to enable features like NetworkPolicy.

DataPlane V2	Description
Technical implementation	DataPlane V2 integrates open-source cilium to enable features like NetworkPolicy.
Supported cluster versions	CCE standard clusters using VPC networks for commercial use of v1.27.16-r30, v1.28.15-r20, v1.29.13-r0, v1.30.10-r0, v1.31.6-r0, or later
Usage	When creating a CCE standard cluster, select the VPC network in the container network configuration and enable DataPlane V2. NOTICE: After DataPlane V2 is enabled, secure containers are not supported. Enabled DataPlane V2 cannot be disabled. DataPlane V2 can only be enabled for new clusters.
Supported OS	Huawei Cloud EulerOS 2.0 is supported. Clusters v1.28.15-r70, v1.29.15-r30, v1.30.14-r30, v1.31.10-r30, v1.32.6-r30, v1.33.5-r20, v1.34.1-r0, and later versions support Ubuntu 22.04.
Performance optimization	eBPF is used to limit the bandwidth. This makes bandwidth limitation more accurate and resource consumption lower.
Bandwidth	With DataPlane V2 enabled, CCE standard clusters on the VPC network model use eBPF for bandwidth limiting, and CCE Turbo clusters use TBF Qdisc. For details, see Configuring QoS for Pods.
NetworkPolicy	The implementation of network policies is different from that of container tunnel networks. For details, see Configuring Network Policies to Restrict Pod Access. The ipBlock selector can only select CIDR blocks outside a cluster. The ipBlock selector does not have good support for the except keyword, so this keyword is not recommended. If a network policy of the egress type is used, the pod fails to access the IP addresses of the hostNetwork pod and node in the cluster.
Resource consumption	The resident cilium-agent process on each node is responsible for eBPF network acceleration. Each cilium-agent process may occupy 80 MiB of memory. Each time a pod is added, the cilium-agent memory consumption may increase by 10 KiB.

Components

After DataPlane V2 is enabled, components listed in the following table are installed.

Component	Description	Resource Type
cilium-operator	Synchronizes CRDs. Removes the node.cilium.io/agent-not-ready taint of a node. Tunes and recycles internal resources.	Deployment
yangtse-cilium	Installs the auxiliary CNI (cilium-cni) for CCE to adapt to Cilium. Deploys cilium-agent.	DaemonSet

Release History

You can run the following command to check the cilium-operator image tag for the DataPlane V2 version:

kubectl get deploy -nkube-system cilium-operator -oyaml | grep "image:" | cut -d ':' -f 3

Information similar to the following is displayed:

3.1.5

Add-on Version	Status	Supported Cluster Version	New Feature	Community Version
1.0.15	Limited OBT	v1.27 v1.28 v1.29 v1.30 v1.31 v1.32	Support for only CCE Turbo clusters Disabled bpf-lb-sock (by setting bpf-lb-sock=false).	v1.14
1.0.8	Limited OBT	v1.27 v1.28 v1.29 v1.30 v1.31	Support for only CCE Turbo clusters Disabled host-based firewalls (by setting enable-host-firewall=false). Disabled L7 network policies (by setting enable-l7-proxy=false).	v1.14

Add-on Version

Status

Supported Cluster Version

New Feature

Community Version

1.0.15

Limited OBT

v1.27

v1.28

v1.29

v1.30

v1.31

v1.32

Support for only CCE Turbo clusters
Disabled bpf-lb-sock (by setting bpf-lb-sock=false).

v1.14

1.0.8