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

[release-6.2]clusterLogForwarder API doesn't indicate that the kafka URL should be tcp or tls

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • Logging 6.2.4
    • Logging 5.8.z, Logging 5.9.z, Logging 6.0.z, Logging 6.1.z, Logging 6.2.z, Logging 6.3.z
    • Log Collection
    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this update, the clusterLogForwarder API did not validate the URL scheme for Kafka outputs. This could cause users to configure a Kafka output with an invalid URL that was missing the required 'tcp://' or 'tls://' prefix, leading to a silent failure where logs were not forwarded as expected. With this update, new validation has been added to the API. The clusterLogForwarder now rejects configurations with a Kafka URL that does not have a tcp or tls scheme, preventing the misconfiguration and ensuring logs can be forwarded successfully.
      Show
      Before this update, the clusterLogForwarder API did not validate the URL scheme for Kafka outputs. This could cause users to configure a Kafka output with an invalid URL that was missing the required ' tcp://' or ' tls://' prefix, leading to a silent failure where logs were not forwarded as expected. With this update, new validation has been added to the API. The clusterLogForwarder now rejects configurations with a Kafka URL that does not have a tcp or tls scheme, preventing the misconfiguration and ensuring logs can be forwarded successfully.
    • Bug Fix
    • Logging - Sprint 274
    • Low

      Description of problem:

      When verifying how the "url" for Kafka should be, it's not indicated what's the format and possible value.

      I'd expect that for any output, I should see the format that the url can take:

      <protocol>://<url>:<port>

      Where protocol could be http/https/tls/tcp and indicated in specific for Kafka and the rest of the outputs the protocol to be used
      Where url, it should be expected to indicate if it's valid to use an ip address or it must be FQDN, in the past, long time ago, some limitations existed on this for some output as it could be syslog

      It's frequent to find issues in the configurations as consequence of not knowing the format and not existing a validation for it.

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

      Logging 6.y
      ClusterLogForwarder API (collector)

      How reproducible:

      Steps to Reproduce:

      1. Run the command `oc explain obsclf.spec.outputs.<output>.url and verify that not indicated the format that it can have

              vparfono Vitalii Parfonov
              rhn-support-ocasalsa Oscar Casal Sanchez
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: