Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article discusses how to resolve an issue that prevents you from using the Azure portal to view resources in the Kubernetes resource viewer.
Symptoms
When you try to view resources in the Kubernetes resource viewer in the Azure portal, you receive the following error message:
Unable to reach the API server '<server-url>' or API is too busy to response. Check your network setting.
Cause 1: You configured authorized IP ranges
You configured your Microsoft Azure Kubernetes Service (AKS) cluster to access the cluster API server by using authorized IP address ranges that your computer can't access.
Solution
When you run the az aks create or az aks update command in Azure CLI, make sure that the --api-server-authorized-ip-ranges parameter includes access for the local client computer to the IP addresses or IP address ranges from which the portal is being browsed.
Cause 2: AKS is a private cluster
Your AKS is created as a private cluster, and you're accessing the Azure portal from a network that can't communicate with the subnet to which your AKS is connected.
Solution
This behavior is expected. To view the AKS resources in the Azure portal, you must access the Azure portal from a client that's located on a network that has connectivity to the AKS subnet. Then, you can view all AKS-related resources in the Azure portal.
More information
Contact us for help
If you have questions, you can ask Azure community support. You can also submit product feedback to Azure feedback community.