Unable to reach the api server or api server is too busy to respond. {"message":"Failed to fetch","stack":"TypeError: Failed to fetch\n at https://portal.azure.com/Content/Dynamic/Ibpv2Frqbqgp.js:113:24094","isError":true}

Hi @Salman Mandal

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Make sure your AKS cluster can successfully communicate with Azure Arc. Network blocks such as firewalls or security settings may be preventing communication. Make sure all of these are in place so that Azure Arc can access the cluster.

It’s also worth checking if your AKS team is healthy and responsive. You can use kubectl get nodes to check if the API server responds as expected. If the cluster is low on resources (such as CPU or memory), it can cause the API server to slow down or fail. You can use kubectl top nodes and kubectl top pods to check for any resource bottlenecks.

Azure Arc uses an agent running in your AKS cluster to manage it. If this agent does not work properly, it can cause problems. To check its status, you can run kubectl get pods -n kube-system . If none of the agent pods are connected, try running and restarting:

kubectl delete pod <arc-agent-pod-name> -n kube-system

If the above steps don’t fix it, you can try uninstalling your AKS cluster from Azure Arc and then rewrite it. To do this:

Go to the Azure Arc section of the Azure portal and select the cluster name.

Now follow the steps to re-register the cluster in Azure Arc.

Sometimes version incompatibility between AKS and Azure Arc can cause problems. Make sure both are fashionable and compatible.

If things are still not working, you can check the logs of the Azure Arc agent to see if there are any error messages. To do this, use:

kubectl logs <arc-agent-pod-name> -n kube-system

It’s also possible that there may be an issue on Azure’s side. You can check the Azure status page to see if there are any ongoing issues with Azure Arc or AKS.

If you have any further queries, do let us know.