Deploy KubeSphere on DigitalOcean

KubeSphere+DOKS

This guide walks you through the steps of deploying KubeSphere on DigitalOcean Kubernetes.

Prepare a DOKS Cluster

A Kubernetes cluster in DO is a prerequisite for installing KubeSphere. Go to your DO account and refer to the image below to create a cluster from the navigation menu.

create-cluster-do

You need to select:

  1. Kubernetes version (e.g. 1.18.6-do.0)
  2. Datacenter region (e.g. Frankfurt)
  3. VPC network (e.g. default-fra1)
  4. Cluster capacity (e.g. 2 standard nodes with 2 vCPUs and 4GB of RAM each)
  5. A name for the cluster (e.g. kubesphere-3)

config-cluster-do

Note

  • To install KubeSphere v3.1.0 on Kubernetes, your Kubernetes version must be v1.17.x, v1.18.x, v1.19.x or v1.20.x.
  • 2 nodes are included in this example. You can add more nodes based on your own needs especially in a production environment.
  • The machine type Standard / 4 GB / 2 vCPUs is for minimal installation. If you plan to enable several pluggable components or use the cluster for production, you can upgrade your nodes to a more powerfull type (such as CPU-Optimized / 8 GB / 4 vCPUs). It seems that DigitalOcean provisions the master nodes based on the type of the worker nodes, and for Standard ones the API server can become unresponsive quite soon.

When the cluster is ready, you can download the config file for kubectl.

download-config-file

Install KubeSphere on DOKS

Now that the cluster is ready, you can install KubeSphere following the steps below:

  • Install KubeSphere using kubectl. The following commands are only for the default minimal installation.

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

  • Inspect the logs of installation:

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

When the installation finishes, you can see the following message:

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

Access KubeSphere Console

Now that KubeSphere is installed, you can access the web console of KubeSphere by following the steps below.

  • Go to the Kubernetes Dashboard provided by DigitalOcean.

    kubernetes-dashboard-access

  • Select the kubesphere-system namespace.

    kubernetes-dashboard-namespace

  • In Services under Service, edit the service ks-console.

    kubernetes-dashboard-edit

  • Change the type from NodePort to LoadBalancer. Save the file when you finish.

    lb-change

  • Access the KubeSphere’s web console using the endpoint generated by DO.

    access-console

    Tip

    Instead of changing the service type to LoadBalancer, you can also access KubeSphere console via NodeIP:NodePort (service type set to NodePort). You need to get the public IP of one of your nodes.

  • Log in to the console with the default account and password (admin/[[email protected]](https://kubesphere.io/cdn-cgi/l/email-protection)). In the cluster overview page, you can see the dashboard as shown in the following image.

    doks-cluster

Enable Pluggable Components (Optional)

The example above demonstrates the process of a default minimal installation. To enable other components in KubeSphere, see Enable Pluggable Components for more details.