Description of problem: When using external gw annotations, the pod traffic is supposed to go out not snat-ed. When a gateway pod exists but we add the annotation later, the pods belonging to the namespace do not get de-snatted Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a gw pod with the gw annotations (and a secondary network) k8s.ovn.org/routing-network: foo <- this must be the name of the secondary network k8s.v1.cni.cncf.io/network-status: '[{"name":"foo","interface":"net1","ips":["172.19.0.5"],"mac":"01:23:45:67:89:10"}]' 2. Add the ns annotation later: k8s.ovn.org/routing-namespaces: externalgw-pod-novxlan-8081 Actual results: Check that the pods traffic is going out SN-atted with the node's IP Expected results: The pods should go out directed to the gw pod with its IP Additional info:
Adding another scenario: With DisableSNATMultipleGWs enabled, add a "k8s.ovn.org/routing-external-gws" annotation to the namespace. The SNAT from the pod is still not removed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759