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

LogForwarder YAML does not show input selector after creation

    XMLWordPrintable

Details

    • Passed
    • NEW
    • NEW
    • Hide
      * Previously, the ClusterLogForwarder CR did not show the `input[].selector` element after it had been created. The current release fixes this issue. When you specify a `selector` in the ClusterLogForwarder CR, it remains. Fixing this bug was necessary for link:https://issues.redhat.com/browse/LOG-883[LOG-883], which enables using pod label selectors to forward application log data. link:https://issues.redhat.com/browse/LOG-1338[(*LOG-1338*)]
      Show
      * Previously, the ClusterLogForwarder CR did not show the `input[].selector` element after it had been created. The current release fixes this issue. When you specify a `selector` in the ClusterLogForwarder CR, it remains. Fixing this bug was necessary for link: https://issues.redhat.com/browse/LOG-883 [ LOG-883 ], which enables using pod label selectors to forward application log data. link: https://issues.redhat.com/browse/LOG-1338 [(* LOG-1338 *)]

    Description

      According to the Epic, we need to add an input selector to the ClusterLogForwarder (CLF) to collect application logs only from pods identified by labels.

      However, with latest CLO image, unable to see the selector field in CLF after CLF is created and in ready status

      Both Provided CLF and the created CLF has been attached.

      ClusterLogging Version: clusterlogging.v5.1.0  

      Attachments

        1. CreatedCLF.yaml
          1.0 kB
        2. ProvidedCLF.yaml
          0.4 kB

        Activity

          People

            kkii@redhat.com Keiichi Kii
            rhn-support-kbharti Kabir Bharti
            Kabir Bharti Kabir Bharti
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: