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

Configurable pruning behavior of oc mirror


    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • oc
    • 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.


      From GitHub issues: https://github.com/openshift/oc-mirror/issues/462

            racedoro@redhat.com Ramon Acedo
            DanielMesser Daniel Messer
            3 Vote for this issue
            14 Start watching this issue