Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-876

[Tech Preview] OC mirror multiple internet disconnected enclaves

    XMLWordPrintable

Details

    • False
    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 54
    • 54% 54%
    • 10,000
    • 3
    • 75% (Medium)
    • 3
    • 7,500
    • 0
    • Program Call

    Description

      Technology Preview of the oc mirror enclaves support (Dev Preview was OCPSTRAT-765 in OpenShift 4.15).

      Feature description

      oc-mirror already focuses on mirroring content to disconnected environments for installing and upgrading OCP clusters.

      This specific feature addresses use cases where mirroring is needed for several enclaves (disconnected environments), that are secured behind at least one intermediate disconnected network.

      In this context, enclave users are interested in:

      • being able to mirror content for several enclaves, and centralizing it in a single internal registry. Some customers are interested in running security checks on the mirrored content, vetting it before allowing mirroring to downstream enclaves.
      • being able to mirror contents directly from the internal centralized registry to enclaves without having to restart the mirroring from internet for each enclave
      • keeping the volume of data transfered from one network stage to the other to a strict minimum, avoiding to transfer a blob or an image more than one time from one stage to another.

       

      Attachments

        Issue Links

          depends on

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CLID-5 [TP] Enclave Support for oc-mirror

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • In Progress

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CFE-942 [TP] Enclave support for oc-mirror

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-1296 [Tech Preview] OC mirror v2

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • New

          Activity

            People

              racedoro@redhat.com Ramon Acedo
              gausingh@redhat.com Gaurav Singh
              Alex Guidi, Luigi Mario Zuccarelli, Ondrej Lolek, Sherine Khoury, Shubha Narayanan
              Ondrej Lolek Ondrej Lolek
              ying zhou ying zhou
              Shubha Narayanan Shubha Narayanan
              Jeremy Peterson Jeremy Peterson
              Eric Rich Eric Rich
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: