現象：
kube-system calico-node-2622l 0/1 Running 2 21h
kube-system calico-node-jqswg 1/1 Running 1 21h
kube-system calico-node-mc4rb 1/1 Running 2 21h
kube-system calico-node-t4zrz 0/1 CrashLoopBackOff
pod日志報錯：kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with 192.168.1.10,192.168.1.12,192.168.1.14,192.168.1.15,192.168.1.162021-08-31 00:01:49.584 [INFO][228] health.go 114: Number of node(s) with BGP peering established = 0
1.通過calicoctl 工具查看 節點網絡狀態
[root@k8s-master-01 ~]# calicoctl node status
Calico process is running.
IPv4 BGP status
+--------------+-------------------+-------+----------+-------------+
| PEER ADDRESS | PEER TYPE | STATE | SINCE | INFO |
+--------------+-------------------+-------+----------+-------------+
| 192.168.1.11 | node-to-node mesh | up | 03:57:45 | Established |
| 192.168.1.12 | node-to-node mesh | wait | 03:57:43 | Established |
| 192.168.1.14 | node-to-node mesh | wait | 03:57:43 | Established |
| 192.168.1.15 | node-to-node mesh | start | 03:57:41 | Passive |
| 192.168.1.16 | node-to-node mesh | start | 03:57:41 | Passive |
+--------------+-------------------+-------+----------+-------------+
備注：UP狀態： 正常的 ，wait狀態： 等待鏡像下載完成 ，start狀態網絡異常 PEER ADDRESS：節點ip
2.出現這個問題是由於節點多網卡引起的，所以直接修改calico.yaml 文件
添加：- name: IP_AUTODETECTION_METHOD
value: "interface=ens*"
# Cluster type to identify the deployment type
- name: CLUSTER_TYPE
value: "k8s,bgp"
- name: IP_AUTODETECTION_METHOD
value: "interface=ens*"
更新：kubeclt apply -f calico.yaml
查看 kubectl get pods -A pod狀態