After creating the K8S cluster, install the CALICO component. Although the CALICO POD is in a running state after installation
But upon checking the event, I see the following error message:
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/bird/bird.ctl: connect: no such file or directory
Warning Unhealthy 19s kubelet Readiness probe failed: 2024-10-24 05:38:42.735 [INFO][162] confd/health.go 180: Number of node(s) with BGP peering established = 0
calico/node is not ready: BIRD is not ready: BGP not established with 192.168.100.186
I searched a lot of content, according to the search results
- All nodes are installed on the local VMWARE, the firewall is turned off, and network communication between nodes is normal
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
bird 9909 root 7u IPv4 58170 0t0 TCP *:bgp (LISTEN)
bird 9909 root 8u IPv4 59810 0t0 TCP dk8s-work1:bgp->dk8s-work2:49865 (ESTABLISHED)
-
The default network card found is ens33
name: IP_AUTODETECTION_METHOD
value: interface=ens33
name: IP -
Using the IP link command to view redundant virtual network cards without the prefix ‘br’, and deleting some state down network cards did not work
The above three methods found online are all ineffective, and the reason cannot be found. I would like to ask everyone for advice.