Azure Kubernetes: TLS handshake timeout
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
- 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):