Edge Node Onboarding¶

According to the node access configuration, obtain the installation files and access commands, and install the EdgeCore edge core software on the node, so that the edge node can establish a connection with DCE Cloud Edge Collaboration and be included in platform management.

When the edge node is first onboarded, the latest version of the EdgeCore edge core software is automatically installed.

The following onboarding procedure applies to Cloud Edge Collaboration module versions earlier than v0.20 (v0.20 not included). If your version is later than v0.20, refer to the latest Edge Node Onboarding Guide.

Prerequisites¶

• The node has been prepared as required and the node environment has been configured, please refer to Requirements to Join Edge Node for details.
• The edge node access configuration has been created, please refer to Create an Access Configuration for details.

Steps¶

1. On the Edge Node List page, click the Onboard Node button, and an onboarding dialog box will pop up on the right.

2. Based on the node environment configuration, select the corresponding access configuration.

3. Click the Download File button, which will redirect you to the Download Center. In the download list, select the edge installation package corresponding to the version and architecture: kantadm_{version}_{architecture}.tar.gz. It is recommended to choose the latest version.

   

4. Copy the edge installation package to the edge node to be onboarded and unzip it.

   Unzip command:

   tar -zxf kantadm_{version}_{arch}.tar.gz
   

   Note

   Place the unpacked kantadm binary file in the /usr/local/bin directory.

5. Onboard the node through the token or the certificate.

   Token InstallationCertificate Installation

   1. On the access configuration interface, click the Token Installation tab in the third step to display the token installation steps.

      Note

      The token in the installation command is valid for 24 hours. For a long-term valid installation method, please use certificate installation.

   2. Onboard the node by executing the following command.

      kantadm join \
        --cloudcore-host=10.31.226.14 \
        --websocket-port=30000 \
        --quic-port=30001 \
        --http-port=30002 \
        --stream-port=30003 \
        --tunnel-port=30004 \
        --node-prefix=edge \
        --token=b2d6bb5d9312c39ffac08ecfd5030bed006b8b67d0799d632d381f19fca9e765.eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2OTQ2NTk3NDV9.0sdaWbYSTURmAYmQwDn_zF7P9TwcRTSMhwPw6l87U7E \
        --cgroup-driver=cgroupfs \
        --remote-runtime-endpoint= \
        --version=v1.12.2 \
        --batch-name=edge \
        --edge-registry=docker.m.daocloud.io/kubeedge \
        --labels=test=1,test1=1
      

   1. On the node onboarding interface, click the Certificate Installation tab in the third step to display the certificate installation steps.

   2. Click the Download Certificate button to download the certificate to your local machine.

   3. Save the certificate and execute the following command.

      mkdir -p /etc/kant && mv ./cert.tar /etc/kant/cert.tar
      

   4. Onboard the node by executing the following command.

      kantadm join \
        --cloudcore-host=10.2.129.13 \
        --websocket-port=30000 \
        --quic-port=30001 \
        --http-port=30002 \
        --stream-port=30003 \
        --tunnel-port=30004 \
        --node-prefix=sh \
        --remote-runtime-endpoint=unix:///run/containerd/containerd.sock \
        --cgroup-driver=cgroupfs \
        --version=v1.12.6 \
        --batch-name=guide-test \
        --edge-registry=docker.m.daocloud.io/kubeedge
      

6. Verify if the edge node has been successfully onboarded.

   1. Select Edge Computing -> Cloud-Edge Collaboration from the left navigation bar to enter the edge unit list page.

   2. Click the edge unit name to enter the edge unit details page.

   3. Select Edge Resources -> Edge Nodes from the left navigation bar to enter the edge node list page.

   4. Check the status of the edge node. If the current status is Healthy, it means the onboarding was successful.

   

Comments