Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-4467

[moved from 3.5] Secure Tempo query and ingest APIs

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • rhosdt-3.6
    • None
    • None
    • None
    • Secure Tempo query and ingest APIs
    • Security & Compliance
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • In Progress
    • OBSDA-988 - Tempo Improvements for 3.4
    • OBSDA-988Tempo Improvements for 3.4
    • 0% To Do, 0% In Progress, 100% Done

      Grafana Tempo operator security

       

      The goal of this epic is to ensure that query and ingest APIs of Tempo are secured with authentication.

       

      Action items:

      • Secure all query APIs with oauth-proxy (now only Jaeger APIs are covered)
      • Make it very clear in documentation that only multitenant deployment provides authentication and authorization for query and ingest 

      Note:

        As discussed, we currently only going to support multitenanty for the openshift console, for this epic we only require documentaton. Still pending discussion about non-multitenancy environments.

              rvargasp@redhat.com Ruben Vargas Palma
              ploffay@redhat.com Pavol Loffay
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: