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

Support non-multitenancy TempoStack and TempoMonolithic

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhosdt-3.9
    • None
    • None
    • None
    • Support non-multitenancy TempoStack and TempoMonolithic instances in Tracing UI
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • In Progress
    • 75% To Do, 0% In Progress, 25% Done

      • Add a required field to Tempo CRs to indicate a non secure instance is going to be created (e.g. tenants.mode=insecure)
      • Add oauth proxy for Tempo query frontend
      • Show non secure instances in the UI

       

       

      The most common question for the Tracing UI is: "Why is my Tempo instance not showing up?"

      The reason why non-multitenancy instances are not supported is because they don't deploy a gateway, and therefore don't have any authentication/authorization.

      To support these instances, we can add a RBAC check on the UI plugin backend (check if user has access to the namespace of the Tempo instance).

              agerstma@redhat.com Andreas Gerstmayr
              agerstma@redhat.com Andreas Gerstmayr
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: