Skip to content

Commit 4a41100

Browse files
committed
Acrolinx
Signed-off-by: nshankar <[email protected]>
1 parent 8f39f9f commit 4a41100

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

articles/aks/istio-about.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ Service-to-service communication is what makes a distributed application possibl
2424

2525
Istio is an open-source service mesh that layers transparently onto existing distributed applications. Istio’s powerful features provide a uniform and more efficient way to secure, connect, and monitor services. Istio enables load balancing, service-to-service authentication, and monitoring – with few or no service code changes. Its powerful control plane brings vital features, including:
2626

27-
* Secure service-to-service communication in a cluster with TLS encryption, strong identity-based authentication and authorization.
27+
* Secure service-to-service communication in a cluster with TLS (Transport Layer Security) encryption, strong identity-based authentication and authorization.
2828
* Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic.
2929
* Fine-grained control of traffic behavior with rich routing rules, retries, failovers, and fault injection.
30-
* A pluggable policy layer and configuration API supporting access controls, rate limits and quotas.
30+
* A pluggable policy layer and configuration API supporting access controls, rate limits, and quotas.
3131
* Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress.
3232

3333
## How is the add-on different from open-source Istio?
@@ -46,20 +46,20 @@ This service mesh add-on uses and builds on top of open-source Istio. The add-on
4646

4747
Istio-based service mesh add-on for AKS currently has the following limitations:
4848
* The add-on doesn't work on AKS clusters that are using [Open Service Mesh addon for AKS][open-service-mesh-about].
49-
* The add-on doesn't work on AKS clusters that have Istio installed on them already outside the add-on installation.
49+
* The add-on doesn't work on AKS clusters with Istio installed outside of the add-on installation.
5050
* The add-on doesn't support adding pods associated with virtual nodes to be added under the mesh.
5151
* The add-on doesn't support egress gateways for outbound traffic control.
52-
* The add-on doesn't support the sidecar-less Ambient dataplane mode.
52+
* The add-on doesn't support the sidecar-less Ambient data plane mode.
5353
* The add-on doesn't support multi-cluster deployments.
5454
* Istio doesn't support Windows Server containers.
5555
* 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.
56-
* 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 static IP address configuration in the Gateway API Istio implementation as part of the Istio add-on in future.
56+
* 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.
5757

5858
## Next steps
5959

6060
### Feedback and Feature Requests
6161

62-
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.
62+
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.
6363

6464
* [Deploy Istio-based service mesh add-on][istio-deploy-addon]
6565
* [Troubleshoot Istio-based service mesh add-on][istio-troubleshooting]

articles/aks/istio-deploy-addon.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -242,7 +242,7 @@ az group delete --name ${RESOURCE_GROUP} --yes --no-wait
242242

243243
### Feedback and Feature Requests
244244

245-
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.
245+
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.
246246

247247
* [Deploy external or internal ingresses for Istio service mesh add-on][istio-deploy-ingress]
248248
* [Scale istiod and ingress gateway HPA][istio-scaling-guide]

articles/aks/istio-deploy-ingress.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ aks-istio-ingressgateway-external LoadBalancer 10.0.10.249 <EXTERNAL_IP>
4141
```
4242

4343
> [!NOTE]
44-
> 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 Gateway API Istio implementation as part of the Istio add-on in future.
44+
> 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.
4545
4646
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:
4747

@@ -226,7 +226,7 @@ Confirm that the sample application's product page is accessible. The expected o
226226

227227
## Delete resources
228228

229-
If you want to clean up the Istio external or internal ingresses, but leave the mesh enabled on the cluster, run the following command:
229+
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:
230230

231231
```azure-cli-interactive
232232
az aks mesh disable-ingress-gateway --ingress-gateway-type <external/internal> --resource-group ${RESOURCE_GROUPS}

0 commit comments

Comments
 (0)