azure-docs
azure-docs copied to clipboard
Please document all the new resources created by Istio
A developer would very likely need to debug the application after enabling Istio. It would be good to understand what resources are added by AKS Istio addon. There are differences from OSM such as the sidecar being called istio-proxy instead of envoy.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 31367f47-0d71-8b44-ca40-e2b1c7cf3d16
- Version Independent ID: 627b0d0f-0d38-e529-2e52-30823cf0008f
- Content: Deploy Istio-based service mesh add-on for Azure Kubernetes Service (preview) - Azure Kubernetes Service
- Content Source: articles/aks/istio-deploy-addon.md
- Service: azure-kubernetes-service
- GitHub Login: @MGoedtel
- Microsoft Alias: shasb
@chitturs Thanks for your feedback! We will investigate and update as appropriate.
@chitturs Thank you for your question. The AKS Istio add-on deploys a set of resources to your AKS cluster to enable Istio functionality. These resources include:
1.Istio control plane components, such as Pilot, Mixer, and Citadel 2.Istio ingress gateway 3.Istio egress gateway 4.Istio sidecar injector webhook 5.Istio CRDs (Custom Resource Definitions) When you enable Istio on your AKS cluster, the sidecar proxy is automatically injected into your application pods. The sidecar proxy is responsible for intercepting all network traffic to and from the pod, and forwarding it to the appropriate destination. In Istio, the sidecar proxy is called "istio-proxy" instead of "envoy", which is used in other service mesh solutions like OSM.
To debug your application after enabling Istio, you can use Istio's built-in observability features, such as distributed tracing, metrics, and logging. You can also use Istio's traffic management features, such as traffic shifting and fault injection, to test and debug your application. Additionally, you can use standard Kubernetes debugging tools, such as kubectl logs and kubectl exec, to troubleshoot issues with your application pods.
I hope this helps! Let me know if you have any further questions.
@chitturs We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation
@ManoharLakkoju-MSFT, please update the doc and close.
@chitturs I'm going to assign this to the document author so they can take a look at it accordingly
@MGoedtel Can you please check and add your comments on this doc update request as applicable.
#please-close