Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Enabled Istio mesh on preexisting cluster but no actual Istio resources present #4800

Open
benjaminxie opened this issue Feb 18, 2025 · 3 comments

Comments

@benjaminxie
Copy link

benjaminxie commented Feb 18, 2025

Describe the bug
I am trying to enable the mesh add-on on a preexisting cluster and am following the instructions at https://learn.microsoft.com/en-us/azure/aks/istio-deploy-addon. I got rid of my previous Istio deployment (I deployed the helm charts myself) and the namespaces are deleted too. However, after the az CLI command is run and despite serviceMeshProfile.mode showing as Istio, I see no aks-istio-system namespace and definitely no Istio-related pods.

To Reproduce
Steps to reproduce the behavior:

  1. Set up RESOURCE_GROUP and CLUSTER environment variables
  2. Run command az aks mesh enable --resource-group ${RESOURCE_GROUP} --name ${CLUSTER}
  3. Run command az aks show --resource-group ${RESOURCE_GROUP} --name ${CLUSTER} --query 'serviceMeshProfile.mode' and see output Istio
  4. Run command kubectl get ns aks-istio-system and get error that there is no aks-istio-system namespace

Expected behavior
I expect to see the aks-istio-system namespace and the related pods.

Environment (please complete the following information):

  • CLI Version 2.61.0
  • Kubernetes version 1.30.5

Additional context
I have also "successfully" upgraded from Istio 1.22 to 1.23 via the web portal but my cluster still lacks any Istio-related resources.

I doubt my reproduction steps will actually lead to someone reproducing my issue and I assume I'm just doing something wrong but I am following the steps and cannot find any logging that points to any issues. I have also run the az aks mesh enable command with the debug flag and also failed to find any clues in the extra output.

@Winbobob
Copy link

There are two options that could help root cause this issue:

  • Option1: create a new AKS cluster and enable addon to see if it works. If so, there could be some components in your existing cluster that prevent istio addon to be installed properly like CRDs, charts.
  • Option2: create a support ticket then we could check the cluster for you.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs Attention 👋 Issues needs attention/assignee/owner label Feb 25, 2025
@biefy
Copy link
Contributor

biefy commented Feb 27, 2025

@benjaminxie how did you uninstall the previous installation? Have you deleted all CRDs?

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs Attention 👋 Issues needs attention/assignee/owner label Feb 27, 2025
Copy link
Contributor

@azure/aks-traffic would you be able to assist?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants