Calico-kube-controllers stuck on ContainerCreating

Open Source Calico Help
1

Hi, what could be the cause of calico-kube-controllers stuck on ContainerCreating?

I see the following after initializing kubeadmn followed by calico.yaml apply:

And then

kubectl get pods -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-kube-controllers-56fcbf9d6b-l8vc7 0/1 ContainerCreating 0 35m kub-master
kube-system calico-node-7nddr 0/1 CrashLoopBackOff 13 (114s ago) 35m 10.5.183.151 kub-master
kube-system coredns-64897985d-bblws 0/1 ContainerCreating 0 36m kub-master
kube-system coredns-64897985d-zlsp4 0/1 ContainerCreating 0 36m kub-master
kube-system etcd-kub-master 1/1 Running 34 36m 10.5.183.151 kub-master
kube-system kube-apiserver-kub-master 1/1 Running 2 36m 10.5.183.151 kub-master
kube-system kube-controller-manager-kub-master 1/1 Running 2 36m 10.5.183.151 kub-master
kube-system kube-scheduler-kub-master 1/1 Running 10 36m 10.5.183.151 kub-master

Where

kubectl describe pod coredns-64897985d-bblws -n kube-system
…
Events:
Type Reason Age From Message

Warning FailedScheduling 35m (x2 over 36m) default-scheduler 0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn’t tolerate.
Normal Scheduled 35m default-scheduler Successfully assigned kube-system/coredns-64897985d-bblws to kub-master
Warning FailedCreatePodSandBox 34m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container “2b76cb535ed86887484e25ace199c72cdba53dfc09d5d04a8d374a8d259dc952” network for pod “coredns-64897985d-bblws”: networkPlugin cni failed to set up pod “coredns-64897985d-bblws_kube-system” network: error getting ClusterInformation: Get “https://[10.96.0.1]:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: dial tcp 10.96.0.1:443: i/o timeout, failed to clean up sandbox container “2b76cb535ed86887484e25ace199c72cdba53dfc09d5d04a8d374a8d259dc952” network for pod “coredns-64897985d-bblws”: networkPlugin cni failed to teardown pod “coredns-64897985d-bblws_kube-system” network: error getting ClusterInformation: Get “https://[10.96.0.1]:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: dial tcp 10.96.0.1:443: i/o timeout]
Normal SandboxChanged 3m45s (x48 over 34m) kubelet Pod sandbox changed, it will be killed and re-created.

And system details and versions:

labuser@kub-master:~/work/calico$ uname -a
Linux kub-master 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
labuser@kub-master:~/work/calico$ cat /etc/os-release

VERSION=“20.04.3 LTS (Focal Fossa)”
labuser@kub-master:~/work/calico$ docker version
Client: Docker Engine - Community
Version: 20.10.12
API version: 1.41
Go version: go1.16.12
Git commit: e91ed57
Built: Mon Dec 13 11:45:27 2021
OS/Arch: linux/amd64
Context: default
Experimental: true

Server: Docker Engine - Community
Engine:
Version: 20.10.12
API version: 1.41 (minimum version 1.12)
Go version: go1.16.12
Git commit: 459d0df
Built: Mon Dec 13 11:43:36 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.12
GitCommit: 7b11cfaabd73bb80907dd23182b9347b4245eb5d
runc:
Version: 1.0.2
GitCommit: v1.0.2-0-g52b36a2
docker-init:
Version: 0.19.0
GitCommit: de40ad0
labuser@kub-master:~/work/calico$

2

Looks like kube-proxy isn’t running.