Skip to content

Commit addb250

Browse files
max-cxmax-cx
committed
OBSDOCS-1415: Release notes for the Distributed Tracing 3.3.1 patch
1 parent 80f99e5 commit addb250

File tree

2 files changed

+196
-0
lines changed

2 files changed

+196
-0
lines changed

‎observability/distr_tracing/distr-tracing-rn.adoc

+129
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,135 @@ You can use the {TempoName} xref:../otel/otel-forwarding-telemetry-data.adoc#ote
1212

1313
include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-features-only.adoc[]
1414

15+
[id="distr-tracing_3-3-1_{context}"]
16+
== Release notes for {DTProductName} 3.3.1
17+
18+
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
19+
20+
////
21+
[id="distr-tracing_3-3-1_cves_{context}"]
22+
=== CVEs
23+
24+
This release fixes the following CVEs:
25+
26+
* link:https://access.redhat.com/security/cve/CVE-202?-????/[CVE-202?-????]
27+
////
28+
29+
[id="distr-tracing_3-3-1_tempo-release-notes_{context}"]
30+
=== {TempoName}
31+
32+
The {TempoName} is provided through the {TempoOperator}.
33+
34+
The {TempoName} 3.3.1 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.5.0.
35+
36+
////
37+
[id="distr-tracing_3-3-1_tempo-release-notes_technology-preview-features_{context}"]
38+
==== Technology Preview features
39+
40+
This update introduces the following Technology Preview feature:
41+
42+
* ???.
43+
44+
:FeatureName: The Tempo monolithic deployment
45+
include::snippets/technology-preview.adoc[leveloffset=+1]
46+
////
47+
48+
////
49+
[id="distr-tracing_3-3-1_tempo-release-notes_new-features-and-enhancements_{context}"]
50+
==== New features and enhancements
51+
52+
This update introduces the following enhancements:
53+
54+
* ???.
55+
////
56+
57+
////
58+
[id="distr-tracing_3-3-1_tempo-release-notes_deprecated-functionality_{context}"]
59+
==== Deprecated functionality
60+
61+
In the {TempoName} 3.3.1, ???.
62+
////
63+
64+
////
65+
[id="distr-tracing_3-3-1_tempo-release-notes_removal-notice_{context}"]
66+
==== Removal notice
67+
68+
In the {TempoName} 3.3.1, the FEATURE has been removed. Bug fixes and support are provided only through the end of the 3.? lifecycle. As an alternative to the FEATURE for USE CASE, you can use the ALTERNATIVE instead.
69+
////
70+
71+
////
72+
[id="distr-tracing_3-3-1_tempo-release-notes_bug-fixes_{context}"]
73+
==== Bug fixes
74+
75+
This update introduces the following bug fixes:
76+
77+
* ????. (link:https://issues.redhat.com/browse/TRACING-????[TRACING-????])
78+
////
79+
80+
[id="distr-tracing_3-3-1_tempo-release-notes_known-issues_{context}"]
81+
==== Known issues
82+
83+
There is currently a known issue:
84+
85+
* Currently, the {TempoShortName} fails on the {ibm-z-title} (`s390x`) architecture. (link:https://issues.redhat.com/browse/TRACING-3545[TRACING-3545])
86+
87+
[id="distr-tracing_3-3-1_jaeger-release-notes_{context}"]
88+
=== {JaegerName}
89+
90+
The {JaegerName} is provided through the {JaegerOperator} Operator.
91+
92+
The {JaegerName} 3.3.1 is based on the open source link:https://www.jaegertracing.io/[Jaeger] release 1.57.0.
93+
94+
[IMPORTANT]
95+
====
96+
Jaeger does not use FIPS validated cryptographic modules.
97+
====
98+
99+
[id="distr-tracing_3-3-1_jaeger-release-notes_support-for-elasticsearch-operator_{context}"]
100+
==== Support for the {es-op}
101+
102+
The {JaegerName} 3.3.1 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
103+
104+
[id="distr-tracing_3-3-1_jaeger-release-notes_deprecated-functionality_{context}"]
105+
==== Deprecated functionality
106+
107+
In the {DTProductName} 3.3.1, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
108+
Red Hat will provide support for these components and fixes for CVEs and bugs with critical and higher severity during the current release lifecycle, but these components will no longer receive feature enhancements.
109+
The {TempoOperator} and the {OTELName} are the preferred Operators for distributed tracing collection and storage.
110+
Users must adopt the OpenTelemetry and Tempo distributed tracing stack because it is the stack to be enhanced going forward.
111+
112+
In the {DTProductName} 3.3.1, the Jaeger agent is deprecated and planned to be removed in the following release.
113+
Red Hat will provide bug fixes and support for the Jaeger agent during the current release lifecycle, but the Jaeger agent will no longer receive enhancements and will be removed.
114+
The OpenTelemetry Collector provided by the {OTELName} is the preferred Operator for injecting the trace collector agent.
115+
116+
////
117+
[id="distr-tracing_3-3-1_jaeger-release-notes_removal-notice_{context}"]
118+
==== Removal notice
119+
120+
In the {JaegerName} 3.3.1, the FEATURE has been removed. Bug fixes and support are provided only through the end of the 3.? lifecycle. As an alternative to the FEATURE for USE CASE, you can use the ALTERNATIVE instead.
121+
////
122+
123+
////
124+
[id="distr-tracing_3-3-1_jaeger-release-notes_bug-fixes_{context}"]
125+
==== Bug fixes
126+
127+
This update introduces the following bug fixes:
128+
129+
* Before this update, ???. With this update, ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
130+
////
131+
132+
[id="distr-tracing_3-3-1_jaeger-release-notes_known-issues_{context}"]
133+
==== Known issues
134+
135+
There are currently known issues:
136+
137+
* Currently, Apache Spark is not supported.
138+
139+
ifndef::openshift-rosa[]
140+
141+
* Currently, the streaming deployment via AMQ/Kafka is not supported on the {ibm-z-title} and {ibm-power-title} architectures.
142+
endif::openshift-rosa[]
143+
15144
[id="distr-tracing_3-3_{context}"]
16145
== Release notes for {DTProductName} 3.3
17146

‎observability/otel/otel-rn.adoc

+67
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,73 @@ You can use the {OTELName} xref:otel-forwarding-telemetry-data.adoc#otel-forward
1212

1313
include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-features-only.adoc[]
1414

15+
[id="otel_3-3-1_{context}"]
16+
== Release notes for {OTELName} 3.3.1
17+
18+
The {OTELName} is provided through the {OTELOperator}.
19+
20+
The {OTELName} 3.3.1 is based on the open source link:https://opentelemetry.io/docs/collector/[OpenTelemetry] release 0.107.0.
21+
22+
////
23+
[id="otel_3-3-1_cves_{context}"]
24+
=== CVEs
25+
26+
This release fixes the following CVEs:
27+
28+
* link:https://access.redhat.com/security/cve/CVE-2024-????[CVE-2024-????]
29+
////
30+
31+
////
32+
[id="otel_3-3-1_technology-preview-features_{context}"]
33+
=== Technology Preview features
34+
35+
This update introduces the following Technology Preview features:
36+
37+
* ???.
38+
39+
:FeatureName: Each of these features
40+
include::snippets/technology-preview.adoc[leveloffset=+1]
41+
////
42+
43+
////
44+
[id="otel_3-3-1_new-features-and-enhancements_{context}"]
45+
=== New features and enhancements
46+
47+
This update introduces the following enhancements:
48+
49+
* ???.
50+
////
51+
52+
////
53+
[id="otel_3-3-1_jaeger-release-notes_deprecated-functionality_{context}"]
54+
=== Deprecated functionality
55+
56+
In the {OTELName} 3.3.1, ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
57+
////
58+
59+
////
60+
[id="otel_3-3-1_removal-notice_{context}"]
61+
=== Removal notice
62+
63+
In the {OTELName} 3.3.1, the FEATURE has been removed. Bug fixes and support are provided only through the end of the 3.? lifecycle. As an alternative to the FEATURE for USE CASE, you can use the ALTERNATIVE instead.
64+
////
65+
66+
[id="otel_3-3-1_bug-fixes_{context}"]
67+
=== Bug fixes
68+
69+
This update introduces the following bug fix:
70+
71+
* Before this update, injection of Nginx auto-instrumentation failed on copying the instrumentation libraries into the application container. With this update, the copy command is configured correctly, which fixes the issue. (link:https://issues.redhat.com/browse/TRACING-4673[TRACING-4673])
72+
73+
////
74+
[id="otel_3-3-1_known-issues_{context}"]
75+
=== Known issues
76+
77+
There are currently known issues:
78+
79+
* ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
80+
////
81+
1582
[id="otel_3-3_{context}"]
1683
== Release notes for {OTELName} 3.3
1784

0 commit comments

Comments
 (0)