RTPROT_KERNEL Causing IPv4PodCIDR Route Discovery Failure in Quagga and FRR #31243
Labels
area/bgp
kind/cfp
kind/community-report
This was reported by a user in the Cilium community, eg via Slack.
kind/feature
This introduces new functionality.
sig/datapath
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
sig/kernel
Requires upstream work in the Linux kernel.
Is there an existing issue for this?
What happened?
We are using the Native-Routing mode with FRR OSPF protocol to announce pod subnets. This setup worked well until we upgraded from Cilium version 1.13 to 1.14. After the upgrade, I found that pod network announcements failed due to the addition of the
proto kernel
field in the pod subnet routes. While these routes are visible usingip r
on the system but absent from Zebra's table (not displayed withshow ip route
in vtysh).While I understand that
proto kernel
is meant to address this issue #24288 , would it be helpful to introduce a configuration option to selectively enable it?Of course the direct reason for FRR's failure to detect
proto kernel
routes is concerning, I have noticed that this discussion has been raised before but remains unanswered FRRouting/frr#14731.Cilium Version
1.14+
The text was updated successfully, but these errors were encountered: