Phase 3 - Pre-Work Unite Consoles (ACM, OCP)

Pre-Work Objectives

Since some of our requirements from the ACM team will not be available for the 4.12 timeframe, the team should work on anything we can get done in the scope of the console repo so that when the required items are available in 4.13, we can be more nimble in delivering GA content for the Unified Console Epic.

Overall GA Key Objective
Providing our customers with a single simplified User Experience(Hybrid Cloud Console)that is extensible, can run locally or in the cloud, and is capable of managing the fleet to deep diving into a single cluster. 
Why customers want this?

1. Single interface to accomplish their tasks
2. Consistent UX and patterns
3. Easily accessible: One URL, one set of credentials

Why we want this?

• Shared code -  improve the velocity of both teams and most importantly ensure consistency of the experience at the code level
• Pre-built PF4 components
• Accessibility & i18n
• Remove barriers for enabling ACM

Phase 2 Goal: Productization of the united Console 

1. Enable user to quickly change context from fleet view to single cluster view
   1. Add Cluster selector with “All Cluster” Option. “All Cluster” = ACM
   2. Shared SSO across the fleet
   3. Hub OCP Console can connect to remote clusters API
   4. When ACM Installed the user starts from the fleet overview aka “All Clusters”
2. Share UX between views
   1. ACM Search —> resource list across fleet -> resource details that are consistent with single cluster details view
   2. Add Cluster List to OCP —> Create Cluster