I am trying to setup a cluster in RHEL 8.9 with calico network. I keep getting below error messages from kubernetes events.
LAST SEEN TYPE REASON OBJECT MESSAGE
22m Normal Scheduled pod/calico-kube-controllers-674fff74c8-mxv5k Successfully assigned kube-system/calico-kube-controllers-674fff74c8-mxv5k to catl0dlas40547
22m Warning FailedCreatePodSandBox pod/calico-kube-controllers-674fff74c8-mxv5k Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox “15c1de85ba4cfb12e989b42015aa9730b560f87281143c8b61378e2164fbbc85”: plugin type=“calico” failed (add): error getting ClusterInformation: Get “https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kubernetes”)
22m Normal SandboxChanged pod/calico-kube-controllers-674fff74c8-mxv5k Pod sandbox changed, it will be killed and re-created.
21m Normal Pulled pod/calico-kube-controllers-674fff74c8-mxv5k Container image “docker.io/calico/kube-controllers:v3.25.1” already present on machine
21m Normal Created pod/calico-kube-controllers-674fff74c8-mxv5k Created container calico-kube-controllers
21m Normal Started pod/calico-kube-controllers-674fff74c8-mxv5k Started container calico-kube-controllers
12m Warning Unhealthy pod/calico-kube-controllers-674fff74c8-mxv5k Readiness probe failed: initialized to false
21m Warning Unhealthy pod/calico-kube-controllers-674fff74c8-mxv5k Liveness probe failed: initialized to false
21m Warning Unhealthy pod/calico-kube-controllers-674fff74c8-mxv5k Liveness probe failed: Error initializing datastore: Get “https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: dial tcp 10.96.0.1:443: i/o timeout
21m Warning Unhealthy pod/calico-kube-controllers-674fff74c8-mxv5k Readiness probe failed: Error initializing datastore: Get “https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: dial tcp 10.96.0.1:443: i/o timeout
2m27s Warning BackOff pod/calico-kube-controllers-674fff74c8-mxv5k Back-off restarting failed container calico-kube-controllers in pod calico-kube-controllers-674fff74c8-mxv5k_kube-system(dd45316e-1e61-4a30-8c1c-70f65f1bc3b2)
22m Normal SuccessfulCreate replicaset/calico-kube-controllers-674fff74c8 Created pod: calico-kube-controllers-674fff74c8
22m Normal Created pod/calico-node-9zvv9 Created container calico-node
22m Normal Started pod/calico-node-9zvv9 Started container calico-node
22m Warning Unhealthy pod/calico-node-9zvv9 Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
22m Normal SuccessfulCreate daemonset/calico-node Created pod: calico-node-9zvv9
22m Normal Scheduled pod/coredns-5d78c9869d-vvqsb Successfully assigned kube-system/coredns-5d78c9869d-vvqsb to catl0dlas40547
22m Warning FailedCreatePodSandBox pod/coredns-5d78c9869d-vvqsb Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox “b2dd9068f6fc29011d9643e05568aab004e6aead0af01199eb8f56d95340b68d”: plugin type=“calico” failed (add): error getting ClusterInformation: Get “https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kubernetes”)
22m Normal SandboxChanged pod/coredns-5d78c9869d-vvqsb Pod sandbox changed, it will be killed and re-created.
22m Normal
Cluster information:
Kubernetes version: v1.27.13
Cloud being used:
Installation method: Kubeadm
Host OS: Red Hat Enterprise Linux 8.9 (Ootpa)
CNI and version: Calico v3.25.1
CRI and version: containerd://1.6.31
Please let me know if any further details required to assits the issue.