-
Epic
-
Resolution: Unresolved
-
Critical
-
MCE 2.10.0
-
Improve CAPI cluster import flow
-
Quality / Stability / Reliability
-
False
-
-
False
-
Green
-
In Progress
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
We introduce capi import flow as documented here https://github.com/stolostron/managedcluster-import-controller/blob/main/docs/clusterapi_cluster_import.md, but we still have some gaps.
- several manual steps should be automated.
- support klusterletConfig.
Why is this important?
A better and consistent user experience of importing capi cluster.
Scenarios
...
Acceptance Criteria
...
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)
