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

Configurable pruning behavior of oc mirror

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • oc
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

    Description

      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

      Attachments

        Issue Links

          depends on

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. 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

          • 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 duplicated by

          Feature Request - Feature requests from customers and/or users RFE-3381 Cannot prevent oc-mirror to perform content removal from a mirror registry

          • 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.
          • Rejected
          is incorporated by

          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.
          • Testing

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CFE-660 oc-mirror Feature requests related to OCI

          • Undefined - Priority not specified.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-863 oc-mirror shouldn't clean out the operator versions that are not referenced in the channel anymore

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated: