Epic Goal

• Move MCO API and CRDs to centralized location openshift/api repo

Why is this important?

Most of the core openshift sub-projects APIs live today in https://github.com/openshift/api/  repo .

• Having APIs at one location allows users to vendor a single repo instead of individual sub-projects. I
• it allows to perform cross-API tasks such as complete documentation for CRDs,  complete API review.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• MCO API and CRDs has been moved successfully to https://github.com/openshift/api/ and MCO is running as expected after this change.

Dependencies (internal and external)

1. Repos like SRIO-v operator, installer, etc who are consuming MCO API directly from MCO repo should vendor and switch to using new location i.e https://github.com/openshift/api/

Previous Work (Optional):

1. https://issues.redhat.com/browse/GRPA-3792
2. https://github.com/openshift/api/pull/620

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>