From 3bb1a1e1ea124fe1071f5eb53ee2f7a9677005f9 Mon Sep 17 00:00:00 2001 From: Elvin Efendi Date: Wed, 20 Feb 2019 10:16:34 -0500 Subject: [PATCH] use correct host for jaeger-collector-host in docs --- docs/user-guide/third-party-addons/opentracing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/third-party-addons/opentracing.md b/docs/user-guide/third-party-addons/opentracing.md index a3243943bf..dc530c2ae1 100644 --- a/docs/user-guide/third-party-addons/opentracing.md +++ b/docs/user-guide/third-party-addons/opentracing.md @@ -17,7 +17,7 @@ We must also set the host to use when uploading traces: ``` zipkin-collector-host: zipkin.default.svc.cluster.local -jaeger-collector-host: jaeger-collector.default.svc.cluster.local +jaeger-collector-host: jaeger-agent.default.svc.cluster.local datadog-collector-host: datadog-agent.default.svc.cluster.local ``` NOTE: While the option is called `jaeger-collector-host`, you will need to point this to a `jaeger-agent`, and not the `jaeger-collector` component. @@ -142,7 +142,7 @@ In the Zipkin interface we can see the details: kind: ConfigMap data: enable-opentracing: "true" - jaeger-collector-host: jaeger-collector.default.svc.cluster.local + jaeger-collector-host: jaeger-agent.default.svc.cluster.local metadata: name: nginx-configuration namespace: kube-system