-
Feature Request
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
1. Proposed title of this feature request
Configurable pruning behavior in oc mirror
2. What is the nature and description of the request?
Today, oc-mirror will always prune images outside of what is available in the public catalog or outside of specified min/max version ranges. The request is to add a tunable to the oc mirror config file to allow to disable pruning on a per operator-basis or per-config basis.
3. Why does the customer need this? (List the business requirements here)
Pruning is mostly useful until it removes content you still need. This could happen because operator versions have been unpublished in the source catalog but are still required per the min/max version range selection.
4. List any affected packages or components.
oc-mirror.
From GitHub issues: https://github.com/openshift/oc-mirror/issues/462
- depends on
-
CLID-20 As a user I want to be able to use oc-mirror in both partial and fully disconnected install scenarios so that I can bulk delete all unwanted images according to the requirements for enclave support
-
- Closed
-
- is caused by
-
-
- Closed
-
- is duplicated by
-
-
- Rejected
-
- is incorporated by
-
CLID-5 [TP] Enclave Support for oc-mirror
-
- Closed
-
-
-
- Closed
-
- is related to
-
OCPBUGS-863 oc-mirror shouldn't clean out the operator versions that are not referenced in the channel anymore
-
- Closed
-
