Unable to delete AKS cluster

Hi UV Panta,
Based on your query,
Could you please check for remaining resources ensure there is no resource should be link check by using below command

kubectl get pods --all-namespaces
kubectl get services --all-namespaces
kubectl get deployments --all-namespaces

Please refer the documentation for more information on commands
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_get/#examples
If you found anything delete them manually

As you mentioned in query it is already deleted but based on error it is link some other resource networking better try to check for any remaining network interfaces, IP configurations, or delegated subnet entries that might still be linked to the cluster's pods. Manually delete any of these unused resources to allow the cluster deletion process to complete successfully

If above things are not working, try to use below command force to delete the cluster

az aks delete --name <cluster-name> --resource-group <resource-group-name> --yes --no-wait

Please refer the documentation for more information on command line
https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-delete

Also, check that the user or identity has the Contributor role on the AKS resource group, as this role is required to manage and delete the cluster.

Please refer the below documentation and community question and answer it is also related to some kind of issue cluster it might help any one point
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/create-upgrade-delete/cannot-delete-ip-subnet-nsg
https://github.com/Azure/AKS/issues/2443

Try the steps mentioned above and let me know how it goes. If you have any further questions or need assistance, please let me know

Hey Akshay,
Thanks for your response.

While trying to delete namespace or any other resources, I get this message:
Failed to load all namespaces.

The same happens with workloads & services.

Also the cli returns following error.

{"code":"BadRequest","details":null,"message":"ManagedCluster is in a state preventing RunCommand feature: PowerState=Running ProvisioningState=Deleting","subcode":""} 

Now, I tried to delete using the command above with the flags --yes --no-wait, but it's still in deleting state and not completed.

I checked the other links. In my case, there's no subnet nsg or any other resource. All of them are already deleted.

Can you suggest what else should I do?

Hi UV Panta,
Thanks for reply and tried on previous steps.
Just wanted you to check when you create an AKS cluster, it automatically creates another resource group. This second group, with the prefix name MC_<resourcegroupname>, contains all the network and related configurations, if it is still present delete this resource as shown in the screenshot below name

If you know about the second MC resource group already deleted the resources in it, that would be great!

Can you check the status of your cluster's provisioning state once, you can use the following command:

az aks show -n <cluster-name> -g <resource-group>

If the cluster is in a transitional state (such as Updating or Deleting) or if there’s an inconsistency in its provisioning state, the deletion might fail or become stuck.

And also, you can run the command below to see what is causing the issue by adding --debug command

 az aks delete -n <clustername> -g <resourcegroup> --debug

I found another community question and answer about deleting a cluster. Over there, they found the issue and were able to delete the cluster by using the debug command. Please refer below link

https://learn.microsoft.com/en-us/answers/questions/973618/aks-cannot-be-deleted-from-the-azure-ui-due-to-an

Hi @Akshay kumar Mandha

I checked them, the cluster is in failed state.
There's no any additional message than the one from I shared above.

Is there any other way to force delete the cluster? The no-wait flag didn't way.

Hi UV Panta,
Have you checked the second resource group, MC_<resourcegroup>? Ensure that all resources in this resource group have been deleted, as this might be causing the issue with the network resources could you please confirm on this?