1. Proposed title of this feature request

Allow to edit OpenShift Dedicated (OSD) ingress controller to use namespaceSelector

2. What is the nature and description of the request?

In OpenShift Dedicated (OSD) users cannot edit the default ingress controller to use namespaceSelector, which allows to exclude certain projects from the default ingress controller by selecting them with a label, as explained here: https://access.redhat.com/solutions/5097511

If they try to modify it via UI or commands such as:

oc patch -n openshift-ingress-operator ingresscontroller/default --patch '{"spec":{"namespaceSelector":{"matchExpressions": [{"key": "key_name", "operator": "NotIn", "values": ["value_name"]}]}}}' --type=merge

This gets automatically reconciled by Hive (SRE).

Instead, their only option is to use the following command:

ocm edit ingress --cluster=<cluster> --excluded-namespaces 'value1, value2' <ingress>

Which requires to specify every single name of each project that needs to be excluded.

Adding a route selector is not useful for them either because they have set the labels at namespace level:

ocm edit ingress --cluster=<cluster> --route-selector <key=value> <ingress>

They would like to be able to have the option to specify which namespaces need to be excluded by labels, as done with namespaceSelector.

3. Why does the customer need this? (List the business requirements here)

namespaceSelector allows to exclude those namespaces by excluding everything namespace that uses a particular label. In their case, they want to exclude the namespaces that have the label "key_name: value_name".

In the current solution in OSD, the user needs to use the command to exclude a large number of namespaces, which they will need to enter manually each namespace and update it again if they create more namespaces that they would like to exclude. This is not practical for users.

4. List any affected packages or components.

OpenShift Dedicated (OSD) default ingress controller