Epic Goal
Update any links that launch the managed cluster's OCP Console to use the multi-cluster console's cluster context pages.
Why is this important?
- Further unify the UX between ACM and OCP, and provide seamless interaction from the fleet to an invidual cluster.
- OCP Console may be disabled on some clusters in the future.
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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>
- is blocked by
-
CONSOLE-2831 Include cluster name in console URLs
- Closed