Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3819

Impl log-file-metric-exporter as an independent daemonset

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • Log Collection
    • 8
    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Log Collection - Sprint 234, Log Collection - Sprint 235, Log Collection - Sprint 236, Log Collection - Sprint 237, Log Collection - Sprint 238, Log Collection - Sprint 239

      Summary

      As a developer of log collection,
      I want a single, independent deployment of the log-file-metric-exporter
      so that we are only collecting container metrics once on a cluster

      Acceptance Criteria

      • Verify LFME API supports configuration of: resources, tolerations, node selectors
      • Verify LFME is deployed to all nodes on the cluster
      • Verify the CLO only deploys an instance of LFME when a CR is defined
      • Verify only 1 instance of LFME is allowed in a cluster
      • Verify commented API docs exist in the upstream operator repo

        1. Screenshot 2023-06-15 at 17.07.46.png
          Screenshot 2023-06-15 at 17.07.46.png
          168 kB
        2. Screenshot 2023-06-15 at 17.08.27.png
          Screenshot 2023-06-15 at 17.08.27.png
          148 kB

          1.
          		 Implement log-file-metric-exporter API Sub-task Closed Undefined Calvin Lee
          2.
          		 Impl controller to reconcile log-file-metric-exporter CR Sub-task Closed Undefined Calvin Lee
          3.
          		 Impl a virtual log-file-metric-exporter when none exists Sub-task Closed Undefined Calvin Lee
          4.
          		 Implement logfilemetricexporter creation through the OCP console Sub-task Closed Normal Calvin Lee

              rh-ee-calee Calvin Lee
              jcantril@redhat.com Jeffrey Cantrill
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: