anchor.diff:  <4> Specify the `kafka` type.
   <5> Specify the URL and port of the Kafka broker as a valid absolute URL, optionally with a specific topic. You can use the `tcp` (insecure) or `tls` (secure TCP) protocol. If the cluster-wide proxy using the CIDR annotation is enabled, the output must be a server name or FQDN, not an IP address.
   <6> If using a `tls` prefix, you must specify the name of the secret required by the endpoint for TLS communication. The secret must exist in the `openshift-logging` project and must have keys of: *tls.crt*, *tls.key*, and *ca-bundle.crt* that point to the respective certificates that they represent.
  -<7> Optional: Specify a name for the pipeline.
  -<8> Specify which log types should be forwarded using that pipeline: `application,` `infrastructure`, or `audit`.
  -<9> Specify the output to use with that pipeline for forwarding the logs.
  -<10> Optional: One or more labels to add to the logs.
  -<11> Optional: Configure multiple outputs to forward logs to other external log aggregtors of any supported type:
  +<7> Optional: To send an insecure output, use a `tcp` prefix in front of the URL. Also omit the `secret` key and its `name` from this output.
  +<8> Optional: Specify a name for the pipeline.
  +<9> Specify which log types should be forwarded using that pipeline: `application,` `infrastructure`, or `audit`.
  +<10> Specify the output to use with that pipeline for forwarding the logs.
  +<11> Optional: One or more labels to add to the logs.
  +<12> Optional: Configure multiple outputs to forward logs to other external log aggregtors of any supported type:
   ** Optional. A name to describe the pipeline.
   ** The `inputRefs` is the log type to forward using that pipeline: `application,` `infrastructure`, or `audit`.
   ** The `outputRefs` is the name of the output to use.
   ** Optional: One or more labels to add to the logs.
  -<12> Optional: Specify `default` to forward logs to the internal Elasticsearch instance.
  +<13> Optional: Specify `default` to forward logs to the internal Elasticsearch instance.
  +
  +. Optional: To forward a single output to multiple kafka brokers, specify an array of kafka brokers as shown in this example:
  ++
  +[source,yaml]
  +----
  +...
  +spec:
  +  outputs:
  +  - name: app-logs
  +    type: kafka
  +    secret:
  +      name: kafka-secret-dev
  +    kafka:  <1>
  +      brokers: <2>
  +        - tls://kafka-broker1.example.com:9093/
  +        - tls://kafka-broker2.example.com:9093/
  +      topic: app-topic <3>
  +...
  +----
  +<1> Specify a `kafka` key that has a `brokers` and `topic` key.
  +<2> Use the `brokers` key to specify an array of one or more brokers.
  +<3> Use the `topic` key to specify the target topic that will receive the logs.
   
   . Create the CR object:
   +
  
positive.code:      - audit
       outputRefs:
       - audit-logs
       - default <12>
       labels:
         logType: audit
  ----
  
negative.code:        name: kafka-secret <6>
     - name: infra-logs
       type: kafka
       url: tcp://kafka.devlab2.example.com:9093/infra-topic <7>
     - name: audit-logs
       type: kafka
       url: tls://kafka.qelab.example.com:9093/audit-topic
       secret:
          name: kafka-secret-qe
    pipelines:
     - name: app-topic <8>
       inputRefs: <9>
       - application
       outputRefs: <10>
       - app-logs
       labels:
         logType: application <11>
     - name: infra-topic <12>
       inputRefs:
       - infrastructure
       outputRefs:
  