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

[Tech Preview] Cluster API Provider for GCP


    • False
    • Hide


    • False
    • OCPSTRAT-764[Outcome] Leverage Cluster API to introduce new features to OpenShift
    • 100% To Do, 0% In Progress, 0% Done
    • 0
    • 0

      Feature Overview

      Move to using the upstream Cluster API (CAPI) in place of the current implementation of the Machine API for standalone Openshift

      prerequisite work Goals completed in OCPSTRAT-1122
      {}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.

      Phase 1 & 2 covers implementing base functionality for CAPI.

      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 MM
            julim Ju Lim
            Joel Speed, Michael McCune, Mike Worthington, Subin MM
            Jianwei Hou Jianwei Hou
            Stephanie Stout Stephanie Stout
            Joel Speed Joel Speed
            Eric Rich Eric Rich
            0 Vote for this issue
            2 Start watching this issue