When configuring static routes for leaking a container route into a VRF, the interface name is mangled once installed in FRR:
container {
name test {
image ubuntu:20.04
network TEST {
}
}
network TEST {
prefix 192.168.0.0/24
}
}
[...]
vrf name TEST {
protocols {
static {
route 192.168.0.0/24 {
interface pod-TEST {
vrf default
}
}
}
}
}Resulting FRR running config:
vrf TEST ip route 192.168.0.0/24 pod_TEST nexthop-vrf default exit-vrf
As shown above, the container network pod-TEST is mangled to pod_TEST causing the static route to fail. Manually changing the running configuration in FRR corrects this behavior and allows the routing to behave as expected.