OSSMDOC-3412: Service Mesh 2.3.2 z stream release notes

Rebasing after conflict resolution with v2.3.2 in common-attributes.

Author: gwynnemonahan

_attributes/common-attributes.adoc

@@ -133,7 +133,7 @@ endif::[]
 :product-dedicated: Red Hat OpenShift Dedicated
 :SMProductName: Red Hat OpenShift Service Mesh
 :SMProductShortName: Service Mesh
-:SMProductVersion: 2.3.1
+:SMProductVersion: 2.3.2
 :MaistraVersion: 2.3
 //Service Mesh v1
 :SMProductVersion1x: 1.1.18.2

modules/ossm-rn-fixed-issues.adoc

@@ -21,6 +21,18 @@ The following issues been resolved in the current release:
 
 * https://issues.redhat.com/browse/OSSM-3025[OSSM-3025] Istiod sometimes fails to become ready. Sometimes, when a mesh contained many member namespaces, the Istiod pod did not become ready due to a deadlock within Istiod. The deadlock is now resolved and the pod now starts as expected.
 
+* https://issues.redhat.com/browse/OSSM-2493[OSSM-2493] Default `nodeSelector` and `tolerations` in SMCP not passed to Kiali. The `nodeSelector` and `tolerations` you add to `SMCP.spec.runtime.defaults` are now passed to the Kiali resource.
+
+* https://issues.redhat.com/browse/OSSM-2492[OSSM-2492] Default tolerations in SMCP not passed to Jaeger. The `nodeSelector` and `tolerations` you add to `SMCP.spec.runtime.defaults` are now passed to the Jaeger resource.
+
+* https://issues.redhat.com/browse/OSSM-2374[OSSM-2374] If you deleted one of the `ServiceMeshMember` resources, then the Service Mesh operator deleted the `ServiceMeshMemberRoll`. While this is expected behavior when you delete the last `ServiceMeshMember`, the operator should not delete the `ServiceMeshMemberRoll` if it contains any members in addition to the one that was deleted. This issue is now fixed and the operator only deletes the ServiceMeshMemberRoll when the last `ServiceMeshMember` resource is deleted.
+
+* https://issues.redhat.com/browse/OSSM-2373[OSSM-2373] Error trying to get OAuth metadata when logging in. To fetch the cluster version, the `system:anonymous` account is used. With the cluster's default bundled ClusterRoles and ClusterRoleBinding, the anonymous account can fetch the version correctly. If the `system:anonymous` account loses its privileges to fetch the cluster version, OpenShift authentication becomes unusable.
++
+This is fixed by using the Kiali SA to fetch the cluster version. This also allows for improved security on the cluster.
+
+* https://issues.redhat.com/browse/OSSM-2371[OSSM-2371] Despite Kiali being configured as "view-only," a user can change the proxy logging level via the Workload details' Logs tab's kebab menu. This issue has been fixed so the options under "Set Proxy Log Level" are disabled when Kiali is configured as "view-only."
+
 * https://issues.redhat.com/browse/OSSM-2344[OSSM-2344] Restarting Istiod causes Kiali to flood CRI-O with port-forward requests. This issue occurred when Kiali could not connect to Istiod and Kiali simultaneously issued a large number of requests to istiod. Kiali now limits the number of requests it sends to istiod.
 
 * https://issues.redhat.com/browse/OSSM-2335[OSSM-2335] Dragging the mouse pointer over the Traces scatterchart plot sometimes caused the Kiali console to stop responding due to concurrent backend requests.

modules/ossm-rn-new-features.adoc

@@ -15,11 +15,33 @@ Module included in the following assemblies:
 
 This release adds improvements related to the following components and concepts.
 
+== New features {SMProductName} version 2.3.2
+
+This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on {product-title} 4.9 or later.
+
+=== Component versions included in {SMProductName} version 2.3.2
+
+|===
+|Component |Version
+
+|Istio
+|1.14.5
+
+|Envoy Proxy
+|1.22.7
+
+|Jaeger
+|1.39
+
+|Kiali
+|1.57.6
+|===
+
 == New features {SMProductName} version 2.3.1
 
 This release of {SMProductName} introduces new features, addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on {product-title} 4.9 or later.
 
-=== Component versions included in {SMProductName} version {SMProductVersion}
+=== Component versions included in {SMProductName} version 2.3.1
 
 |===
 |Component |Version
@@ -125,6 +147,28 @@ Additionally, the SMMR must also be configured for cluster-wide deployment. This
 ----
 <1> Adds all namespaces to the mesh, including any namespaces you subsequently create. The following namespaces are not part of the mesh: kube, openshift, kube-* and openshift-*.
 
+== New features {SMProductName} version 2.2.6
+
+This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on {product-title} 4.9 or later.
+
+=== Component versions included in {SMProductName} version 2.2.6
+
+|===
+|Component |Version
+
+|Istio
+|1.12.9
+
+|Envoy Proxy
+|1.20.8
+
+|Jaeger
+|1.39
+
+|Kiali
+|1.48.4
+|===
+
 == New features {SMProductName} version 2.2.5
 
 This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on {product-title} 4.9 or later.
@@ -355,7 +399,7 @@ This release of {SMProductName} addresses Common Vulnerabilities and Exposures (
 |1.36
 
 |Kiali
-|1.36.14
+|1.36.15
 |===
 
 == New features {SMProductName} 2.1.5.2