-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
None
-
Provide doc links for cluster provisioning for each provider in UI
-
False
-
False
-
To Do
-
ACM-637 - Self-managed IPI provider support
Epic Goal
- Similar to the ACM credentials page, we should include help links that launch out to docs that help users navigate the cluster install process
Why is this important?
- Users frequently ask questions to receive help related to cluster install configurations
- The OpenShift install documentation contains more information about configurations, including many not natively supported by the UI
- Inform users that the cluster provisioning features they are using are the OpenShift install features they may already have used before.
Scenarios
- After selecting an infrastructure provider and OCP version, prompt the user with a notification indicating that they are using X install method (OpenShift installer via Hive, Assisted Installer, or HyperShift) and provide a link to launch to the documentation for the specific infrastructure provider and version selected.
- Mention if a configuration is not displayed as a UI widget, they should be able to manually update the install-config.yaml in the YAML editor.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
