This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 87%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPG%3C/text%3E%3C/svg%3E)
We can't see Kubernetes resources via Kubectl and the portal. This is for all my team members. This issue started this morning. We are on version 1.26.3. No updates/changes have happened in the last 3 weeks.
kubectl get pods --all-namespaces
Unable to connect to the server: dial tcp ...: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
When trying to view workloads from the AKS portal. This error displays:
Network error
Unable to reach the api server 'https://.........azmk8s.io' or api server is too busy to respond. Check your network settings and refresh to try again
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 4%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Hello, @Pierre Gadea !
If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!
We became fully operational again by deleting the cluster and recreating it. No other option was left since this is a mission-critical cluster and we could wait no further.
Hi @Pierre Gadea,
It seems this is a private AKS cluster and you need to use a VM that has access to the AKS cluster's Azure Virtual Network (VNet).
Options for connecting to the private cluster: https://learn.microsoft.com/en-us/azure/aks/private-clusters?tabs=azure-portal#options-for-connecting-to-the-private-cluster
We became fully operational again by deleting the cluster and recreating it.