Uploaded image for project: 'OpenShift Edge Enablement'
  1. OpenShift Edge Enablement
  2. OCPEDGE-61

Leverage Composable OpenShift feature to make image-registry optional

XMLWordPrintable

    • Leverage Composable OpenShift feature to make image-registry optional
    • Product / Portfolio Work
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Yellow
    • Hide

      2023-09-4:

      Dev: Capability merged in

      Docs: 

      QE: 

      Show
      2023-09-4 : Dev: Capability merged in Docs:  QE: 
    • M
    • 5

      Goal

      • Add a capability to make image-registry an optional component

       

      Why is this important?

      • To reduce overall footprint of OpenShift for Telco environments

       

      Scenarios

      1. ...

       

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement
      • ...

       

      Dependencies (internal and external)

      1. ...

       

      Previous Work (Optional):

      1. …

       

      Open questions:

      1. …

       

      Done Checklist

      • CI -  CI is running, tests are automated and merged.
      • Release Technical Enablement N/A
      • Upstream code and tests merged: OCPVE-631
      • Upstream documentation merged: TELCODOCS-1539
      • Downstream build attached to advisory: N/A
      • Test plans in Polarion: Test cases
      • Automated tests merged: openshift-tests-private
      • Downstream documentation merged: N/A

              bzamalut@redhat.com Bulat Zamalutdinov
              jerpeter@redhat.com Geri Peterson (Inactive)
              None
              XiuJuan Wang XiuJuan Wang
              Daniel Macpherson Daniel Macpherson
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: