The test was previously listing networkpolicies to validate only in
the namespace operator-controller is deployed in.
Upstream, that is valid since the namespace that operator-controller is
deployed in, is the namespace that all other components are deployed in
(and therefore all the network polices we expect to find).

A different distribution of olmv1 (downstream) could decide to deploy the
policies in different namespaces, in which case the test will not look into
all the namespaces it should look into.

This PR fixes the issue by searching in the namespaces both operator-controller
and catalogd is deployed in.

openshift-ci bot added the approved

label

anik120 added a commit to anik120/operator-controller that referenced this pull request

Follow up to (2034)[operator-framework#2034]

When there is a dual namespace deployment, the default-deny-all policy
is duplicated in both namespaces.

This PR updates the list of `allowedPolicies` to include both policies
if a dual namespace deployment is detected.

openshift-merge-bot bot pushed a commit that referenced this pull request

Follow up to (2034)[#2034]

When there is a dual namespace deployment, the default-deny-all policy
is duplicated in both namespaces.

This PR updates the list of `allowedPolicies` to include both policies
if a dual namespace deployment is detected.