-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
3
-
True
-
False
-
HAC Infra OCM - Sprint 237
As a user I want to be able to create an "oidc provider" and "operater-roles with prefix" before submitting a Hypershift cluster creation request because the request, at some point in the future, may return an error from the backend if OIDC provider or operator-roles have not been created.
This will primarily be done on Step 5 "Cluster roles and policies":
Acceptance Criteria
- Add rosa operator-roles cli instructions (prefilled with selected oidc-id and operator-role prefix) under the Operator role prefix input box. Will update automatically on selected oidc-id change or operator-role prefix changes.
- For Rosa classic, update button switcher text
Operator roles
Add this rosa cli for 'HCP' only:
rosa create operator-roles --hosted-cp --prefix "<user-defined>" --oidc-config-id "<odic-config-id>"
UX
Since we are now adding "operator roles" cli commands, do we need to udpate the buttons choices for Rosa classic?
There was suggestions of:
- "Create OIDC Post Installation|Later" instead of "Red Hat managed the OIDC"
- "Create OIDC Now" for "Manage the OIDC myself".
Implementation Notes
- is cloned by
-
OCMUI-848 [Rosa Hypershift Wizard] Updates to Cluster roles and policies step - Change the Operator roles prefix field to a Drop Down with the prefix options
- To Do
- is related to
-
HAC-4246 [Hypershift ROSA] ROSA wizard allows to proceed to next step without selecting a OIDC config from "Cluster roles and policies" step
- Closed
-
HAC-4245 [Hypershift ROSA] Operator role section (Step 2 & 3) are not hidden when no config id is selected
- Closed
-
HAC-4247 [ROSA Classic] When selecting 'Create OIDC Now' option, do not send 'manual' to backend cluster create request.
- Closed
- relates to
-
PD-1545 [ROSA] Cluster roles and policies step allows for OIDC and operator role pre-creation
- Closed
- mentioned on