Background
Starting with ACM and Hosted inventory +hypershift and now with ROSA + HyperShift we are seeing a pattern where a customer has to choose which type of cluster they want based on their infrastructure. We don't have consistency here yet.

Goal
Create a convention for an additional step where the user can from different options and have enough information to make an informed choice.

Desired outcome
A card layout that is flexible enough to be used for different use cases

• type of install: IPI, UPI, Assisted
• type of control plane: Hosted, standalone
• type of management : self, Red Hat

Design Assets:
HyperShift + Rosa in OCM
HyperShift + Host Inventory in ACM