Uploaded image for project: 'OpenShift Network Plumbing'
  1. OpenShift Network Plumbing
  2. NP-819

Make ovnk log level configurable

XMLWordPrintable

    • ovnk log cfg
    • Proactive Architecture
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • To Do
    • OCPSTRAT-839MicroShift technical enhancements V4.15
    • 0% To Do, 0% In Progress, 100% Done
    • S
    • uShift Sprint 245

      Epic Goal

      Currently, microshift hardcodes the ovnkube logs to log-level to 4. Goal is to make this configurable, e.g. in the ovn.yaml config file where the MTU is set, or by re-using the "debugging.logLevel". In general, more fine grained control (i.e., its own parameter) is better, to avoid spamming of logs. 

      Why is this important?

      Log Levels should never be hard coded, to allow for changes for better supportability.

      Acceptance Criteria

      • Ovnk log level not hard coded any more
      • If new cfg parameter, docs needs to be updated.

      Previous Work (Optional):

      See discussion here:

      https://docs.google.com/document/d/1F5YrHnOT3MAoj5EL26N9s4A9hF-c3ljgGm8F1ArVpns/edit?disco=AAAAzvh2l5A

      Done Checklist

      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              pliurh Peng Liu
              dfroehli42rh Daniel Fröhlich
              Mike Fiedler Mike Fiedler
              Shauna Diaz Shauna Diaz
              Doug Hellmann Doug Hellmann
              Peng Liu Peng Liu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: