Proposed title of this feature request

As soon as the OCP CMO has a CRD that can be used for configuration of alertmanagers we should try to make use of it ACM side. This will solves issues with conflicts between policies and the CMO configuration that MCO adds.

What is the nature and description of the request?

Operators should generally be configured by an accompanying CRD. Currently CMO uses a config map for that due to historical reasons. While developing and implementing a CRD is not complex, making the transition painless for users will be rather tricky.

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

A CRD has several advantages over a config map:

• The specification is well known and to a degree self-documenting
• We can specify validation and legal values right in the CRD.
• The APIServer will validate user resources based on our specifications, so users get immediate feedback on errors instead of having to check if their config was applied and check logs.
• Many users expect to interact with operators through a CRD
• Compatible with GitOps workflows.
• List any affected packages or components.

CMO

We should have a telemetry signal to track adoption.