Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-5824

APIcast integration with Jaeger in another project, namespace

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.9.1 GA
    • 2.8 GA
    • Gateway
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • QE
    • +

      This steps to Installing Jaeger show Jaeger being installed in the same project as 3scale. Jaeger can be run in a separate project/namespace with the following changes to jaeger_config.json shown in the documentation.

      • change "hostPort" : "127.0.0.1:5778"
        to "hostPort" : "jaeger-agent.logs.svc.cluster.local:5778",
      • change "localAgentHostPort" : "jaeger-agent:6831"
        to "localAgentHostPort" : "jaeger-agent.logs.svc.cluster.local:-5778-6831"

      This has been done by a customer. I have verified it my own local instance.
      I am creating this task for QE (who tests in the same namespace for simplicity) and eloycoto to verify/confirm there are no issues with the above.  

        1. configmap-jaeger-sepnamespace-config.yaml
          1 kB

              Unassigned Unassigned
              rhn-support-cvajjhal Chandrasekhar Vajjhala (Inactive)
              David Rajnoha David Rajnoha (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: