Merge pull request openshift#12 from pavolloffay/distributed-tracing-3.0-drop-jaeger-exporter

TRACING-3569 | Drop OTELcol Jaeger exporter

Author: max-cx

modules/distr-tracing-otel-config-collector.adoc

@@ -38,8 +38,8 @@ spec:
           http:
     processors:
     exporters:
-      jaeger:
-        endpoint: jaeger-production-collector-headless.tracing-system.svc:14250
+      otlp:
+        endpoint: jaeger-production-collector-headless.tracing-system.svc:4317
         tls:
           ca_file: "/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt"
       prometheus:
@@ -76,7 +76,7 @@ spec:
 
 |exporters:
 |An exporter sends data to one or more back ends or destinations. By default, no exporters are configured. There must be at least one enabled exporter for a configuration to be considered valid. Exporters are enabled by being added to a pipeline. Exporters might be used with their default settings, but many require configuration to specify at least the destination and security settings.
-|`otlp`, `otlphttp`, `jaeger`, `logging`, `prometheus`
+|`otlp`, `otlphttp`, `logging`, `prometheus`
 |None
 
 |service:
@@ -343,33 +343,6 @@ The OTLP HTTP exporter exports data using the OpenTelemetry protocol (OTLP).
 <2> The client side TLS configuration. Defines paths to TLS certificates.
 <3> Headers are sent in every HTTP request.
 
-[id="jaeger-exporter_{context}"]
-==== Jaeger exporter
-
-The Jaeger exporter exports data using the Jaeger proto format through gRPC.
-
-* Support level: link:https://access.redhat.com/support/offerings/techpreview[Technology Preview]
-* Supported signals: traces
-
-.OpenTelemetry Collector custom resource with enabled Jaeger exporter
-[source,yaml]
-----
-  config: |
-    exporters:
-      jaeger:
-        endpoint: jaeger-all-in-one:14250 <1>
-        tls: <2>
-          ca_file: ca.pem
-          cert_file: cert.pem
-          key_file: key.pem
-    service:
-      pipelines:
-        traces:
-          exporters: [jaeger]
-----
-<1> The Jaeger gRPC endpoint.
-<2> The client side TLS configuration. Defines paths to TLS certificates.
-
 [id="logging-exporter_{context}"]
 ==== Logging exporter