Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-2803

Quay should notify Clair when manifests are garbage collected

    XMLWordPrintable

Details

    • Notify Clair when manifests are garbage collected
    • False
    • False
    • Green
    • To Do
    • 0
    • 0% 0%
    • 0

    Description

      When Quay no longer has a manifest in its database, it should notify Clair via a to-be-implemented API that the manifest can be forgotten.

      Attachments

        Issue Links

          is blocked by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. PROJQUAY-2802 clair needs to be able to forget manifests

          • 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 related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PROJQUAY-465 Quay as a cache proxy / pull-through cache for other registries

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CLAIRDEV-18 Finalize strategy for Clair garbage collection

          • 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.
          • To Do
          relates to

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-4126 Clair database growing

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. PROJQUAY-3839 Add ability for Clair to GC its database

          • 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.
          • Closed
          links to

          Web Link RHBA-2023:113766 Red Hat Quay v3.10.0 minor release

          Activity

            People

              sleesinc Kenny Lee Sin Cheong
              hdonnay Henry Donnay
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: