Kubesphere 与 Rancher 有什么区别？

mkdir -p /home/ks cd /home/ks

export KKZONE=cn curl -sfL https://get-kk.kubesphere.io | sh -

curl -sfL https://get-kk.kubesphere.io | VERSION={version} sh -

./kk version --show-supported-k8s v1.19.0 v1.19.8 v1.19.9 v1.19.15 ... v1.29.10 v1.30.0 v1.30.1 v1.30.2 v1.30.3 v1.30.4 v1.30.5 v1.30.6 v1.31.0 v1.31.1 v1.31.2

./kk create config --with-kubernetes v1.30.6

./kk init os

apiVersion: kubekey.kubesphere.io/v1alpha2 kind: Cluster metadata: name: sample spec: hosts: - {name: node1, address: 192.168.150.128, internalAddress: 192.168.150.128, user: root, password: "123@213"} roleGroups: etcd: - node1 control-plane: - node1 worker: - node1 controlPlaneEndpoint: ## Internal loadbalancer for apiservers # internalLoadbalancer: haproxy domain: lb.kubesphere.local address: "" port: 6443 system: ntpServers: - node1 # 配置时间同步，所有节点服务器同步node1的时间 timezone: "Asia/Shanghai" kubernetes: version: v1.30.6 clusterName: cluster.local autoRenewCerts: true # 此处修改运行时为:docker containerManager: docker # 部署 kubernetes v1.24+ 版本，建议将 containerManager 设置为 containerd etcd: type: kubekey network: plugin: calico kubePodsCIDR: 10.233.64.0/18 kubeServiceCIDR: 10.233.0.0/18 ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni multusCNI: enabled: false registry: privateRegistry: "" namespaceOverride: "" registryMirrors: [] insecureRegistries: [] addons: []

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

root@gj-VM:/home/ks# ./kk create cluster -f config-sample.yaml _ __ _ _ __ | | / / | | | | / / | |/ / _ _| |__ ___| |/ / ___ _ _ | \| | | | '_ \ / _ \ \ / _ \ | | | | |\ \ |_| | |_) | __/ |\ \ __/ |_| | \_| \_/\__,_|_.__/ \___\_| \_/\___|\__, | __/ | |___/ 11:39:29 CST [GreetingsModule] Greetings 11:39:29 CST message: [node1] Greetings, KubeKey! 11:39:29 CST success: [node1] 11:39:29 CST [NodePreCheckModule] A pre-check on nodes 11:39:29 CST success: [node1] 11:39:29 CST [ConfirmModule] Display confirmation form +-------+------+------+---------+----------+-------+-------+---------+-----------+--------+--------+------------+------------+-------------+------------------+--------------+ | name | sudo | curl | openssl | ebtables | socat | ipset | ipvsadm | conntrack | chrony | docker | containerd | nfs client | ceph client | glusterfs client | time | +-------+------+------+---------+----------+-------+-------+---------+-----------+--------+--------+------------+------------+-------------+------------------+--------------+ | node1 | y | y | y | y | y | y | y | y | y | | y | | | | CST 11:39:29 | +-------+------+------+---------+----------+-------+-------+---------+-----------+--------+--------+------------+------------+-------------+------------------+--------------+ This is a simple check of your environment. Before installation, ensure that your machines meet all requirements specified at https://github.com/kubesphere/kubekey#requirements-and-recommendations Install k8s with specify version: v1.30.6 [Notice] For Kubernetes v1.24 and later, dockershim has been deprecated. Current runtime is set to Docker and `cri-dockerd` will be installed to support Kubernetes v1.24 and later. Yoc can also specify a container runtime other than Docker to install Kubernetes v1.24 or later. You can set "spec.kubernetes.containerManager" in the configuration file to "containerd" or add "--container-manager containerd" to the "./kk create cluster" command. For more information, see: https://github.com/kubesphere/kubekey/blob/master/docs/commands/kk-create-cluster.md https://kubernetes.io/docs/setup/production-environment/container-runtimes/#container-runtimes https://kubernetes.io/blog/2022/02/17/dockershim-faq/ https://github.com/Mirantis/cri-dockerd Continue this installation? [yes/no]:

11:50:23 CST success: [LocalHost] 11:50:23 CST Pipeline[CreateClusterPipeline] execute successfully Installation is complete. Please check the result using the command: kubectl get pod -A

root@gj-VM:/home/ks# kubectl get pod -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system calico-kube-controllers-848b87ffbc-6hh97 1/1 Running 0 29m kube-system calico-node-ks586 1/1 Running 0 29m kube-system coredns-848f88b9dc-hsmh9 1/1 Running 0 29m kube-system coredns-848f88b9dc-k9djl 1/1 Running 0 29m kube-system kube-apiserver-node1 1/1 Running 0 29m kube-system kube-controller-manager-node1 1/1 Running 0 29m kube-system kube-proxy-2l2rx 1/1 Running 0 29m kube-system kube-scheduler-node1 1/1 Running 0 29m kube-system nodelocaldns-l59qn 1/1 Running 0 29m

curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash root@gj-VM:/home/ks# curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11903 100 11903 0 0 13760 0 --:--:-- --:--:-- --:--:-- 13760 [WARNING] Could not find git. It is required for plugin installation. Helm v3.16.3 is available. Changing from version v3.14.3. Downloading https://get.helm.sh/helm-v3.16.3-linux-amd64.tar.gz Verifying checksum... Done. Preparing to install helm into /usr/local/bin helm installed into /usr/local/bin/helm

helm upgrade --install -n kubesphere-system --create-namespace ks-core https://charts.kubesphere.io/main/ks-core-1.1.3.tgz --debug --wait --set global.imageRegistry=swr.cn-southwest-2.myhuaweicloud.com/ks

Thank you for choosing KubeSphere Helm Chart. Please be patient and wait for several seconds for the KubeSphere deployment to complete. 1. Wait for Deployment Completion Confirm that all KubeSphere components are running by executing the following command: kubectl get pods -n kubesphere-system 2. Access the KubeSphere Console Once the deployment is complete, you can access the KubeSphere console using the following URL: http://192.168.150.128:30880 3. Login to KubeSphere Console Use the following credentials to log in: Account: admin Password: P@88w0rd

root@node1:~# kubectl get pod -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system calico-kube-controllers-848b87ffbc-2mqwb 1/1 Running 1 (2m25s ago) 130m kube-system calico-node-kmspv 1/1 Running 1 (2m25s ago) 130m kube-system coredns-9dc95d955-4th25 1/1 Running 1 (2m25s ago) 130m kube-system coredns-9dc95d955-zr77b 1/1 Running 1 (2m25s ago) 130m kube-system kube-apiserver-node1 1/1 Running 1 (2m25s ago) 131m kube-system kube-controller-manager-node1 1/1 Running 1 (2m25s ago) 131m kube-system kube-proxy-rlnsq 1/1 Running 1 (2m25s ago) 130m kube-system kube-scheduler-node1 1/1 Running 1 (2m25s ago) 131m kube-system nodelocaldns-rx4w2 1/1 Running 1 (2m25s ago) 130m kubesphere-system extensions-museum-d77fddd77-5tqpp 1/1 Running 1 (2m25s ago) 70m kubesphere-system ks-apiserver-59b7c94c77-fpkmv 1/1 Running 1 (2m25s ago) 70m kubesphere-system ks-console-b9ff8948c-687zd 1/1 Running 1 (2m25s ago) 70m kubesphere-system ks-controller-manager-777888fdb8-nlkmr 1/1 Running 1 (2m25s ago) 70m

kubectl config view --raw

clusters: - cluster: server: https://<member-cluster-node-ip>:6443

docker tag swr.cn-southwest-2.myhuaweicloud.com/ks/kubesphere/kubectl:v1.27.17 kubesphere/kubectl:v1.27.17 docker tag swr.cn-southwest-2.myhuaweicloud.com/ks/kubesphere/ks-console:v4.1.2 kubesphere/ks-console:v4.1.2