Capturing 12/22 conversation in Slack re: configuring OTEL Collector to talk to Jaeger

M: I am trying to get our product opentelemetry collector to talk to our product jaeger, do you know what certs you used so that jaeger would accept the connection?

ok, so just setting the ca_file seemed to do the trick. I guess this means there is no authorization/authentication between OpenTelemetry Collector and Jaeger? its just open to anyone that wants to use it

B:  This is what works for me, with jaeger also deployed in the tracing-system namespace.

 
apiVersion: v1
kind: ConfigMap
metadata:
  name: otelcol-cabundle
  namespace: tracing-system
  annotations:
   service.beta.openshift.io/inject-cabundle: "true"
—
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: otelcol
  namespace: tracing-system
spec:
  mode: deployment
  volumeMounts:
  - name: cabundle-volume
   mountPath: /etc/pki/ca-trust/source/service-ca
   readonly: true
  volumes:
  - name: cabundle-volume
   configMap:
    name: otelcol-cabundle
  config: |
   receivers:
    otlp:
     protocols:
      grpc:
      http:
   processors:
   exporters:
    jaeger:
     endpoint: jaeger-collector-headless.tracing-system.svc:14250
     ca_file: "/etc/pki/ca-trust/source/service-ca/service-ca.crt"
  service:
   pipelines:
    traces:
     receivers: [otlp]
     processors: []
     exporters: [jaeger]
 

Separate thread

M: and anybody know why the 'tls' option for the Jaeger exporter doesn't seem to work with our product OpenTelemetry collector?

B: I just tested with the product jaeger and otel operators in CRC, and it works fine for me. One issue is that the ca_file entry in the opentelemetry-collector config schema was moved between the 0.33.0 version in our product and the newer community versions that we've been using in our dev cluster. I'll include a note about this in the writeup. We should also fix the opentelemetry-operator's migration for this before we productize a newer version.

 move ca_file to be directly under jaeger and remove the tls entry. The ca_file entry moves under tls in 0.38.0 and newer.

We should get the migration for this setting fixed in the upstream operator before we productize a newer version.