Skip to content

Commit 5482c78

Browse files
committed
OBSDOCS-1596: Release notes for the Tempo 3.5.1 patch
1 parent c387e78 commit 5482c78

File tree

3 files changed

+48
-4
lines changed

3 files changed

+48
-4
lines changed

modules/distr-tracing-tempo-config-query-frontend.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ The query frontend component is responsible for sharding the search space for an
9696
|type: boolean
9797

9898
|`jaegerQuery.monitorTab.prometheusEndpoint`
99-
|The endpoint to the Prometheus instance that contains the span rate, error, and duration (RED) metrics. For example, `+https://thanos-querier.openshift-monitoring.svc.cluster.local:9091+`.
99+
|The endpoint to the Prometheus instance that contains the span rate, error, and duration (RED) metrics. For example, `+https://thanos-querier.openshift-monitoring.svc.cluster.local:9092+`.
100100
|type: string
101101

102102
|===

modules/distr-tracing-tempo-config-spanmetrics.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ spec:
9595
enabled: true
9696
monitorTab:
9797
enabled: true # <1>
98-
prometheusEndpoint: https://thanos-querier.openshift-monitoring.svc.cluster.local:9091 # <2>
98+
prometheusEndpoint: https://thanos-querier.openshift-monitoring.svc.cluster.local:9092 # <2>
9999
redMetricsNamespace: "" <3>
100100
ingress:
101101
type: route

observability/distr_tracing/distr-tracing-rn.adoc

+46-2
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,11 @@ include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-fea
1717

1818
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
1919

20+
[IMPORTANT]
21+
====
22+
The {TempoName} 3.5.1 patch release has been released.
23+
====
24+
2025
////
2126
[id="distr-tracing_3-5_cves_{context}"]
2227
=== CVEs
@@ -27,7 +32,7 @@ This release fixes the following CVEs:
2732
////
2833

2934
[id="distr-tracing_3-5_tempo-release-notes_{context}"]
30-
=== {TempoName}
35+
=== {TempoName} 3.5
3136

3237
The {TempoName} 3.5 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/tempo-operator-bundle/642c3e0eacf1b5bdbba7654a/history[{TempoOperator} 0.15.3].
3338

@@ -55,8 +60,47 @@ This update introduces the following bug fix:
5560

5661
* Before this update, the {TempoOperator} failed when the `TempoStack` custom resource had the `spec.storage.tls.enabled` field set to `true` and used an Amazon S3 object store with the Security Token Service (STS) authentication. With this update, such a `TempoStack` custom resource configuration does not cause the {TempoOperator} to fail.
5762

63+
[id="distr-tracing_3-5_tempo-release-notes_known-issues_{context}"]
64+
==== Known issues
65+
66+
There is currently a known issue:
67+
68+
* Currently, when the OpenShift tenancy mode is enabled, the ServiceAccount of the gateway component of a TempoStack or TempoMonolithic instance requires the TokenReview and SubjectAccessReview permissions for authorization.
69+
+
70+
Workaround: Deploy the instance in a dedicated namespace, and carefully audit which users have the permission to read the secrets in this namespace.
71+
72+
[id="distr-tracing_3-5-1_tempo-release-notes_{context}"]
73+
=== {TempoName} 3.5.1
74+
75+
The {TempoName} 3.5.1 is a patch release.
76+
77+
[id="distr-tracing_3-5-1_tempo-release-notes_cves_{context}"]
78+
==== CVEs
79+
80+
The {TempoName} 3.5.1 release fixes the following CVEs:
81+
82+
* link:https://access.redhat.com/security/cve/CVE-2025-2786[CVE-2025-2786]
83+
84+
* link:https://access.redhat.com/security/cve/CVE-2025-2842[CVE-2025-2842]
85+
86+
[id="distr-tracing_3-5-1_tempo-release-notes_breaking-changes_{context}"]
87+
==== Breaking changes
88+
89+
The {TempoName} 3.5.1 update introduces the following breaking change:
90+
91+
* With this update, for a user to create or modify a `TempoStack` or `TempoMonolithic` custom resource with enabled multi-tenancy, the user must have permissions to create a TokenReview and SubjectAccessReview.
92+
93+
[id="distr-tracing_3-5-1_tempo-release-notes_known-issues_{context}"]
94+
==== Known issues
95+
96+
There is currently a known issue:
97+
98+
* Currently, when the OpenShift tenancy mode is enabled, the ServiceAccount of the gateway component of a TempoStack or TempoMonolithic instance requires the TokenReview and SubjectAccessReview permissions for authorization.
99+
+
100+
Workaround: Deploy the instance in a dedicated namespace, and carefully audit which users have the permission to read the secrets in this namespace.
101+
58102
[id="distr-tracing_3-5_jaeger-release-notes_{context}"]
59-
=== {JaegerName}
103+
=== {JaegerName} 3.5
60104

61105
The {JaegerName} 3.5 is the last release of the {JaegerName} that Red Hat plans to support.
62106

0 commit comments

Comments
 (0)