devbox
繁依Fanyi0
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

在ubuntu22.04上安装k8s-1.29.3_ubantu kubectlv1.29.3

作者：繁依Fanyi0 | 2024-05-21 06:37:30

赞

踩

ubantu kubectlv1.29.3

1、准备机器

1.1、安装虚拟机

    虚拟机镜像采用ubuntu-22.04.3-live-server-amd64.iso，一路回车直到系统安装完成。用root登录，能ping通宿主机和外网就可以了。

1.2、配置虚拟机
1.2.1、关闭防火墙
  1. # systemctl disable ufw
  2.  
  3.  
  4. // 若没有该config文件不做如下2行
  5. # sed -ri 's/SELINUX=permissive/SELINUX=disabled/' /etc/selinux/config
  6. # sed -ri 's/SELINUX=enforcing/SELINUX=disabled/' /etc/selinux/config
1.2.2、网络时间同步
  1. // 同步aliyun时间
  2. # apt install ntpdate
  3. # crontab -e
  4. 0 */1 * * * /usr/sbin/ntpdate time1.aliyun.com
  5.  
  6. // 设置时区
  7. # timedatectl set-timezone Asia/Shanghai
1.2.3、配置内核转发和网桥过滤
  1. // 配置
  2. # cat > /etc/sysctl.d/k8s.conf << EOF
  3. net.bridge.bridge-nf-call-ip6tables = 1
  4. net.bridge.bridge-nf-call-iptables = 1
  5. net.ipv4.ip_forward = 1
  6. vm.swappiness = 0
  7. EOF
  8.  
  9. // 启动
  10. # modprobe br_netfilter
  11.  
  12. // 检查
  13. # lsmod | grep br_netfilter
  14. br_netfilter           32768  0
  15. bridge                307200  1 br_netfilter
  16.  
  17. // 开机启动
  18. # cat > /etc/modules-load.d/k8s.conf << EOF
  19. overlay
  20. br_netfilter
  21. EOF
1.2.4、安装ipset和ipvsadm
  1. # apt install ipset ipvsadm
  2.  
  3. # cat > /etc/modules-load.d/ipvs.conf << EOF
  4. ip_vs
  5. ip_vs_rr
  6. ip_vs_wrr
  7. ip_vs_sh
  8. nf_conntrack
  9. EOF
1.2.5、关闭交换区
  1. # cat /etc/fstab
  2.  
  3. # <file system> <mount point>   <type>  <options>       <dump>  <pass>
  4. # / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
  5. /dev/disk/by-id/dm-uuid-LVM-aMgPZgZ6o3cHyNRGU08LFhzfZuvDoqjTrxFfUt6c3Zu3FwpXO7xWyoRZSNRaLZq1 / ext4 defaults 0 1
  6. # /boot was on /dev/sda2 during curtin installation
  7. /dev/disk/by-uuid/9314b4f8-368c-4f1b-ba74-9fb759ad9270 /boot ext4 defaults 0 1
  8. #/swap.img       none    swap    sw      0       0

注释掉最后关于交换区的一行。

1.2.6、配置/etc/hosts
  1. // 在/etc/hosts文件后面加上以下内容
  2. 10.0.1.11 master1
  3. 10.0.1.21 worker1
  4. 10.0.1.22 worker2
  5. 10.0.1.23 worker3

2、安装容器

2.1、安装containerd
  1. # apt install containerd
  2. # apt remove containerd
  3. // 在安装containerd的时候，系统附带重新安装了新的runc
  4.  
  5. // 然后到github上下载cri-containerd，才能支持crictl命令，可以在win下用迅雷下载比较快，然后复制到虚拟机上。
  6. # wget https://github.com/containerd/containerd/releases/download/v1.7.14/cri-containerd-1.7.14-linux-amd64.tar.gz
  7. // 解压
  8. # tar xvf cri-containerd-1.7.14-linux-amd64.tar.gz -C /
  9.  
  10. // 修改配置
  11. # mkdir /etc/containerd
  12. # containerd config default > /etc/containerd/config.toml
  13. // 将该文件里面65行的版本号改为3.9
  14. #    sandbox_image = "registry.k8s.io/pause:3.8"
  15.     sandbox_image = "registry.aliyuncs.com/google_containers/pause:3.9"
  16. // 将该文件里面137行改为true
  17. #             SystemdCgroup = false
  18.              SystemdCgroup = true
  19.  
  20.  
  21. // 最后将containerd设为开机自启动
  22. # systemctl enable containerd

3、构建k8s

3.1、下载k8s软件
3.1.1、snap下载
  1. // snap下载
  2. # snap install kubeadm --classic
  3.  
  4. # snap install kubectl --classic
  5.  
  6. # snap install kubelet --classic
  7.  
  8. // 查看kubelet服务状态
  9. # systemctl status snap.kubelet.daemon.service
  10.  
  11. # cd /etc/systemd/system
  12. # mv snap.kubelet.daemon.service kubelet.service
  13. # systemctl disable snap.kubelet.daemon.service
  14. # systemctl enable kubelet.service
  15. # reboot
  16.  
  17. apt install conntrack
  18. apt install socat
  19.  
  20.  
  21. // 关机
  22. # shutdown -h 0
  23.  
  24.
3.1.2、apt下载
  1. // apt下载
  2. // 从社区获取apt下载源包含k8s1.29版本，用aliyun也可以，但版本号最高为k8s1.28
  3. # curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.29/deb/Release.key | gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
  4.  
  5. # echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.29/deb/ /' | tee /etc/apt/sources.list.d/kubernetes.list
  6.  
  7. // 更新apt源
  8. # apt update
  9.  
  10. // 查看新源里面有什么版本的kubeadm
  11. # apt-cache policy kubeadm
  12. kubeadm:
  13.   Installed: (none)
  14.   Candidate: 1.28.2-00
  15.   Version table:
  16.      1.28.2-00 500
  17.         500 https://pkgs.k8s.io/core:/stable:/v1.28/deb  Packages
  18.      1.28.2-00 500
  19.         500 https://pkgs.k8s.io/core:/stable:/v1.28/deb  Packages
  20.      1.28.2-00 500
  21.         500 https://pkgs.k8s.io/core:/stable:/v1.28/deb  Packages
  22.      1.28.2-00 500
  23.         500 https://pkgs.k8s.io/core:/stable:/v1.28/deb  Packages
  24. // 发现最新版是1.28.2-00
  25.  
  26. // 进行安装
  27. # apt install kubeadm kubectl kubelet
  28. // 保持版本不被自动升级
  29. # apt-mark hold kubeadm kubectl kubelet
  30.  
  31. // 关机
  32. # shutdown -h 0
  33.  
  34.
3.2、复制虚拟机master1

在virtualbox里面复制一个虚拟机，取名k8s_master1，修改IP地址

在virtualbox里面复制一个虚拟机，取名k8s_worker1，修改IP地址

  1. # hostnamectl hostname master1
  2. // 各个worker虚拟机还需要修改IP地址，并将各自的IP和机器名称加入/etc/hosts
  3.  
  4.  
  5. // 在master1上做初始化
  6. # kubeadm init --kubernetes-version=v1.29.3 --image-repository registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/16
  7.  
  8. # kubeadm init --kubernetes-version=v1.29.3 --image-repository registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/16 --apiserver-advertise-address=10.0.1.11
  9.  
  10. // 一次成功！
  11. # kubeadm init --image-repository registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/16 --apiserver-advertise-address=10.0.1.11
  12. [init] Using Kubernetes version: v1.29.3
  13. [preflight] Running pre-flight checks
  14. [preflight] Pulling images required for setting up a Kubernetes cluster
  15. [preflight] This might take a minute or two, depending on the speed of your internet connection
  16. [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
  17. [certs] Using certificateDir folder "/etc/kubernetes/pki"
  18. [certs] Generating "ca" certificate and key
  19. [certs] Generating "apiserver" certificate and key
  20. [certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local master1] and IPs [10.96.0.1 10.0.1.11]
  21. [certs] Generating "apiserver-kubelet-client" certificate and key
  22. [certs] Generating "front-proxy-ca" certificate and key
  23. [certs] Generating "front-proxy-client" certificate and key
  24. [certs] Generating "etcd/ca" certificate and key
  25. [certs] Generating "etcd/server" certificate and key
  26. [certs] etcd/server serving cert is signed for DNS names [localhost master1] and IPs [10.0.1.11 127.0.0.1 ::1]
  27. [certs] Generating "etcd/peer" certificate and key
  28. [certs] etcd/peer serving cert is signed for DNS names [localhost master1] and IPs [10.0.1.11 127.0.0.1 ::1]
  29. [certs] Generating "etcd/healthcheck-client" certificate and key
  30. [certs] Generating "apiserver-etcd-client" certificate and key
  31. [certs] Generating "sa" key and public key
  32. [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
  33. [kubeconfig] Writing "admin.conf" kubeconfig file
  34. [kubeconfig] Writing "super-admin.conf" kubeconfig file
  35. [kubeconfig] Writing "kubelet.conf" kubeconfig file
  36. [kubeconfig] Writing "controller-manager.conf" kubeconfig file
  37. [kubeconfig] Writing "scheduler.conf" kubeconfig file
  38. [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
  39. [control-plane] Using manifest folder "/etc/kubernetes/manifests"
  40. [control-plane] Creating static Pod manifest for "kube-apiserver"
  41. [control-plane] Creating static Pod manifest for "kube-controller-manager"
  42. [control-plane] Creating static Pod manifest for "kube-scheduler"
  43. [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
  44. [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
  45. [kubelet-start] Starting the kubelet
  46. [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
  47. [apiclient] All control plane components are healthy after 4.503238 seconds
  48. [upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
  49. [kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
  50. [upload-certs] Skipping phase. Please see --upload-certs
  51. [mark-control-plane] Marking the node master1 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
  52. [mark-control-plane] Marking the node master1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
  53. [bootstrap-token] Using token: yyjh09.6he5wfuvsgpclctr
  54. [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
  55. [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
  56. [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
  57. [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
  58. [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
  59. [bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
  60. [kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
  61. [addons] Applied essential addon: CoreDNS
  62. [addons] Applied essential addon: kube-proxy
  63.  
  64. Your Kubernetes control-plane has initialized successfully!
  65.  
  66. To start using your cluster, you need to run the following as a regular user:
  67.  
  68.   mkdir -p $HOME/.kube
  69.   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  70.   sudo chown $(id -u):$(id -g) $HOME/.kube/config
  71.  
  72. Alternatively, if you are the root user, you can run:
  73.  
  74.   export KUBECONFIG=/etc/kubernetes/admin.conf
  75.  
  76. You should now deploy a pod network to the cluster.
  77. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  78.   https://kubernetes.io/docs/concepts/cluster-administration/addons/
  79.  
  80. Then you can join any number of worker nodes by running the following on each as root:
  81.  
  82. kubeadm join 10.0.1.11:6443 --token yyjh09.6he5wfuvsgpclctr \
  83.         --discovery-token-ca-cert-hash sha256:ea410f8b9757ca344212ff3e906ec9eb44f1902b5ee7a24bdb9c3fe9d8621d5a
  84.  
  85. // 安装成功了！检查一下
  86. # kubectl get node
  87. E0319 11:28:28.217021    8109 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
  88. E0319 11:28:28.217430    8109 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
  89. E0319 11:28:28.219640    8109 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
  90. E0319 11:28:28.219773    8109 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
  91. E0319 11:28:28.222284    8109 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
  92. The connection to the server localhost:8080 was refused - did you specify the right host or port?
  94. // 按照成功提示信息执行如下命令
  95. # mkdir -p $HOME/.kube
  96. # cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  97. # chown $(id -u):$(id -g) $HOME/.kube/config
  99. // 重新检查
  100. # kubectl get node
  101. NAME      STATUS     ROLES           AGE   VERSION
  102. master1   NotReady   control-plane   11m   v1.29.3
  104. # kubectl get pod -A
  105. NAMESPACE     NAME                              READY   STATUS    RESTARTS   AGE
  106. kube-system   coredns-857d9ff4c9-sl62g          0/1     Pending   0          12m
  107. kube-system   coredns-857d9ff4c9-z6jjq          0/1     Pending   0          12m
  108. kube-system   etcd-master1                      1/1     Running   0          12m
  109. kube-system   kube-apiserver-master1            1/1     Running   0          12m
  110. kube-system   kube-controller-manager-master1   1/1     Running   0          12m
  111. kube-system   kube-proxy-5l598                  1/1     Running   0          12m
  112. kube-system   kube-scheduler-master1            1/1     Running   0          12m
  116. // 在worker节点上按照master1上初始化成功之后的提示操作
  117. # kubeadm join 10.0.1.11:6443 --token yyjh09.6he5wfuvsgpclctr \
  118.         --discovery-token-ca-cert-hash sha256:ea410f8b9757ca344212ff3e906ec9eb44f1902b5ee7a24bdb9c3fe9d8621d5a
  120. // 按照成功提示信息执行如下命令
  121. # mkdir -p $HOME/.kube
  122. # cp -i /etc/kubernetes/kubelet.conf $HOME/.kube/config
  123. # chown $(id -u):$(id -g) $HOME/.kube/config
  125. // 检查节点加入情况
  126. # kubectl get node
  127. NAME      STATUS     ROLES           AGE    VERSION
  128. master1   NotReady   control-plane   91m    v1.29.3
  129. worker1   NotReady   <none>          7m3s   v1.29.3

4、构建网络

  1. // 用helm来安装calico，首先检查系统有没有安装helm
  2. # helm
  3. Command 'helm' not found, but can be installed with:
  4. snap install helm
  5.  
  6. // 没有安装，按照提示安装
  7. # snap install helm
  8. error: This revision of snap "helm" was published using classic confinement and thus may perform
  9.        arbitrary system changes outside of the security sandbox that snaps are usually confined to,
  10.        which may put your system at risk.
  11.  
  12.        If you understand and want to proceed repeat the command including --classic.
  13. root@master1:~# snap install helm --classic
  14. helm 3.14.3 from Snapcrafters✪ installed
  15.  
  16.  
  17. # Installing
  18.  
  19. 1. Add the projectcalico helm repository.
  20.  
  21.    ```
  22.    helm repo add projectcalico https://projectcalico.docs.tigera.io/charts
  23.    ```
  24.  
  25. 1. Create the tigera-operator namespace.
  26.  
  27.    ```
  28.    kubectl create namespace tigera-operator
  29.    ```
  30.  
  31. 1. Install the helm chart into the `tigera-operator` namespace.
  32.  
  33.    ```
  34.    helm install calico projectcalico/tigera-operator --namespace tigera-operator
  35.  
  36.  
  37.  
  38. // 检查
  39. # kubectl get pod -A
  40. NAMESPACE         NAME                                      READY   STATUS              RESTARTS   AGE
  41. calico-system     calico-kube-controllers-fbb8d4c9c-nqd9k   0/1     Pending             0          28s
  42. calico-system     calico-node-7v465                         0/1     Init:0/2            0          28s
  43. calico-system     calico-node-dbmx9                         0/1     Init:1/2            0          28s
  44. calico-system     calico-typha-8b695c9cc-v2vsf              1/1     Running             0          28s
  45. calico-system     csi-node-driver-64mpv                     0/2     ContainerCreating   0          28s
  46. calico-system     csi-node-driver-q5jm5                     0/2     ContainerCreating   0          28s
  47. kube-system       coredns-857d9ff4c9-sl62g                  0/1     Pending             0          100m
  48. kube-system       coredns-857d9ff4c9-z6jjq                  0/1     Pending             0          100m
  49. kube-system       etcd-master1                              1/1     Running             0          100m
  50. kube-system       kube-apiserver-master1                    1/1     Running             0          100m
  51. kube-system       kube-controller-manager-master1           1/1     Running             0          100m
  52. kube-system       kube-proxy-5l598                          1/1     Running             0          100m
  53. kube-system       kube-proxy-798fq                          1/1     Running             0          17m
  54. kube-system       kube-scheduler-master1                    1/1     Running             0          100m
  55. tigera-operator   tigera-operator-748c69cf45-gdhdg          1/1     Running             0          39s
  56.  
  57. // 一直重复检查，直到左右pod处于Running状态
  58. # kubectl get pod -A
  59. NAMESPACE          NAME                                      READY   STATUS    RESTARTS   AGE
  60. calico-apiserver   calico-apiserver-67dd77d667-4c4vf         0/1     Running   0          29s
  61. calico-apiserver   calico-apiserver-67dd77d667-8glv5         0/1     Running   0          29s
  62. calico-system      calico-kube-controllers-fbb8d4c9c-nqd9k   1/1     Running   0          2m11s
  63. calico-system      calico-node-7v465                         1/1     Running   0          2m11s
  64. calico-system      calico-node-dbmx9                         1/1     Running   0          2m11s
  65. calico-system      calico-typha-8b695c9cc-v2vsf              1/1     Running   0          2m11s
  66. calico-system      csi-node-driver-64mpv                     2/2     Running   0          2m11s
  67. calico-system      csi-node-driver-q5jm5                     2/2     Running   0          2m11s
  68. kube-system        coredns-857d9ff4c9-sl62g                  1/1     Running   0          102m
  69. kube-system        coredns-857d9ff4c9-z6jjq                  1/1     Running   0          102m
  70. kube-system        etcd-master1                              1/1     Running   0          102m
  71. kube-system        kube-apiserver-master1                    1/1     Running   0          102m
  72. kube-system        kube-controller-manager-master1           1/1     Running   0          102m
  73. kube-system        kube-proxy-5l598                          1/1     Running   0          102m
  74. kube-system        kube-proxy-798fq                          1/1     Running   0          18m
  75. kube-system        kube-scheduler-master1                    1/1     Running   0          102m
  76. tigera-operator    tigera-operator-748c69cf45-gdhdg          1/1     Running   0          2m22s
  77.  
  78.  
  79. // 检查node状态# kubectl get node
  80. NAME      STATUS   ROLES           AGE    VERSION
  81. master1   Ready    control-plane   102m   v1.29.3
  82. worker1   Ready    <none>          18m    v1.29.3
  83.  
  84. // worker1的校色标签为<none>，修改为worker
  85. # kubectl label node worker1 node-role.kubernetes.io/worker=worker
  86. node/worker1 labeled
  87.  
  88.

5、测试与监控

5.1、部署ngins进行测试

编写nginx.yaml

  1. apiVersion: apps/v1
  2. kind: Deployment
  3. metadata:
  4.   name: nginxweb
  5. spec:
  6.   selector:
  7.     matchLabels:
  8.       app: nginxweb1
  9.   replicas: 2
  10.   template:
  11.     metadata:
  12.       labels:
  13.         app: nginxweb1
  14.     spec:
  15.       containers:
  16.       - name: nginxwebc
  17.         image: nginx:latest
  18.         imagePullPolicy: IfNotPresent
  19.         ports:
  20.         - containerPort: 80
  21.  
  22. ---
  23. apiVersion: v1
  24. kind: Service
  25. metadata:
  26.   name: nginxweb-service
  27. spec:
  28.   externalTrafficPolicy: Cluster
  29.   selector:
  30.     app: nginxweb1
  31.   ports:
  32.   - protocol: TCP
  33.     port: 80
  34.     targetPort: 80
  35.     nodePort: 30080
  36.   type: NodePort
  1. # kubectl delete -f nginx.yaml
  2. deployment.apps "nginxweb" deleted
  3. service "nginxweb-service" deleted
  4.  
  5. # kubectl get all
  6. NAME                            READY   STATUS    RESTARTS   AGE
  7. pod/nginxweb-64c569cccc-rj47x   1/1     Running   0          2m59s
  8. pod/nginxweb-64c569cccc-wppsh   1/1     Running   0          2m59s
  9.  
  10. NAME                       TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
  11. service/kubernetes         ClusterIP   10.96.0.1      <none>        443/TCP        3h13m
  12. service/nginxweb-service   NodePort    10.96.240.49   <none>        80:30080/TCP   2m59s
  13.  
  14. NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
  15. deployment.apps/nginxweb   2/2     2            2           2m59s
  16.  
  17. NAME                                  DESIRED   CURRENT   READY   AGE
  18. replicaset.apps/nginxweb-64c569cccc   2         2         2       2m59s
  19.  
  20. # curl 10.96.240.49
  21. <!DOCTYPE html>
  22. <html>
  23. <head>
  24. <title>Welcome to nginx!</title>
  25. <style>
  26. html { color-scheme: light dark; }
  27. body { width: 35em; margin: 0 auto;
  28. font-family: Tahoma, Verdana, Arial, sans-serif; }
  29. </style>
  30. </head>
  31. <body>
  32. <h1>Welcome to nginx!</h1>
  33. <p>If you see this page, the nginx web server is successfully installed and
  34. working. Further configuration is required.</p>
  35.  
  36. <p>For online documentation and support please refer to
  37. <a href="http://nginx.org/">nginx.org</a>.<br/>
  38. Commercial support is available at
  39. <a href="http://nginx.com/">nginx.com</a>.</p>
  40.  
  41. <p><em>Thank you for using nginx.</em></p>
  42. </body>
  43. </html>
  44.  
  45. // 或者通过win浏览器访问http://10.0.1.11:30080
  46. Welcome to nginx!
  47. If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
  48.  
  49. For online documentation and support please refer to nginx.org.
  50. Commercial support is available at nginx.com.
  51.  
  52. Thank you for using nginx.
  53.  
  54.
5.2、安装dashboard
  1. # helm repo add kubernetes-dashboard https://kubernetes.github.io/dashboard/
  2. "kubernetes-dashboard" has been added to your repositories
  3. root@master1:~/test# helm upgrade --install kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard --create-namespace --namespace kubernetes-dashboard
  4. Release "kubernetes-dashboard" does not exist. Installing it now.
  5. NAME: kubernetes-dashboard
  6. LAST DEPLOYED: Wed Mar 20 08:08:32 2024
  7. NAMESPACE: kubernetes-dashboard
  8. STATUS: deployed
  9. REVISION: 1
  10. TEST SUITE: None
  11. NOTES:
  12. *************************************************************************************************
  13. *** PLEASE BE PATIENT: Kubernetes Dashboard may need a few minutes to get up and become ready ***
  14. *************************************************************************************************
  15.  
  16. Congratulations! You have just installed Kubernetes Dashboard in your cluster.
  17.  
  18. To access Dashboard run:
  19.   kubectl -n kubernetes-dashboard port-forward svc/kubernetes-dashboard-kong-proxy 8443:443
  20.  
  21. NOTE: In case port-forward command does not work, make sure that kong service name is correct.
  22.       Check the services in Kubernetes Dashboard namespace using:
  23.         kubectl -n kubernetes-dashboard get svc
  24.  
  25. Dashboard will be available at:
  26.   https://localhost:8443

上述安装不好使，下列安装一次成功！

最后得到如下的管理界面

完成任务，谢谢浏览！

声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/繁依Fanyi0/article/detail/601269
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号