1. Proposed title of this feature request
Ability to declare the  Operators related to ACM used on a cluster

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

• When deploying ACM on a cluster, it must be possible to determine exactly which version of each Operator should be used.

• When updating on Operator related to ACM, it must be possible to determine to which version the Operator should be updated to.

• It must be possible to schedule the update of the Operators related to ACM to pre-determined maintenance windows. Operators must never update outside of this controlled maintenance window.

3. Why does the customer need this? (List the business requirements here)
Our customers typically follow a workflow where a version of a configuration, including specific versions of all software components such as Operators, is defined.
This version of the configuration is then tested in a pre-production environment before being graduated to production.
For this workflow to work, it must be possible to declare the versions of all Operators which are part of a particular version of a configuration.
A customer with a large network of maybe tens of ACM instances in production need the ability to validate a specific configuration (including software versions) before rolling this out in production.
ACM instances updating randomly and outside of controlled maintenance windows is not acceptable

A workaround is currently available involving maintaining of a custom catalogue for each version of the validated solution. This is however cumbersome and it would be much preferred if the Operators related to ACM could be managed directly without the need for custom catalogues.