Deploy KubeSphere on GKE
This guide walks you through the steps of deploying KubeSphere on Google Kubernetes Engine.
Prepare a GKE Cluster
A standard Kubernetes cluster in GKE is a prerequisite of installing KubeSphere. Go to the navigation menu and refer to the image below to create a cluster.
In Cluster basics, select a Master version. The static version
1.15.12-gke.2
is used here as an example.In default-pool under Node Pools, define 3 nodes in this cluster.
Go to Nodes, select the image type and set the Machine Configuration as below. When you finish, click Create.
Note
- To install KubeSphere 3.4 on Kubernetes, your Kubernetes version must be v1.20.x, v1.21.x, v1.22.x, v1.23.x, * v1.24.x, * v1.25.x, and * v1.26.x. For Kubernetes versions with an asterisk, some features of edge nodes may be unavailable due to incompatability. Therefore, if you want to use edge nodes, you are advised to install Kubernetes v1.23.x.
- 3 nodes are included in this example. You can add more nodes based on your own needs especially in a production environment.
- The machine type e2-medium (2 vCPU, 4GB memory) is for minimal installation. If you want to enable pluggable components or use the cluster for production, please select a machine type with more resources.
- For other settings, you can change them as well based on your own needs or use the default value.
When the GKE cluster is ready, you can connect to the cluster with Cloud Shell.
Install KubeSphere on GKE
Install KubeSphere using kubectl. The following commands are only for the default minimal installation.
kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.4.1/kubesphere-installer.yaml kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.4.1/cluster-configuration.yaml
Inspect the logs of installation:
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l 'app in (ks-install, ks-installer)' -o jsonpath='{.items[0].metadata.name}') -f
When the installation finishes, you can see the following message:
##################################################### ### Welcome to KubeSphere! ### ##################################################### Console: http://10.128.0.44:30880 Account: admin Password: P@88w0rd NOTES: 1. After logging into the console, please check the monitoring status of service components in the "Cluster Management". If any service is not ready, please wait patiently until all components are ready. 2. Please modify the default password after login. ##################################################### 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.
In Services & Ingress, select the service ks-console.
In Service details, click Edit and change the type from
NodePort
toLoadBalancer
. Save the file when you finish.Access the web console of KubeSphere using the endpoint generated by GKE.
Tip
Instead of changing the service type toLoadBalancer
, you can also access KubeSphere console viaNodeIP:NodePort
(service type set toNodePort
). You may need to open port30880
in firewall rules.Log in to the console with the default account and password (
admin/P@88w0rd
). In the cluster overview page, you can see the dashboard.
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.
Feedback
Was this page Helpful?
Receive the latest news, articles and updates from KubeSphere
Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.