Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-321

Support Log Forwarding API without mTLS with external Elastic Search

    XMLWordPrintable

Details

    • Outcome
    • Resolution: Done
    • Normal
    • None
    • None
    • PM Logging
    • Market Problem
    • False
    • False
    • 0
    • 0% 0%
    • Undefined
    • 0

    Description

      1. Proposed title of this feature request: Support Log Forwarding API without mTLS with external Elastic Search
      2. What is the nature and description of the request? fluentd cannot connect to the external ELK cluster because the current implementation requires mTLS
      3. Why does the customer need this? (List the business requirements here) customer is looking at the "Forwarding logs using the Log Forwarding API" method and is unable to get OpenShift logging working
      4. List any affected packages or components. This is affecting OCP 4.3 & 4.4

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. LOG-1235 Using HTTPS without a secret does not translate into the correct 'scheme' value in Fluentd

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-1467 Expand Collector Configuration Capabilities

          • Undefined - Priority not specified.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-1468 Relax Authorization Requirements for Log Forwarding

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jamparke@redhat.com Jamie Parker
              rhn-support-ncarmich Noreen Carmichael
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: