Skip to content

Create External Edge Unit

External Edge Unit refers to integrating the existing KubeEdge installed in the enterprise system into DCE 5.0 Cloud Edge for unified management.

KubeEdge: An open-source system that extends native containerized application orchestration capabilities to edge nodes.

  • CloudCore: The core component of KubeEdge on the cloud side.
  • ControllerManager: KubeEdge CRD extension currently used for edge applications and edge node groups.

The following explains the steps to create an external edge unit:

  1. Select Cloud Edge Collaboration from the left navigation bar to enter the edge unit list page. Click the Create Edge Unit button at the top right of the page, and select External Edge Unit from the dropdown list;

    Create External Edge Unit

  2. Fill in the basic information;

    • Edge Unit Name: A combination of lowercase letters, numbers, hyphens (-), and dots (.), with no consecutive symbols; must start and end with a letter or number; can contain up to 253 characters.
    • Cluster: The cluster running the edge unit control plane.
    • KubeEdge Version: A specific version of the KubeEdge open-source system for extending containerized application orchestration capabilities to edge hosts, built on Kubernetes and providing infrastructure support for network applications.
    • Description: Description information of the edge unit.

    Note

    If you are working with a single-node cluster, please ensure that the master node supports scheduling by removing the NoSchedule taint. This will prevent failures during the installation of system components.

    Basic Information

  3. Fill in Advanced Settings

    Note

    If you use the online installation method, you only need to complete the access configuration. If you use the offline one, you also need to provide the component repository information.

    Access Settings

    It refers to the access settings for KubeEdge cloud components. Edge nodes use these settings to establish a connection with the cloud.

    • Communication Protocol: the communication protocol for the cloud-edge signaling channel. When the cloud-edge network is frequently unstable, it is recommended to use the QUIC protocol.
    • Access Address: the access address for the KubeEdge cloud component CloudCore, which needs to be accessible by edge nodes. Edge nodes use this address to establish a connection with the cloud.
    • Ports: CloudCore on the cloud side opens NodePort ports to the edge by default. If there is a conflict, please modify them.
      • WebSocketPort: the port for the WebSocket access protocol, default is 10000.
      • QUICPort: the port for the QUIC access protocol, default is 10001.
      • HTTPServerPort: the HTTP service port, default is 10002.
      • CloudStreamPort: the cloud stream processing interface port, default is 10003.
      • TunnelPort: the data channel port for edge node business data, default is 10004.

    Network Config

  4. After completing the above information configuration, click the OK button to finish creating the edge unit, and automatically return to the edge unit list.

Next step: Manage Edge Units

Comments