<p>I've been running an app on Kubernetes very smoothly for the past few weeks, until today I found that my Kubernetes master is no longer available.</p>

<p>But <strong>the application is still up</strong>, seemingly because the cluster's nodes are still available in Google Compute Engine: </p>

<p><a href="https://i.stack.imgur.com/S2Dd5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/S2Dd5.png" alt="gcloud compute engine nodes"></a></p>

<p>(We don't use any compute instances aside from our K8s cluster.)</p>

<p>My <code>gcloud</code> CLI has all the right configuration:</p>

<pre><code>$ gcloud config list
Your active configuration is: [default]

[compute]
...
[container]
use_client_certificate = True
[core]
account = {email}
disable_usage_reporting = True
project = {myproject}
</code></pre>

<p>Even my <code>kubectl</code> CLI is configured to use the cluster that once existed:</p>

<pre><code>$ kubectl config current-context
gke_{myproject}_us-central1-a_{clustername}
</code></pre>

<p>But any <code>kubectl</code> call results in a timeout.</p>

<pre><code>$ kubectl get pods
Unable to connect to the server: dial tcp {ipv4 address}:443: i/o timeout
</code></pre>

<p><code>gcloud</code> and the Google Container Engine web UI both agree that there are no clusters:</p>

<pre><code>$ gcloud container clusters list
*crickets*
</code></pre>

<p>I got in touch with Google Support to solve this problem. The cluster's master instance was erroneously marked as abusive, and the master was taken down. Google was able to bring it back up. After that, there was a process to return the cluster to its normal state.</p>

<p>I suppose the solution here is to contact support.</p>
