请稍等 ...
×

采纳答案成功!

向帮助你的同学说点啥吧!感谢那些助人为乐的人

calico 容器启动不起来

老师您好! 麻烦您帮我分析下 通过报错的问题我也没有解决。
离线安装-k8s-1.22.1 calico-3.19.3

[root@k8s-master ~]# kubectl get pods --all-namespaces  -o wide
NAMESPACE     NAME                                       READY   STATUS                  RESTARTS      AGE     IP            NODE         NOMINATED NODE   READINESS GATES
default       myngx1-5476695b96-2l84m                    0/1     Pending                 0             17h     <none>        <none>       <none>           <none>
kube-system   calico-kube-controllers-6b59cd85f8-s264z   0/1     ContainerCreating       0             3m55s   <none>        k8s-master   <none>           <none>
kube-system   calico-node-6htkk                          0/1     Init:ImagePullBackOff   0             3m55s   10.24.24.70   k8s-node01   <none>           <none>
kube-system   calico-node-h6w9f                          0/1     CrashLoopBackOff        5 (51s ago)   3m55s   10.24.24.71   k8s-master   <none>           <none>

[root@k8s-master ~]# kubectl describe pod calico-kube-controllers-6b59cd85f8-s264z -n kube-system
Name:                 calico-kube-controllers-6b59cd85f8-s264z
Namespace:            kube-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Node:                 k8s-master/10.24.24.71
Start Time:           Mon, 06 Jun 2022 11:02:22 +0800
Labels:               k8s-app=calico-kube-controllers
                      pod-template-hash=6b59cd85f8
Annotations:          <none>
Status:               Pending
IP:                   
IPs:                  <none>
Controlled By:        ReplicaSet/calico-kube-controllers-6b59cd85f8
Containers:
  calico-kube-controllers:
    Container ID:   
    Image:          docker.io/calico/kube-controllers:v3.19.3
    Image ID:       
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Liveness:       exec [/usr/bin/check-status -l] delay=10s timeout=1s period=10s #success=1 #failure=6
    Readiness:      exec [/usr/bin/check-status -r] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      ENABLED_CONTROLLERS:  node
      DATASTORE_TYPE:       kubernetes
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-bqt5r (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  kube-api-access-bqt5r:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 CriticalAddonsOnly op=Exists
                             node-role.kubernetes.io/master:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age                   From               Message
  ----     ------                  ----                  ----               -------
  Warning  FailedScheduling        4m58s                 default-scheduler  0/2 nodes are available: 2 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.
  Normal   Scheduled               4m50s                 default-scheduler  Successfully assigned kube-system/calico-kube-controllers-6b59cd85f8-s264z to k8s-master
  Warning  FailedCreatePodSandBox  4m48s                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "d22b3cfabda3f56960655df37f2c25248476f943178641622bda4bcea462e343" network for pod "calico-kube-controllers-6b59cd85f8-s264z": networkPlugin cni failed to set up pod "calico-kube-controllers-6b59cd85f8-s264z_kube-system" network: error getting ClusterInformation: connection is unauthorized: Unauthorized, failed to clean up sandbox container "d22b3cfabda3f56960655df37f2c25248476f943178641622bda4bcea462e343" network for pod "calico-kube-controllers-6b59cd85f8-s264z": networkPlugin cni failed to teardown pod "calico-kube-controllers-6b59cd85f8-s264z_kube-system" network: error getting ClusterInformation: connection is unauthorized: Unauthorized]
  Normal   SandboxChanged          11s (x23 over 4m48s)  kubelet            Pod sandbox changed, it will be killed and re-created.


[root@k8s-master ~]# journalctl -f  -u kubelet
-- Logs begin at 六 2022-06-04 11:41:48 CST. --
6月 06 11:19:48 k8s-master kubelet[10648]: E0606 11:19:48.453881   10648 kuberuntime_manager.go:989] "Failed to stop sandbox" podSandboxID={Type:docker ID:d22b3cfabda3f56960655df37f2c25248476f943178641622bda4bcea462e343}
6月 06 11:19:48 k8s-master kubelet[10648]: E0606 11:19:48.453933   10648 kuberuntime_manager.go:751] "killPodWithSyncResult failed" err="failed to \"KillPodSandbox\" for \"2ca91924-d990-4bad-8a08-b5c829a86001\" with KillPodSandboxError: \"rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \\\"calico-kube-controllers-6b59cd85f8-s264z_kube-system\\\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized\""
6月 06 11:19:48 k8s-master kubelet[10648]: E0606 11:19:48.453973   10648 pod_workers.go:747] "Error syncing pod, skipping" err="failed to \"KillPodSandbox\" for \"2ca91924-d990-4bad-8a08-b5c829a86001\" with KillPodSandboxError: \"rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \\\"calico-kube-controllers-6b59cd85f8-s264z_kube-system\\\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized\"" pod="kube-system/calico-kube-controllers-6b59cd85f8-s264z" podUID=2ca91924-d990-4bad-8a08-b5c829a86001
6月 06 11:19:52 k8s-master kubelet[10648]: E0606 11:19:52.381046   10648 pod_workers.go:747] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"calico-node\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=calico-node pod=calico-node-h6w9f_kube-system(68698bda-003b-4bce-a5c3-6851a0111d73)\"" pod="kube-system/calico-node-h6w9f" podUID=68698bda-003b-4bce-a5c3-6851a0111d73
6月 06 11:20:01 k8s-master kubelet[10648]: E0606 11:20:01.461179   10648 cni.go:380] "Error deleting pod from network" err="error getting ClusterInformation: connection is unauthorized: Unauthorized" pod="kube-system/calico-kube-controllers-6b59cd85f8-s264z" podSandboxID={Type:docker ID:d22b3cfabda3f56960655df37f2c25248476f943178641622bda4bcea462e343} podNetnsPath="" networkType="calico" networkName="k8s-pod-network"
6月 06 11:20:01 k8s-master kubelet[10648]: E0606 11:20:01.461816   10648 remote_runtime.go:144] "StopPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"calico-kube-controllers-6b59cd85f8-s264z_kube-system\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized" podSandboxID="d22b3cfabda3f56960655df37f2c25248476f943178641622bda4bcea462e343"
6月 06 11:20:01 k8s-master kubelet[10648]: E0606 11:20:01.461850   10648 kuberuntime_manager.go:989] "Failed to stop sandbox" podSandboxID={Type:docker ID:d22b3cfabda3f56960655df37f2c25248476f943178641622bda4bcea462e343}
6月 06 11:20:01 k8s-master kubelet[10648]: E0606 11:20:01.461890   10648 kuberuntime_manager.go:751] "killPodWithSyncResult failed" err="failed to \"KillPodSandbox\" for \"2ca91924-d990-4bad-8a08-b5c829a86001\" with KillPodSandboxError: \"rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \\\"calico-kube-controllers-6b59cd85f8-s264z_kube-system\\\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized\""
6月 06 11:20:01 k8s-master kubelet[10648]: E0606 11:20:01.461941   10648 pod_workers.go:747] "Error syncing pod, skipping" err="failed to \"KillPodSandbox\" for \"2ca91924-d990-4bad-8a08-b5c829a86001\" with KillPodSandboxError: \"rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \\\"calico-kube-controllers-6b59cd85f8-s264z_kube-system\\\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized\"" pod="kube-system/calico-kube-controllers-6b59cd85f8-s264z" podUID=2ca91924-d990-4bad-8a08-b5c829a86001
6月 06 11:20:05 k8s-master kubelet[10648]: E0606 11:20:05.380626   10648 pod_workers.go:747] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"calico-node\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=calico-node pod=calico-node-h6w9f_kube-system(68698bda-003b-4bce-a5c3-6851a0111d73)\"" pod="kube-system/calico-node-h6w9f" podUID=68698bda-003b-4bce-a5c3-6851a0111d73

[root@k8s-master ~]# docker images
REPOSITORY                                                                      TAG       IMAGE ID       CREATED         SIZE
nginx                                                                           latest    0e901e68141f   8 days ago      142MB
calico/node                                                                     v3.19.3   5ee77fcf72b4   8 months ago    154MB
registry.cn-hangzhou.aliyuncs.com/google_containers/calico/node                 v3.19.3   5ee77fcf72b4   8 months ago    154MB
calico/pod2daemon-flexvol                                                       v3.19.3   c34539dc5eef   8 months ago    21.7MB
registry.cn-hangzhou.aliyuncs.com/google_containers/calico/pod2daemon-flexvol   v3.19.3   c34539dc5eef   8 months ago    21.7MB
calico/cni                                                                      v3.19.3   71da92beaffe   8 months ago    146MB
registry.cn-hangzhou.aliyuncs.com/google_containers/calico/cni                  v3.19.3   71da92beaffe   8 months ago    146MB
calico/kube-controllers                                                         v3.19.3   ed1e25e26ab5   8 months ago    60.6MB
registry.cn-hangzhou.aliyuncs.com/google_containers/calico/kube-controllers     v3.19.3   ed1e25e26ab5   8 months ago    60.6MB
registry.cn-hangzhou.aliyuncs.com/google_containers/pause                       3.5       ed210e3e4a5b   14 months ago   683kB


[root@k8s-master ~]# docker ps -a
CONTAINER ID   IMAGE                                                           COMMAND                  CREATED          STATUS                      PORTS     NAMES
ed29b7d58105   5ee77fcf72b4                                                    "start_runit"            4 minutes ago    Exited (1) 4 minutes ago              k8s_calico-node_calico-node-h6w9f_kube-system_68698bda-003b-4bce-a5c3-6851a0111d73_8
d22b3cfabda3   registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.5   "/pause"                 20 minutes ago   Exited (0) 20 minutes ago             k8s_POD_calico-kube-controllers-6b59cd85f8-s264z_kube-system_2ca91924-d990-4bad-8a08-b5c829a86001_0
2bed28089d8c   c34539dc5eef                                                    "/usr/local/bin/flex…"   20 minutes ago   Exited (0) 20 minutes ago             k8s_flexvol-driver_calico-node-h6w9f_kube-system_68698bda-003b-4bce-a5c3-6851a0111d73_0
a872a8155bbc   71da92beaffe                                                    "/opt/cni/bin/install"   20 minutes ago   Exited (0) 20 minutes ago             k8s_install-cni_calico-node-h6w9f_kube-system_68698bda-003b-4bce-a5c3-6851a0111d73_0
6042acecb28b   71da92beaffe                                                    "/opt/cni/bin/calico…"   20 minutes ago   Exited (0) 20 minutes ago             k8s_upgrade-ipam_calico-node-h6w9f_kube-system_68698bda-003b-4bce-a5c3-6851a0111d73_0
3afd329add5d   registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.5   "/pause"                 20 minutes ago   Up 20 minutes                         k8s_POD_calico-node-h6w9f_kube-system_68698bda-003b-4bce-a5c3-6851a0111d73_0



正在回答 回答被采纳积分+3

1回答

刘果国 2022-06-07 09:21:03

关注这里:0/2 nodes are available: 2 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.

节点尚不是ready状态,先解决ready的问题


0 回复 有任何疑惑可以回复我~
  • 提问者 慕仰4468487 #1
    谢谢老师的回复。但是我有个疑问 就是目前master节点的ready状态,也没有污点。而且这个错误是不是在第二条 Normal   Scheduled  Successfully assigned kube-system/calico-kube-controllers-6b59cd85f8-s264z to k8s-master   已经自愈了?  所以这个 0/2 nodes are available: 2 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate这里就不用关注了?
    回复 有任何疑惑可以回复我~ 2022-06-07 15:47:02
  • 提问者 慕仰4468487 #2
    老师可以加一下您的联系方式或者群之类的吗?这样沟通不太及时 而且这里回复也不能贴图之类的
    回复 有任何疑惑可以回复我~ 2022-06-07 15:49:51
  • 刘果国 回复 提问者 慕仰4468487 #3
    不行,一步一步来,上一步的问题先解决好 再往下走 要不然错误揉一起了很难排查
    回复 有任何疑惑可以回复我~ 2022-06-08 09:16:35
问题已解决,确定采纳
还有疑问,暂不采纳
意见反馈 帮助中心 APP下载
官方微信