Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-593

Consume MCO API and CRDs from openshift/api repo

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • 8
    • False
    • False
    • Undefined
    • MCO Sprint 240, MCO Sprint 241, MCO Sprint 242, MCO Sprint 243
    • 0
    • 0.000

      Description:

      As a MCO developer, it is easier to update and maintain APIs and CRDs when it is co-located with other core operators.

      Most of the core openshift sub-project API and CRDs live today in centralized location  https://github.com/openshift/api/  . This was done as part of enhancement https://github.com/openshift/enhancements/blob/master/enhancements/api-review/centralized-manifest-openapi-generation.md and makes sense for MCO as well.

       

      Acceptance Criteria:

      • MCO starts using own APIs and CRDs from vendored openshift/api
      • MCO works as expected with all current tests passing
      • Send an email to aos-devel once API/CRD move has been successfully done

       
       

              jkyros@redhat.com John Kyros (Inactive)
              rhn-engineering-skumari Sinny Kumari
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: