You can use the {TempoName} in combination with the {OTELName}.
The {DTProductName} 3.3.1 is a maintenance release with no changes because the {DTProductName} is bundled with the {OTELName} that is released with a bug fix.
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
The {TempoName} is provided through the {TempoOperator}.
The {TempoName} 3.3.1 is based on the open source Grafana Tempo 2.5.0.
There is currently a known issue:
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
The {JaegerName} 3.3.1 is based on the open source Jaeger release 1.57.0.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
The {JaegerName} 3.3.1 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
In the {DTProductName} 3.3.1, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release. 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. The {TempoOperator} and the {OTELName} are the preferred Operators for distributed tracing collection and storage. Users must adopt the OpenTelemetry and Tempo distributed tracing stack because it is the stack to be enhanced going forward.
In the {DTProductName} 3.3.1, the Jaeger agent is deprecated and planned to be removed in the following release. 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. The OpenTelemetry Collector provided by the {OTELName} is the preferred Operator for injecting the trace collector agent.
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
The {TempoName} is provided through the {TempoOperator}.
The {TempoName} 3.3 is based on the open source Grafana Tempo 2.5.0.
This update introduces the following enhancements:
-
Support for securing the Jaeger UI and Jaeger APIs with the OpenShift OAuth Proxy. (TRACING-4108)
-
Support for using the service serving certificates, which are generated by {product-title}, on ingestion APIs when multitenancy is disabled. (TRACING-3954)
-
Support for ingesting by using the OTLP/HTTP protocol when multitenancy is enabled. (TRACING-4171)
-
Support for the AWS S3 Secure Token authentication. (TRACING-4176)
-
Support for automatically reloading certificates. (TRACING-4185)
-
Support for configuring the duration for which service names are available for querying. (TRACING-4214)
This update introduces the following bug fixes:
-
Before this update, storage certificate names did not support dots. With this update, storage certificate name can contain dots. (TRACING-4348)
-
Before this update, some users had to select a certificate when accessing the gateway route. With this update, there is no prompt to select a certificate. (TRACING-4431)
-
Before this update, the gateway component was not scalable. With this update, the gateway component is scalable. (TRACING-4497)
-
Before this update the Jaeger UI might fail with the 504 Gateway Time-out error when accessed via a route. With this update, users can specify route annotations for increasing timeout, such as
haproxy.router.openshift.io/timeout: 3m, when querying large data sets. (TRACING-4511)
There is currently a known issue:
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
The {JaegerName} 3.3 is based on the open source Jaeger release 1.57.0.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
The {JaegerName} 3.3 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
In the {DTProductName} 3.3, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release. 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. The {TempoOperator} and the {OTELName} are the preferred Operators for distributed tracing collection and storage. Users must adopt the OpenTelemetry and Tempo distributed tracing stack because it is the stack to be enhanced going forward.
In the {DTProductName} 3.3, the Jaeger agent is deprecated and planned to be removed in the following release. 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. The OpenTelemetry Collector provided by the {OTELName} is the preferred Operator for injecting the trace collector agent.
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
The {TempoName} is provided through the {TempoOperator}.
This update introduces the following bug fix:
-
Before this update, secrets were perpetually generated on {product-title} 4.16 because the operator tried to reconcile a new
openshift.io/internal-registry-pull-secret-refannotation for service accounts, causing a loop. With this update, the operator ignores this new annotation. (TRACING-4434)
There is currently a known issue:
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
This release fixes CVE-2024-25062.
The {TempoName} is provided through the {TempoOperator}.
There is currently a known issue:
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
The {TempoName} is provided through the {TempoOperator}.
This update introduces the following Technology Preview feature:
-
Support for the Tempo monolithic deployment.
This update introduces the following enhancements:
-
{TempoName} 3.2 is based on the open source Grafana Tempo 2.4.1.
-
Allowing the overriding of resources per component.
This update introduces the following bug fixes:
-
Before this update, the Jaeger UI only displayed services that sent traces in the previous 15 minutes. With this update, the availability of the service and operation names can be configured by using the following field:
spec.template.queryFrontend.jaegerQuery.servicesQueryDuration. (TRACING-3139) -
Before this update, the
query-frontendpod might get stopped when out-of-memory (OOM) as a result of searching a large trace. With this update, resource limits can be set to prevent this issue. (TRACING-4009)
There is currently a known issue:
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
In the {DTProductName} 3.2, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release. 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. The {TempoOperator} and the {OTELName} are the preferred Operators for distributed tracing collection and storage. Users must adopt the OpenTelemetry and Tempo distributed tracing stack because it is the stack to be enhanced going forward.
In the {DTProductName} 3.2, the Jaeger agent is deprecated and planned to be removed in the following release. 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. The OpenTelemetry Collector provided by the {OTELName} is the preferred Operator for injecting the trace collector agent.
This update introduces the following enhancements for the {JaegerShortName}:
-
{JaegerName} 3.2 is based on the open source Jaeger release 1.57.0.
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
This release fixes CVE-2023-39326.
The {TempoName} is provided through the {TempoOperator}.
There are currently 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. (TRACING-3139)
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
In the {DTProductName} 3.1.1, Jaeger and support for Elasticsearch remain 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 the {DTProductName} 3.1.1, Tempo provided by the {TempoOperator} and the OpenTelemetry Collector provided by the {OTELName} 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.
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
The {TempoName} is provided through the {TempoOperator}.
This update introduces the following enhancements for the {TempoShortName}:
-
{TempoName} 3.1 is based on the open source Grafana Tempo 2.3.1.
-
Support for cluster-wide proxy environments.
-
Support for TraceQL to Gateway component.
This update introduces the following bug fixes for the {TempoShortName}:
-
Before this update, when a TempoStack instance was created with the
monitorTabenabled in {product-title} 4.15, the requiredtempo-redmetrics-cluster-monitoring-viewClusterRoleBinding was not created. This update resolves the issue by fixing the Operator RBAC for the monitor tab when the Operator is deployed in an arbitrary namespace. (TRACING-3786) -
Before this update, when a TempoStack instance was created on an {product-title} cluster with only an IPv6 networking stack, the compactor and ingestor pods ran in the
CrashLoopBackOffstate, resulting in multiple errors. This update provides support for IPv6 clusters.(TRACING-3226)
There are currently 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. (TRACING-3139)
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
The {JaegerName} is provided through the {JaegerOperator} Operator.
|
Important
|
Jaeger does not use FIPS validated cryptographic modules. |
In the {DTProductName} 3.1, Jaeger and support for Elasticsearch remain 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 the {DTProductName} 3.1, Tempo provided by the {TempoOperator} and the OpenTelemetry Collector provided by the {OTELName} 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.
This update introduces the following enhancements for the {JaegerShortName}:
-
{JaegerName} 3.1 is based on the open source Jaeger release 1.53.0.
This update introduces the following bug fix for the {JaegerShortName}:
-
Before this update, the connection target URL for the
jaeger-agentcontainer in thejager-querypod was overwritten with another namespace URL in {product-title} 4.13. This was caused by a bug in the sidecar injection code in thejaeger-operator, causing nondeterministicjaeger-agentinjection. With this update, the Operator prioritizes the Jaeger instance from the same namespace as the target deployment. (TRACING-3722)
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.51.0 |
{TempoName} |
Tempo |
2.3.0 |
In the {DTProductName} 3.0, Jaeger and support for 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 the {DTProductName} 3.0, Tempo provided by the {TempoOperator} and the OpenTelemetry Collector provided by the {OTELName} 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.
This update introduces the following enhancements for the {JaegerShortName}:
-
Support for the ARM architecture.
-
Support for cluster-wide proxy environments.
This update introduces the following bug fix for the {JaegerShortName}:
-
Before this update, the {JaegerName} Operator used other images than
relatedImages. This caused the ImagePullBackOff error in disconnected network environments when launching thejaegerpod because theoc adm catalog mirrorcommand mirrors images specified inrelatedImages. This update provides support for disconnected environments when using theoc adm catalog mirrorCLI command. (TRACING-3546)
This update introduces the following enhancements for the {TempoShortName}:
-
Support for the ARM architecture.
-
Support for span request count, duration, and error count (RED) metrics. The metrics can be visualized in the Jaeger console deployed as part of Tempo or in the web console in the Observe menu.
This update introduces the following bug fixes for the {TempoShortName}:
-
Before this update, the
TempoStackCRD was not accepting custom CA certificate despite the option to choose CA certificates. This update fixes support for the custom TLS CA option for connecting to object storage. (TRACING-3462) -
Before this update, when mirroring the {DTProductName} Operator images to a mirror registry for use in a disconnected cluster, the related Operator images for
tempo,tempo-gateway,opa-openshift, andtempo-querywere not mirrored. This update fixes support for disconnected environments when using theoc adm catalog mirrorCLI command. (TRACING-3523) -
Before this update, the query frontend service of the {DTProductName} was using internal mTLS when gateway was not deployed. This caused endpoint failure errors. This update fixes mTLS when Gateway is not deployed. (TRACING-3510)
There are currently 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. (TRACING-3139)
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545)
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.47.0 |
{TempoName} |
Tempo |
2.1.1 |
This release fixes CVE-2023-46234.
There are currently known issues:
-
Currently, the custom TLS CA option is not implemented for connecting to object storage. (TRACING-3462)
-
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. (TRACING-3139)
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545) -
Currently, the Tempo query frontend service must not use internal mTLS when Gateway is not deployed. This issue does not affect the Jaeger Query API. The workaround is to disable mTLS. (TRACING-3510)
WorkaroundDisable mTLS as follows:
-
Open the {TempoOperator} ConfigMap for editing by running the following command:
$ oc edit configmap tempo-operator-manager-config -n openshift-tempo-operator (1)-
The project where the {TempoOperator} is installed.
-
-
Disable the mTLS in the Operator configuration by updating the YAML file:
data: controller_manager_config.yaml: | featureGates: httpEncryption: false grpcEncryption: false builtInCertManagement: enabled: false
-
Restart the {TempoOperator} pod by running the following command:
$ oc rollout restart deployment.apps/tempo-operator-controller -n openshift-tempo-operator
-
-
Missing images for running the {TempoOperator} in restricted environments. The {TempoName} CSV is missing references to the operand images. (TRACING-3523)
WorkaroundAdd the {TempoOperator} related images in the mirroring tool to mirror the images to the registry:
kind: ImageSetConfiguration apiVersion: mirror.openshift.io/v1alpha2 archiveSize: 20 storageConfig: local: path: /home/user/images mirror: operators: - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: tempo-product channels: - name: stable additionalImages: - name: registry.redhat.io/rhosdt/tempo-rhel8@sha256:e4295f837066efb05bcc5897f31eb2bdbd81684a8c59d6f9498dd3590c62c12a - name: registry.redhat.io/rhosdt/tempo-gateway-rhel8@sha256:b62f5cedfeb5907b638f14ca6aaeea50f41642980a8a6f87b7061e88d90fac23 - name: registry.redhat.io/rhosdt/tempo-gateway-opa-rhel8@sha256:8cd134deca47d6817b26566e272e6c3f75367653d589f5c90855c59b2fab01e9 - name: registry.redhat.io/rhosdt/tempo-query-rhel8@sha256:0da43034f440b8258a48a0697ba643b5643d48b615cdb882ac7f4f1f80aad08e
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.47.0 |
{TempoName} |
Tempo |
2.1.1 |
This release fixes CVE-2023-44487.
There are currently known issues:
-
Currently, the custom TLS CA option is not implemented for connecting to object storage. (TRACING-3462)
-
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. (TRACING-3139)
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545) -
Currently, the Tempo query frontend service must not use internal mTLS when Gateway is not deployed. This issue does not affect the Jaeger Query API. The workaround is to disable mTLS. (TRACING-3510)
WorkaroundDisable mTLS as follows:
-
Open the {TempoOperator} ConfigMap for editing by running the following command:
$ oc edit configmap tempo-operator-manager-config -n openshift-tempo-operator (1)-
The project where the {TempoOperator} is installed.
-
-
Disable the mTLS in the Operator configuration by updating the YAML file:
data: controller_manager_config.yaml: | featureGates: httpEncryption: false grpcEncryption: false builtInCertManagement: enabled: false
-
Restart the {TempoOperator} pod by running the following command:
$ oc rollout restart deployment.apps/tempo-operator-controller -n openshift-tempo-operator
-
-
Missing images for running the {TempoOperator} in restricted environments. The {TempoName} CSV is missing references to the operand images. (TRACING-3523)
WorkaroundAdd the {TempoOperator} related images in the mirroring tool to mirror the images to the registry:
kind: ImageSetConfiguration apiVersion: mirror.openshift.io/v1alpha2 archiveSize: 20 storageConfig: local: path: /home/user/images mirror: operators: - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: tempo-product channels: - name: stable additionalImages: - name: registry.redhat.io/rhosdt/tempo-rhel8@sha256:e4295f837066efb05bcc5897f31eb2bdbd81684a8c59d6f9498dd3590c62c12a - name: registry.redhat.io/rhosdt/tempo-gateway-rhel8@sha256:b62f5cedfeb5907b638f14ca6aaeea50f41642980a8a6f87b7061e88d90fac23 - name: registry.redhat.io/rhosdt/tempo-gateway-opa-rhel8@sha256:8cd134deca47d6817b26566e272e6c3f75367653d589f5c90855c59b2fab01e9 - name: registry.redhat.io/rhosdt/tempo-query-rhel8@sha256:0da43034f440b8258a48a0697ba643b5643d48b615cdb882ac7f4f1f80aad08e
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.47.0 |
{TempoName} |
Tempo |
2.1.1 |
-
Before this update, connection was refused due to a missing gRPC port on the
jaeger-querydeployment. This issue resulted intransport: Error while dialing: dial tcp :16685: connect: connection refusederror message. With this update, the Jaeger Query gRPC port (16685) is successfully exposed on the Jaeger Query service. (TRACING-3322) -
Before this update, the wrong port was exposed for
jaeger-production-query, resulting in refused connection. With this update, the issue is fixed by exposing the Jaeger Query gRPC port (16685) on the Jaeger Query deployment. (TRACING-2968) -
Before this update, when deploying {SMProductShortName} on {sno} clusters in disconnected environments, the Jaeger pod frequently went into the
Pendingstate. With this update, the issue is fixed. (TRACING-3312) -
Before this update, the Jaeger Operator pod restarted with the default memory value due to the
reason: OOMKillederror message. With this update, this issue is fixed by removing the resource limits. (TRACING-3173)
This release introduces the following enhancements for the {TempoShortName}:
-
Support the operator maturity Level IV, Deep Insights, which enables upgrading, monitoring, and alerting of the TempoStack instances and the {TempoOperator}.
-
Add Ingress and Route configuration for the Gateway.
-
Support the
managedandunmanagedstates in theTempoStackcustom resource. -
Expose the following additional ingestion protocols in the Distributor service: Jaeger Thrift binary, Jaeger Thrift compact, Jaeger gRPC, and Zipkin. When the Gateway is enabled, only the OpenTelemetry protocol (OTLP) gRPC is enabled.
-
Expose the Jaeger Query gRPC endpoint on the Query Frontend service.
-
Support multitenancy without Gateway authentication and authorization.
-
Before this update, the {TempoOperator} was not compatible with disconnected environments. With this update, the {TempoOperator} supports disconnected environments. (TRACING-3145)
-
Before this update, the {TempoOperator} with TLS failed to start on {product-title}. With this update, the mTLS communication is enabled between Tempo components, the Operand starts successfully, and the Jaeger UI is accessible. (TRACING-3091)
-
Before this update, the resource limits from the {TempoOperator} caused error messages such as
reason: OOMKilled. With this update, the resource limits for the {TempoOperator} are removed to avoid such errors. (TRACING-3204)
There are currently known issues:
-
Currently, the custom TLS CA option is not implemented for connecting to object storage. (TRACING-3462)
-
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. (TRACING-3139)
-
Currently, the {TempoShortName} fails on the {ibm-z-title} (
s390x) architecture. (TRACING-3545) -
Currently, the Tempo query frontend service must not use internal mTLS when Gateway is not deployed. This issue does not affect the Jaeger Query API. The workaround is to disable mTLS. (TRACING-3510)
WorkaroundDisable mTLS as follows:
-
Open the {TempoOperator} ConfigMap for editing by running the following command:
$ oc edit configmap tempo-operator-manager-config -n openshift-tempo-operator (1)-
The project where the {TempoOperator} is installed.
-
-
Disable the mTLS in the Operator configuration by updating the YAML file:
data: controller_manager_config.yaml: | featureGates: httpEncryption: false grpcEncryption: false builtInCertManagement: enabled: false
-
Restart the {TempoOperator} pod by running the following command:
$ oc rollout restart deployment.apps/tempo-operator-controller -n openshift-tempo-operator
-
-
Missing images for running the {TempoOperator} in restricted environments. The {TempoName} CSV is missing references to the operand images. (TRACING-3523)
WorkaroundAdd the {TempoOperator} related images in the mirroring tool to mirror the images to the registry:
kind: ImageSetConfiguration apiVersion: mirror.openshift.io/v1alpha2 archiveSize: 20 storageConfig: local: path: /home/user/images mirror: operators: - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: tempo-product channels: - name: stable additionalImages: - name: registry.redhat.io/rhosdt/tempo-rhel8@sha256:e4295f837066efb05bcc5897f31eb2bdbd81684a8c59d6f9498dd3590c62c12a - name: registry.redhat.io/rhosdt/tempo-gateway-rhel8@sha256:b62f5cedfeb5907b638f14ca6aaeea50f41642980a8a6f87b7061e88d90fac23 - name: registry.redhat.io/rhosdt/tempo-gateway-opa-rhel8@sha256:8cd134deca47d6817b26566e272e6c3f75367653d589f5c90855c59b2fab01e9 - name: registry.redhat.io/rhosdt/tempo-query-rhel8@sha256:0da43034f440b8258a48a0697ba643b5643d48b615cdb882ac7f4f1f80aad08e
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.42 |
{TempoName} |
Tempo |
0.1.0 |
This release introduces support for the {TempoName} as a Technology Preview feature for {DTProductName}.
The feature uses version 0.1.0 of the {TempoName} and version 2.0.1 of the upstream {TempoShortName} components.
You can use the {TempoShortName} to replace Jaeger so that you can use S3-compatible storage instead of ElasticSearch. Most users who use the {TempoShortName} instead of Jaeger will not notice any difference in functionality because the {TempoShortName} supports the same ingestion and query protocols as Jaeger and uses the same user interface.
If you enable this Technology Preview feature, note the following limitations of the current implementation:
-
The {TempoShortName} currently does not support disconnected installations. (TRACING-3145)
-
When you use the Jaeger user interface (UI) with the {TempoShortName}, the Jaeger UI lists only services that have sent traces within the last 15 minutes. For services that have not sent traces within the last 15 minutes, those traces are still stored even though they are not visible in the Jaeger UI. (TRACING-3139)
Expanded support for the {TempoOperator} is planned for future releases of the {DTProductName}. Possible additional features might include support for TLS authentication, multitenancy, and multiple clusters. For more information about the {TempoOperator}, see the Tempo community documentation.
This release introduces support for ingesting OpenTelemetry protocol (OTLP) to the {JaegerName} Operator. The Operator now automatically enables the OTLP ports:
-
Port 4317 for the OTLP gRPC protocol.
-
Port 4318 for the OTLP HTTP protocol.
This release also adds support for collecting Kubernetes resource attributes to the {OTELName} Operator.
This release adds support for auto-provisioning certificates using the {es-op}.
Self-provisioning by using the {JaegerName} Operator to call the {es-op} during installation.
+
|
Important
|
When upgrading to the {DTProductName} 2.4, the Operator recreates the Elasticsearch instance, which might take five to ten minutes. Distributed tracing will be down and unavailable for that period. |
Creating the Elasticsearch instance and certificates first and then configuring the {JaegerShortName} to use the certificate is a Technology Preview for this release.
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.30.2 |
Operator |
Component |
Version |
{JaegerName} |
Jaeger |
1.30.1 |
With this release, the {JaegerName} Operator is now installed to the openshift-distributed-tracing namespace by default. Before this update, the default installation had been in the openshift-operators namespace.
-
This release introduces a breaking change to how to configure certificates in the OpenTelemetry custom resource file. With this update, the
ca_filemoves undertlsin the custom resource, as shown in the following examples.CA file configuration for OpenTelemetry version 0.33spec: mode: deployment config: | exporters: jaeger: endpoint: jaeger-production-collector-headless.tracing-system.svc:14250 ca_file: "/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt"
CA file configuration for OpenTelemetry version 0.41.1spec: mode: deployment config: | exporters: jaeger: endpoint: jaeger-production-collector-headless.tracing-system.svc:14250 tls: ca_file: "/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt"
This release introduces the following new features and enhancements:
-
Rebrands Red Hat OpenShift Jaeger as the {DTProductName}.
-
Updates {JaegerName} Operator to Jaeger 1.28. Going forward, the {DTProductName} will only support the
stableOperator channel. Channels for individual releases are no longer supported. -
Adds support for OpenTelemetry protocol (OTLP) to the Query service.
-
Introduces a new distributed tracing icon that appears in the OperatorHub.
-
Includes rolling updates to the documentation to support the name change and new features.
This release adds the {OTELName} as a Technology Preview, which you install using the {OTELName} Operator. {OTELName} is based on the OpenTelemetry APIs and instrumentation. The {OTELName} includes the OpenTelemetry Operator and Collector. You can use the Collector to receive traces in the OpenTelemetry or Jaeger protocol and send the trace data to the {DTProductName}. Other capabilities of the Collector are not supported at this time. The OpenTelemetry Collector allows developers to instrument their code with vendor agnostic APIs, avoiding vendor lock-in and enabling a growing ecosystem of observability tooling.
This release addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.