Epic Goal

• Remove the standalone console component for ACM

Why is this important?

• ACM is moving towards dynamic plugin integration with the core OCP console
• Eliminate burden on engineering, QE, CEE for having to support two instances of the UX

Scenarios

1. Upon installing ACM 2.7, the standalone ACM console is not available on the "multicloud-console" route.
2. Upon upgrading to ACM 2.7, the standalone ACM console is not available on the "multicloud-console" route.
3. In scenarios 1 and 2, the ACM Console is not an option from the OCP Console App Switcher
4. In 2.6.z, add a persistent banner at the top of the standalone console indicating that the standalone console will be removed in the next release and provide a link to the ACM UX on the OCP Console route.
   • Use similar design as https://docs.openshift.com/container-platform/4.11/web_console/customizing-the-web-console.html#creating-custom-notification-banners_customizing-web-console

Non-Scenarios

1. The ACM standalone console in 2.7 is supported on OCP 4.9 or earlier
   • RHACM 2.7's minimum supported OpenShift version will be 4.10

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• All scenarios are supported.
• Any documentation related to the standalone console is removed.
• Release note is provided that the standalone ACM console was removed.
• Dev and QE tests only support test automation for the dynamic plugin.

Dependencies (internal and external)

1. ACM-1476 Remove Management Ingress component from ACM
2. ACM-1322 Remove Observability's Dependency on OAuth Proxy

Previous Work (Optional):

1. …

Open questions::

1. Does dev want to keep the standalone console behind a feature flag, for dev use?
   • How would this work if we wanted to adopt OpenShift console SDK
2. The Grafana dashboard will be on a different domain/route, do the launch out links to Grafana still work?

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>