Value Statement

Most managed OpenShift instances do support updating the the version and channels. We should not block this in the UI. The exception is HCP (Hosted Control Plane) clusters. This story completes the implementation started in ACM-8807.

Definition of Done for Engineering Story Owner (Checklist)

• OSD, ARO classic, and IBM (RHOKS/RHOIC) clusters allow the version and channel to be updated
  • QE validated this for ROSA classic; OSD is blocked by https://issues.redhat.com/browse/ACM-10077

• ARO and IBM (RHOKS/RHOIC) clusters are identified as such in the cluster list and on the cluster details page

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_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

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