-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Strategic Product Work
-
False
-
-
False
-
OCPSTRAT-764Leverage Cluster API functionality in OpenShift (rather than MAPI)
-
36% To Do, 36% In Progress, 27% Done
-
0
-
Program Call
Feature Overview (aka. Goal Summary)
Implement Migration core for MAPI to CAPI for AWS
- This feature covers the design and implementation of converting from using the Machine API (MAPI) to Cluster API (CAPI) for AWS
- This Design investigates possible solutions for AWS
- Once AWS shim/sync layer is implemented use the architecture for other clouds in phase-2 & phase 3
Acceptance Criteria
When customers use CAPI, There must be no negative effect to switching over to using CAPI . Seamless migration of Machine resources. the fields in MAPI/CAPI should reconcile from both CRDs.
- blocks
-
OCPSTRAT-684 Migrate MAPI to Cluster API (CAPI)-Phase 2
- New
- is cloned by
-
OCPSTRAT-1905 Migrate MAPI to Cluster API for Azure -Phase 2
- New
-
OCPSTRAT-1906 Migrate MAPI to Cluster API for GCP -Phase 1
- New
- links to
(12 links to)