UDN: Pod2Services L3/L2 isolation is broken on LGW

[tssurya]

What happened?

when you try to go from UDN pod to clusterIP service on default network; it seems given the LB doesn't DNAT this; this is sent into mpX into the host and is getting conveyed via br-ex into GR where its DNATed and reply is successful?

What did you expect to happen?

udn pod should not be able to reach clusterIPs on default network

How can we reproduce it (as minimally and precisely as possible)?

LGW kind cluster run the pod2Services e2e for L3

Anything else we need to know?

No response

OVN-Kubernetes version

$ ovnkube --version
# paste output here

Kubernetes version

$ kubectl version
# paste output here

OVN version

$ oc rsh -n ovn-kubernetes ovnkube-node-xxxxx (pick any ovnkube-node pod on your cluster)
$ rpm -q ovn
# paste output here

OVS version

$ oc rsh -n ovn-kubernetes ovs-node-xxxxx (pick any ovs pod on your cluster)
$ rpm -q openvswitch
# paste output here

Platform

Is it baremetal? GCP? AWS? Azure?

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)