Jaime Caamaño Ruiz

> Any "manual" preservation of the routes (ie ovnk monitors and installs the route if frrk8s goes down) is risky imo and can be worse if not handled correctly Yeah,...

> > Any "manual" preservation of the routes (ie ovnk monitors and installs the route if frrk8s goes down) is risky imo and can be worse if not handled correctly...

I have a major concern with this approach. By reporting even the most transient errors as status conditions, it just looks like we are using them as an extra logging...

> > I have a major concern with this approach. By reporting even the most transient errors as status conditions, it just looks like we are using them as an...

Ok, new failures that I haven't seen before ``` [FAIL] Network Segmentation: Network Policies on a user defined primary network pods within namespace should be isolated when deny policy is...

> "e2e ingress traffic validation" failed with "docker: Error response from daemon: Head "https://registry.k8s.io/v2/e2e-test-images/agnhost/manifests/2.26": net/http: TLS handshake timeout.". At some point agnhost image became available and the following tests were...

Issues opened for the flakes https://github.com/ovn-org/ovn-kubernetes/issues/4783 https://github.com/ovn-org/ovn-kubernetes/issues/4784

@yboaron I think that the appropriate fix is for the documentation to not use `targetVRF: default` and omit targetVRF instead. Issue #5580 reports section https://github.com/ovn-kubernetes/ovn-kubernetes/blob/master/docs/features/bgp-integration/route-advertisements.md#import-routes-into-a-cudn not working but it is...

I think for now we can't claim we support this. Fixing docs here https://github.com/ovn-kubernetes/ovn-kubernetes/pull/5774 Reproducing the explanation of the problem from https://github.com/ovn-kubernetes/ovn-kubernetes/pull/5699#issuecomment-3574768060 ``` we don't support establishing a BGP session...