Value Statement

It is possible for users to put ACM/MCE into a bad state if MCE is upgraded manually while managed by ACM. While there are logs in the MCH operator that indicate this, it would be better to have this information front-and-center where users are more likely to check. This change will create a ConsoleNotification resource (part of openshift api) to create a giant warning banner.

apiVersion: console.openshift.io/v1
kind: ConsoleNotification
metadata:
  name: important-banner
spec:
  text: "WARNING: ACM in unexpected configuration: MCE 2.10 is ahead of the expected 2.9 channel."
  location: BannerTop # Options: BannerTop, BannerBottom, BannerTopBottom
  backgroundColor: '#880808' # Dark red background (hex color)
  color: '#ffffff'         # White text (hex color)

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.

-------------------------------------------------------------------------------------------------------