-
Notifications
You must be signed in to change notification settings - Fork 306
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] Cannot complete instructions for setting up Web Application Routing add-on #3743
Comments
Hello @sam-huang1223 I have just tested this on one of my clusters and I am retrieving the Managed Identity Object ID as expected. I tested this on using the cloud shell. can you please check again and let me know. |
Same problem on my side. I had to create a brand new AKS. |
Can you confirm if you are using the latest aks-preview extension? |
Action required from @Azure/aks-pm |
@sam-huang1223 can you run The minimum versions should be:
These are the versions that are working for me:
|
@sam-huang1223 are you still having this issue with the latest AZ CLI version? |
This issue will now be closed because it hasn't had any activity for 7 days after stale. sam-huang1223 feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion. |
Describe the bug
In https://learn.microsoft.com/en-us/azure/aks/web-app-routing?tabs=without-osm, it asks us to run
MANAGEDIDENTITY_OBJECTID=$(az aks show -g ${RGNAME} -n ${CLUSTERNAME} --query ingressProfile.webAppRouting.identity.objectId -o tsv)
after enabling the add-on for an existing cluster. However, this returns null and further inspection of the ingressProfile field reveals that this identity block doesn't seem to exist. Perhaps this commands need to be updated?To Reproduce
Expected behavior
ManagedIdentity field is populated (this worked about a year ago when I first attempted experimenting with the web app routing add-on)
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
If web app routing doesn't work for us, Snorkel will need to migrate to using application gateway for our azure deployments which may not be ideal.
The text was updated successfully, but these errors were encountered: