Merge pull request #48755 from rh-tokeefe/OSSMDOC-601

OSSMDOC-601: Document that ServiceMeshExtenson doesn't work

Author: JStickler

modules/ossm-rn-known-issues.adoc

@@ -34,10 +34,7 @@ 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.
+* 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.
 +
 Workaround: Use the `techPreview` `jwksResolverExtraRootCA` field to enable additional JWKS CA certificates.
 
@@ -46,6 +43,11 @@ Workaround: Use the `techPreview` `jwksResolverExtraRootCA` field to enable addi
 +
 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-1505[OSSM-1505] This issue only occurs when using the `ServiceMeshExtension` resource on OpenShift Container Platform 4.11. When you use `ServiceMeshExtension` on OpenShift Container Platform 4.11 the resource never becomes ready. If you inspect the issue using `oc describe ServiceMeshExtension` you will see the following error:  `stderr: Error creating mount namespace before pivot: function not implemented`.
++
+Workaround: `ServiceMeshExtension` was deprecated in {SMProductShortName} 2.2. Migrate from `ServiceMeshExtension` to the `WasmPlugin` resource.
+For more information, see Migrating from `ServiceMeshExtension` to `WasmPlugin` resources.
+
 * 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-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.