Description of problem:

Trying to use the Service Proxy for Kubernetes and apply an AdminPolicyBasedExternalRoute to a cluster. In the document https://clouddocs.f5.com/service-proxy/latest/spk-adminpolicybasedexternalroute.html there is a note under step 1.B saying "When both the tmm.ovn_meg.enabled and tmm.icni2.enabled parameters are set to true, the AdminPolicyBasedExternalRoute CR of Multiple External Gateway takes precedence over ICNI 2.0." When setting this up however, we do not see the Multiple External Gateway feature take precedence over OVN-Kubernetes as namespaces without a AdminPolicyBasedExternalRoute still have OVN routes created for it. We need to know if this is a bug that needs fixing or if there's a misunderstanding of the documentation.

How reproducible:

Steps to Reproduce:

1. Bring up SPK setup by enabling ovn_meg and icni2 flags .
2. Create two namespaces.
3. Apply an AdminPolicyBasedExternalRoute CR with only one target namespace.
4. Install apps in both namespaces and observe that OVN routes created for apps present in both namespaces.

Actual results:

OVN routes created for apps present in both namespaces and also egress traffic is working for both apps.

Expected results:

As the AdminPolicyBasedExternalRoute CR has only one target namespace, OVN routes have to create only for the app pods mentioned in target namespace, but OVN routes should not create for the apps pods present in other namespaces.

Affected Platforms: Affecting a customer on OCP 4.14