Epic Goal

...

This Epic is a follow up of: https://issues.redhat.com/browse/ACM-14379

We will close this spike story and start on a new set of spikes for more granular tracking.

ACM-17918
ACM-17914
ACM-17917
ACM-17919

We were able to demonstrate through prototyping that the key questions posed in this spike are possible.
Remaining issues we have identified are identified in this document.
Fleet API compatibility (exploring a technical solution in ACM-17914)
Hub cluster compatibility
UX of where functionality lives
Packaging question of how UI is delivered
Initial discussions with CNV engineering focused on defining the interface between ACM and CNV; we will improve the design of the prototype via ACM-17918 and continue syncing with CNV on a weekly basis

Why is this important?

Determines whether we can attain console efficiency by consuming the existing console and user experience, and uplift this to multi-cluster (cost is the delta)

Scenarios

Similar experience to single cluster but with a multi-cluster workflow.  List of virtual machines is across the fleet (multi-cluster) before you dive into the details (single cluster view). We don't want to leave the hub real-estate for the served paged, just pulling the data.

Acceptance Criteria

Functional single cluster virtual machine pages from the hub with an intuitive flow from the fleet to the individual virtual machine.

Dependencies (internal and external)

1. Search
2. API Proxy
3. Impersonation by the API proxy
4. Pattern for OIDC as the IDP

Previous Work (Optional):

1. https://issues.redhat.com/browse/ACM-14379

Done Checklist

• DEV - All spikes are completed with an option to continue the work to Developer Preview