You can create an edge node pool to centrally manage a group of nodes, including node labels and taints. This topic describes how to create an edge node pool.
Prerequisites
An ACK Edge cluster is created.
Create an edge node pool
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose .
On the Node Pools page, click Create Edge Node Pool.
In the Create Edge Node Pool (Beta) dialog box, configure the parameters of the edge node pool and click Submit.
Edge node pool parameters
Parameter | Can be modified after creation | Description |
Node Pool Name |
| The name must be 1 to 63 characters in length, and can contain digits, letters, hyphens (-), and underscores (_). The name must start with a letter or digit. |
Container Runtime |
| ACK Edge of Kubernetes 1.24 or later supports only containerd. |
Cloud-edge Network Connection |
| Internet: Nodes in the node pool communicate with nodes in the cloud over the Internet. Applications deployed on the edge nodes cannot directly access virtual private clouds (VPCs) over the Internet. If your applications at the edge do not strongly rely on the cloud and do not have requirements for cloud-edge communication and data security, we recommend that you select this connection mode. VPC: You can connect nodes in the node pool to the cloud by using Express Connect, VPN, or Cloud Enterprise Network (CEN). This greatly improves the quality and security of cloud-edge communication. If your applications at the edge strongly rely on cloud-edge communication and have high requirements for the quality and security of cloud-edge communication, we recommend that you select this connection mode. If you want to use this connection mode, make sure that an Express Connect circuit is used to connect nodes in the node pool to the cloud. |
Inter-node Connection |
| Yes: enables network communication at Layer 3 among all nodes in the node pool. Note If the node pool is deployed in a data center or VPC, you can enable inter-node communication. No: disables network communication at Layer 3 among all nodes in the node pool. Note If the edge devices deployed in the same node pool do not need to communicate with each other, you can disable inter-node communication. |
Pod Network Type |
| Container Network: Pods have an independent network stack and do not occupy host network ports. You need to install components such as Flannel, kube-proxy, and CoreDNS. This network type is suitable for scenarios that require fine-grained container network control. Host Network: Pods use the network stack of the node and share IP addresses and ports with the host. By default, components such as Flannel, kube-proxy, and CoreDNS are not installed. This network type is suitable for lightweight business scenarios and scenarios that do not require communication between services. |
Node Label |
| Add labels to the nodes in the node pool. |
Taints |
| Add taints to nodes in the node pool. |
References
For more information about how to modify the basic information of an existing edge node pool, see Modify an edge node pool.
For more information about how to delete an existing edge node pool, see Delete an edge node pool.