As part of the ACM/OCP console integration designs, the two consoles should function as a single web application with one URL.

ACM has an architecture where each component is a microservice that contributes its own UI behind a single ingress with a shared masthead and navigation. We should investigate whether this approach is feasible for integrating the OCP console.

Goals

• Work with the ACM team to understand their architecture for integration
• Develop a prototype that shows the two console together under a single URL with a common masthead and navigation
• Uncover any challenges that we didn't anticipate and problems with this approach

Non Goals

• This POC is not intended to be the decision point of the adoption of a singular console strategy. That discussion is still underway.
• This POC will not address sharing elements such as Alerts, custom logos, and ConsoleLinks in the masthead

Open Questions

• How do we handle masthead elements that need data from the API, such as Alerts, ConsoleLinks, custom logos?
• Do customizations such as ConsoleLinks and custom logos always come from the Hub cluster?
• Do we need a shared the notification drawer component that shows the same Alerts and recommendations between the two consoles?
• How does this change the About dialog?

Acceptance Criteria

• Working code that has both consoles running under the same URL
• A document detailing what we've learned, what any roadblocks are, and possible solutions to problems encountered