BZ202918: Clarify the rebranding still includes Jaeger components. #39611
Conversation
JStickler
added
branch/enterprise-4.6
service-mesh
openshift-ci
bot
added
the
size/XS
|
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: 43583d0 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61af93544f7f4000077f5ee3 😎 Browse the preview: https://deploy-preview-39611--osdocs.netlify.app/openshift-enterprise/latest/jaeger/distributed-tracing-release-notes |
| * Introduces a new OpenTelemetry Operator based on OpenTelemetry 0.33. Note that this Operator is a Technology Preview. | ||
| * Updates {ProductShortName} Operator to Jaeger 1.28. Going forward, {ProductName} will only support the `stable` Operator channel. Channels for individual releases are no longer supported. | ||
|
|
||
| * Introduces a new OpenTelemetry Operator based on OpenTelemetry 0.33. Note that this Operator is a Technology Preview. |
There was a problem hiding this comment.
We shouldn't refer to this as the 'OpenTelemetry Operator', we should refer to this as the 'Red Hat OpenShift distributed tracing data collection' operator which is based on OpenTelemetry 0.33
| This release includes the following: | ||
|
|
||
| * Introduces a new OpenTelemetry Operator based on OpenTelemetry 0.33. Note that this Operator is a Technology Preview. | ||
| * Updates {ProductShortName} Operator to Jaeger 1.28. Going forward, {ProductName} will only support the `stable` Operator channel. Channels for individual releases are no longer supported. |
There was a problem hiding this comment.
We may want to make it more clear that its based on Jaeger 1.28 and not that it is Jaeger 1.28
| == New features and enhancements {ProductName} 2.0.0 | ||
|
|
||
| This release marks the rebranding of Red Hat OpenShift Jaeger to {ProductName}. This effort includes the following: | ||
| This release marks the rebranding of Red Hat OpenShift Jaeger to {ProductName}. This name change is to reflect that the distributed tracing solution encompasses more than just Jaeger project components, but also Elasticsearch, AMQ Streams, and OpenTelemetry. The rebranding also allows for new technologies and components to be added in the future under the distributed tracing name. |
There was a problem hiding this comment.
I don't know if I would mention Elasticsearch and AMQ stream here. Those are components which we can use with our distributed tracing solution, but they are their own separate components. Elasticsearch and AMQ streams are also not something new with this release or as part of our rebranding.
|
@JStickler: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
bot
added
the
needs-rebase
2 participants
Adding a sentence to the New Features topic that I hope addresses the confusion around whether Jaeger is still part of the distributed tracing solution.
BZ2029218
BZ2029221
Preview is here -> https://deploy-preview-39611--osdocs.netlify.app/openshift-enterprise/latest/jaeger/distributed-tracing-release-notes#distr-tracing-rn-new-features_distributed-tracing-release-notes