Merge pull request #95749 from max-cx/OBSDOCS-2062

OBSDOCS-2062: Release notes for DT&OTel 3.6.1 patch

Author: xenolinux

observability/distr_tracing/distr-tracing-rn.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-rn"]
-= Release notes for the {DTShortName}
+= Release notes for the {TempoName}
 :context: distr-tracing-rn
 
 toc::[]
@@ -12,6 +12,30 @@ You can use the {TempoName} xref:../../observability/otel/otel-forwarding-teleme
 
 include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-features-only.adoc[]
 
+[id="distr-tracing_3-6-1_{context}"]
+== Release notes for the {TempoName} 3.6.1
+
+The {TempoName} 3.6.1 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/tempo-operator-bundle/642c3e0eacf1b5bdbba7654a/history[{TempoOperator} 0.16.0].
+
+The {TempoName} 3.6.1 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.7.2.
+
+[id="distr-tracing_3-6-1_cves_{context}"]
+=== CVEs
+
+This release fixes the following CVEs:
+
+* link:https://access.redhat.com/security/cve/CVE-2025-4673[CVE-2025-4673]
+* link:https://access.redhat.com/security/cve/CVE-2025-6020[CVE-2025-6020]
+
+[id="distr-tracing_3-6-1_tempo-release-notes_known-issues_{context}"]
+=== Known issues
+
+The {TempoName} 3.6.1 has the following known issue:
+
+* Currently, when the `openshift` tenancy mode is enabled, the `ServiceAccount` object of the gateway component of either a `TempoStack` or `TempoMonolithic` instance requires the `TokenReview` and `SubjectAccessReview` permissions for authorization.
++
+Workaround: Deploy the instance in a dedicated namespace, and carefully audit which users have the permission to read the secrets in this namespace.
+
 [id="distr-tracing_3-6_{context}"]
 == Release notes for {DTShortName} 3.6
 
@@ -73,7 +97,7 @@ This update introduces the following bug fixes:
 
 The {TempoName} 3.6 has the following known issue:
 
-* Currently, when the OpenShift tenancy mode is enabled, the `ServiceAccount` object of the gateway component of either a `TempoStack` or `TempoMonolithic` instance requires the `TokenReview` and `SubjectAccessReview` permissions for authorization.
+* Currently, when the `openshift` tenancy mode is enabled, the `ServiceAccount` object of the gateway component of either a `TempoStack` or `TempoMonolithic` instance requires the `TokenReview` and `SubjectAccessReview` permissions for authorization.
 +
 Workaround: Deploy the instance in a dedicated namespace, and carefully audit which users have the permission to read the secrets in this namespace.
 

observability/otel/otel-rn.adoc

@@ -12,6 +12,37 @@ You can use the {OTELName} xref:../../observability/otel/otel-forwarding-telemet
 
 include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-features-only.adoc[]
 
+[id="otel_3-6-1_{context}"]
+== Release notes for {OTELName} 3.6.1
+
+The {OTELName} 3.6.1 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/opentelemetry-operator-bundle/615618406feffc5384e84400/history[{OTELOperator} 0.127.0].
+
+[NOTE]
+====
+The {OTELName} 3.6.1 is based on the open source link:https://opentelemetry.io/docs/collector/[OpenTelemetry] release 0.127.0.
+====
+
+[id="otel_3-6-1_cves_{context}"]
+=== CVEs
+
+This release fixes the following CVEs:
+
+* link:https://access.redhat.com/security/cve/CVE-2025-4673[CVE-2025-4673]
+* link:https://access.redhat.com/security/cve/CVE-2025-6020[CVE-2025-6020]
+
+[id="otel_3-6-1_known-issues_{context}"]
+=== Known issues
+
+There is currently a known issue with the following exporters:
+
+* AWS CloudWatch Logs Exporter
+* AWS EMF Exporter
+* AWS X-Ray Exporter
+
+This known issue affects deployments that use the optional `endpoint` field of the exporter configuration in the `OpenTelemetryCollector` custom resource. Not specifying the protocol, such as `https://`, as part of the endpoint value results in the `unsupported protocol scheme` error.
+
+Workaround: Include the protocol, such as `https://`, as part of the endpoint value.
+
 [id="otel_3-6_{context}"]
 == Release notes for {OTELName} 3.6
 
@@ -97,7 +128,7 @@ There is currently a known issue with the following exporters:
 * AWS EMF Exporter
 * AWS X-Ray Exporter
 
-This known issue affects deployments that use the optional `endpoint` field of the exporter configuration in the Collector custom resource. Not specifying the protocol, such as `https://`, as part of the endpoint value results in the `unsupported protocol scheme` error.
+This known issue affects deployments that use the optional `endpoint` field of the exporter configuration in the `OpenTelemetryCollector` custom resource. Not specifying the protocol, such as `https://`, as part of the endpoint value results in the `unsupported protocol scheme` error.
 
 Workaround: Include the protocol, such as `https://`, as part of the endpoint value.