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

Quay Operator can control Clair log level

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • quay-operator
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • 0

      Goal: Support personnel and user administrators can leverage the Quay Operator's QuayRegistry CRD to easily configure Clair's log level in order to enable debug logging.

      Background: In various support interactions it became necessary to reproduce behavior with debug logging enabled. For Quay this is doable today with a configuration override that set an environment variable called "DEBUGLOG". Clair does not support reading its logging configuration from the environment It however does support drop in configuration files, see https://quay.github.io/clair/reference/config.html#configuration-dropins

      Required deliverables:

      • the clair component in the QuayRegistry CRD gets an option log_level parameter which can be set to either one of the values defined in https://quay.github.io/clair/reference/config.html#log_level
      •  when the log_level property is configured, the Quay operator creates a ConfigMap that contains the logging config snippet for Clair as a valid RFC6902 patch
      • the configmap is mounted to all Clair pods as a JSON or YAML patch described in the Clair config dropin config documentation: https://datatracker.ietf.org/doc/html/rfc6902 and Clair pods are restarted
      • upon removal/in absence of the log_level key on the QuayRegistry CRD the config map and volume mounts are removed

            Unassigned Unassigned
            DanielMesser Daniel Messer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: