UDN: unnecessary logical route policies added to routers when UDN is enabled

[trozet]

What happened?

#4561 (comment)

What did you expect to happen?

LRPs for masquerade IP via mgmt port shouldn't exist. There's no reason for pod to access the GR masquerade IP via host.

Additionally, the LRP on the cluster default network ovn_cluster_router for the UDN should not be there.

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

launch a cluster and create an l3 primary udn

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)