Calico节点无法使用服务器的IP地址进行构建 [英] Calico node cannot build with server's ip address
问题描述
当我将k8s工作节点添加到主控制平面时，calico-node的pod报告错误，表明服务器的ip连接不正常.
When I add the k8s work node to the master control-plane, the pod of calico-node report a error show that the server's ip connection is unhealthy.
Warning Unhealthy 36s kubelet, izbp1a13o0oyyyt66ldcdhsj
Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with XX.XX.XX.XX
2020-02-03 08:16:54.740 [INFO][119] health.go 156: Number of node(s) with BGP peering established = 0
我使用kubeadm创建集群，主节点似乎可以工作了.当我加入其他工作节点时，将显示此错误，它似乎是calico net框架在它们之间无法正常工作.
I using kubeadm to create the cluster, the master node seems work ready. This error show when I join other work node, it looks like the calico net framework not work correctly between them.
kubectl get nodes显示两个节点都准备就绪.
The kubectl get nodes show the two node are all ready.
kubectl get pods --all-namespaces表示在名称空间kube-system中有两个印花布节点吊舱，并且它们都在上面显示了报告错误.
The kubectl get pods --all-namespaces show there are two calico-node pod in the namespace kube-system, and they are all report error show above.
推荐答案
Error: calico/node is not ready: BIRD is not ready: BGP not established with x.x.x.x
以下三大原因
1:Kubernetes中的此未就绪"状态错误表示特定对等点在群集中不可访问.检查环境中是否允许两个对等方之间的BGP连接.
1 : This "unready" status error in Kubernetes means that a particular peer is unreachable in the cluster. Check that BGP connectivity between the two peers is allowed in the environment.
2:如果为节点到节点的网格配置了非活动的节点资源，也会发生此错误.要解决此问题，请停用旧节点.
2: This error can also occur if inactive Node resources are configured for node-to-node mesh. To fix this, decommission the stale nodes.
3:当与非网状对等体的BGP连接断开时，也会发生此错误.如果这是BGP拓扑中的常见情况，则可以禁用BIRD准备情况检查.有关更多信息，请参见节点准备情况.
3: This error can also occur when BGP connections to non-mesh peers go down. If this is a common occurrence in your BGP topology, you can disable BIRD readiness checks. See node readiness for more information.
这篇关于Calico节点无法使用服务器的IP地址进行构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
