This message was deleted.
# azure
a
This message was deleted.
c
Is the same happening for an AKS cluster provisionned from Rancher (from the UI, not Terraform) ?
which Rancher version ?
p
Rancher version 2.7.5 and 2.7.7 (I've recently upgraded). I'll try deploying one via the UI to see if it is any different.
👍 1
So, it doesn't seem to impact the cluster made manually through the UI, only the ones created via the terraform provider. Odd, but it gives me something to investigate. Any ideas on why this would happen would be appreciated.
c
tbh I don't know
you could file in a GitHub issue the current state of your troubleshooting
p
I may do that. I'm going to try chasing it down a bit first, now that I have a lead - there may be something different that I set in my terraform that I can pick apart.
For anyone else who runs into this: it looks like the issue was that I was using the rancher2_cluster_sync resource with the AKS cluster, and that triggered the issue.