Deploy KubeSphere on Oracle OKE

    • A standard Kubernetes cluster in OKE is a prerequisite of installing KubeSphere. Go to the navigation menu and refer to the image below to create a cluster.

    • In the pop-up window, select Quick Create and click Launch Workflow.

      oke-quickcreate

      Note

      In this example, Quick Create is used for demonstration which will automatically create all the resources necessary for a cluster in Oracle Cloud. If you select Custom Create, you need to create all the resources (such as VCN and LB Subnets) by yourself.

    • Next, you need to set the cluster with basic information. Here is an example for your reference. When you finish, click Next.

      Note

      • To install KubeSphere 3.2.0 on Kubernetes, your Kubernetes version must be v1.19.x, v1.20.x, v1.21.x, or v1.22.x (experimental).
      • In Oracle Cloud, a Shape is a template that determines the number of CPUs, amount of memory, and other resources that are allocated to an instance. is used in this example. For more information, see Standard Shapes.
      • 3 nodes are included in this example. You can add more nodes based on your own needs especially in a production environment.

    • Review cluster information and click Create Cluster if no adjustment is needed.

      create-cluster

    • Make sure the Cluster Status is Active and click Access Cluster.

      access-cluster

    • In the pop-up window, select Cloud Shell Access to access the cluster. Click Launch Cloud Shell and copy the code provided by Oracle Cloud.

    • In Cloud Shell, paste the command so that we can execute the installation command later.

      cloud-shell-oke

      Warning

      If you do not copy and execute the command above, you cannot proceed with the steps below.

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

    Now that KubeSphere is installed, you can access the web console of KubeSphere either through NodePort or LoadBalancer.

    • Check the service of KubeSphere console through the following command:

    • The output may look as below. You can change the type to LoadBalancer so that the external IP address can be exposed.

      Tip

      It can be seen above that the service ks-console is being exposed through a NodePort, which means you can access the console directly via NodeIP:NodePort (the public IP address of any node is applicable). You may need to open port in firewall rules.

    • Execute the command to edit the service configuration.

    • Navigate to type and change NodePort to LoadBalancer. Save the configuration after you finish.

      change-svc-type

    • Execute the following command again and you can see the IP address displayed as below.

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