Define labels for route/ingress

[tolusha]

Signed-off-by: Anatolii Bazko abazko@redhat.com

What does this PR do

Possibility to define label(s) for route to work with router sharding

Reference issue

https://issues.redhat.com/browse/CRW-1034

[davidfestal]

I'm not very convinced about the use of new CheClusterSpecDevfileRegistry and CheClusterSpecPluginRegistry sections.

These new sections would in fact contain only the label-related field, while most other registry-related settings would still be in the "Server" section.
Of course adding 2 new sections would completely make sense if we were ready to refactor the schema completely, and bring all the registry-related settings in the dedicated registry section. But I assume we would not start such a refactoring now since it which would break backward compatibility of the CRD schema.

So I'd rather follow the existing pattern, and use names like devfileRegistryLabels in the server section since we already had devfileRegistryImage, devfileRegistryPullPolicy, ...

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AndrienkoAleksandr, davidfestal, tolusha
To complete the pull request process, please assign
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment