Enable Pluggable Components - Quickstart

    For more information about each component, see Overview of Enable Pluggable Components.

    Note

    • multicluster is not covered in this tutorial. If you want to enable this feature, you need to set a corresponding value for clusterRole. For more information, see .
    • Make sure your machine meets the hardware requirements before the installation. Here is the recommendation if you want to enable all pluggable components: CPU ≥ 8 Cores, Memory ≥ 16 G, Disk Space ≥ 100 G.

    For most of the pluggable components, you can follow the steps below to enable them. If you need to enable KubeEdge, and Service Topology, refer to the corresponding tutorials directly.

    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 , you create a default file config-sample.yaml. Modify the file by executing the following command:

      Note

      If you adopt All-in-one Installation, 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 pluggable components in this mode (for example, for testing purpose), refer to the to see how pluggable components can be installed after installation.

    2. In this file, enable the pluggable components you want to install by changing false to for enabled. Here is the complete file for your reference. Save the file after you finish.

    3. Create a cluster using the configuration file:

      1. ./kk create cluster -f config-sample.yaml

    Installing on Kubernetes

    1. First download the file cluster-configuration.yaml and edit it.

    2. To enable the pluggable component you want to install, change false to true for enabled under the component in this file.

    3. Save this local file and execute the following commands to start installation.

      1. kubectl apply -f cluster-configuration.yaml

    Whether you install KubeSphere on Linux or on Kubernetes, you can check the status of the components you have enabled in the web console of KubeSphere after installation. Go to System Components, and you can see the component status.

    Enable Pluggable Components After Installation

    The KubeSphere web console provides a convenient way for users to view and operate on different resources. To enable pluggable components after installation, you only need to make few adjustments on the console directly. For those who are accustomed to the Kubernetes command-line tool, kubectl, they will have no difficulty in using KubeSphere as the tool is integrated into the console.

    Note

    If you need to enable KubeEdge, and Service Topology, refer to the corresponding tutorials directly.

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

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

      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.

    3. In Custom Resources, click the three dots on the right of ks-installer and select Edit YAML.

    4. In this YAML file, enable the pluggable components you want to install by changing false to true for enabled. After you finish, click OK to save the configuration.

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

      Tip

      You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.

    6. The output will display a message as below if the component is successfully installed.

      1. #####################################################
      2. ### Welcome to KubeSphere! ###
      3. Console: http://192.168.0.2:30880
      4. Password: [email protected]
      5. NOTES
      6. 1. After you log into the console, please check the
      7. monitoring status of service components in
      8. "Cluster Management". If any service is not
      9. ready, please wait patiently until all components
      10. are up and running.
      11. 2. Please change the default password after login.
      12. #####################################################
      13. https://kubesphere.io 20xx-xx-xx xx:xx:xx
      14. #####################################################