From 60a5e4bc100d4941c9d0497474ed9c24a5aef837 Mon Sep 17 00:00:00 2001 From: Tim Rozet Date: Thu, 20 Jun 2024 18:10:09 -0400 Subject: [PATCH] Clarify rawConfig in example Signed-off-by: Tim Rozet --- enhancements/network/bgp-ovn-kubernetes.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/enhancements/network/bgp-ovn-kubernetes.md b/enhancements/network/bgp-ovn-kubernetes.md index 01f0bb2b08..2f5cb496aa 100644 --- a/enhancements/network/bgp-ovn-kubernetes.md +++ b/enhancements/network/bgp-ovn-kubernetes.md @@ -395,7 +395,9 @@ spec: In the above configuration generated by OVN-Kubernetes, the subnet 10.0.1.0/24 which belongs to VRF blue, is being imported into the default VRF, and advertised to the 172.18.0.5 neighbor. This is because the targetVRF was defaulted so the routes are leaked and advertised in the default VRF. Additionally, routes are being imported from the default VRF -into the blue VRF. +into the blue VRF. At the time of this writing, FRR-K8S does not support importing vrf routes as an API, and thus rawConfig +is used. However, when implementing this enhancement every attempt should be made to add support into FRR-K8S to use its +API rather than using rawConfig. ##### Example 2: VRF Lite - Advertising pod IPs from a user-defined network over BGP with VPN