[SRVCOM-3387] Integrations - add mention of supported OSSM version

Added a link to Supported Configurations

Improve phrasing for SRVCOM-3387

Peer Review feedback for SRVCOM-3387

Author: ochromy

integrations/serverless-ossm-setup.adoc

@@ -8,6 +8,13 @@ toc::[]
 
 The {ServerlessOperatorName} provides Kourier as the default ingress for Knative. However, you can use {SMProductShortName} with {ServerlessProductName} whether Kourier is enabled or not. Integrating with Kourier disabled allows you to configure additional networking and routing options that the Kourier ingress does not support, such as mTLS functionality.
 
+[IMPORTANT]
+====
+Integration of {SMProductName} 3 with {ServerlessProductName} is not supported.
+
+For a list of supported versions, see link:https://access.redhat.com/articles/4912821[Red Hat OpenShift Serverless Supported Configurations].
+====
+
 Note the following assumptions and limitations:
 
 * All Knative internal components, as well as Knative Services, are part of the {SMProductShortName} and have sidecars injection enabled. This means that strict mTLS is enforced within the whole mesh. All requests to Knative Services require an mTLS connection, with the client having to send its certificate, except calls coming from OpenShift Routing.