Azure Kubernetes: TLS handshake timeout

那年仲夏 提交于 2019-12-05 12:45:49

Piling on: we are adding capacity as fast as possible for the preview.

For now, Azure AKS still in preview. We have a general service outage in West US 2 that we are investigating.

During the time we investigate, cluster creations in West US 2 will not be possible and existing customers might not work.

We will update this thread when we fix the issue.

We apologize for the inconvenience.

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)

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!