openshift · lhite8041 · Jun 11, 2026 · Jun 12, 2026
diff --git a/modules/ossm-about-istio-ambient-mode.adoc b/modules/ossm-about-istio-ambient-mode.adoc
@@ -36,7 +36,7 @@ The L7 features require deploying `waypoint` proxies, which introduces minimal a
 Ambient mode is a newer architecture and might involve different operational considerations than traditional sidecar models.
 ====
 
-While well-defined discovery selectors allow a service mesh deployed in ambient mode alongside a mesh in sidecar mode, this scenario has not been thoroughly validated. To avoid potential conflicts, install {istio} ambient mode only on clusters that do not have an existing {SMProductName} installation. Ambient mode remains a Technology Preview feature.
+While well-defined discovery selectors allow a service mesh deployed in ambient mode alongside a mesh in sidecar mode, this scenario has not been thoroughly validated. To avoid potential conflicts, install {istio} ambient mode only on clusters that do not have an existing {SMProductName} installation.
 
 [IMPORTANT]
 ====

diff --git a/modules/ossm-deploying-bookinfo-application-istio-ambient-mode.adoc b/modules/ossm-deploying-bookinfo-application-istio-ambient-mode.adoc
@@ -14,7 +14,7 @@ For more information about the `bookinfo` application, see "About the Bookinfo a
 
 .Prerequisites
 
-* You have deployed a cluster on {ocp-product-title} 4.15 or later, which includes the supported {k8s} Gateway API custom resource definitions (CRDs) required for {istio} ambient mode.
+* You have deployed a cluster on {ocp-product-title} 4.19 or later, which includes the supported {k8s} Gateway API custom resource definitions (CRDs) required for {istio} ambient mode.
 
 * You have logged in to the {ocp-product-title} cluster either through the web console as a user with the `cluster-admin` role, or with the `oc login` command, depending on the installation method.
 

diff --git a/modules/ossm-installing-multi-primary-multi-network-mesh-ambient.adoc b/modules/ossm-installing-multi-primary-multi-network-mesh-ambient.adoc
@@ -8,14 +8,9 @@
 
 [role="_abstract"]
 
-Install {istio} and configure it for ambient mode in the multi-primary multi-network topology on two {ocp-product-title} clusters.
+Install {istio} and configure it for ambient mode in the multi-primary multi-network topology on two {ocp-product-title} clusters. (For a mesh spanning more than two clusters, you can adapt these instructions.)
 
-[NOTE]
-====
-In this procedure, `CLUSTER1` is the East cluster and `CLUSTER2` is the West cluster.
-====
-
-You can adapt these instructions for a mesh spanning more than two clusters.
+include::snippets/technology-preview-ambient-multicluster.adoc[]
 
 .Prerequisites
 
@@ -59,7 +54,7 @@ In addition to bare metal, the MetalLB Operator can offer load balancing for ins
 $ export ISTIO_VERSION=1.27.3
 ----
 
-. Install {istio} on the East cluster:
+. Install {istio} on the East cluster (`CLUSTER1`):
 
 .. Create an `{istio}` resource on the East cluster by running the following command:
 +
@@ -152,7 +147,7 @@ EOF
 $ oc --context="${CTX_CLUSTER1}" wait gateway/istio-eastwestgateway -n istio-system --for=condition=Programmed=True --timeout=3m
 ----
 
-. Install {istio} on the West cluster:
+. Install {istio} on the West cluster (`CLUSTER2`):
 
 .. Create an `Istio` resource on the West cluster by running the following command:
 +

diff --git a/modules/ossm-verifying-multi-cluster-topology-ambient.adoc b/modules/ossm-verifying-multi-cluster-topology-ambient.adoc
@@ -10,10 +10,7 @@
 
 Deploy sample applications and verify traffic across two {ocp-product-title} clusters with {SMProductShortName} in ambient mode.
 
-[NOTE]
-====
-In this procedure, `CLUSTER1` is the East cluster and `CLUSTER2` is the West cluster.
-====
+include::snippets/technology-preview-ambient-multicluster.adoc[]
 
 .Prerequisites
 
@@ -33,7 +30,7 @@ In this procedure, `CLUSTER1` is the East cluster and `CLUSTER2` is the West clu
 
 .Procedure
 
-. Deploy sample applications on the East cluster:
+. Deploy sample applications on the East cluster (`CLUSTER1`):
 
 .. Create a sample application namespace on the East cluster by running the following command:
 +
@@ -98,7 +95,7 @@ $ oc --context="${CTX_CLUSTER1}" wait --for condition=available -n sample deploy
 $ oc --context="${CTX_CLUSTER1}" wait --for condition=available -n sample deployment/sleep
 ----
 
-. Deploy the sample applications on the West cluster:
+. Deploy the sample applications on the West cluster (`CLUSTER2`):
 
 .. Create a sample application namespace on the West cluster by running the following command:
 +

diff --git a/snippets/technology-preview-ambient-multicluster.adoc b/snippets/technology-preview-ambient-multicluster.adoc
@@ -0,0 +1,13 @@
+// snippet included in the following modules:
+//
+// * service-mesh-docs-main/modules/ossm-installing-multi-primary-multi-network-mesh-ambient.adoc
+// * service-mesh-docs-main/modules/ossm-verifying-multi-cluster-topology-ambient.adoc
+:_mod-docs-content-type: SNIPPET
+
+[IMPORTANT]
+====
+Ambient mode in a multi-primary multi-network topology is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
+
+For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
+====
+