Merge pull request #47739 from rh-tokeefe/OSSMDOC-586

OSSMDOC-586: Service Mesh 2.2.1 Release Notes

Author: JStickler

_attributes/common-attributes.adoc

@@ -122,7 +122,7 @@ endif::[]
 :product-dedicated: Red Hat OpenShift Dedicated
 :SMProductName: Red Hat OpenShift Service Mesh
 :SMProductShortName: Service Mesh
-:SMProductVersion: 2.2
+:SMProductVersion: 2.2.1
 :MaistraVersion: 2.2
 //Service Mesh v1
 :SMProductVersion1x: 1.1.18.2

modules/ossm-rn-fixed-issues.adoc

@@ -19,6 +19,17 @@ The following issues been resolved in the current release:
 [id="ossm-rn-fixed-issues-ossm_{context}"]
 == {SMProductShortName} fixed issues
 
+* https://issues.redhat.com/browse/OSSM-1668[OSSM-1668]
+`jwksResolverCA` field is missing in `SMCP`.
+
+* https://issues.redhat.com/browse/OSSM-1325[OSSM-1325] istiod pod crashes and displays the following error message: `fatal error: concurrent map iteration and map write`.
+
+* https://issues.redhat.com/browse/OSSM-1211[OSSM-1211]
+Configuring Federated service meshes for failover does not work as expected.
++
+The Istiod pilot log displays the following error: `envoy connection [C289] TLS error: 337047686:SSL routines:tls_process_server_certificate:certificate verify failed`
++
+
 * https://issues.redhat.com/browse/OSSM-1099[OSSM-1099]
 The Kiali console displayed the message `Sorry, there was a problem. Try a refresh or navigate to a different page.`
 

modules/ossm-rn-known-issues.adoc

@@ -34,24 +34,13 @@ These are the known issues in {SMProductName}:
 
 * link:https://github.com/istio/istio/issues/14743[Istio-14743] Due to limitations in the version of Istio that this release of {SMProductName} is based on, there may be applications that are currently incompatible with {SMProductShortName}. See the linked community issue for details.
 
-* https://issues.redhat.com/browse/OSSM-1668[OSSM-1668]
-`jwksResolverCA` field is missing in `SMCP`.
-+
-If you upgrade from Service Mesh operator 2.1.3 to Service Mesh operator 2.2, then the `jwksResolverCA` field is not supported. You must use the `techPreview` `jwksResolverExtraRootCA` field to enable additional JWKS CA certificates.
 //Keep OSSM-1655 in RN, closed as "explained" error is expected.
 * https://issues.redhat.com/browse/OSSM-1655[OSSM-1655] Kiali dashboard shows error after enabling mTLS in `SMCP`.
 +
 After enabling the `spec.security.controlPlane.mtls` setting in the SMCP, the Kiali console displays the following error message `No subsets defined`.
 
 * https://issues.redhat.com/browse/OSSM-1396[OSSM-1396] If a gateway resource contains the `spec.externalIPs` setting, instead of being recreated when the `ServiceMeshControlPlane` is updated, the gateway is removed and never recreated.
 
-* https://issues.redhat.com/browse/OSSM-1211[OSSM-1211]
-Configuring Federated service meshes for failover does not work as expected.
-+
-The Istiod pilot log displays the following error: `envoy connection [C289] TLS error: 337047686:SSL routines:tls_process_server_certificate:certificate verify failed`
-+
-There is no workaround at this time.
-
 * https://issues.redhat.com/browse/OSSM-1168[OSSM-1168] When service mesh resources are created as a single YAML file, the Envoy proxy sidecar is not reliably injected into pods. When the SMCP, SMMR, and Deployment resources are created individually, the deployment works as expected.
 //Keep OSSM-1052 in RN - Closed as documented.
 * https://issues.redhat.com/browse/OSSM-1052[OSSM-1052] When configuring a Service `ExternalIP` for the ingressgateway in the service mesh control plane, the service is not created. The schema for the SMCP is missing the parameter for the service. The workaround for this issue is to disable the gateway creation in the SMCP spec and manage the gateway deployment entirely manually (including Service, Role and RoleBinding).

modules/ossm-rn-new-features.adoc

@@ -19,11 +19,33 @@ Module included in the following assemblies:
 * *Policy Enforcement* - Apply organizational policy to the interaction between services, ensure access policies are enforced and resources are fairly distributed among consumers. Policy changes are made by configuring the mesh, not by changing application code.
 * *Telemetry* - Gain understanding of the dependencies between services and the nature and flow of traffic between them, providing the ability to quickly identify issues.
 
+== New features {SMProductName} version {SMProductVersion}
+
+This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs), bug fixes, and is supported on OpenShift Container Platform 4.9 and 4.10.
+
+=== Component versions included in {SMProductName} version {SMProductVersion}
+
+|===
+|Component |Version
+
+|Istio
+|1.12.7
+
+|Envoy Proxy
+|1.20.6
+
+|Jaeger
+|1.34.1
+
+|Kiali
+|1.48.1
+|===
+
 == New features {SMProductName} 2.2
 
 This release of {SMProductName} adds new features and enhancements, and is supported on OpenShift Container Platform 4.9 and 4.10.
 
-=== Component versions included in {SMProductName} version {SMProductVersion}
+=== Component versions included in {SMProductName} version 2.2
 
 |===
 |Component |Version
@@ -87,6 +109,28 @@ spec:
 ----
 Restricting route attachment on Gateway API listeners is possible using the `SameNamespace` or `All` settings. Istio ignores usage of label selectors in `listeners.allowedRoutes.namespaces` and reverts to the default behavior (`SameNamespace`).
 
+== New features {SMProductName} 2.1.4
+
+This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
+
+=== Component versions included in {SMProductName} version 2.1.4
+
+|===
+|Component |Version
+
+|Istio
+|1.9.9
+
+|Envoy Proxy
+|1.17.1
+
+|Jaeger
+|1.29.1
+
+|Kiali
+|1.36.11
+|===
+
 == New features {SMProductName} 2.1.3
 
 This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
@@ -309,10 +353,10 @@ This release of {SMProductName} addresses Common Vulnerabilities and Exposures (
 |1.14.5
 
 |Jaeger
-|1.24.1
+|1.28.0
 
 |Kiali
-|1.24.14-1
+|1.24.15-1
 |===
 
 == New features {SMProductName} 2.0.9