You can add different types of resources to the edge node pool in a Container Service for Kubernetes (ACK) Edge cluster. These resources include Elastic Compute Service (ECS) instances from different regions, on-premises nodes, nodes from other cloud providers, and servers distributed in factories, stores, vehicles, and ships. This topic describes how to add an edge node to an edge node pool in an ACK Edge cluster.
Prerequisites
An ACK Edge cluster is created. For more information, see Create an ACK Edge cluster in the console.
Limits
Make sure that your cluster has a sufficient node quota. To add more nodes, submit an application in the Quota Center console. For more information about the quota limits of ACK Edge clusters, see Quotas and limits.
Some endpoints are accessed when you add edge nodes. You must configure the network security group for edge nodes to access required endpoints. For more information, see Configure endpoints and IP routing for edge nodes.
When adding edge nodes, you must choose an operating system for each node. The following table lists the operating systems that are supported for nodes:
Architecture
Operating system version
System kernel version
ACK Edge version
AMD64/x86_64
Anolis7.9 and Anolis8.6
4.19.X
1.16.9-aliyunedge.1 and later
AMD64/x86_64
Alibaba Cloud Linux 2.1903
4.19.X
1.20.11-aliyunedge.1 and later
AMD64/x86_64
Alibaba Cloud Linux 3
5.10.X
1.20.11-aliyunedge.1 and later
AMD64/x86_64
CentOS 7.4, CentOS 7.5, CentOS 7.6, CentOS 7.7, CentOS 7.8, and CentOS 7.9
3.10.X
1.12.6-aliyunedge.1 and later
AMD64/x86_64
CentOS 8.0 and CentOS 8.2
4.18.X
1.18.8-aliyunedge.1 and later
AMD64/x86_64
Ubuntu 16.04
4.4.X
1.18.8-aliyunedge.1 and later
AMD64/x86_64
Ubuntu 18.04
4.15.X
1.12.6-aliyunedge.1 and later
AMD64/x86_64
Ubuntu 18.04
5.4.X
1.16.9-aliyunedge.1 and later
AMD64/x86_64
Ubuntu 18.04
5.11.X
1.18.8-aliyunedge.1 and later
AMD64/x86_64
Ubuntu 20.04
5.4.X
1.18.8-aliyunedge.1 and later
AMD64/x86_64
Ubuntu 20.04 and Ubuntu 22.04
5.15.X
1.26.3-aliyun.1 and later
AMD64/x86_64
Red Hat Enterprise Linux 8.8 and Red Hat Enterprise Linux 8.10
4.18.X
1.26.3-aliyun.1 and later
AMD64/x86_64
Kylin V10
4.19.X
1.26.3-aliyun.1 and later
AMD64/x86_64
UnionTech OS Server 20
4.19.X
1.26.3-aliyun.1 and later
Arm64
CentOS 8.0
4.19.X
1.14.8-aliyunedge.1 and later
Arm64
Ubuntu 18.04
4.9.X
1.14.8-aliyunedge.1 and later
Arm64
Ubuntu 18.04
4.19.X
1.14.8-aliyunedge.1 and later
Arm64
Ubuntu 20.04
5.10.X
1.22.15-aliyunedge.1 and later
To add GPU-accelerated nodes, see Add a GPU-accelerated node.
Add a node
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 navigation pane, choose .
On the Node Pools page, find the node pool that you want to manage and choose in the Actions column.
On the page that appears, click Manual to manually add existing instances.
NoteIn manual mode, you can add ECS instances, ENS instances, and edge nodes.
Click Next Step to go to the Instance Information wizard page. You can set the parameters that are used to add the node. For more information, see Parameters.
NoteThe default value of Script Validity Period is 1 hour. If you want to use the script for more than 1 hour, you can set the validity period to meet your requirement. If you set Script Validity Period to 0 hours, the script is permanently valid.
After you set the parameters, click Next Step. On the Complete wizard page, click Copy to copy the script to the edge node that you want to add. Then, execute the script on the node.
If the following result is returned, the edge node is added to the cluster.
Parameters
Parameter | Description | Example |
| Specifies whether to add a node in the quiet mode. During the process of adding a node, some steps may require your intervention, such as deciding whether to reinstall the existing runtime on the node. |
|
| Specifies whether to use |
|
| The name of the node. |
|
| The list of components to be installed. For a regular node, set this parameter to ["kube-proxy","flannel","coredns"]. |
|
| Specifies whether the node to be added is a GPU-accelerated node. By default, this parameter is empty. For more information about the supported GPU models, see GPU models. |
|
| Specifies the labels to be added to the node. You can add labels to all nodes within the node pool. If there is a conflict between this |
|
| Specifies the annotations to be added to the node configurations. If there is a conflict between the |
|
| Specifies the taints to be added to the node. |
|
| Specifies the network interface controller (NIC). This parameter specifies the following information:
|
This value indicates that the name of the NIC that is recorded in the default route entry of the node is used by Flannel. |
| This parameter specifies the working directory of the runtime. The parameter takes effect only when |
|
| Specifies the source of system component images on the node. |
|
| Specifies whether to manually synchronize the time. |
|
| The name of the NIC that is used by the Flannel plug-in. We recommend that you use the nodeIface parameter instead. |
|
| Specifies whether to enable |
|
References
If you have any problems when you add edge nodes, see FAQs about edge nodes.
For more information about how to remove an edge node, see Remove edge nodes.
ACK Edge clusters support edge node autonomy. Edge node autonomy ensures that applications on an edge node can still run as expected when the edge node is disconnected from the cloud. For more information, see Configure edge node autonomy.