Value Statement

As an engineer, I want to find a way to display a warning when user upgrades OCP to a version that is incompatible with the version of ACM installed.

Definition of Done for Engineering Story Owner (Checklist)

• TBD

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.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 9/17/25:

Summary of the Work:
I added the annotation olm.properties: '[

]' to the CSV. When installed through OLM, this will set the max version and strongly discourage upgrading past that version

Key Areas to Verify:

1. Just make sure the annotation is there. When this is applied to z-streams, there will be more to test, but since there isn't a 4.21 yet, you won't be able to verify this directly. However, I smoketested with setting the value to 4.18 and installed on a 4.18 cluster, and `oc adm upgrade` did indeed warn that upgrading was no recommended due to the multiclusterhub-csv version requirements

Fix or Feature Availability:
Code merged on: 2025-09-18