【发布时间】:2019-05-19 17:29:34
【问题描述】:
上下文
我们目前在 kubernetes(v1.8.7) 上有 3 个稳定的集群。这些集群是由一个不再可用的外部团队创建的,我们的文档有限。我们正在尝试升级到更高的稳定版本(v1.13.0)。我们知道我们需要一次升级 1 个版本,所以 1.8 -> 1.9 -> 1.10 等等。
已解决的问题
- 关于如何从 1.8 升级到 1.9 的任何指示?
-
我们尝试安装 kubeadm v1.8.7 并运行
kubeadm upgrade plan,但输出失败 -[飞行前] 运行飞行前检查 无法从文件“/etc/kubernetes/admin.conf”创建 Kubernetes 客户端:无法加载管理员 kubeconfig [打开 /etc/kubernetes/admin.conf:没有这样的文件或目录]
我们找不到文件 admin.conf。关于我们如何重新生成它或它需要什么信息的任何建议?
新问题
由于我们现在有了 admin.conf 文件,我们安装了 kubectl、kubeadm 和 kubelet v 1.9.0 -apt-get install kubelet=1.9.0-00 kubeadm=1.9.0-00 kubectl=1.9.0-00。
当我运行kubeadm upgrade plan v1.9.0
我明白了
root@k8s-master-dev-0:/home/azureuser# kubeadm upgrade plan v1.9.0
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/health] FATAL: [preflight] Some fatal errors occurred:
[ERROR APIServerHealth]: the API Server is unhealthy; /healthz didn't return "ok"
[ERROR MasterNodesReady]: couldn't list masters in cluster: Get https://<k8s-master-dev-0 ip>:6443/api/v1/nodes?labelSelector=node-role.kubernetes.io%2Fmaster%3D: dial tcp <k8s-master-dev-0 ip>:6443: getsockopt: connection refused
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
root@k8s-master-dev-0:/home/azureuser# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
heapster-75f8df9884-nxn2z 2/2 Running 0 42d
kube-addon-manager-k8s-master-dev-0 1/1 Running 2 1d
kube-addon-manager-k8s-master-dev-1 1/1 Running 4 123d
kube-addon-manager-k8s-master-dev-2 1/1 Running 2 169d
kube-apiserver-k8s-master-dev-0 1/1 Running 100 1d
kube-apiserver-k8s-master-dev-1 1/1 Running 4 123d
kube-apiserver-k8s-master-dev-2 1/1 Running 2 169d
kube-controller-manager-k8s-master-dev-0 1/1 Running 3 1d
kube-controller-manager-k8s-master-dev-1 1/1 Running 4 123d
kube-controller-manager-k8s-master-dev-2 1/1 Running 4 169d
kube-dns-v20-5d9fdc7448-smf9s 3/3 Running 0 42d
kube-dns-v20-5d9fdc7448-vtjh4 3/3 Running 0 42d
kube-proxy-cklcx 1/1 Running 1 123d
kube-proxy-dldnd 1/1 Running 4 169d
kube-proxy-gg89s 1/1 Running 0 169d
kube-proxy-mrkqf 1/1 Running 4 149d
kube-proxy-s95mm 1/1 Running 10 169d
kube-proxy-zxnb7 1/1 Running 2 169d
kube-scheduler-k8s-master-dev-0 1/1 Running 2 1d
kube-scheduler-k8s-master-dev-1 1/1 Running 6 123d
kube-scheduler-k8s-master-dev-2 1/1 Running 4 169d
kubernetes-dashboard-8555bd85db-4txtm 1/1 Running 0 42d
tiller-deploy-6677dc8d46-5n5cp 1/1 Running 0 42d
【问题讨论】:
标签: kubernetes upgrade kubeadm