背景:

持续升级过程:Kubernetes 1.16.15升级到1.17.17,Kubernetes 1.17.17升级到1.18.20Kubernetes 1.18.20升级到1.19.12

集群配置:

主机名 系统 ip
k8s-vip slb 10.0.0.37
k8s-master-01 centos7 10.0.0.41
k8s-master-02 centos7 10.0.0.34
k8s-master-03 centos7 10.0.0.26
k8s-node-01 centos7 10.0.0.36
k8s-node-02 centos7 10.0.0.83
k8s-node-03 centos7 10.0.0.40
k8s-node-04 centos7 10.0.0.49
k8s-node-05 centos7 10.0.0.45
k8s-node-06 centos7 10.0.0.18

1. 参考官方文档

参照:https://kubernetes.io/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/

2. 确认可升级版本与升级方案

  1. yum list --showduplicates kubeadm --disableexcludes=kubernetes

通过以上命令查询到1.20当前最新版本是1.20.9-0版本。master有三个节点还是按照个人习惯先升级k8s-master-03节点
image.png

3. 升级k8s-master-03节点控制平面

依然k8s-master-03执行:

1. yum升级kubernetes插件

  1. yum install kubeadm-1.20.9-0 kubelet-1.20.9-0 kubectl-1.20.9-0 --disableexcludes=kubernetes

image.png

2. 腾空节点检查集群是否可以升级

依然算是温习drain命令:

  1. kubectl drain k8s-master-03 --ignore-daemonsets
  2. sudo kubeadm upgrade plan

image.png

3. 升级版本到1.20.9

  1. kubeadm upgrade apply 1.20.9

image.png

  1. [root@k8s-master-03 ~]# sudo systemctl daemon-reload
  2. [root@k8s-master-03 ~]# sudo systemctl restart kubelet
  3. [root@k8s-master-03 ~]# kubectl uncordon k8s-master-03
  4. node/k8s-master-03 uncordoned
  5. [root@k8s-master-03 ~]# kubectl get nodes
  6. [root@k8s-master-03 ~]# kubectl get pods -n kube-system

image.png
image.png

4. 升级其他控制平面(k8s-master-01 k8s-master-02)

  1. yum install kubeadm-1.20.9-0 kubelet-1.20.9-0 kubectl-1.20.9-0 --disableexcludes=kubernetes
  2. sudo kubeadm upgrade node
  3. sudo systemctl daemon-reload
  4. sudo systemctl restart kubelet

image.png
image.png

5. work节点的升级

  1. yum install kubeadm-1.20.9-0 kubelet-1.20.9-0 kubectl-1.20.9-0 --disableexcludes=kubernetes
  2. sudo kubeadm upgrade node
  3. sudo systemctl daemon-reload
  4. sudo systemctl restart kubelet

注: 个人都没有腾空节点,看个人需求了
image.png
image.png

6. 验证升级

  1. kubectl get nodes

image.png

7. 其他——v1.20.0中禁用了selfLink

由于我的Prometheus oprator是0.4的分支,就准备卸载重新安装了。版本差距太大了。现在也不想搞什么分支用了直接用主线版本了:
基本过程参照:Kubernetes 1.20.5 安装Prometheus-Oprator。基本过程都没有问题,讲一个有问题的地方:
我的kubernetes1.16升级上来的这个集群storageclass是用的nfs:

  1. kubectl get sc

image.png
最后一

  1. kubectl get pods -n monitoring
  2. kubectl logs -f prometheus-operator-84dc795dc8-lkl5r -n monitoring

image.png
image.png
看关键词吧:
additional 貌似是自动发现的配置?
首先将prometheus-prometheus.yaml文件中的自动发现的配置注释掉。嗯服务还是没有起来,再看一眼日志:

  1. kubectl logs -f prometheus-operator-84dc795dc8-lkl5r -n monitoring

没有什么新的输出,但是看一眼pv,pvc没有创建。去看一下nfs的pod日志:

  1. kubectl get pods -n nfs
  2. kubectl logs -f nfs-client-provisioner-6cb4f54cbc-wqqw9 -n nfs

image.png
class “managed-nfs-storage”: unexpected error getting claim reference: selfLink was empty, can’t make reference
百度selfLink参照:https://www.orchome.com/10024
image.png
修改三个master节点的kube-apiserver.yaml
然后pv,pvc创建成功 Prometheus 服务启动成功。然后再回过头来看一眼我的additional自动发现配置:
我在Kubernetes 1.20.5 安装Prometheus-Oprator
image.png
拿我的老版本的这个文件试试?:

  1. cat <<EOF > prometheus-additional.yaml
  2. - job_name: 'kubernetes-service-endpoints'
  3. kubernetes_sd_configs:
  4. - role: endpoints
  5. relabel_configs:
  6. - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
  7. action: keep
  8. regex: true
  9. - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
  10. action: replace
  11. target_label: __scheme__
  12. regex: (https?)
  13. - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
  14. action: replace
  15. target_label: __metrics_path__
  16. regex: (.+)
  17. - source_labels: [__address__, __meta_kubernetes_service_annotation_prometheus_io_port]
  18. action: replace
  19. target_label: __address__
  20. regex: ([^:]+)(?::\d+)?;(\d+)
  21. replacement: $1:$2
  22. - action: labelmap
  23. regex: __meta_kubernetes_service_label_(.+)
  24. - source_labels: [__meta_kubernetes_namespace]
  25. action: replace
  26. target_label: kubernetes_namespace
  27. - source_labels: [__meta_kubernetes_service_name]
  28. action: replace
  29. target_label: kubernetes_name
  30. EOF
  1. kubectl delete secret additional-configs -n monitoring
  2. kubectl create secret generic additional-configs --from-file=prometheus-additional.yaml -n monitoring

再看日志启动起来了。初步先怀疑我配置文件中的prometheus-additional.yaml 有问题。当然了这是个人问题了。强调的主要是master节点kube-apiserver.yaml文件的修改添加:

  1. - --feature-gates=RemoveSelfLink=false