kubectl exec 拨号后端时出错:x509:由未知机构签名的证书

问题描述 投票:0回答:2

经过长时间的努力,我刚刚创建了集群,部署了一个示例容器 busybox,现在我尝试运行命令 exec,但出现以下错误:

拨打后端时出错:x509:由未知机构签署的证书

我该如何解决这个问题:这是 v=9 日志级别的命令输出。 kubectl exec -v=9 -ti busybox -- nslookup kubernetes 我还在日志中注意到,这个失败的curl命令实际上是第一个GET命令传递的第二个命令,它返回结果没有任何问题..(GEThttps://myloadbalancer.local:6443/api/v1/命名空间/默认/pods/busybox 200 OK

curl -k -v -XPOST  -H "X-Stream-Protocol-Version: v4.channel.k8s.io" -H "X-Stream-Protocol-Version: v3.channel.k8s.io" -H "X-Stream-Protocol-Version: v2.channel.k8s.io" -H "X-Stream-Protocol-Version: channel.k8s.io" -H "User-Agent: kubectl/v1.19.0 (linux/amd64) kubernetes/e199641" 'https://myloadbalancer.local:6443/api/v1/namespaces/default/pods/busybox/exec?command=nslookup&command=kubernetes&container=busybox&stdin=true&stdout=true&tty=true'
I1018 02:19:40.776134  129813 round_trippers.go:443] POST https://myloadbalancer.local:6443/api/v1/namespaces/default/pods/busybox/exec?command=nslookup&command=kubernetes&container=busybox&stdin=true&stdout=true&tty=true 500 Internal Server Error in 43 milliseconds
I1018 02:19:40.776189  129813 round_trippers.go:449] Response Headers:
I1018 02:19:40.776206  129813 round_trippers.go:452]     Content-Type: application/json
I1018 02:19:40.776234  129813 round_trippers.go:452]     Date: Sun, 18 Oct 2020 02:19:40 GMT
I1018 02:19:40.776264  129813 round_trippers.go:452]     Content-Length: 161
I1018 02:19:40.776277  129813 round_trippers.go:452]     Cache-Control: no-cache, private
I1018 02:19:40.777904  129813 helpers.go:216] server response object: [{
  "metadata": {},
  "status": "Failure",
  "message": "error dialing backend: x509: certificate signed by unknown authority",
  "code": 500
}]
F1018 02:19:40.778081  129813 helpers.go:115] Error from server: error dialing backend: x509: certificate signed by unknown authority
goroutine 1 [running]:

添加更多信息: 这是在 UBUNTU 20.04 上。作为初学者,我一步步手动创建集群,我需要这种经验,而不是使用 kubeadm 或 minikube 等工具来进行操作

xxxx@master01:~$ kubectl exec -ti busybox -- nslookup kubernetes
Error from server: error dialing backend: x509: certificate signed by unknown authority
xxxx@master01:~$ kubectl get pods --all-namespaces
NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE
default                busybox                                      1/1     Running   52         2d5h
kube-system            coredns-78cb77577b-lbp87                     1/1     Running   0          2d5h
kube-system            coredns-78cb77577b-n7rvg                     1/1     Running   0          2d5h
kube-system            weave-net-d9jb6                              2/2     Running   7          2d5h
kube-system            weave-net-nsqss                              2/2     Running   0          2d14h
kube-system            weave-net-wnbq7                              2/2     Running   7          2d5h
kube-system            weave-net-zfsmn                              2/2     Running   0          2d14h
kubernetes-dashboard   dashboard-metrics-scraper-7b59f7d4df-dhcpn   1/1     Running   0          2d3h
kubernetes-dashboard   kubernetes-dashboard-665f4c5ff-6qnzp         1/1     Running   7          2d3h
tinashe@master01:~$ kubectl logs busybox
Error from server: Get "https://worker01:10250/containerLogs/default/busybox/busybox": x509: certificate signed by unknown authority
xxxx@master01:~$

xxxx@master01:~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
kubernetes kubectl kubelet
2个回答
1
投票

**为简单起见进行了编辑:

我的集群操作员 kube-apiserver 降级,导致我的证书失败。解决降级问题是解决总体问题所必需的,从而导致 x509 错误。验证所有 master 均已就绪,apiserver 项目中的 pod 也已计划并准备就绪。请参阅下面的 KCS 了解更多信息:

https://access.redhat.com/solutions/4849711

**删除了以下有关本地证书拉取/导出的过时/不正确信息。


0
投票

当服务器的 IP 更改(在新虚拟机上恢复快照)时,我遇到了类似的问题。经过一番努力,我能够修复重新生成服务器证书的问题。

如果您正在运行标准 Kubernetes:

kubeadm certs renew all 

以我使用 Microk8s 为例:

sudo microk8s refresh-certs --cert ca.crt
sudo microk8s refresh-certs --cert front-proxy-client.crt
sudo microk8s refresh-certs --cert server.crt
© www.soinside.com 2019 - 2024. All rights reserved.