calico-node not ready
Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with …
env
- sealos-3.3
- kube-1.19.16
- centos7 x2 2c4g
log
[root@c7-100 ~]# kubectl get cs,node,pods -A -o wide|grep 0/1
Warning: v1 ComponentStatus is deprecated in v1.19+
kube-system pod/calico-node-5lgqr 0/1 Running 0 63s 172.24.20.100 c7-100 <none> <none>
[root@c7-100 ~]#
[root@c7-100 ~]# kubectl describe pod/calico-node-5lgqr -n kube-system
Name: calico-node-5lgqr
Namespace: kube-system
...
Normal Started 77s kubelet Started container calico-node
Warning Unhealthy 67s kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with 172.24.20.1012024-10-15 00:17:27.183 [INFO][134] readiness.go 88: Number of node(s) with BGP peering established = 0
Warning Unhealthy 57s kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with 172.24.20.1012024-10-15 00:17:37.183 [INFO][154] readiness.go 88: Number of node(s) with BGP peering established = 0
resolve
1.检查calico/node route id
[root@c7-100 ~]# kubectl exec -it pod/calico-node-5lgqr -n kube-system -- bash
root@c7-100:/#
root@c7-100:/# cat /etc/calico/confd/config/bird.cfg
# Generated by confd
include "bird_aggr.cfg";
include "bird_ipam.cfg";
router id 172.24.20.100; //发现route id是正确的
....
2.检查本地apiserver地址
[root@c7-101 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
172.24.20.101 c7-101
# 10.103.97.2 apiserver.cluster.local (vip地址，改为master ip)
172.24.20.100 apiserver.cluster.local
3.reboot
master/node
4.check
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
componentstatus/scheduler Healthy ok
componentstatus/controller-manager Healthy ok
componentstatus/etcd-0 Healthy {"health":"true"}
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
node/c7-100 Ready master 14h v1.19.16 172.24.20.100 <none> CentOS Linux 7 (Core) 3.10.0-1160.71.1.el7.x86_64 docker://19.3.0
node/c7-101 Ready <none> 14h v1.19.16 172.24.20.101 <none> CentOS Linux 7 (Core) 3.10.0-1160.71.1.el7.x86_64 docker://19.3.0
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system pod/calico-kube-controllers-69b47f4dfb-564lm 1/1 Running 3 14h 192.168.10.204 c7-100 <none> <none>
kube-system pod/calico-node-2w4fl 1/1 Running 2 14h 172.24.20.101 c7-101 <none> <none>
kube-system pod/calico-node-5lgqr 1/1 Running 0 140m 172.24.20.100 c7-100 <none> <none>
kube-system pod/coredns-f9fd979d6-4rsql 1/1 Running 3 14h 192.168.10.203 c7-100 <none> <none>
kube-system pod/coredns-f9fd979d6-rzcwf 1/1 Running 3 14h 192.168.10.202 c7-100 <none> <none>
kube-system pod/etcd-c7-100 1/1 Running 3 14h 172.24.20.100 c7-100 <none> <none>
kube-system pod/kube-apiserver-c7-100 1/1 Running 3 14h 172.24.20.100 c7-100 <none> <none>
kube-system pod/kube-controller-manager-c7-100 1/1 Running 2 14h 172.24.20.100 c7-100 <none> <none>
kube-system pod/kube-proxy-8268z 1/1 Running 3 14h 172.24.20.100 c7-100 <none> <none>
kube-system pod/kube-proxy-w9d84 1/1 Running 2 14h 172.24.20.101 c7-101 <none> <none>
kube-system pod/kube-scheduler-c7-100 1/1 Running 2 14h 172.24.20.100 c7-100 <none> <none>
kube-system pod/kube-sealyun-lvscare-c7-101 1/1 Running 1 117m 172.24.20.101 c7-101 <none> <none>