You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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].
33
+
34
+
[NOTE]
35
+
====
36
+
The {TempoName} 3.5 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.7.1.
This update introduces the following enhancements:
43
+
44
+
* With this update, you can configure the Tempo backend services to report the internal tracing data by using the OpenTelemetry Protocol (OTLP).
45
+
* With this update, the `traces.span.metrics` namespace becomes the default metrics namespace on which the Jaeger query retrieves the Prometheus metrics. The purpose of this change is to provide compatibility with the OpenTelemetry Collector version 0.109.0 and later where this namespace is the default. Customers who are still using an earlier OpenTelemetry Collector version can configure this namespace by adding the following field and value: `spec.template.queryFrontend.jaegerQuery.monitorTab.redMetricsNamespace: ""`.
* Before this update, the `oauth-proxy` container did not have any compute resources assigned to it. With this update, the container correctly sets the resources as specified in the `TempoStack` custom resource.
54
+
////
55
+
56
+
* 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.
The {JaegerName} 3.5 is the last release of the {JaegerName} that Red Hat plans to support.
62
+
63
+
In the {DTProductName} 3.5, Jaeger and support for Elasticsearch remain deprecated.
64
+
65
+
[WARNING]
66
+
====
67
+
Support for the {JaegerName} ends on November 3, 2025.
68
+
69
+
The {JaegerOperator} Operator (Jaeger) will be removed from the `redhat-operators` catalog on November 3, 2025.
70
+
====
71
+
72
+
You must migrate to the {OTELName} Operator and the {TempoOperator} for distributed tracing collection and storage. For more information, see the following resources:
* link:https://access.redhat.com/solutions/7083722[Jaeger Deprecation and Removal in OpenShift] (Red Hat Knowledgebase solution)
81
+
82
+
[NOTE]
83
+
====
84
+
The {JaegerName} 3.5 is based on the open source link:https://www.jaegertracing.io/[Jaeger] release 1.65.0.
85
+
====
86
+
// 1.62.0 was fixed until Jaeger's removal
87
+
88
+
The {JaegerName} 3.5 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/jaeger-operator-bundle/613b50f3a052bb39f2c5f31e/history[{JaegerOperator} Operator 1.65.0].
89
+
90
+
[IMPORTANT]
91
+
====
92
+
Jaeger does not use FIPS validated cryptographic modules.
The {JaegerName} Operator uses a custom resource definition (CRD) file that defines the architecture and configuration settings to be used when creating and deploying the {JaegerShortName} resources. You can install the default configuration or modify the file.
Operator Lifecycle Manager (OLM) controls the installation, upgrade, and role-based access control (RBAC) of Operators in a cluster. The OLM runs by default in {product-title}.
Copy file name to clipboardExpand all lines: observability/otel/otel-collector/otel-collector-receivers.adoc
-6Lines changed: 0 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -106,9 +106,6 @@ The Jaeger Receiver ingests traces in the Jaeger formats.
106
106
107
107
The Host Metrics Receiver ingests metrics in the OTLP format.
108
108
109
-
:FeatureName: The Host Metrics Receiver
110
-
include::snippets/technology-preview.adoc[]
111
-
112
109
.OpenTelemetry Collector custom resource with an enabled Host Metrics Receiver
113
110
[source,yaml]
114
111
----
@@ -290,9 +287,6 @@ spec:
290
287
291
288
The Kubelet Stats Receiver extracts metrics related to nodes, pods, containers, and volumes from the kubelet's API server. These metrics are then channeled through the metrics-processing pipeline for additional analysis.
292
289
293
-
:FeatureName: The Kubelet Stats Receiver
294
-
include::snippets/technology-preview.adoc[]
295
-
296
290
.OpenTelemetry Collector custom resource with an enabled Kubelet Stats Receiver
If you are already using the {JaegerName} for your applications, you can migrate to the {OTELName}, which is based on the link:https://opentelemetry.io/[OpenTelemetry] open-source project.
The {OTELName} 3.5 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/opentelemetry-operator-bundle/615618406feffc5384e84400/history[{OTELOperator} 0.119.0].
19
+
20
+
[NOTE]
21
+
====
22
+
The {OTELName} 3.5 is based on the open source link:https://opentelemetry.io/docs/collector/[OpenTelemetry] release 0.119.0.
This update introduces the following enhancements:
43
+
44
+
* The following link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] features reach General Availability:
45
+
** Host Metrics Receiver
46
+
** Kubelet Stats Receiver
47
+
* With this update, the OpenTelemetry Collector uses the OTLP HTTP Exporter to push logs to a LokiStack instance.
48
+
* With this update, the Operator automatically creates RBAC rules for the Kubernetes Events Receiver (`k8sevents`), Kubernetes Cluster Receiver (`k8scluster`), and Kubernetes Objects Receiver (`k8sobjects`) if the Operator has sufficient permissions. For more information, see "Creating the required RBAC resources automatically" in _Configuring the Collector_.
In the {OTELName} 3.5, the Loki Exporter, which is a temporary Technology Preview feature, is deprecated. The Loki Exporter is planned to be removed in the {OTELName} 3.6. If you currently use the Loki Exporter for the OpenShift Logging 6.1 or later, replace the Loki Exporter with the OTLP HTTP Exporter.
In the {OTELName} 3.5, ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
60
+
////
61
+
62
+
////
63
+
[id="otel_3-5_removal-notice_{context}"]
64
+
=== Removal notice
65
+
66
+
In the {OTELName} 3.5, 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.
67
+
////
68
+
69
+
[id="otel_3-5_bug-fixes_{context}"]
70
+
=== Bug fixes
71
+
72
+
This update introduces the following bug fix:
73
+
74
+
* Before this update, manually created routes for the Collector services were unintentionally removed when the Operator pod was restarted. With this update, restarting the Operator pod does not result in the removal of the manually created routes.
In the {OTELName} 3.3.1, ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
@@ -158,7 +228,7 @@ This update introduces the following enhancements:
158
228
* Support for automatically reloading certificates in both the OpenTelemetry Collector and instrumentation. (link:https://issues.redhat.com/browse/TRACING-4186[TRACING-4186])
In {OTELName} 3.2, use of empty values and `null` keywords in the OpenTelemetry Collector custom resource is deprecated and planned to be unsupported in a future release. Red Hat will provide bug fixes and support for this syntax during the current release lifecycle, but this syntax will become unsupported. As an alternative to empty values and `null` keywords, you can update the OpenTelemetry Collector custom resource to contain empty JSON objects as open-closed braces `{}` instead.
Copy file name to clipboardExpand all lines: snippets/distr-tracing-assembly-tip-for-jaeger-replacements.adoc
+7-9Lines changed: 7 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -14,18 +14,16 @@
14
14
15
15
:_mod-docs-content-type: SNIPPET
16
16
17
-
[IMPORTANT]
17
+
[WARNING]
18
18
====
19
19
[subs="attributes+"]
20
-
{FeatureName} is a deprecated feature. Deprecated functionality is still included in {product-title} and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments.
20
+
The {JaegerName} 3.5 is the last release of the {JaegerName} that Red Hat plans to support.
21
21
22
-
The {JaegerOperator} Operator (Jaeger) will be removed from the `redhat-operators` catalog in a future release. For more information, see the Red Hat Knowledgebase solution link:https://access.redhat.com/solutions/7083722[Jaeger Deprecation and Removal in OpenShift].
22
+
In the {DTProductName} 3.5, Jaeger and support for Elasticsearch remain deprecated.
23
23
24
-
You must migrate to the {OTELName} Operator and the {TempoOperator} for distributed tracing collection and storage. For more information, see "Migrating" in the {OTELShortName} documentation, "Installing" in the {OTELName} documentation, and "Installing" in the {TempoShortName} documentation.
24
+
Support for the {JaegerName} ends on November 3, 2025.
25
+
26
+
The {JaegerOperator} Operator (Jaeger) will be removed from the `redhat-operators` catalog on November 3, 2025. For more information, see the Red Hat Knowledgebase solution link:https://access.redhat.com/solutions/7083722[Jaeger Deprecation and Removal in OpenShift].
25
27
26
-
ifndef::openshift-rosa,openshift-dedicated[]
27
-
For the most recent list of major functionality that has been deprecated or removed within {product-title}, refer to the _Deprecated and removed features_ section of the {product-title} release notes.
28
-
endif::openshift-rosa,openshift-dedicated[]
28
+
You must migrate to the {OTELName} Operator and the {TempoOperator} for distributed tracing collection and storage. For more information, see "Migrating" in the {OTELShortName} documentation, "Installing" in the {OTELName} documentation, and "Installing" in the {TempoShortName} documentation.
29
29
====
30
-
// Undefine {FeatureName} attribute, so that any mistakes are easily spotted
0 commit comments