User story:

As a user, I want to add the correct OIDC information including a BYO-OIDC for a Hypershift control plane when creating a ROSA cluster.

Acceptance criteria:

1. For classic ROSA clusters, users can let Red Hat manage the cluster's OIDC. In this mode, users have the ability to choose  between manual and auto mode (current functionality) along with an operator roles prefix.
2. For classic ROSA clusters, users can choose to manage their OIDC themselves instead. Note - this is referred to as "self-managed OIDC provider".  Items shall include:
   • directions to run the CLI command to create a new OIDC provider.  
   • ability to select the config ID from a Dropdown (required)
   • ability to add operator roles prefix (required)
3. For hypershift clusters, users cannot choose, as they will always use "Manage the OIDC myself", therefore there is no switch toggle. Neither can they select the manual / auto mode, and "manual" mode will be used internally on the created cluster.

• In Review page, the configuration ID will be displayed when users manage the OIDC themselves.

  Mockups:

Mockups | PD 1466

-------------------------------------------------------------------------------------------------------------------------------

Implementation details

rosa cli oidc-config commands/usage  

Open questions:

• What validation and/or feedback will be needed? 
• What is the content for the helper icons?

NOTES:

This will also require adjusting the helper text and adding help icons 

-------------------------------------------------------------------------------------------------------------------------------

Historical summary

When the BYO-OIDC workflow is introduced to ROSA cluster creation, we will want to offer this in the UI workflow for cluster provisioning for Hosted (Hypershift) clusters as well.

This will include:

• adding stages to the ROSA on Hypershift UI to instruct the user about BYO-OIDC
• adding fields to accept configuration ARNs and other parameters from the user related to OIDC configuration
• providing verification and feedback to the user related to OIDC configuration