KubeEdge

    KubeEdge has components running in two separate places - cloud and edge nodes. The components running on the cloud, collectively known as CloudCore, include Controllers and Cloud Hub. Cloud Hub serves as the gateway for the requests sent by edge nodes while Controllers function as orchestrators. The components running on edge nodes, collectively known as EdgeCore, include EdgeHub, EdgeMesh, MetadataManager, and DeviceTwin. For more information, see the KubeEdge website.

    After you enable KubeEdge, you can and deploy workloads on them.

    When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.

    1. In the tutorial of Installing KubeSphere on Linux, you create a default file . Modify the file by executing the following command:

      Note

      If you adopt , you do not need to create a config-sample.yaml file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable KubeEdge in this mode (for example, for testing purposes), refer to the following section to see how KubeEdge can be installed after installation.

    2. In this file, navigate to kubeedge.enabled and change false to true.

      1. kubeedge:
      2.   enabled: true # Change "false" to "true".
      1. ./kk create cluster -f config-sample.yaml

    Installing on Kubernetes

    As you install KubeSphere on Kubernetes, you can enable KubeEdge first in the file.

    1. Download the file cluster-configuration.yaml and edit it.

    2. In this local file, navigate to kubeedge.enabled and enable it by setting it to true.

      1. kubeedge:
      2.   enabled: true # Change "false" to "true".

    3. Set the value of kubeedge.cloudCore.cloudHub.advertiseAddress to the public IP address of your cluster or an IP address that can be accessed by edge nodes.

    4. Save the file and execute the following commands to start installation:

      1. kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.2.0/kubesphere-installer.yaml
      2. kubectl apply -f cluster-configuration.yaml

    1. Log in to the console as . Click Platform in the upper-left corner and select Cluster Management.

    2. Click CRDs and enter clusterconfiguration in the search bar. Click the result to view its detail page.

      Info

      A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.

    4. In this YAML file, navigate to kubeedge.enabled and enable it by setting it to true.

    5. Set the value of kubeedge.cloudCore.cloudHub.advertiseAddress to the public IP address of your cluster or an IP address that can be accessed by edge nodes. After you finish, click OK in the lower-right corner to save the configuration.

    6. You can use the web kubectl to check the installation process by executing the following command:

      1. kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f

      Note

      You can find the web kubectl tool by clicking KubeEdge - 图3 in the lower-right corner of the console.

    On the Cluster Management page, verify that the Edge Nodes module has appeared under Nodes.

    Execute the following command to check the status of Pods:

    1. kubectl get pod -n kubeedge

    The output may look as follows if the component runs successfully:

    Note