Shulou(Shulou.com)06/02 Report--

After normal installation and deployment of Kubernetes Dashboard, you cannot access it through some browsers (such as Chrome browser). This is usually due to a problem with the date of the certificate generated when deploying Kubernetes Dashboard. The solution can be solved in the form of a self-signed certificate.

Based on the previous test deployment environment

IP address hostname system kernel version CPU memory 192.168.100.6master01.cluster.k8CentOS 7.65.2.64c4G192.168.100.7node01.cluster.k8CentOS 7.65.2.64c4G192.168.100.8node02.cluster.k8CentOS 7.65.2.64c4G1, Generate self-signed certificate 1) generate certificate request keyopenssl genrsa-out dashboard.key 20482) generate certificate request openssl req-days 3650-new-out dashboard.csr-key dashboard.key-subj'/ CN=**192.168.100.6**'3) generate self-signed certificate openssl x509-req-in dashboard.csr-signkey dashboard.key-out dashboard.crt2, Create a secret1 with the same name as in the KubernetesDashboard deployment file) delete the previously deployed Dashboardkubectl delete-f kubernetes-dashboard.yaml2) create a secret with the same name as in the KubernetesDashboard deployment file

Kubectl create secret generic kubernetes-dashboard-certs-- from-file=dashboard.key-- from-file=dashboard.crt3) comment on the Dashboard Secret section of the kubernetes-dashboard.yaml file

4) reapply and deploy the kubernetes-dashboard.yaml file kubectl apply-f kubernetes-dashboard.yaml3, access it through the browser, and you can basically open it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.