Bug 1900804

Description of problem:
Want to keep default fluentd -> elasticsearch pipelines. However, also want to forward logs from specific namespaces to an external endpoint.
Defining 4 pipelines (3 default pipelines plus the external endpoint), it appears Elasticsearch only begins receiving logs from the "filtered" namespaces (which are supposed to send to both internal ES and external endpoint).


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

How reproducible:
Unconfirmed -- working on reproducer


Actual results:
*Only* the 3 "filtered" namespaces show up in elasticsearch

Expected results:
*All* namespaces should show up in elasticsearch

Additional info:

Custom input defined:

  inputs:
    - application:
        namespaces:
          - example1
          - example2
          - example3
      name: example-app-logs

Defined pipelines as follows:

  pipelines:
    - inputRefs:
        - audit
      name: audit-logs
      outputRefs:
        - default
    - inputRefs:
        - infrastructure
      name: infrastructure-logs
      outputRefs:
        - default
    - inputRefs:
        - example-app-logs
      name: example-app-pipeline
      outputRefs:
        - fluentd-app
    - inputRefs:
        - application
      name: application-logs
      outputRefs:
        - default

Customer noted this as well:
"I removed the fluentdForward pipeline (example-app-pipeline) and Elasticsearch is capturing everything again. And note, this is even with me keeping the example-app-logs input around. So I don't think the definition of the application input automatically overrides the default one, it's only when example-app-logs is actually used as an inputRef, the behaviour of the application inputRef matches example-app-logs."

I'll attach ClusterLogForwarding yaml momentarily.