Kubernetes binary deployment (4) web UI Interface deployment

This is the fourth article on kubernetes binary deployment

If you haven't read the first article before, you can take a look at the following:

Kubernetes binary deployment (1) single node deployment

Kubernetes binary deployment (II) Multi-node deployment

Kubernetes binary deployment (3) load balanced deployment

Operate 1 on master01, create dashborad working directory [root@localhost K8s] # mkdir dashboard2, copy official files [root@localhost K8s] # cd dashboard/ [root@localhost dashboard] # ls dashboard-configmap.yaml dashboard-rbac.yaml dashboard-service.yamldashboard-controller.yaml dashboard-secret.yaml k8s-admin.yaml## related files purpose: dashboard-configmap.yaml: configure application dashboard-rbac.yaml: authorize access to api Web interface dashboard-service.yaml: access application dashboard-controller.yaml: controller dashboard-secret.yaml: security, encryption k8s-admin.yaml: generate token 3, Component creation [root@localhost dashboard] # kubectl create-f dashboard-rbac.yamlrole.rbac.authorization.k8s.io/kubernetes-dashboard-minimal createdrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard-minimal created [root@localhost dashboard] # kubectl create-f dashboard-secret.yamlsecret/kubernetes-dashboard-certs createdsecret/kubernetes-dashboard-key-holder created [root@localhost dashboard] # kubectl create-f dashboard-configmap.yamlconfigmap/kubernetes-dashboard-settings created [root@localhost dashboard] # kubectl create-f dashboard-controller. Yamlserviceaccount/kubernetes-dashboard createddeployment.apps/kubernetes-dashboard created [root@localhost dashboard] # kubectl create-f dashboard-service.yamlservice/kubernetes-dashboard created4, After completion, view how to create [root@localhost dashboard] # kubectl get pods-n kube-systemNAME READY STATUS RESTARTS AGEkubernetes-dashboard-65f974f565-8b88b 1 Running 0 2m56s5 under the specified kube-system namespace, and see how to access [root@localhost dashboard] # kubectl get pods Svc-n kube-systemNAME READY STATUS RESTARTS AGEpod/kubernetes-dashboard-65f974f565-8b88b 1 Running 0 4m4sNAME TYPE CLUSTER-IP EXTERNAL-IP PORT (S) AGEservice/kubernetes-dashboard NodePort 10.0.0.26 443:30001/TCP 3m50s6, If you visit nodeIP, you can access the browser and access https://192.168.35.101:30001/.

7. The solution to the problem that google browser cannot access is as follows: (1) self-signed certificate [root@localhost dashboard] # vim dashboard-cert.shcat > dashboard-csr.json