Uploaded image for project: 'Network Edge'
  1. Network Edge
  2. NE-1441

Bump openshift-router image to RHEL9

XMLWordPrintable

    • Bump openshift-router image to RHEL9
    • 8
    • False
    • None
    • False
    • Green
    • To Do
    • 9% To Do, 0% In Progress, 91% Done
    • M
    • 0
    • 0.0
    • Approved

      Template:

      Networking Definition of Planned

      Epic Template descriptions and documentation

      Epic Goal

      Bump the openshift-router container image to RHEL9 with help from the ART Team.

      Why is this important?

      OpenShift is transitioning to RHEL9 base images and we must move to RHEL9 by 4.16. RHEL9 introduces OpenSSL 3.0. OpenSSL 3.0 has shown 

      Planning Done Checklist

      The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

      • Priority+ is set by engineering
      • Epic must be Linked to a +Parent Feature
      • Target version+ must be set
      • Assignee+ must be set
      • (Enhancement Proposal is Implementable
      • (No outstanding questions about major work breakdown
      • (Are all Stakeholders known? Have they all been notified about this item?
      • Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
        1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
        2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

      Additional information on each of the above items can be found here: Networking Definition of Planned

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement
        details and documents.
      • Openshift-Router image is RHEL9
      • Investigation to RHEL9 Performance degradation is complete

      ...

      Dependencies (internal and external)

      1. Perf & Scale
      2. ART Team

      ...

      Previous Work (Optional):

      1. ART Issue: https://issues.redhat.com/browse/ART-8359
      2. RHEL9 Router Smoke Test: https://github.com/openshift/router/pull/538 
      3. RHEL9 ART Slack Thread

      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>

            gspence@redhat.com Grant Spence
            gspence@redhat.com Grant Spence
            ANDREW MCDERMOTT
            Shudi Li Shudi Li
            Ashley Hardin Ashley Hardin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: