Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2488

Add the required features to Openshift Integrated Registry to be used as disconnected registry for OCP releases and OLM Images



    • Feature Request
    • Resolution: Done
    • Normal
    • None
    • None
    • Registry
    • None
    • False
    • False
    • 0
    • 0% 0%


      1. Proposed title of this feature request
          - Integrated and Disconnected registry for OCP and OLM

      2. What is the nature and description of the request?

      When you enables the Openshift internal registry (integrated) to be 'Managed' it deploys a pod which holds an internal registry. This can be used by the OCP users to upload their images but it cannot be used as a Openshift Internal Registry to host:

      • OCP Releases
      • OLM Images

      3. Why does the customer need this? (List the business requirements here)

      This is a feature very useful on Edge scenarios when a SNO is deployed on the Far Edge and it cannot access internet, but itself and eventually the internal network.

      This also allows the SNO to hold some sleepy software into the registry avoiding to load the Edge SNO and having more computational strength for Real Time tasks. These sleeping software can be waken up via policies using ACM or Argo in future steps.

      Customers affected:

      • Verizon Far Edge
      • Ericsson

      4. List any affected packages or components.

      Openshift Integrated Registry





            DanielMesser Daniel Messer
            jparrill@redhat.com Juan Manuel Parrilla Madrid
            0 Vote for this issue
            7 Start watching this issue