Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-683

Migrate MAPI to Cluster API for AWS -Phase 1

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-764Leverage Cluster API functionality in OpenShift (rather than MAPI)
    • 0% To Do, 50% In Progress, 50% 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.

              rh-ee-smodeel Subin M
              rh-ee-smodeel Subin M
              Joel Speed, Michael McCune, Mike Worthington, Subin M
              Yang Yang Yang Yang
              Stephanie Stout Stephanie Stout
              Joel Speed Joel Speed
              Subin M Subin M
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: