Normal Epic Goal
For Managed OpenShift (Classic, not HCP), the Channel and Upgrade levers are the same as self-managed OpenShift (controlled through the CVO). The UI has been blocking these actions, this Epic is to remove the blocking code.
Why is this important?
Customers want a consistent and central place to interact with their fleet of clusters regardless of cluster type.
Scenarios
As an MCE Console user, I can:
- See the correct RH product name for ROSA, ARO, and OSD (Classic and HCP)
- ROSA, ARO, OSD should displayed the acronymed name, not "OpenShift"
- Displays ROSA, ARO, OSD regardless of Classic vs HCP
- Change the version channel for ROSA Classic, ARO Classic, and OSD Classic
- Upgrade the cluster for ROSA Classic, ARO Classic, OSD Classic
Non-Scenarios
- No version channel change or upgrade support for HCP flavors (ROSA)
Acceptance Criteria
All Scenarios complete
Dependencies (internal and external)
Previous Work (Optional):
Open questions:
- Does the Foundation code accurately differentiate Classic and HCP?
- Are there any issues with ClusterCurator performing upgrade hooks or even triggering the upgrade for managed OpenShift classic?
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 - Downstream documentation merged: <link to meaningful PR>
