Resolve comments

Signed-off-by: nshankar <[email protected]>

Author: nshankar13

articles/aks/istio-about.md

@@ -46,20 +46,21 @@ This service mesh add-on uses and builds on top of open-source Istio. The add-on
 
 Istio-based service mesh add-on for AKS currently has the following limitations:
 * The add-on doesn't work on AKS clusters that are using [Open Service Mesh addon for AKS][open-service-mesh-about].
-* The add-on doesn't work on AKS clusters with Istio installed outside of the add-on installation.
+* The add-on doesn't work on AKS clusters with self-managed installations of Istio.
 * The add-on doesn't support adding pods associated with virtual nodes to be added under the mesh.
-* The add-on doesn't support egress gateways for outbound traffic control.
-* The add-on doesn't support the sidecar-less Ambient data plane mode.
-* The add-on doesn't support multi-cluster deployments.
+* The add-on doesn't yet support egress gateways for outbound traffic control.
+* The add-on doesn't yet support the sidecar-less Ambient mode. Microsoft is currently contributing to Ambient workstream under Istio open source. Ambient mode is on the roadmap and will product integration is being continuously evaluated as the Ambient workstream evolves.
+* The add-on doesn't yet support multi-cluster deployments.
 * Istio doesn't support Windows Server containers.
-* Customization of mesh through the following custom resources is blocked for now - `ProxyConfig, WorkloadEntry, WorkloadGroup, Telemetry, IstioOperator, WasmPlugin`. For `EnvoyFilter`, the add-on only supports customization of Lua filters (`type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua`) - other `EnvoyFilter` types are currently blocked.
+* Customization of mesh through the following custom resources is blocked for now - `ProxyConfig, WorkloadEntry, WorkloadGroup, Telemetry, IstioOperator, WasmPlugin`. 
+* For `EnvoyFilter`, the add-on only supports customization of Lua filters (`type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua`). Note that this EnvoyFilter is allowed but any issue arising from the Lua script itself is not supported (to learn more about our support policy and distinction between "allowed" and "supported" configurations, see [the following section][istio-meshconfig-support]). Other `EnvoyFilter` types are currently blocked. other `EnvoyFilter` types are currently blocked.
 * Gateway API for Istio ingress gateway or managing mesh traffic (GAMMA) are currently not yet supported with Istio addon. It's planned to allow customizations such as ingress static IP address configuration as part of the Gateway API implementation for the add-on in future.
 
 ## Next steps
 
-### Feedback and Feature Requests
+### Feedback and feature requests
 
-Feedback and feature requests for the Istio-based service mesh add-on should be raised as a new issue in the [AKS GitHub repository][aks-gh-issues]. Please open a new issue with the `mesh` label. 
+You can provide feedback or create feature requests for the add-on on [AKS GitHub repository][aks-gh-issues] by creating a new issue with the `mesh` label. 
 
 * [Deploy Istio-based service mesh add-on][istio-deploy-addon]
 * [Troubleshoot Istio-based service mesh add-on][istio-troubleshooting]
@@ -73,5 +74,6 @@ Feedback and feature requests for the Istio-based service mesh add-on should be
 [istio-ingress]: ./istio-deploy-ingress.md
 [istio-troubleshooting]: /troubleshoot/azure/azure-kubernetes/extensions/istio-add-on-general-troubleshooting
 [aks-gh-issues]: https://github.com/Azure/AKS/issues
+[istio-meshconfig-support]: ./istio-meshconfig.md#allowed-supported-and-blocked-values
 
 [istio-deploy-addon]: istio-deploy-addon.md

articles/aks/istio-deploy-addon.md

@@ -240,9 +240,9 @@ az group delete --name ${RESOURCE_GROUP} --yes --no-wait
 
 ## Next steps
 
-### Feedback and Feature Requests
+### Feedback and feature requests
 
-Feedback and feature requests for the Istio-based service mesh add-on should be raised as a new issue in the [AKS GitHub repository][aks-gh-issues]. Please open a new issue and add the `mesh` label. 
+You can provide feedback or create feature requests for the add-on on [AKS GitHub repository][aks-gh-issues] by creating a new issue with the `mesh` label. 
 
 * [Deploy external or internal ingresses for Istio service mesh add-on][istio-deploy-ingress]
 * [Scale istiod and ingress gateway HPA][istio-scaling-guide]

articles/aks/istio-deploy-ingress.md

@@ -17,7 +17,7 @@ This article shows you how to deploy external or internal ingresses for Istio se
 
 ## Prerequisites
 
-This guide assumes you followed the [documentation][istio-deploy-addon] to enable the Istio add-on on an AKS cluster, deploy sample applications, and set environment variables.
+This guide assumes you followed the [documentation][istio-deploy-addon] to enable the Istio add-on on an AKS cluster, deploy a sample application, and set environment variables.
 
 ## Enable external ingress gateway
 
@@ -41,7 +41,7 @@ aks-istio-ingressgateway-external   LoadBalancer   10.0.10.249   <EXTERNAL_IP>
 ```
 
 > [!NOTE]
-> Customizations to IP address on internal and external gateways aren't supported yet. IP address customizations on the ingress specifications are reverted back by the Istio add-on. It's planned to allow these customizations in the Gateway API implementation for the Istio add-on in future.
+> Customizations to IP address on internal and external gateways aren't supported yet. IP address customizations on the ingress specifications are reverted back by the Istio add-on.It's planned to allow these customizations in the Gateway API implementation for the Istio add-on in future.
 
 Applications aren't accessible from outside the cluster by default after enabling the ingress gateway. To make an application accessible, map the sample deployment's ingress to the Istio ingress gateway using the following manifest:
 
@@ -229,7 +229,7 @@ Confirm that the sample application's product page is accessible. The expected o
 If you want to clean up the Istio external or internal ingress gateways, but leave the mesh enabled on the cluster, run the following command:
 
 ```azure-cli-interactive
-az aks mesh disable-ingress-gateway --ingress-gateway-type <external/internal> --resource-group ${RESOURCE_GROUPS}
+az aks mesh disable-ingress-gateway --ingress-gateway-type <external/internal> --resource-group ${RESOURCE_GROUP}
 ```
 
 If you want to clean up the Istio service mesh and the ingresses (leaving behind the cluster), run the following command: