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

Using HTTPS without a secret does not translate into the correct 'scheme' value in Fluentd

XMLWordPrintable

    • Logging (Core) - Sprint 209

      Currently, you need to always provide a Secret to work with HTTPS. It seems that this code line is responsible for that.

      With the following LF CR:

      apiVersion: logging.openshift.io/v1
kind: ClusterLogForwarder
metadata:
  name: instance
  namespace: openshift-logging
spec:
  outputs:
    - name: es-created-by-user
      type: elasticsearch
      url: 'https://elasticsearch-server.openshift-logging.svc:9200'
  pipelines:
    - name: forward-to-external-es
      inputRefs:
      - infrastructure
      - application
      - audit
      outputRefs:
      - es-created-by-user

      Expected Fluentd entry:

      @type elasticsearch
@id es_created_by_user
host elasticsearch-server.openshift-logging.svc
port 9200
verify_es_version_at_startup false
scheme https

      Actual:

      @type elasticsearch
@id es_created_by_user
host elasticsearch-server.openshift-logging.svc
port 9200
verify_es_version_at_startup false
scheme http

              jcantril@redhat.com Jeffrey Cantrill
              cvogel1 Christian Heidenreich (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: