[kubernetes series] kubesphere is installed on kubernetes

---

One 、 preparation

1. Version for

stay Kubernetes Installation on KubeSphere 3.3.0,Kubernetes Version must be ：v1.19.x,v1.20.x,v1.21.x,v1.22.x or v1.23.x（ Experimental support ）. If the version does not meet the requirements , Please refer to 【Kubernetes series 】K8s from 1.24.1 Downgrade to 1.23.8 Downgrade or upgrade to a qualified version .

2. Hardware requirements

The machine meets the minimum hardware requirements ：CPU > 1 nucleus , Memory > 2 GB.

3. Requirements configured StorageClass

Kubernetes The cluster has been configured with default settings StorageClass. Confirmation method ：

kubectl get sc

[[email protected] ~]# kubectl get sc
NAME                  PROVISIONER      RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE                                                                                                     
managed-nfs-storage   fuseim.pri/ifs   Delete          Immediate           false                  3h6m       

Two 、 Deploy KubeSphere

1. install

Execute the following command to install ：

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

It's common to report mistakes ：

[[email protected] kubesphere]# kubectl apply -f kubesphere-installer.yaml 
namespace/kubesphere-system created
serviceaccount/ks-installer created
clusterrole.rbac.authorization.k8s.io/ks-installer created
clusterrolebinding.rbac.authorization.k8s.io/ks-installer created
deployment.apps/ks-installer created
error: unable to recognize "kubesphere-installer.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"

resolvent ：
Modify the configuration file kubesphere-installer.yaml, take “apiextensions.k8s.io/v1beta1” Change it to “apiextensions.k8s.io/v1”.

2. Check the log

Check the installation log ：

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

3. see Pod

see Pod Is it working ：

kubectl get pod --all-namespaces

kubectl get pods --all-namespaces
NAMESPACE           NAME                                      READY   STATUS    RESTARTS   AGE
kube-system         calico-kube-controllers-6b77fff45-czfmp   1/1     Running   0          60m
kube-system         calico-node-fsbl4                         1/1     Running   0          60m
kube-system         coredns-6d8c4cb4d-cpjh9                   1/1     Running   0          20h
kube-system         coredns-6d8c4cb4d-csc8f                   1/1     Running   0          20h
kube-system         etcd-master01                             1/1     Running   0          20h
kube-system         kube-apiserver-master01                   1/1     Running   0          20h
kube-system         kube-controller-manager-master01          1/1     Running   0          20h
kube-system         kube-proxy-r5rtc                          1/1     Running   0          20h
kube-system         kube-scheduler-master01                   1/1     Running   0          20h
kubesphere-system   ks-installer-c9655d997-vb2pr              1/1     Running   0          8m33s

4. View console

If Pod Running normally , Check the port of the console with the following command （ The default is 30880）：

kubectl get svc/ks-console -n kubesphere-system

[[email protected] ~]# kubectl get svc/ks-console -n kubesphere-system
NAME         TYPE       CLUSTER-IP    EXTERNAL-IP   PORT(S)        AGE
ks-console   NodePort   10.10.3.219   <none>        80:30880/TCP   6h59m

5. visit Web Console

Make sure that the port... Is open in the security group 30880, And pass NodePort (IP:30880) Use default account and password (admin/[email protected]) visit Web Console .
http://192.168.1.28:30880