-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Product / Portfolio Work
-
-
11% To Do, 78% In Progress, 11% Done
-
False
-
-
False
-
M
-
None
-
-
-
-
-
-
-
None
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 for vSphere, Azure,GCP - Phase 2
-
- New
-
-
OCPSTRAT-1596 [Tech Preview] Support EC2 Dedicated Hosts on AWS
-
- In Progress
-
- clones
-
OCPSTRAT-683 Migrate MAPI to Cluster API for AWS (TP) - Phase 1
-
- Closed
-
- depends on
-
OCPSTRAT-683 Migrate MAPI to Cluster API for AWS (TP) - Phase 1
-
- Closed
-
- is depended on by
-
OCPSTRAT-2410 AWS IPI: Enable setting the throughput flag for GP3 drives on master/worker instances during installation
-
- New
-
- is related to
-
CORS-4005 Migrate Installer to create Cluster API Machines
-
- In Progress
-
- links to