Create and manage edge node pools
Use the Container Service for Kubernetes (ACK) console to centrally manage edge node pools, including creating, editing, and deleting them.
Access
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
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, 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 Basic Information 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 data.
Edit an edge node pool
On the Node Pools page, find the target node pool and click Edit in the Actions column.
On the Edit Edge Node Pool page, modify the editable parameters and click Submit.
NoteOnly the node pool name, node labels, and taints can be modified. For more information, see Edge node pool parameters.
Delete an edge node pool
On the Node Pools page, find the target node pool, click
in the Actions column, and then select Delete.In the Node Pool Deletion dialog box, read the notes, then click OK.
NoteIf the edge node pool contains any edge nodes, first remove the edge nodes, and then delete the node pool. Otherwise, the deletion fails.
Edge node pool parameters
Parameter | Modifiable | Description |
Node Pool Name |
| The name must be 1 to 63 characters long. It can contain letters, digits, underscores (_), and hyphens (-). It must start with a letter, a digit, or a Chinese character. |
Container Runtime |
| ACK Edge clusters of v1.24 and later support only the containerd runtime. |
Cloud-edge Network Connection |
| Internet: Nodes in the node pool interact with nodes in the cloud over the internet. Applications in the node pool cannot directly access the VPC internal network in the cloud. Select this option if your edge services have a low dependency on the cloud and have no requirements for communication quality or security. VPC: Nodes in the node pool connect to the cloud network through dedicated connections, such as Express Connect, a VPN gateway, or Cloud Enterprise Network (CEN). This provides more secure, higher-quality communication. We recommend that you select this option if your services require frequent cloud-edge interaction and have high standards for network quality and security. Set up the required dedicated network connection between the nodes and the cloud on your own in advance. |
Inter-node Connection |
| Yes: Enables Layer 3 network connectivity among all nodes in this node pool. Note Use case: A standard IDC or VPC is configured as a node pool where hosts communicate over an internal network. No: Disables Layer 3 network connectivity among all nodes in this node pool. Note Use case: A group of distributed edge devices are in the same node pool but do not require network communication with each other. |
Pod Network Type |
| Container Network: Each Pod has an independent network stack and does not use the host's network ports. This mode requires components such as Flannel, kube-proxy, and CoreDNS. It is suitable for scenarios that require granular control over the container network. Host Network: Pods use the host's network stack, sharing the same IP address 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. This mode supports larger cluster sizes and is suitable for lightweight services or scenarios where inter-service communication is not required. |
Node Labels |
| Adds labels to all nodes in the node pool. |
Taints |
| Adds taints to all nodes in the node pool. |
