Huaweicloud CCE network training

1. cce cluster network mode

The container network assigns IP addresses to pods in a cluster and provides networking services. In CCE, you can select the following network models for your cluster:

Network Model Comparison

Dimension	Tunnel Network	VPC Network	Cloud Native Network 2.0
Application scenarios	1. Common container service scenarios 2. Scenarios that do not have high requirements on network latency and bandwidth	1. Scenarios that have high requirements on network latency and bandwidth 2. Containers can communicate with VMs using a microservice registration framework, such as Dubbo and CSE.	1. Scenarios that have high requirements on network latency, bandwidth, and performance 2. Containers can communicate with VMs using a microservice registration framework, such as Dubbo and CSE.
Core technology	OVS	IPvlan and VPC route	VPC ENI/sub-ENI
Applicable clusters	CCE cluster	CCE cluster	CCE Turbo cluster
Network isolation	Kubernetes native NetworkPolicy for pods	No	Pods support security group isolation.
Passthrough networking	No	No	Yes
IP address management	The container CIDR block is allocated separately. CIDR blocks are divided by node and can be dynamically allocated (CIDR blocks can be dynamically added after being allocated.)	The container CIDR block is allocated separately. CIDR blocks are divided by node and statically allocated (the CIDR block cannot be changed after a node is created).	The container CIDR block is divided from the VPC subnet and does not need to be allocated separately.
Network performance	Performance loss due to VXLAN encapsulation	No tunnel encapsulation. Cross-node packets are forwarded through VPC routers, delivering performance equivalent to that of the host network.	The container network is integrated with the VPC network, eliminating performance loss.
Networking scale	A maximum of 2,000 nodes are supported.	By default, 200 nodes are supported. Each time a node is added to the cluster, a route is added to the VPC route tables (including the default and custom ones). Therefore, the cluster scale is limited by the VPC route tables.	A maximum of 2,000 nodes are supported.

performance: ENI > VPC > Tunnel

Number of network nodes: (ENI,Tunnel) > VPC

Elastic Network Interfaces (ENIs) , Reference qingtian Architecture

Note: After a cluster is created, the network model cannot be changed.

Offical link about network

The following figure shows the creation on the CCE GUI：

CCE Turbo vs CCE

CCE Turbo is an enhancement of CCE.

**Table 1** Cluster types
Dimension	Sub-dimension	CCE Turbo Cluster	CCE Cluster
Cluster	Positioning	Next-gen container cluster, with accelerated computing, networking, and scheduling. Designed for Cloud Native 2.0	Standard cluster for common commercial use
Cluster	Node type	Hybrid deployment of VMs and bare-metal servers	Hybrid deployment of VMs and bare-metal servers
Networking	Model	Cloud Native Network 2.0: applies to large-scale and high-performance scenarios. Max networking scale: 2,000 nodes	Cloud-native network 1.0: applies to common, smaller-scale scenarios. Tunnel network model VPC network model
	Performance	Flattens the VPC network and container network into one. No performance loss.	Overlays the VPC network with the container network, causing certain performance loss.
	Container network isolation	Associates pods with security groups. Unifies security isolation in and out the cluster via security groups' network policies.	Tunnel network model: supports network policies for intra-cluster communications. VPC network model: supports no isolation.
Security	Isolation	Physical machine: runs Kata containers, allowing VM-level isolation. VM: runs common containers, isolated by cgroups.	Runs common containers, isolated by cgroups.

Offical link about CCE Turbo Clusters and CCE Clusters

The following figure shows the creation on the CCE Turbo GUI：

Ingress

An ingress is an independent resource in the Kubernetes cluster and defines rules for forwarding external access traffic. we can customize forwarding rules based on domain names and URLs to implement fine-grained distribution of access traffic.

ELB Ingress & Nginx Ingress

捐赠本站(Donate)

如您感觉文章有用，可扫码捐赠本站！(If the article useful, you can scan the QR code to donate))