Uploaded image for project: 'OpenShift Image Registry'
  1. OpenShift Image Registry
  2. IR-209

Allow users to specificy a maximum spec tag count

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • API
    • None
    • Limit Imagestream Tag Count
    • To Do
    • None
    • False
    • None
    • False
    • None
    • None
    • None

      As discussed here:
      https://coreos.slack.com/archives/CB95J6R4N/p1631564419212700?thread_ts=1630435609.052600&cid=CB95J6R4N

      There are use cases where a user or component might grow the set of spec tags each release.

      Rather than making such components responsible for their own management/pruning of spec tags to ensure the total number of tags in the imagestream stays under our recommended limit of ~100, it would be useful if it was possible to annotation an imagestream with a max spec tag count and have our existing imagestream controller logic automatically prune away the oldest (by order in the spec array) tags over the specified limit.

      cc ccoleman1@redhat.com obulatov@redhat.com

          1.
          		 Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          		 QE Tracker Sub-task Closed Undefined Unassigned
          3.
          		 TE Tracker Sub-task Closed Undefined Unassigned

              Unassigned Unassigned
              bparees@redhat.com Ben Parees
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: