Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7711

Merge ARO installer patches into OCP

XMLWordPrintable

    • False
    • False
    • ?
    • No
    • ?
    • ?
    • ?
    • 0
    • 0% 0%
    • Undefined

       

      Epic Goal

      Why is this important?

      • Today we care carrying a number of patches to the installer. In order to make sure that changes to Openshift don't conflict with the patches and to minimize the time it takes for ARO to support the next minor release, we need these patches to be included in OCP 

      Acceptance Criteria

      • Openshift installer code can be used directly with ARO. 

      Dependencies (internal and external)

      1. ARO patches list: https://github.com/Azure/ARO-RP/blob/master/docs/upstream-differences.md 

       

      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>

            Unassigned Unassigned
            jboutaud@redhat.com Jerome Boutaud
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: