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.
Summary
This article discusses how to resolve a scenario in which you can't use authorized IP address ranges to access the API server for a Microsoft Azure Kubernetes Service (AKS) cluster.
Symptoms
If you try to create or manage resources in an AKS cluster, you can't access the cluster API server. When you run kubectl, you receive the following error message:
Unable to connect to the server: dial tcp x.x.x.x:443: i/o timeout
Cause
You configured your AKS cluster to access the cluster API server by using authorized IP address ranges that your computer can't access.
Solution
Make sure that when you run the az aks create or az aks update command in Azure CLI, the --api-server-authorized-ip-ranges parameter includes the IP addresses or IP address ranges of the automation, development, or tooling systems that are being used.