TRACING-3926 | Release notes for RHOSDT 3.1

_topic_maps/_topic_map.yml

@@ -2729,6 +2729,8 @@ Topics:
 - Name: Distributed tracing release notes
   Dir: distr_tracing_rn
   Topics:
+  - Name: Distributed tracing 3.1
+    File: distr-tracing-rn-3-1
   - Name: Distributed tracing 3.0
     File: distr-tracing-rn-3-0
   - Name: Distributed tracing 2.9.2

distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1.adoc

@@ -0,0 +1,94 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="distributed-tracing-rn-3-0"]
+= Release notes for {DTProductName} 3.1
+:context: distributed-tracing-rn-3-1
+
+toc::[]
+
+include::modules/distr-tracing-product-overview.adoc[leveloffset=+1]
+
+[id="component-versions_distributed-tracing-rn-3-1"]
+== Component versions in the {DTProductName} 3.1
+
+[options="header"]
+|===
+|Operator |Component |Version
+|{JaegerName}
+|Jaeger
+|1.53.0
+
+|xref:../../otel/otel-release-notes.adoc[{OTELName}]
+|OpenTelemetry
+|0.93.0
+
+|{TempoName}
+|Tempo
+|2.3.1
+|===
+
+// Jaeger section
+[id="jaeger-release-notes_distributed-tracing-rn-3-1"]
+== {JaegerName}
+
+[id="deprecated-functionality_jaeger-release-notes_distributed-tracing-rn-3-1"]
+=== Deprecated functionality
+
+In Red Hat OpenShift distributed tracing 3.1, Jaeger and Elasticsearch are deprecated, and both are planned to be removed in a future release. Red Hat will provide critical and above CVE bug fixes and support for these components during the current release lifecycle, but these components will no longer receive feature enhancements.
+
+In Red Hat OpenShift distributed tracing 3.1, Tempo provided by the {TempoOperator} and the OpenTelemetry collector provided by the Red Hat build of OpenTelemetry are the preferred Operators for distributed tracing collection and storage. The OpenTelemetry and Tempo distributed tracing stack is to be adopted by all users because this will be the stack that will be enhanced going forward.
+
+[id="new-features-and-enhancements_jaeger-release-notes_distributed-tracing-rn-3-1"]
+=== New features and enhancements
+
+This update introduces the following enhancements for the {JaegerShortName}:
+
+* Nothing
+
+[id="bug-fixes_jaeger-release-notes_distributed-tracing-rn-3-1"]
+=== Bug fixes
+
+This update introduces the following bug fixes for the {JaegerShortName}:
+
+* Fix nondeterministic jaeger-agent injection. Now the operator prefers Jaeger instance from the same namespace as the target deployment. (link:https://issues.redhat.com/browse/TRACING-3722[TRACING-3722])
+
+[id="known-issues_jaeger-release-notes_distributed-tracing-rn-3-1"]
+=== Known issues
+
+* Currently, Apache Spark is not supported.
+
+ifndef::openshift-rosa[]
+
+* Currently, the streaming deployment via AMQ/Kafka is not supported on the IBM Z and IBM Power Systems architectures.
+endif::openshift-rosa[]
+
+// Tempo section
+[id="tempo-release-notes_distributed-tracing-rn-3-1"]
+== {TempoName}
+
+[id="new-features-and-enhancements_tempo-release-notes_distributed-tracing-rn-3-1"]
+=== New features and enhancements
+
+This update introduces the following enhancements for the {TempoShortName}:
+
+* Added support for TraceQL to Gateway component.
+* Added monolithic custom resource in dev-preview support.
+* Support for cluster-wide proxy environments.
+
+[id="bug-fixes_tempo-release-notes_distributed-tracing-rn-3-1"]
+=== Bug fixes
+
+This update introduces the following bug fixes for the {TempoShortName}:
+
+* Fix operator RBAC for the monitor tab when the operator is deployed in arbitrary namespace. (link:https://issues.redhat.com/browse/TRACING-3786[TRACING-3786])
+* Fix support for IPv6 clusters.(link:https://issues.redhat.com/browse/TRACING-3226[TRACING-3226])
+
+[id="known-issues_tempo-release-notes_distributed-tracing-rn-3-1"]
+=== Known issues
+
+* Currently, when used with the {TempoOperator}, the Jaeger UI only displays services that have sent traces in the last 15 minutes. For services that did not send traces in the last 15 minutes, traces are still stored but not displayed in the Jaeger UI. (link:https://issues.redhat.com/browse/TRACING-3139[TRACING-3139])
+* Currently, the {TempoShortName} fails on the IBM Z (`s390x`) architecture. (link:https://issues.redhat.com/browse/TRACING-3545[TRACING-3545])
+
+include::modules/support.adoc[leveloffset=+1]
+
+include::modules/making-open-source-more-inclusive.adoc[leveloffset=+1]

otel/otel-release-notes.adoc

@@ -29,6 +29,33 @@ Data enrichment and processing:: Before forwarding data to analysis tools, the C
 
 Multi-backend receiving and exporting:: The Collector can receive and send data to multiple monitoring and analysis platforms simultaneously.
 
+[id="otel-3-1-rn"]
+== {OTELName} 3.1
+
+{OTELName} 3.1 is based on link:https://opentelemetry.io/[OpenTelemetry] 0.93.0.
+
+[id="new-features-and-enhancements_otel-3-1-rn"]
+=== New features and enhancements
+
+This update introduces the following enhancements:
+
+* Add support for target allocator in the OpenTelemetry collector. The target allocator is an optional component of the operator that shards Prometheus receiver scrape targets across deployed fleet of OpenTelemetry collector. The target allocator as well provides integration with Prometheus `PodMonitor` and `ServiceMonitor` custom resources.
+
+[id="removal-notice_otel-3-1-rn"]
+=== Removal notice
+
+* Nothing
+
+[id="bug-fixes_otel-3-1-rn"]
+=== Bug fixes
+
+* Nothing
+
+[id="known-issues_otel-3-1-rn"]
+=== Known issues
+
+* Nothing
+
 [id="otel-3-0-rn"]
 == {OTELName} {DTProductVersion}