1、访问http://192.168.31.211:31103/kibana失败，但是其它IP（192.168.31.212等）可以，检查发现192.168.31.211的calico-node的READY：0/1，原因是kube-proxy没有运行：启动kube-proxy，删除重建Pod：calico-node后访问OK。
- kube-proxy宕掉的原因怀疑是安装zerotier不兼容（因为两者功能都是修改转发规则,维护路由信息）。（参见linux常用命令2_技术支持department的技术博客）
# k -n kube-system get pod -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
calico-node-mq5s7 0/1 Running 0 2d 192.168.31.211 k8s-master01 <none> <none>
# k -n kube-system describe pod calico-node-mq5s7
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 112s (x6754 over 16h) kubelet (combined from similar events): Readiness probe failed: 2022-12-14 04:19:39.700 [INFO][7961] 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.31.212,192.168.31.213,192.168.31.214,192.168.31.215,192.168.31.216,192.168.31.217,192.168.31.218,192.168.31.219
Warning Unhealthy 5s kubelet Readiness probe failed: 2022-12-14 04:24:49.670 [INFO][9225] 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.31.212,192.168.31.213,192.168.31.214,192.168.31.215,192.168.31.216,192.168.31.217,192.168.31.218,192.168.31.219
Warning Unhealthy 60s (x2 over 61s) kubelet 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
Warning Unhealthy 58s kubelet Readiness probe failed: 2022-12-14 04:29:24.274 [INFO][214] 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.31.212,192.168.31.213,192.168.31.214,192.168.31.215,192.168.31.216,192.168.31.217,192.168.31.218,192.168.31.219
# systemctl start kube-proxy //# systemctl enable kube-proxy
# k -n kube-system delete pod calico-node-mq5s7 //删除重建pod
