Skip to content

Commit 96e7129

Browse files
JSticklerJStickler
committed
OSSMDOC-478: distributed tracing 2.2 Release Notes.
1 parent 464f271 commit 96e7129

File tree

5 files changed

+35
-16
lines changed

5 files changed

+35
-16
lines changed

‎modules/distr-tracing-document-attributes.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,15 @@
1414

1515
:DTProductName: Red Hat OpenShift distributed tracing
1616
:DTShortName: distributed tracing
17-
:DTProductVersion: 2.0
17+
:DTProductVersion: 2.1
1818

1919
:JaegerName: Red Hat OpenShift distributed tracing platform
2020
:JaegerShortName: distributed tracing platform
21-
:JaegerVersion: 1.28.0
21+
:JaegerVersion: 1.30.0
2222

2323
:OTELName: Red Hat OpenShift distributed tracing data collection
2424
:OTELShortName: distributed tracing data collection
25-
:OTELVersion: 0.33.0
25+
:OTELVersion: 0.42.0
2626

2727
:product-build:
2828
:DownloadURL: registry.redhat.io

‎modules/distr-tracing-rn-fixed-issues.adoc‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Module included in the following assemblies:
33
* distributed-tracing-release-notes.adoc
44
* service_mesh/v2x/servicemesh-release-notes.adoc
55
////
6-
6+
:_content-type: REFERENCE
77
[id="distr-tracing-rn-fixed-issues_{context}"]
88
= {DTProductName} fixed issues
99
////
@@ -14,6 +14,15 @@ Fix - What did we change to fix the problem?
1414
Result - How has the behavior changed as a result? Try to avoid “It is fixed” or “The issue is resolved” or “The error no longer presents”.
1515
////
1616

17+
* 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:
18+
+
19+
[source,terminal]
20+
----
21+
{"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}
22+
----
23+
+
24+
This issue was resolved by exposing only the HTTP(S) port of the query service, and not the gRPC port.
25+
1726
* link:https://issues.redhat.com/browse/TRACING-2009[TRACING-2009] The Jaeger Operator has been updated to include support for the Strimzi Kafka Operator 0.23.0.
1827
1928
* link:https://issues.redhat.com/browse/TRACING-1907[TRACING-1907] The Jaeger agent sidecar injection was failing due to missing config maps in the application namespace. The config maps were getting automatically deleted due to an incorrect `OwnerReference` field setting and as a result, the application pods were not moving past the "ContainerCreating" stage. The incorrect settings have been removed.

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

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Module included in the following assemblies:
33
* service_mesh/v2x/servicemesh-release-notes.adoc
44
* distributed-tracing--release-notes.adoc
55
////
6-
6+
:_content-type: REFERENCE
77
[id="distr-tracing-rn-known-issues_{context}"]
88
= {DTProductName} known issues
99

@@ -22,15 +22,6 @@ These limitations exist in {DTProductName}:
2222
2323
These are the known issues for {DTProductName}:
2424

25-
* 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:
26-
+
27-
[source,terminal]
28-
----
29-
{"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}
30-
----
31-
+
32-
This does not affect Jaeger functionality. There is no workaround at this time.
33-
3425
* 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:
3526
3627
** Jaeger Operator channel: *1.17.x stable* or *1.20.x stable*

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

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,27 @@ Feature – Describe the new functionality available to the customer. For enhanc
77
Reason – If known, include why has the enhancement been implemented (use case, performance, technology, etc.). For example, showcases integration of X with Y, demonstrates Z API feature, includes latest framework bug fixes.
88
Result – If changed, describe the current user experience.
99
////
10-
10+
:_content-type: REFERENCE
1111
[id="distr-tracing-rn-new-features_{context}"]
1212
= New features and enhancements
1313

1414
This release adds improvements related to the following components and concepts.
1515

16+
== New features and enhancements {DTProductName} 2.2.0
17+
18+
This release of {DTProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
19+
20+
=== Component versions supported in {DTProductName} version 2.2.0
21+
22+
|===
23+
|Component |Version
24+
|Jaeger
25+
|1.30.0
26+
27+
|OpenTelemetry
28+
|0.42.0
29+
|===
30+
1631
== New features and enhancements {DTProductName} 2.1.0
1732

1833
This release of {DTProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Module included in the following assemblies:
33
- rhbjaeger-release-notes.adoc
44
////
5-
5+
:_content-type: CONCEPT
66
[id="distr-tracing-rn-tech-preview_{context}"]
77
= {DTProductName} Technology Preview
88
////
@@ -17,6 +17,10 @@ Technology Preview features are not supported with Red Hat production service le
1717
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/.
1818
====
1919

20+
== {DTProductName} 2.2.0 Technology Preview
21+
22+
Unsupported OpenTelemetry Collector components included in the 2.1 release have been removed.
23+
2024
== {DTProductName} 2.1.0 Technology Preview
2125

2226
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.

0 commit comments

Comments
 (0)