k8s编码由于属性max_concurrent而显示CrashLoopBackOff的豆荚

Question

我相信，在k8s从1.18提升到1.19后，这个问题已经提出来了。升级机群后，我没有检查。

k8scka@master:~$ kubectl get pods -n kube-system
NAME                                       READY   STATUS             RESTARTS   AGE
calico-kube-controllers-7dbc97f587-dfbwl   1/1     Running            0          8d
calico-node-jkgwv                          1/1     Running            0          10d
calico-node-wkncc                          1/1     Running            0          10d
coredns-66bff467f8-frh49                   0/1     CrashLoopBackOff   2093       7d10h
coredns-66bff467f8-wlb22                   0/1     CrashLoopBackOff   2092       7d10h
etcd-master                                1/1     Running            0          8d
kube-apiserver-master                      1/1     Running            0          8d
kube-controller-manager-master             1/1     Running            0          8d
kube-proxy-ljz55                           1/1     Running            0          8d
kube-proxy-w8nvg                           1/1     Running            0          8d
kube-scheduler-master                      1/1     Running            0          8d
k8scka@master:~$

Answer 1

否则，我们可以升级核心解决问题。

Answer 2

验证代码CM并删除属性max_concurrent.问题自动解决。