calico kube controllers and calico-node pods is not ready but is running

Question

I have installed a kubernetes cluster with kubeadm with the instructions base on the below link :

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm

and cri-dockerd for Container Runtime via the link :

https://github.com/Mirantis/cri-dockerd

the installed go version for build the code is : "go1.21.0 linux/amd64"

and for pod Networking (Calico) as the link :

https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises

The cluster and nodes are ok : and and

But I have problems with some calico related pods !

The Events :

Please help me, I'm new in Kubernetes learning. Thanks in advance.

Can anybody check the below link for the issue ? https://docs.docker.com/engine/release-notes/24.0 Bug fixes and enhancements : The Go client now avoids using UNIX socket paths in the HTTP Host: header, in order to be compatible with changes introduced in go1.20.6. — Keyvan Soleimani, Sep 02 '23 at 08:29
I think the issue was mentioned at this link too : https://stackoverflow.com/questions/76698552/invalid-host-header-when-running-k3d-clusterrun — Keyvan Soleimani, Sep 02 '23 at 08:49

score 0 · Answer 1 · answered Sep 03 '23 at 05:25

I searched for the issue and realize that downgrading "docker" to 24.0.4 and "go" to go1.20.5 is the solution, because there are some security changes at version go1.20.6+ that makes the related error and there are some best related links as below :

https://docs.docker.com/engine/release-notes/24.0

https://discuss.kubernetes.io/t/http-invalid-host-header-error-while-executing-a-command-in-pod/24868

https://gitlab.com/gitlab-org/gitlab-runner/-/issues/36051

Invalid host header when running k3d clusterRun

https://bugs.gentoo.org/910491

https://github.com/golang/go/issues/61076

https://github.com/moby/moby/issues/45935