Merge pull request #40987 from JStickler/OSSMDOC-456

OSSMDOC-454: Release Notes for distributed tracing 2.1.0

Author: JStickler

modules/distr-tracing-rn-known-issues.adoc

@@ -22,6 +22,15 @@ These limitations exist in {DTProductName}:
 
 These are the known issues for {DTProductName}:
 
+* link:https://issues.redhat.com/browse/TRACING-2337[TRACING-2337] Jaeger is logging a repetitive warning message in the Jaeger logs similar to the following:
++
+[source,terminal]
+----
+{"level":"warn","ts":1642438880.918793,"caller":"channelz/logging.go:62","msg":"[core]grpc: Server.Serve failed to create ServerTransport: connection error: desc = \"transport: http2Server.HandleStreams received bogus greeting from client: \\\"\\\\x16\\\\x03\\\\x01\\\\x02\\\\x00\\\\x01\\\\x00\\\\x01\\\\xfc\\\\x03\\\\x03vw\\\\x1a\\\\xc9T\\\\xe7\\\\xdaCj\\\\xb7\\\\x8dK\\\\xa6\\\"\"","system":"grpc","grpc_log":true}
+----
++
+This does not affect Jaeger functionality. There is no workaround at this time.
+
 * link:https://issues.redhat.com/browse/TRACING-2057[TRACING-2057] The Kafka API has been updated to `v1beta2` to support the Strimzi Kafka Operator 0.23.0. However, this API version is not supported by AMQ Streams 1.6.3. If you have the following environment, your Jaeger services will not be upgraded, and you cannot create new Jaeger services or modify existing Jaeger services:
 
 ** Jaeger Operator channel: *1.17.x stable* or *1.20.x stable*

modules/distr-tracing-rn-new-features.adoc

@@ -9,6 +9,25 @@ Result – If changed, describe the current user experience.
 ////
 
 [id="distr-tracing-rn-new-features_{context}"]
+= New features and enhancements
+
+This release adds improvements related to the following components and concepts.
+
+== New features and enhancements {DTProductName} 2.1.0
+
+This release of {DTProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
+
+=== Component versions supported in {DTProductName} version 2.1.0
+
+|===
+|Component |Version
+|Jaeger
+|1.29.1
+
+|OpenTelemetry
+|0.41.1
+|===
+
 == New features and enhancements {DTProductName} 2.0.0
 
 This release marks the rebranding of Red Hat OpenShift Jaeger to {DTProductName}. This release consists of the following changes, additions, and improvements:
@@ -31,11 +50,10 @@ This release marks the rebranding of Red Hat OpenShift Jaeger to {DTProductName}
 
 This release also addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
 
-== Component versions supported in {DTProductName} version 2.0.0
+=== Component versions supported in {DTProductName} version 2.0.0
 
 |===
 |Component |Version
-
 |Jaeger
 |1.28.0
 

modules/distr-tracing-rn-technology-preview.adoc

@@ -17,6 +17,35 @@ Technology Preview features are not supported with Red Hat production service le
 These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
 ====
 
+== {DTProductName} 2.1.0 Technology Preview
+
+This release introduces a breaking change to how to configure certificates in the OpenTelemetry custom resource file. In the new version, the `ca_file` moves under `tls` in the custom resource, as shown in the following examples.
+
+.CA file configuration for OpenTelemetry version 0.33
+[source,yaml]
+----
+spec:
+  mode: deployment
+  config: |
+    exporters:
+      jaeger:
+        endpoint: jaeger-production-collector-headless.tracing-system.svc:14250
+        ca_file: "/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt"
+----
+
+.CA file configuration for OpenTelemetry version 0.41.1
+[source,yaml]
+----
+spec:
+  mode: deployment
+  config: |
+    exporters:
+      jaeger:
+        endpoint: jaeger-production-collector-headless.tracing-system.svc:14250
+        tls:
+          ca_file: "/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt"
+----
+
 == {DTProductName} 2.0.0 Technology Preview
 
 This release includes the addition of the {OTELName}, which you install using the {OTELName} Operator. {OTELName} is based on the link:https://opentelemetry.io/[OpenTelemetry] APIs and instrumentation.