1. Proposed title of this feature request

Extend Subscription API with .spec.config.labels, similar to .spec.config.annotations

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

In order to "propagate" additional custom information to CRDs deployed by any Operator we have two ways as of today:

• The Subscription API allows for using annotations through the .spec.config.annotations key [0]
• The ClusterServiceVersion API allows labels [1] as you would need

As Subscription creates the Install Plan (IP), and then Cluster Service Version (CSV) accordingly, it would be more meaningful having control of labels at Subscription resource level.

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

The customer is using some 3rd party Operators which would need custom labels to be applied to the corresponding deployed CRDs. This is a needed step for correctly route and manage network traffic in their blueprint, which is GitOps based and leverages on git-versioning the Subscription YAML content only.

1. List any affected packages or components

OLM

 
[0] https://docs.openshift.com/container-platform/4.17/rest_api/operatorhub_apis/subscription-operators-coreos-com-v1alpha1.html#spec-config
[1] https://docs.openshift.com/container-platform/4.17/rest_api/operatorhub_apis/clusterserviceversion-operators-coreos-com-v1alpha1.html#spec-install-spec-deployments-2