-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
Logging 5.9
-
None
-
1
-
False
-
-
False
-
-
-
Low
In our documentation we have a good example on how to configure a Kafka output destination for the Cluster Log Forwarder: https://docs.openshift.com/container-platform/4.15/observability/logging/log_collection_forwarding/configuring-log-forwarding.html#cluster-logging-collector-log-forward-kafka_configuring-log-forwarding
However the example is missing documentation for the field ".spec.outputs[].tls.insecureSkipVerify", when customers would like to skip the TLS verification.
The suggestion would be to extend an existing example with that field set to "true":
apiVersion: logging.openshift.io/v1 kind: ClusterLogForwarder metadata: name: <log_forwarder_name> namespace: <log_forwarder_namespace> spec: serviceAccountName: <service_account_name> outputs: - name: app-logs type: kafka url: tls://kafka.example.devlab.com:9093/app-topic secret: name: kafka-secret - name: infra-logs type: kafka url: tcp://kafka.devlab2.example.com:9093/infra-topic tls: insecureSkipVerify: true - name: audit-logs type: kafka url: tls://kafka.qelab.example.com:9093/audit-topic secret: name: kafka-secret-qe [..]
- depends on
-
OBSDOCS-831 Requirements for when log forwarding when using SSL/TLS
- New
-
OBSDOCS-773 clusterlogforwarder.spec.tls.insecureSkipVerify is valid for all the outputs
- To Do