1

在使用 kubespray 将 Kubernetes 从 1.14 升级到 1.15 期间，我的团队在“升级第一个主服务器”步骤中遇到了以下消息的阻塞问题：

[upgrade/apply] FATAL: couldn''t upgrade control plane.
kubeadm has tried to recover everything into the earlier state.
Errors faced: [failed to renew certificates for component "kube-apiserver":
failed to renew certificate apiserver-kubelet-client:
unable to sign certificate:
must specify at least one ExtKeyUsage,
rename /etc/kubernetes/tmp/kubeadm
-backup-manifests-2019-09-19-09-06-27/kube-apiserver.yaml /etc/kubernetes/manifests/kube-apiserver.yaml: no such file or directory]'

尝试隔离任务并手动运行 kubeadm 命令行会导致相同的错误消息：

#/usr/local/bin/kubeadm upgrade apply -y v1.15.3 --config=/etc/kubernetes/kubeadm-config.yaml --ignore-preflight-errors=all --allow-experimental-upgrades --allow-release-candidate-upgrades --etcd-upgrade=false -v 6

甚至尝试手动更新证书：

/etc/kubernetes/pki# kubeadm alpha certs renew apiserver-kubelet-client -v 9
I0919 14:42:11.515503   18597 initconfiguration.go:105] detected and using CRI socket: /var/run/dockershim.sock
I0919 14:42:11.515897   18597 interface.go:384] Looking for default routes with IPv4 addresses
I0919 14:42:11.515916   18597 interface.go:389] Default route transits interface “eth0”
I0919 14:42:11.516284   18597 interface.go:196] Interface eth0 is up
(...)
I0919 14:42:11.516835   18597 feature_gate.go:216] feature gates: &{map[]}
failed to renew certificate apiserver-kubelet-client: unable to sign certificate: must specify at least one ExtKeyUsage

最终找到了解决方案并发布在下面。

4

1 回答 1

4

问题来自 kubeadm，它在必须更新旧证书时使用旧证书。但是当这些初始证书太旧或手动生成时，它们可能不包含一些需要存在的必填字段。

在错误消息中，ExtKeyUsage指的是X509v3 Extended Key Usage字段。

您可以通过查看您的证书来检查：涉及 2 个证书：apiserver-kubelet-client.crt和front-proxy-client.crt

它们位于位于 的主控主机上/etc/kubernetes/pki。

你可以检查他们

# openssl x509 -in apiserver-kubelet-client.crt -text -noout

如果它们不包含以下内容（接近尾声），那么 kubeadm 将完全无法更新证书

(...)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Extended Key Usage:
                TLS Web Client Authentication

TL;博士;

解决方案只是使用以下过程创建全新的证书

######### Backup your certificates (just in case)
master01:/etc/kubernetes/pki# cp -a /etc/kubernetes/pki /root/backup_cert/
######### Delete incomplete certificates
master01:/etc/kubernetes/pki# rm apiserver-kubelet-client.*
master01:/etc/kubernetes/pki# rm front-proxy-client.*
######### Then recreate them
master01:/etc/kubernetes/pki# kubeadm init phase certs apiserver-kubelet-client 
master01:/etc/kubernetes/pki# kubeadm init phase certs front-proxy-client

您现在可以重新启动升级过程，这应该没问题。（注意：如果您的集群处于您的第一个 master 处于 SchedulingDisabled 状态的状态，那么不要忘记解开主机，因为 kubespray playbook 无法解决该问题）

于 2019-09-20T10:46:10.007 回答