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

Improve clair database update process for disconnected environments

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Clair, Quay
    • None
    • BU Product Work
    • False
    • None
    • False
    • Not Selected

      Currently the update process for clair definitions in quay requires a lot of work for the Customer.

       

      They need to (as of https://docs.redhat.com/en/documentation/red_hat_quay/3.12/html-single/vulnerability_reporting_with_clair_on_red_hat_quay/index#clair-disconnected-ocp-configuration):

      1. setup and maintain a connected clair
      2. export the updaters
      3. transfer the updaters
      4. connect the clair database to their transfer host
      5. import the updaters

      (and doing some clair.config steps which I left out)

      They are also required to update the Clair CPE mapping files regularly to ensure rpm scanning (see https://docs.redhat.com/en/documentation/red_hat_quay/3.12/html-single/vulnerability_reporting_with_clair_on_red_hat_quay/index#mapping-repositories-to-cpe-information)

       

      In opposition to this the update-process for clair definition files in RHACS is 

      1. Download the definitions from red hat
      2. transfer the file
      3. Upload the definitions to central

       

      After the great work that went into unifying the scanning experience in quay and rhacs it would be nice to also have a similar experience regarding the update process.

              DanielMesser Daniel Messer
              sluetzen Steffen Lützenkirchen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: