Release Notes
Announcements
Release Notes
Creating a Registered Node
Directions
Installing Operating Systems for Registered Nodes
Currently, registered nodes must use [TencentOS Server 3.1] or [TencentOS Server 2.4 (TK4)]. Details are as follows:
Operating System | Description | Download URL |
TencentOS Server 3.1 | It is compatible with the CentOS 8 user mode and uses the T-Kernel 4 deeply optimized based on LTS kernel 5.4. | |
TencentOS Server 2.4 (TK4) | It is compatible with the CentOS 7 user mode and uses the T-Kernel 4 deeply optimized based on LTS kernel 5.4. |
Note:
TencentOS Server is the Linux operating system designed by Tencent for cloud scenarios. With specific features and optimized performance, it provides a high-performance, secure, and reliable operating environment for applications in Cloud Virtual Machine (CVM) instances.
Enabling Support for Registered Nodes
Cluster of the Global Router Mode
If your cluster is networked in Global Router (GR) mode, you can enable registered nodes of the Direct Connect (DC) version and the public network version.
1. Log in to the TKE console and click Cluster in the left sidebar.
2. On the Cluster management page, click the desired cluster ID to go to the Basic information page.
3. Click the Registered Node switch.
4. You can enable direct connect access and public network access seperately.
5. Click Enable.
Cluster of the VPC-CNI Mode
If your cluster is networked in VPC-CNI mode, you can only enable registered nodes of the DC version as follows:
Cluster of the Cilium-Overly Mode
If your cluster is networked in Cilium-Overlay mode, registered nodes can be automatically added to the cluster.
Set Container network add-on to Cilium-Overlay.
Subnet: TKE will create a proxy ENI in the selected subnet for registered nodes to access cloud resources.
After the Cilium-Overlay cluster is created, the registered node feature is enabled by default. To query related information, log in to the TKE console and choose Basic information > Node management > Worker node.
Adding a Registered Node
Creating a Registered Node Pool
Note:
Registered nodes can be managed only through the registered node pool.
1. Log in to the TKE console and click Cluster in the left sidebar.
2. On the Cluster management page, click the desired cluster ID to go to the Basic information page.
3. Choose Node management > Worker node in the left sidebar to go to the Node pool tag page.
4. Click Create to open the "Select the node type" page, and select Registered node pool.
5. Specify the configurations on "Node pool" page.
Network type: Select Direct Connect access or Public Network access.
Node type: Select CPU node or GPU node. This selection is available only DC access.
Node pool name: It specifies the name of the node pool.
Container directory: Select this option to set up the container and image storage directory. It is recommended to store to the data disk, such as
/var/lib/docker.Runtime components: It specifies the runtime component of the container. docker and containerd are supported.
Runtime version: It specifies the version of the runtime component.
Cordon initial nodes: If Cordon this node is selected, new pods cannot be scheduled to this node. You can uncordon the node manually, or run the uncordon command in custom data as needed.
Labels: Click Add and customize the settings of the label. The specified label will be automatically added to nodes created in the node pool to help filter and manage external nodes using labels.
Taints: This is a node-level attribute and is usually used with
Tolerations. You can specify this parameter for all the nodes in the node pool, so as to stop scheduling pods that do not meet the requirements to these nodes and drain such pods from the nodes.
The value of Taints usually consists of key, value, and effect. Valid values of effect:PreferNoSchedule: Optional. Try not to schedule a pod to a node with a taint that cannot be tolerated by the pod.
NoSchedule: When a node contains a taint, a pod without the corresponding toleration must not be scheduled.
NoExecute: When a node contains a taint, a pod without the corresponding toleration to the taint are not be scheduled to the node and any such pods already on the node are drained.
Annotations: You can use Kubernetes annotations to attach arbitrary non-identifying metadata to objects.
Management: Parameters of kubelet, nameservers, hosts, and KernelArgs (kernel) can be configured.
Kubelet custom parameter: You can customize kubelet parameters.
Custom data: Specify custom data to configure the node, that is, to run the configured script when the node is started. You need to ensure the reentrant and retry logic of the script. The script and its log files can be viewed in the node path:
/usr/local/qcloud/tke/userscript.6. Click Create.
Adding a Registered Node
Do the following to add registered nodes to the node pool:
1. On the node pool page, click the desired node pool ID.
2. On the node pool details page, click Create node to get the script.
3. In the CPU node initialization script window, select a value for Node initialization method, and copy or download the script. When this is a "Direct Connect access" node pool:
Public network: Selected by default. For an IDC node, directly download the installation script file (31 KB in size) over the public network.
Private network: If your IDC node cannot access the public network, access the private network through a DC line to download the installation script file.
4. When this is a "Public Network access" node pool, the script is generated automatically.
5. Run the script on your server.
Note:
The script download link is valid for 1 hour. Since the script is downloaded by using COS, you need to ensure that the IDC node can access COS through the private/public network.
6. Run the following command to add the "Direct Connect access" node:
./ add2tkectl-cls-m57oxxxp-np-xxxx install
Note:
If the node fails to be added because the related Docker and containerd add-ons are installed on an external node, run the following command to delete the add-ons and add the node again:
./add2tkectl-cls-m57oxxxp-np-xxxx clear
7. Run the following command to add the "Public Network access" node:
./ edgectl install -n [nodeName]
Note:
If the node fails to be added because the related Docker and containerd add-ons are installed on an external node, run the following command to delete the add-ons and add the node again:
./edgectl clear
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback