Unable to connect AKS cluster: connection time out

1
votes

I've created an AKS cluster in the UK region in Azure.

Currently, I can no longer access my AKS cluster. Connecting to the public IPs fails; all connections time out.

Furthermore, I can't run the kubectl command either:

fcarlier@ubuntu:~$ kubectl get nodes Unable to connect to the server: net/http: TLS handshake timeout

Is there a known issue with AKS in that region or is it something on my side?

3
azurekubernetesazure-container-service

3 Answers

1
votes

Is there a known issue with AKS in that region or is it something on my side?

Sorry to give you a bad experience.
For now, Azure AKS still in preview, please try to recreate it, ukwest works fine now.

Here is a similar case about you, please refer to it.

0
votes

I just successfully created a single node AKS cluster on UK West with no issues. Can you please retest? For now, I would avoid provisioning on West US 2 until the threshold issues are fixed. I'm aware the AKS team is actively engaged to restore service on West US. Sorry for the inconvenience. Below is the sample cmd to create in UK if you need the reference. Hope this helps.

  1. Create Resource Group (UK West):az group create --name myResourceGroupUK --location ukwest
  2. Create AKS cluster in (UK west):az aks create --resource-group myResourceGroupUK --name myK8sClusterUK --agent-count 1 --generate-ssh-keys
0
votes

I just finished a big post over here on this topic (which is not as straight forward as a single solution / workaround): 'Unable to connect Net/http: TLS handshake timeout' — Why can't Kubectl connect to Azure Kubernetes server? (AKS)

That being said, the solution to this one for me was to scale the nodes up — and then back down — for my impacted Cluster from the Azure Kubernetes service blade web console.

Workaround / Potential Solution

  1. Log into the Azure Console — Kubernetes Service blade.
  2. Scale your cluster up by 1 node.
  3. Wait for scale to complete and attempt to connect (you should be able to).
  4. Scale your cluster back down to the normal size to avoid cost increases.

Total time it took me ~2 mins.

More Background Info on the Issue

Also added this solution to the full ticket description write up that I posted over here (if you want more info have a read):

'Unable to connect Net/http: TLS handshake timeout' — Why can't Kubectl connect to Azure Kubernetes server? (AKS)