Im struggling with Mikrotik BGP to make it work with Kubernetes ( k3s ) with Cilium CNI. Im not sure what the role must be. I tried with local ibgp, same AS different AS. There is no peer connections. As you can see I also play with default-originate. Any kind of help will be awesome.
Code: Select all
] /routing/bgp/connection> print
Flags: D - dynamic, X - disabled, I - inactive
0 name="PEER_TO_K3S_WN_1"
remote.address=192.168.1.201
local.default-address=192.168.1.1 .role=ebgp
routing-table=main as=65000
output.default-originate=always
1 name="PEER_TO_K3S_WN_2"
remote.address=192.168.1.202
local.default-address=192.168.1.1 .role=ebgp
routing-table=main as=65000
output.default-originate=always
2 name="PEER_TO_K3S_WN_3"
remote.address=192.168.1.203
local.default-address=192.168.1.1 .role=ebgp
routing-table=main as=65000 address-families=""
output.default-originate=never
Code: Select all
apiVersion: cilium.io/v2alpha1
kind: CiliumBGPPeeringPolicy
metadata:
name: bgp-policy
spec:
nodeSelector:
matchLabels:
bgp-policy: a
virtualRouters:
- exportPodCIDR: true
localASN: 65001
neighbors:
- peerASN: 65000
peerAddress: 192.168.1.1/32
Code: Select all
apiVersion: "cilium.io/v2alpha1"
kind: CiliumLoadBalancerIPPool
metadata:
name: "lbpool"
spec:
cidrs:
- cidr: "172.198.1.0/24"
disabled: false
Code: Select all
k3s-rpi (main) ✗ cilium bgp peers
Node Local AS Peer AS Peer Address Session State Uptime Family Received Advertised
k3s-worker-node-01 64512 64512 192.168.1.1 active 0s ipv4/unicast 0 0
ipv6/unicast 0 0
k3s-worker-node-02 64512 64512 192.168.1.1 active 0s ipv4/unicast 0 0
ipv6/unicast 0 0
k3s-worker-node-03 64512 64512 192.168.1.1 active 0s ipv4/unicast 0 0
ipv6/unicast 0 0
Cilium example config:
https://docs.cilium.io/en/stable/networ ... rol-plane/
Example with OpnSense:
https://devopstales.github.io/home/cili ... se-bgp-v2/
