Merge pull request #35210 from JStickler/OSSMDOC-374

OSSMDOC-374: Jaeger 1.24.0 Release Notes.

Author: jeana-redhat

jaeger/jaeger_install/rhbjaeger-updating.adoc

@@ -9,4 +9,6 @@ The Operator Lifecycle Manager (OLM) controls the installation, upgrade, and rol
 The OLM queries for available Operators as well as upgrades for installed Operators.
 For more information about how {product-title} handled upgrades, refer to the xref:../../operators/understanding/olm/olm-understanding-olm.adoc#olm-understanding-olm[Operator Lifecycle Manager] documentation.
 
-The update approach used by the Jaeger Operator upgrades the managed Jaeger instances to the version associated with the Operator. Whenever a new version of the Jaeger Operator is installed, all the Jaeger application instances managed by the Operator will be upgraded to the Operator's  version.  For example, if version 1.10 is installed (both Operator and backend components) and the Operator is upgraded to version 1.11, then as soon as the Operator upgrade has completed, the Operator will scan for running Jaeger instances and upgrade them to 1.11 as well.
+The update approach used by the Jaeger Operator upgrades the managed Jaeger instances to the version associated with the Operator. Whenever a new version of the Jaeger Operator is installed, all the Jaeger application instances managed by the Operator will be upgraded to the Operator's version. For example, if version 1.10 is installed (both Operator and backend components) and the Operator is upgraded to version 1.11, then as soon as the Operator upgrade has completed, the Operator will scan for running Jaeger instances and upgrade them to 1.11 as well.
+
+For specific instructions for how to update the OpenShift Elasticsearch Operator, refer to xref:../../logging/cluster-logging-upgrading.adoc#cluster-logging-upgrading_cluster-logging-upgrading[Updating OpenShift Logging].

modules/jaeger-document-attributes.adoc

@@ -12,7 +12,7 @@
 :ProductName: OpenShift Jaeger
 :ProductShortName: Jaeger
 :ProductRelease:
-:ProductVersion: 1.20.4
+:ProductVersion: 1.24.0
 :product-build:
 :DownloadURL: registry.redhat.io
 :cloud-redhat-com: Red Hat OpenShift Cluster Manager
@@ -25,7 +25,7 @@
 
 :DocInfoProductName: Red Hat OpenShift Jaeger
 :DocInfoProductName: OpenShift Jaeger
-:DocInfoProductNumber: 1.20.4
+:DocInfoProductNumber: 1.24.0
 //
 // Book Names:
 // Defining the book names in document attributes instead of hard-coding them in

modules/jaeger-install-elasticsearch.adoc

@@ -44,12 +44,7 @@ If you have already installed the OpenShift Elasticsearch Operator as part of Op
 The Elasticsearch installation requires the *openshift-operators-redhat* namespace for the OpenShift Elasticsearch Operator. The other {ProductName} operators are installed in the `openshift-operators` namespace.
 ====
 +
-. Select the *Update Channel* that matches your {product-title} installation. For example, if you are installing on {product-title} version 4.8, select the 4.8 update channel.
-+
-[NOTE]
-====
-For {product-title} version 4.7 select the 4.6 update channel.
-====
+. Select *stable-5.x* as the *Update Channel*.
 
 . Select the *Automatic* Approval Strategy.
 +

modules/jaeger-rn-fixed-issues.adoc

@@ -15,6 +15,10 @@ Fix - What did we change to fix the problem?
 Result - How has the behavior changed as a result?  Try to avoid “It is fixed” or “The issue is resolved” or “The error no longer presents”.
 ////
 
+* link:https://issues.redhat.com/browse/TRACING-2009[TRACING-2009] The Jaeger Operator has been updated to include support for the Strimzi Kafka Operator 0.23.0.
+
+* link:https://issues.redhat.com/browse/TRACING-1907[TRACING-1907] The Jaeger agent sidecar injection was failing due to missing config maps in the application namespace. The config maps were getting automatically deleted due to an incorrect `OwnerReference` field setting and as a result, the application pods were not moving past the "ContainerCreating" stage. The incorrect settings have been removed.
+
 * link:https://issues.redhat.com/browse/TRACING-1725[TRACING-1725] Follow-up to TRACING-1631. Additional fix to ensure that Elasticsearch certificates are properly reconciled when there are multiple Jaeger production instances, using same name but within different namespaces. See also link:https://bugzilla.redhat.com/show_bug.cgi?id=1918920[BZ-1918920].
 
 * link:https://issues.jboss.org/browse/TRACING-1631[TRACING-1631] Multiple Jaeger production instances, using same name but within different namespaces, causing Elasticsearch certificate issue. When multiple service meshes were installed, all of the Jaeger Elasticsearch instances had the same Elasticsearch secret instead of individual secrets, which prevented the OpenShift Elasticsearch Operator from communicating with all of the Elasticsearch clusters.

modules/jaeger-rn-known-issues.adoc

@@ -9,9 +9,9 @@ Module included in the following assemblies:
 = Jaeger known issues
 
 ////
-Consequence - What user action or situation would make this problem appear (Selecting the Foo option with the Bar version 1.3 plugin enabled results in an error message)?  What did the customer experience as a result of the issue? What was the symptom?
+Consequence - What user action or situation would make this problem appear (Selecting the Foo option with the Bar version 1.3 plugin enabled results in an error message)? What did the customer experience as a result of the issue? What was the symptom?
 Cause (if it has been identified) - Why did this happen?
-Workaround (If there is one)- What can you do to avoid or negate the effects of this issue in the meantime?  Sometimes if there is no workaround it is worthwhile telling readers to contact support for advice.  Never promise future fixes.
+Workaround (If there is one)- What can you do to avoid or negate the effects of this issue in the meantime? Sometimes if there is no workaround it is worthwhile telling readers to contact support for advice. Never promise future fixes.
 Result - If the workaround does not completely address the problem.
 ////
 
@@ -23,6 +23,13 @@ These limitations exist in Jaeger:
 
 These are the known issues in Jaeger:
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1918920[BZ-1918920] The Elasticsearch pods does not get restarted automatically after an update.  As a workaround, restart the pods manually.
+* link:https://issues.redhat.com/browse/TRACING-2057[TRACING-2057] The Kafka API has been updated to `v1beta2` to support the Strimzi Kafka Operator 0.23.0.  However, this API version is not supported by AMQ Streams 1.6.3. If you have the following environment, your Jaeger services will not be upgraded, and you cannot create new Jaeger services or modify existing Jaeger services:
 
-* link:https://issues.redhat.com/browse/TRACING-809[TRACING-809] Jaeger Ingester is incompatible with Kafka 2.3. When there are two or more instances of the Jaeger Ingester and enough traffic it will continuously generate rebalancing messages in the logs.  This is due to a regression in Kafka 2.3 that was fixed in Kafka 2.3.1.  For more information, see https://github.com/jaegertracing/jaeger/issues/1819[Jaegertracing-1819].
+** Jaeger Operator channel: *1.17.x stable* or *1.20.x stable*
+** AMQ Streams Operator channel: *amq-streams-1.6.x*
++
+To resolve this issue, switch the subscription channel for your AMQ Streams Operator to either *amq-streams-1.7.x* or *stable*.
+
+* link:https://bugzilla.redhat.com/show_bug.cgi?id=1918920[BZ-1918920] The Elasticsearch pods does not get restarted automatically after an update. As a workaround, restart the pods manually.
+
+* link:https://issues.redhat.com/browse/TRACING-809[TRACING-809] Jaeger Ingester is incompatible with Kafka 2.3. When there are two or more instances of the Jaeger Ingester and enough traffic it will continuously generate rebalancing messages in the logs. This is due to a regression in Kafka 2.3 that was fixed in Kafka 2.3.1. For more information, see https://github.com/jaegertracing/jaeger/issues/1819[Jaegertracing-1819].

modules/jaeger-rn-new-features.adoc

@@ -3,12 +3,26 @@ Module included in the following assemblies:
 - rhbjaeger-release-notes.adoc
 ////
 ////
-Feature – Describe the new functionality available to the customer.  For enhancements, try to describe as specifically as possible where the customer will see changes.
-Reason – If known, include why has the enhancement been implemented (use case, performance, technology, etc.).   For example, showcases integration of X with Y, demonstrates Z API feature, includes latest framework bug fixes.
+Feature – Describe the new functionality available to the customer. For enhancements, try to describe as specifically as possible where the customer will see changes.
+Reason – If known, include why has the enhancement been implemented (use case, performance, technology, etc.). For example, showcases integration of X with Y, demonstrates Z API feature, includes latest framework bug fixes.
 Result – If changed, describe the current user experience.
 ////
 
 [id="jaeger-rn-new-features_{context}"]
+== New features {ProductName} 1.24.0
+
+This release of {ProductName} includes the following new features:
+
+* Adds support for the Red Hat Elasticsearch Operator 5.0 and 5.1.
+
+* Adds Elasticsearch rollover support.
+
+* Adds Elasticsearch tolerations support.
+
+* Updates the Jaeger Operator to include support for the Strimzi Kafka Operator 0.23.0. A known issue and workaround associated with this update is documented in the "Known Issues" section.
+
+* This release also addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
+
 == New features {ProductName} 1.20.4
 This release of {ProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
 

modules/ossm-install-ossm-operator.adoc

@@ -24,7 +24,7 @@ To install {ProductName}, install following Operators in this order. Repeat the
 . Click *Install*.
 
 . On the *Install Operator* page, select installation options.
-.. For the OpenShift Elasticsearch Operator, in the *Update Channel* section, select *4.6*.
+.. For the OpenShift Elasticsearch Operator, in the *Update Channel* section, select *stable-5.x*.
 .. For the Jaeger, Kiali, and {ProductName} Operators, accept the defaults.
 +
 The Jaeger, Kiali and {ProductName} are installed in the `openshift-operators` namespace. The OpenShift Elasticsearch Operator is installed in the `openshift-operators-redhat` namespace.