You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/istio-about.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,10 +24,10 @@ Service-to-service communication is what makes a distributed application possibl
24
24
25
25
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:
26
26
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.
28
28
* Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic.
29
29
* 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.
31
31
* Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress.
32
32
33
33
## 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
46
46
47
47
Istio-based service mesh add-on for AKS currently has the following limitations:
48
48
* 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.
50
50
* The add-on doesn't support adding pods associated with virtual nodes to be added under the mesh.
51
51
* 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.
53
53
* The add-on doesn't support multi-cluster deployments.
54
54
* Istio doesn't support Windows Server containers.
55
55
* 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.
57
57
58
58
## Next steps
59
59
60
60
### Feedback and Feature Requests
61
61
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.
63
63
64
64
*[Deploy Istio-based service mesh add-on][istio-deploy-addon]
65
65
*[Troubleshoot Istio-based service mesh add-on][istio-troubleshooting]
Copy file name to clipboardExpand all lines: articles/aks/istio-deploy-addon.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,7 +242,7 @@ az group delete --name ${RESOURCE_GROUP} --yes --no-wait
242
242
243
243
### Feedback and Feature Requests
244
244
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.
246
246
247
247
*[Deploy external or internal ingresses for Istio service mesh add-on][istio-deploy-ingress]
248
248
*[Scale istiod and ingress gateway HPA][istio-scaling-guide]
> 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.
45
45
46
46
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:
47
47
@@ -226,7 +226,7 @@ Confirm that the sample application's product page is accessible. The expected o
226
226
227
227
## Delete resources
228
228
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:
230
230
231
231
```azure-cli-interactive
232
232
az aks mesh disable-ingress-gateway --ingress-gateway-type <external/internal> --resource-group ${RESOURCE_GROUPS}
0 commit comments