This topic describes how to add an edge node as a worker node to an existing Container Service for Kubernetes (ACK) Edge cluster in the ACK console. Make sure that the node to be added can communicate with the Kubernetes API server of the cluster. You can add Elastic Compute Service (ECS) instances, Edge Node Service (ENS) instances, and on-premises servers to an ACK Edge cluster.
Prerequisites
An ACK Edge cluster is created. For more information, see Create an ACK Edge cluster.
ENS is activated and an edge service is created if you want the system to automatically add edge nodes.
Limits
Make sure that you have a sufficient node quota in the cluster. To add more nodes, submit an application in the . For more information about the quota limits of ACK Edge clusters, see Limits.
Only ENS nodes with at least 2 vCPUs and 4 GB of memory can be automatically added to an ACK Edge cluster. In addition, the ENS nodes must be in the Running state and run CentOS 7.4 or 7.6.
If you want to manually add nodes, the nodes must run operating systems that are listed in the following table.
Architecture
Operating system version
System kernel version
ACK Edge version
AMD64/X86_64
Anolis7.9 and Anolis8.6
4.19.X
1.22.15-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
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
Add a node
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of the cluster that you want to manage and choose in the left-side navigation pane.
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, you can select Manual to manually add existing instances.
NoteIn Manual mode, you can add ECS instances, ENS instances, and on-premises servers.
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 | Usage notes | Standard mode |
flannelIface | The name of the network interface controller (NIC) that is used by the Flannel plug-in. | The name of the NIC that is recorded in the default route entry of the node. | |
enableIptables | Specifies whether to enable |
| |
quiet | Specifies whether to answer all questions with |
| |
manageRuntime | Specifies whether to use edgeadm to install and manage the runtime. |
| |
nodeNameOverride | The name of the node. |
| |
allowedClusterAddons | The list of components to be installed. By default, this parameter is left empty, which indicates that no component is installed. For a regular node, set this parameter to ["kube-proxy","flannel","coredns"]. |
| |
gpuVersion | Specifies whether the node to be added is a GPU-accelerated node. By default, this parameter is empty. The following GPU models are supported: Nvidia_Tesla_T4, Nvidia_Tesla_P4, Nvidia_Tesla_P100, Nvidia_Tesla_V100, and Nvidia_Tesla_A10. |
| |
inDedicatedNetwork | Specifies whether an Express Connect circuit is used to add the node to the ACK Edge cluster. |
| |
labels | Specifies the labels to be added to the node. |
| |
annotations | Specifies the annotations to be added to the node configurations. |
| |
nodeIface | This parameter specifies the following information:
|
| |
runtimeRootDir | This parameter specifies the working directory of the runtime. The parameter takes effect only when |
|
Public IP addresses to be accessed when you add nodes
Access address | Description |
cs-anony.aliyuncs.com | None |
aliacs-k8s-{{region}}.oss-{{region}}.aliyuncs.com |
|
Public endpoint of the API server | You can view the public endpoint of the API server on the Basic Information tab. |
The IP address of the Internet-facing SLB instance that is created for tunnel-server | The public endpoint of Services in the cluster kube-system/x-tunnel-server-svc. |
ntp1.aliyun.com cn.ntp.org.cn | None |
dockerauth-{{region}}.aliyuncs.com |
|
aliregistry-{{region}}.oss-{{region}}.aliyuncs.com |
|
registry.{{region}}.aliyuncs.com |
|
System tools: net-tools, iproute, chrony (or ntpdate), crontabs, pciutils, socat, ebtables, iptables, and conntrack-tools |
|