You can use the Container Service for Kubernetes (ACK) console to manage edge node pools. For example, you can create, edit, and delete node pools.
Procedure
Log on to the ACK console. In the navigation pane on the left, click Clusters.
On the Clusters page, find the cluster you want and click its name. In the left-side pane, choose .
Create an edge node pool
On the Node Pools page, click Create Edge Node Pool.
On the Create Edge Node Pool page, configure the parameters as described in Edge node pool parameters, and then click Submit.
View an edge node pool
On the Node Pools page, click the name of a node pool to view the following information.
Click the Overview tab to view information such as the node pool ID, container runtime, cloud-edge network connection, inter-node connection, pod network mode, node labels, and taints.
Click the Monitor tab to view node monitoring information.
Edit an edge node pool
On the Node Pools page, find the target node pool and click Edit on the right.
On the Edit Edge Node Pool page, modify the parameters as needed and click Confirm.
NoteYou can modify only the node pool name, node labels, and taints. For more information, see Edge node pool parameters.
Delete an edge node pool
On the Node Pools page, find the target node pool, and on the right, click
> Delete.In the Confirm to Delete Node Pool dialog box, carefully read the notes about deleting the node pool. After you confirm the information, click OK.
NoteIf an edge node pool contains edge nodes, you must first remove the edge nodes before you can delete the node pool. Otherwise, the deletion fails.
Edge node pool parameters
Parameter | Modifiable after creation | Description |
Node Pool Name |
| The name must be 1 to 63 characters in length. It can contain digits, underscores (_), and hyphens (-). It must start with a letter, a Chinese character, or a digit. |
Container Runtime |
| ACK Edge clusters of V1.24 or later support only the containerd runtime. |
Cloud-edge Network Connection |
| Internet: Nodes in the node pool communicate with cloud nodes over the internet. Applications on the edge nodes cannot directly access the VPC in the cloud. Select this mode if your edge applications do not have a strong dependency on the cloud and have no requirements for cloud-edge communication or security. VPC: Nodes in the node pool connect to the cloud network through methods such as Express Connect, VPN, or Cloud Enterprise Network (CEN). This provides higher quality and more secure cloud-edge communication. Select this mode if your business has a strong demand for cloud-edge interaction and high requirements for network quality and security. You must set up the required infrastructure, such as a leased line, between the nodes and the cloud in advance. |
Inter-node Connection |
| Yes: Layer 3 network communication is enabled among all nodes in the node pool. Note Scenario: A standard IDC or VPC is a node pool, and the hosts within this node pool can communicate with each other over the internal network. No: Layer 3 network communication is disabled among all nodes in the node pool. Note Scenario: A group of scattered edge devices are in the same node pool, and the hosts do not need to communicate with each other. |
Pod Network Type |
| Container Network: Pods have an independent network stack and do not occupy host network ports. You must install components such as Flannel, kube-proxy, and CoreDNS. This mode is suitable for scenarios that require fine-grained control over the container network. 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 on nodes in a node pool that uses the host network mode. This mode supports larger cluster sizes and is suitable for lightweight services and scenarios where services do not need to communicate with each other. |
Node Labels |
| Add labels to all nodes in the node pool. |
Taints |
| Add taints to all nodes in the node pool. |
