Carlos Vicent Domenech

Hello. We experienced a similar issue running AKS 1.22.6 and 1.23.5. We found a similar issue on github [Kubernetes issue 105204](https://github.com/kubernetes/kubernetes/issues/105204). We resolved the problem upgrading to latest patch version...

Hello there @singvey999 This version is unsupported, have you upgraded and checked if the K8s 1.24.x has this issue ?

Hello @teocrispy91. Can you check the current nodepool k8s version? ```bash az aks nodepool show --cluster-name testcluster --name testwin --resource-group test ``` Old clusters using nodepool without VMSS can get...

Hello @teocrispy91 As I mentioned there are two kind of AKS clusters when it comes to nodepools defined by the `vm-set-type` argument when calling the az client. * availabilitySet: this...

Hello @rob2universe First at all, when you create a AKS cluster the way you have created it comes without a namespace called `ingress-nginx`. Therefore when you are executing ```batch (eval...

Hello @rob2universe . Have you got the chance to check the previous comment I posted two weeks ago ? Best regards.

Hello @dmacobr . Have you tried to restart the coredns pods from kube-system namespace ? BR