I’m looking to integrate consul connect with opentracing (jaeger) with deployments in Kubernetes. I’m using the official consul-helm chart to deploy consul and so on.
I have tried out this demo https://github.com/hashicorp/consul-demo-tracing
although it left me a bit confused:
the demo is using the fake service, which has opentracing instrumentation implemented within. I thought the point of using a service mesh is that the service mesh can automatically report spans to the collector without explicitly instrumenting the code? (whether or not it’s useful that’s a different debate).
I’m looking at the envoy configuration for jaeger https://github.com/envoyproxy/envoy/tree/master/examples/jaeger-tracing, and it appears that it requires
listener section specified for the initial opentracing span: https://github.com/envoyproxy/envoy/blob/master/examples/jaeger-tracing/service1-envoy-jaeger.yaml#L2-L31
My question is, how do I specify that in the context of consul-helm in kubernetes? Has anyone done that?
Thanks in advance!