Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-2606

Hybrid SRE: Decoupling installer from release payload

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Decoupling installer from release payload
    • Proactive Architecture
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-735 - Decouple OpenShift Installer from release payload
    • OCPSTRAT-735Decouple OpenShift Installer from release payload
    • 100% To Do, 0% In Progress, 0% Done

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • The latest openshift-install can install any z-stream of its matched X.Y version

      Why is this important?

      • Decouples fix delivery from the version of the product being installed
        • Fixes for CVEs in openshift-installer code itself
        • Defect fixes for code in openshift-installer
      • Also allows the latest builds of the installer image to install older versions of the product without that image being flagged for including a vulnerable package (ie: glibc or openssl rpms in the image)

      Scenarios

      1. There's a CVE in openshift-install codebase fixed in 4.12.25 but a need to continue installing 4.12.20 without potentially executing vulnerable code
      2. There's a known incompatibility between 4.12.25+ installer and < 4.12.10, therefore 4.12.25 should error out if asked to install versions < 4.12.10 because they're specifically known to be incompatible.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      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
              beth.white Beth White
              Gaoyun Pei Gaoyun Pei
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: