Epic Goal

OLM will be populating deprecation notices in the Subscription status.

An OperatorPolicy should be noncompliant by default if the user is using a deprecated operator or channel. The OperatorPolicy `spec.statusConfig` should allow the user to disable this affecting the compliance and only be notified through the compliance message.

See:  What's New in OpenShift 4.17

Why is this important?

When a user is managing a large fleet of clusters, they may not be aware that they have an OperatorPolicy that is installing a now deprecated operator. This alerts the user of this situation.

See OCPSTRAT-828

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. Available from OpenShift 4.16 (back-ported to z-stream)

Previous Work (Optional):

1. ...

Open questions:

1. Is it possible for OperatorPolicy to suggest the in-life version like the OpenShift Console does?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.