-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Update oc-mirror v2 mirror-to-disk process such that an annotated version of the imageset-config.yaml input file is created but with the exact versions of OCP releases and operators that oc-mirror v2 pulled to disk
2. What is the nature and description of the request?
This would be an update to the mirror-to-disk or mirror-to-mirror process such that users can see the exact versions of the software that are being mirrored.
3. Why does the customer need this? (List the business requirements here)
Most customer that move content, like OCP and operators, into their offline/disconnected environments have a strict process that must be followed for that data to be brought into the environment. A core requirement of these processes is to list the exact version number of any software that is being brought in. For example, a customer must be able to detail to their transfer team that they are requesting that OpenShift 4.18.21, gitops operator 1.2.3, and kubevirt 4.5.6 are being transferred into the offline/disconnected space. Without the version information customers are not allowed to move content per their data transfer policies. This is a requirement of many man NAPS customers.
4. List any affected packages or components.
oc-mirror v2
- is related to
-
CLID-440 Review NAPS RFEs
-
- In Progress
-