OSSMDOC-567: Document upgrade considerations for 2.2.

Author: JStickler

modules/ossm-upgrade-21-22-changes.adoc

@@ -0,0 +1,14 @@
+// Module included in the following assemblies:
+// * service_mesh/v2x/upgrading-ossm.adoc
+
+:_content-type: CONCEPT
+[id="ossm-upgrade-21-22-changes_{context}"]
+= Upgrade changes from version 2.1 to version 2.2
+
+Upgrading the control plane from version 2.1 to 2.2 introduces the following behavioral changes:
+
+* The `istio-node` DaemonSet is renamed to `istio-cni-node` to match the name in upstream Istio.
+
+* Istio 1.10 updated Envoy to send traffic to the application container using `eth0` rather than `lo` by default.
+
+* This release adds support for the `WasmPlugin` API and deprecates the `ServiceMeshExtention` API.

modules/ossm-upgrade-known-issues.adoc

@@ -0,0 +1,19 @@
+// Module included in the following assemblies:
+// * service_mesh/v2x/upgrading-ossm.adoc
+
+:_content-type: REFERENCE
+[id="ossm-upgrade-known-issues_{context}"]
+= Known issues that may affect upgrade
+
+Known issues that may affect your upgrade include:
+
+* {SMProductName} does not support the use of `EnvoyFilter` configuration except where explicitly documented. If you are using Envoy Filters, and the configuration generated by Istio has changed due to the new version of Envoy introduced by upgrading your `ServiceMeshControlPlane`, that has the potential to break any `EnvoyFilter` you may have implemented.
+
+* https://issues.redhat.com/browse/OSSM-1505[OSSM-1505] `ServiceMeshExtension` does not work with {product-title} version 4.11. Because `ServiceMeshExtension` has been deprecated in {SMProductName} 2.2, this known issue will not be fixed and you must migrate your extensions to `WasmPluging`
+
+* https://issues.redhat.com/browse/OSSM-1396[OSSM-1396] If a gateway resource contains the `spec.externalIPs` setting, rather than being recreated when the `ServiceMeshControlPlane` is updated, the gateway is removed and never recreated.
+
+//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.
++
+Workaround: Disable the gateway creation in the SMCP spec and manage the gateway deployment entirely manually (including Service, Role and RoleBinding).

service_mesh/v2x/upgrading-ossm.adoc

@@ -15,18 +15,28 @@ include::modules/ossm-understanding-versions.adoc[leveloffset=+1]
 
 include::modules/ossm-upgrade-considerations.adoc[leveloffset=+1]
 
+include::modules/ossm-upgrade-known-issues.adoc[leveloffset=+1]
+
 include::modules/ossm-upgrading-operator.adoc[leveloffset=+1]
 
 ifdef::openshift-enterprise[]
 For more information about upgrading Operators, refer to the xref:../../operators/admin/olm-upgrading-operators.adoc[Operator Lifecycle Manager] documentation.
 endif::[]
 
+[id="upgrading-control-plane"]
+== Upgrading the Service Mesh control plane
+
+include::modules/ossm-upgrade-21-22-changes.adoc[leveloffset=+2]
+
 include::modules/ossm-upgrading-from-21-to-22.adoc[leveloffset=+2]
 
 include::modules/ossm-upgrade-20-21-changes.adoc[leveloffset=+2]
 
 include::modules/ossm-upgrading-from-20-to-21.adoc[leveloffset=+2]
 
-include::modules/ossm-upgrade-apps-workloads.adoc[leveloffset=+1]
-
 include::modules/ossm-migrating-to-20.adoc[leveloffset=+1]
+
+[id="upgrading-data-plane"]
+== Upgrading the data plane
+
+include::modules/ossm-upgrade-apps-workloads.adoc[leveloffset=+1]