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

Loki output not present in CLO CRD

    XMLWordPrintable

Details

    • Logging (Core) - Sprint 205
    • Passed
    • NEW
    • NEW
    • Hide
      * Before this update, the Custom Resource Definition (CRD) for the Red Hat OpenShift Logging Operator was missing the Loki output type, which caused the admission controller to reject the `ClusterLogForwarder` custom resource object. With this update, the CRD includes Loki as an output type, so administrators can configure `ClusterLogForwarder` to send logs to a Loki server.
      Show
      * Before this update, the Custom Resource Definition (CRD) for the Red Hat OpenShift Logging Operator was missing the Loki output type, which caused the admission controller to reject the `ClusterLogForwarder` custom resource object. With this update, the CRD includes Loki as an output type, so administrators can configure `ClusterLogForwarder` to send logs to a Loki server.

    Description

      Not able to do see 'loki' defined as an output enum in the CLO.

      CRD. https://github.com/openshift/cluster-logging-operator/blob/master/bundle/manifests/logging.openshift.io_clusterlogforwarders_crd.yaml# L299 

      5.2 is using bundle instead of manifests.

      Can you let me know if this needs to be updated to fwd logs to loki?

      Attachments

        Activity

          People

            jcantril@redhat.com Jeffrey Cantrill
            rhn-support-kbharti Kabir Bharti
            Kabir Bharti Kabir Bharti
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: