可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试):
问题:
I created a new cluster as per the Azure guide and created the cluster without issue but when I enter the kubectl get nodes to list the nodes I only get this response Unable to connect to the server: net/http: TLS handshake timeout.
I tried once in the Cloud Shell and once on my machine using the latest version of the Azure CLI (2.0.20).
I saw that there was a similar earlier issue regarding Service Principal credentials, which I updated but that didn't seem to solve my issue either.
Any guidance would be greatly appreciated.
回答1:
Piling on: we are adding capacity as fast as possible for the preview.
回答2:
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.
回答3:
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
- Log into the Azure Console ― Kubernetes Service blade.
- Scale your cluster up by 1 node.
- Wait for scale to complete and attempt to connect (you should be able to).
- 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)
