Adopt Mitch's changes

Signed-off-by: Keith Mattix II <[email protected]>

Author: keithmattix

content/en/docs/ambient/install/multicluster/_index.md

@@ -32,19 +32,18 @@ the current state and limitations of this feature:
 
 ### Supported Configurations
 
-Currently, ambient multicluster **only supports**:
-- **Multi-network topologies** with multiple primary clusters
-- **Double HBONE encapsulation** for cross-cluster traffic
+Currently, ambient multicluster only supports:
+- **Multi-network topologies** with each cluster acting as a primary cluster.
 - **Universal waypoint deployments** across all clusters with identical names
 
 ### Critical Limitations
 
 #### Network Topology Restrictions
-- **Multi-cluster single-network configurations are untested, broken, and pre-experimental**
-  - Do not attempt to deploy ambient across clusters that share the same network
+- **Multi-cluster single-network configurations are untested, and may be broken**
+  - Use caution when deploying ambient across clusters that share the same network
   - Only multi-network configurations are supported
 
-#### Control Plane Limitations  
+#### Control Plane Limitations
 - **Primary remote configuration is not currently supported**
   - You can only have multiple primary clusters
   - Configurations with one or more remote clusters will not work correctly
@@ -58,7 +57,7 @@ Currently, ambient multicluster **only supports**:
 #### Service Visibility and Scoping
 - **Service scope configurations are not read from across clusters**
   - Only the local cluster's service scope configuration is used as the source of truth
-  - Remote cluster service scopes are ignored, which can lead to unexpected traffic behavior
+  - Remote cluster service scopes are not respected, which can lead to unexpected traffic behavior
   - Cross-cluster service discovery may not respect intended service boundaries
 
 #### Gateway Limitations

content/en/docs/ambient/install/multicluster/before-you-begin/index.md

@@ -75,11 +75,7 @@ below may have to be altered based on your choice of CA.
 
 ## Next steps
 
-You're now ready to install an Istio ambient mesh across multiple clusters. The
-particular steps will depend on your requirements for network and
-control plane topology.
-
-Choose the installation that best fits your needs:
+You're now ready to install an Istio ambient mesh across multiple clusters.
 
 - [Install Multi-Primary on Different Networks](/docs/ambient/install/multicluster/multi-primary_multi-network)
 

content/en/docs/ambient/install/multicluster/multi-primary_multi-network/index.md

@@ -10,7 +10,7 @@ owner: istio/wg-environments-maintainers
 {{< boilerplate alpha >}}
 
 Follow this guide to install the Istio control plane on both `cluster1` and
-`cluster2`, making each a {{< gloss >}}primary cluster{{< /gloss >}}. Cluster
+`cluster2`, making each a {{< gloss >}}primary cluster{{< /gloss >}} (this is currently the only supported configuration in ambient mode). Cluster
 `cluster1` is on the `network1` network, while `cluster2` is on the
 `network2` network. This means there is no direct connectivity between pods
 across cluster boundaries.
@@ -92,6 +92,18 @@ Then, install the `istiod` chart in `cluster1` with the following multi-cluster
 $ helm install istiod istio/istiod -n istio-system --kube-context "${CTX_CLUSTER1}" --set global.meshID=mesh1 --set global.multiCluster.clusterName=cluster1 --set global.network=network1 --set profile=ambient --set pilot.env.AMBIENT_ENABLE_MULTI_NETWORK="true"
 {{< /text >}}
 
+Next, install the CNI node agent in ambient mode:
+
+{{< text syntax=bash snip_id=install_cni >}}
+$ helm install istio-cni istio/cni -n istio-system --kube-context "${CTX_CLUSTER1}"--set profile=ambient
+{{< /text >}}
+
+Finally, install the ztunnel data plane:
+
+{{< text syntax=bash snip_id=install_ztunnel >}}
+$ helm install ztunnel istio/ztunnel -n istio-system --kube-context "${CTX_CLUSTER1}
+{{< /text >}}
+
 {{< /tab >}}
 
 {{< /tabset >}}
@@ -163,7 +175,7 @@ TODO: Handle revisions
 Apply the configuration to `cluster1`:
 
 {{< text bash >}}
-$ istioctl install --context="${CTX_CLUSTER1}" -f cluster1-ewgateway.yaml
+$ kubectl apply --context="${CTX_CLUSTER1}" -f cluster1-ewgateway.yaml
 {{< /text >}}
 
 {{< /tab >}}
@@ -180,7 +192,9 @@ istio-eastwestgateway   LoadBalancer   10.80.6.124   34.75.71.237   ...       51
 
 ## Expose services in `cluster1`
 
-TODO: change to explanation about service/namespace scope
+{{< text bash >}}
+$ kubectl --context="${CTX_CLUSTER1}" label svc helloworld -n sample istio.io/global="true"
+{{< /text >}}
 
 ## Set the default network for `cluster2`
 
@@ -243,6 +257,18 @@ Then, install the `istiod` chart in `cluster2` with the following multi-cluster
 $ helm install istiod istio/istiod -n istio-system --kube-context "${CTX_CLUSTER2}" --set global.meshID=mesh1 --set global.multiCluster.clusterName=cluster2 --set global.network=network2 --set profile=ambient --set pilot.env.AMBIENT_ENABLE_MULTI_NETWORK="true"
 {{< /text >}}
 
+Next, install the CNI node agent in ambient mode:
+
+{{< text syntax=bash snip_id=install_cni >}}
+$ helm install istio-cni istio/cni -n istio-system --kube-context "${CTX_CLUSTER2}"--set profile=ambient
+{{< /text >}}
+
+Finally, install the ztunnel data plane:
+
+{{< text syntax=bash snip_id=install_ztunnel >}}
+$ helm install ztunnel istio/ztunnel -n istio-system --kube-context "${CTX_CLUSTER2}
+{{< /text >}}
+
 {{< /tab >}}
 
 {{< /tabset >}}
@@ -297,7 +323,7 @@ TODO: Handle revisions
 Apply the configuration to `cluster2`:
 
 {{< text bash >}}
-$ istioctl install --context="${CTX_CLUSTER2}" -f cluster2-ewgateway.yaml
+$ kubectl apply --context="${CTX_CLUSTER2}" -f cluster2-ewgateway.yaml
 {{< /text >}}
 
 {{< /tab >}}
@@ -314,7 +340,9 @@ istio-eastwestgateway   LoadBalancer   10.0.12.121   34.122.91.98   ...       51
 
 ## Expose services in `cluster2`
 
-TODO: change to explanation about service/namespace scope
+{{< text bash >}}
+$ kubectl --context="${CTX_CLUSTER2}" label svc helloworld -n sample istio.io/global="true"
+{{< /text >}}
 
 ## Enable Endpoint Discovery