-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Spike: Cluster API POC
-
False
-
False
-
Cloud
-
Done
-
OCPPLAN-7719 - Cluster API integration
-
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
Epic Goal
- Do a proof of concept investigating how we would implement and integrate the Cluster API (CAPI) into OpenShift
Why is this important?
- The CAPI upstream effort is moving along nicely and a move to Beta is being planned
- There are capabilities in CAPI that extend beyond what the MAPI can do today
- We need to better understand what CAPI will mean for OpenShift, a POC is the best way to do that
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>
