• False
    • Hide


    • False
    • OCPSTRAT-764Leverage Cluster API functionality in OpenShift (rather than MAPI)
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • Program Call

      Feature Overview

      This feature is about reducing the complexity of the CAPI install system architecture which is needed for using the upstream Cluster API (CAPI) in place of the current implementation of the Machine API for standalone Openshift
      prerequisite work Goals
      Complete the design of the Cluster API (CAPI) architecture and build the core operator logic needed for Phase-1, incorporating the assets from different repositories to simplify asset management.

      Background, and strategic fit

      • Initially CAPI did not meet the requirements for cluster/machine management that OCP had the project has moved on, and CAPI is a better fit now and also has better community involvement.
      • CAPI has much better community interaction than MAPI.
      • Other projects are considering using CAPI and it would be cleaner to have one solution
      • Long term it will allow us to add new features more easily in one place vs. doing this in multiple places.

      Acceptance Criteria

      There must be no negative effect to customers/users of the MAPI, this API must continue to be accessible to them though how it is implemented "under the covers" and if that implementation leverages CAPI is open

            rh-ee-smodeel Subin M
            julim Ju Lim
            Joel Speed, Michael McCune, Mike Worthington, Subin M
            Jianwei Hou Jianwei Hou
            Jeana Routh Jeana Routh
            Joel Speed Joel Speed
            Eric Rich Eric Rich
            0 Vote for this issue
            3 Start watching this issue