Epic Goal

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

Why is this important?

• While initially CAPI did not meet the requirements for cluster/machine management that OCP had the project has moved on and is a better fit now
• CAPI project is planning on moving to beta 
• CAPI has much better community interaction than MAPI
• Other projects are considering using CAPI and it would be cleaner to have one solution

Scenarios

1. I want to create/delete nodes

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

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>