我正在运行 Calico Node2Node Mesh。并成功设置与我的上游交换机的对等互连。
看起来很奇怪,似乎每个节点都在宣传所有节点网络。我认为每个节点都应该宣传其 /26 范围和服务范围。相反,它会通告所有 4 /26(节点特定子网)和服务范围。我担心这有一些多路径问题。
这是预期的行为吗?
172.16。路由是特定于节点的 172.20。是 kube clusterip 服务的地方
172.16.149.0/26 proto bgp metric 20
nexthop via 192.168.101.201 dev vlan101 weight 1
nexthop via 192.168.101.202 dev vlan101 weight 1
nexthop via 192.168.101.203 dev vlan101 weight 1
nexthop via 192.168.101.204 dev vlan101 weight 1
172.16.155.64/26 proto bgp metric 20
nexthop via 192.168.101.201 dev vlan101 weight 1
nexthop via 192.168.101.202 dev vlan101 weight 1
nexthop via 192.168.101.203 dev vlan101 weight 1
nexthop via 192.168.101.204 dev vlan101 weight 1
172.16.176.192/26 proto bgp metric 20
nexthop via 192.168.101.201 dev vlan101 weight 1
nexthop via 192.168.101.202 dev vlan101 weight 1
nexthop via 192.168.101.203 dev vlan101 weight 1
nexthop via 192.168.101.204 dev vlan101 weight 1
172.16.248.128/26 proto bgp metric 20
nexthop via 192.168.101.201 dev vlan101 weight 1
nexthop via 192.168.101.202 dev vlan101 weight 1
nexthop via 192.168.101.203 dev vlan101 weight 1
nexthop via 192.168.101.204 dev vlan101 weight 1
172.20.0.0/16 proto bgp metric 20
nexthop via 192.168.101.201 dev vlan101 weight 1
nexthop via 192.168.101.202 dev vlan101 weight 1
nexthop via 192.168.101.203 dev vlan101 weight 1
nexthop via 192.168.101.204 dev vlan101 weight 1
172.20.88.169 proto bgp metric 20
nexthop via 192.168.101.201 dev vlan101 weight 1
nexthop via 192.168.101.202 dev vlan101 weight 1
nexthop via 192.168.101.203 dev vlan101 weight 1
nexthop via 192.168.101.204 dev vlan101 weight 1
印花布 BGP 清单
---
apiVersion: projectcalico.org/v3
kind: BGPPeer
metadata:
name: netgate
spec:
peerIP: 192.168.100.1
asNumber: 65534