由于证书问题,无法启动通过头盔部署的kubernetes仪表板

时间:2020-04-05 08:00:21

标签: kubernetes openssl ssl-certificate kubernetes-helm kubernetes-dashboard

我对kubernetes非常陌生,并通过Google和社交平台学习kubernetes。我在启动最近使用舵机部署的kubernetes仪表板时遇到了问题。

设置

使用虚拟盒通过流浪者设置集群,节点运行ubuntu 18.04。

Kubectl版本v1.13.0

头盔版本:“ v3.1.2通过chocolaty安装在Windows 10 Powershell上。

问题陈述

我已经使用来自稳定版/ kubernetes-dashboard版本1.10.1的helm命令部署了kubernetes-dashboard。我已经使用NodePort公开了Kubedashboard服务,但是当我尝试通过Chrome连接到本地Windows系统上的kubernetes-dashboard时,出现以下错误。

Your connection is not private
Attackers might be trying to steal your information from 192.168.5.21 (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_INVALID

vagrant@master-1:~$ curl -vvv https://192.168.5.21:32224
* Rebuilt URL to: https://192.168.5.21:32224/
*   Trying 192.168.5.21...
* TCP_NODELAY set
* Connected to 192.168.5.21 (192.168.5.21) port 32224 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: self signed certificate
* stopped the pause stream!
* Closing connection 0
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

我想了解为什么应用程序生成自签名证书而不使用主节点的CA证书。您能帮我解决这个问题吗?

谢谢

0 个答案:

没有答案