Major Epic Goal
- Re-design the entry point selection of a user choosing an infrastructure provider to create a cluster
Why is this important?
- The list of providers and the availability of different topology options varies among them
- User needs to easily be able to access the specific provider and deployment pattern they want; and know what is supported in each infrastructure
- For UI implementation, the resources required to create a deployment under a certain provider, deployment pattern, or topology will highly vary so the abstract entry point will ease also ease the front-end code.
Scenarios
- ...
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>
