<p>I've created a cluster on Google Kubernetes Engine (previously Google Container Engine) and installed the Google Cloud SDK and the Kubernetes tools with it on my Windows machine.</p>

<p>It worked well for some time, and, out of nowhere, it stopped working. Every command I'm issuing with <code>kubectl</code> provokes the following:</p>

<pre><code>Unable to connect to the server: net/http: TLS handshake timeout
</code></pre>

<p>I've searched Google, the Kubernetes Github Issues, Stack Overflow, Server Fault ... without success.</p>

<p>I've tried the following:</p>

<ul>
<li>Restart my computer</li>
<li>Change wifi connection</li>
<li>Check that I'm not somehow using a proxy</li>
<li>Delete and re-create my cluster</li>
<li>Uninstall the Google Cloud SDK (and kubectl) from my machine and re-install them</li>
<li>Delete my <code>.kube</code> folder (config and cache)</li>
<li>Check my <code>.kube/config</code></li>
<li>Change my cluster's version (tried 1.8.3-gke.0 and 1.7.8-gke.0)</li>
<li>Retry several hours later</li>
<li>Tried both on PowerShell and cmd.exe</li>
</ul>

<p>Note that the cluster seem to work perfectly, since I have my application running on it and can interact with it normally through the Google Cloud Shell.</p>

<p>Running:</p>

<pre><code>gcloud container clusters get-credentials cluster-2 --zone europe-west1-b --project ___

kubectl get pods
</code></pre>

<p>works on Google Cloud Shell and provokes the <code>TLS handshake timeout</code> on my machine.</p>

<p>For others seeing this issue, there is another cause to consider.</p>

<p>After doing:</p>

<pre><code>gcloud config set project $PROJECT_NAME
gcloud config set container/cluster $CLUSTER_NAME
gcloud config set compute/zone europe-west2
gcloud beta container clusters get-credentials $CLUSTER_NAME --region europe-west2 --project $PROJECT_NAME
</code></pre>

<p>I was then seeing:</p>

<pre><code>kubectl cluster-info
Unable to connect to the server: net/http: TLS handshake timeout
</code></pre>

<p>I tried everything suggested here and elsewhere. When the above worked without issue from my home desktop, I discovered that shared workspace wifi was disrupting TLS/VPNs to control the internet access!</p>
