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

invalid tune parameters does not invalidate clf

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • OBSDA-549 - Reliability and performance tuning for log collection
    • NEW
    • Release Note Not Required
    • Log Collection - Sprint 250

      Description of problem:

      If a tune parameter is invalid for any output type, the clusterlogforwarder is still valid and will generate a vector.toml

      Version-Release number of selected component (if applicable):

      Logging 5.9

      How reproducible:

      Always

      Steps to Reproduce:

      1.  Create a CLF as follows:

       

      apiVersion: "logging.openshift.io/v1"
      kind: ClusterLogForwarder
      metadata:
        name: custom-tune-forwarder
        namespace: openshift-logging
      spec:
        serviceAccountName: test-sa
        outputs:
          - name: rsyslog-west
            type: syslog
            syslog:
              appName: myapp
            url: 'udp://rsyslogserver.west.example.com:514'
            tuning:
              compression: gzip
        pipelines:
          - name: app-logs
            inputRefs:
              - application
            outputRefs:
              - rsyslog-west

       

      2. Check status of CLF

      Actual results:

      CLF is in a valid state and collector pods are up even if compression is not set for the specific output.

      Expected results:

      CLF should be invalid and collector pods should not be up.

            rh-ee-calee Calvin Lee
            rh-ee-calee Calvin Lee
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: