Any idea why replacing of an aks cluster is failing with unknown provider error? it almost seems as if it’s attempting to recreate all of the k8s resources using the old provider urn.
i have seen this behavior in a couple environments now and have had to resort to manually deleting the new aks cluster, exporting the stack, deleting all of the k8s resources and the old provider, and regenerating everything again. obviously not ideal. @broad-dog-22463
attempting to run
again after the failed update just results in the same error