-
Feature
-
Resolution: Done
-
Normal
-
None
-
Strategic Product Work
-
False
-
False
-
OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
-
0% To Do, 0% In Progress, 100% Done
-
10,000
-
3
-
75% (Medium)
-
3
-
7,500
-
0
-
Program Call
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.
- causes
-
RFE-3186 Configurable pruning behavior of oc mirror
- Accepted
-
RFE-4758 Enable oc-mirror to mirror two specific versions of operators without mirroring versions in between similar to the shortestPath option for platform images
- Accepted
- depends on
-
CFE-942 [TP] Enclave support for oc-mirror
- Closed
-
CLID-5 [TP] Enclave Support for oc-mirror
- Closed
- is cloned by
-
OCPSTRAT-1296 [Tech Preview] OC mirror v2
- Closed