<p>I have a GKE cluster running in us-central1 with a preemptable node pool.  I have nodes in each zone (us-central1-b,us-central1-c,us-central1-f).  For the last 10 hours, I get the following error for the underlying node vm:</p>

<pre><code>Instance '[instance-name]' creation failed: The zone 
'[instance-zone]' 
does not have enough resources available to fulfill 
the request. Try a different zone, or try again 
later.
</code></pre>

<p>I tried creating new clusters in different regions with different machine types, using HA (multi-zone) settings and I get the same error for every cluster.</p>

<p>I saw an issue on <a href="https://status.cloud.google.com/incident/container-engine/18005" rel="nofollow noreferrer">Google Cloud Status Dashboard</a> and tried with the console, as recommended, and it errors out with a timeout error.</p>

<p>Is anyone else having this problem?  Any idea what I may be dong wrong?</p>

<p><strong>UPDATES</strong></p>

<ul>
<li>Nov 11

<ul>
<li>I stood up a cluster in us-west2, this was the only one which would work.  I used gcloud command line, it seems the UI was not effective. There was a note similar to this situation, use gcloud not ui, on the Google Cloud Status Dashboard.</li>
<li>I tried creating node pools in us-central1 with the gcloud command line, and ui, to no avail.</li>
<li>I'm now federating deployments across regions and standing up multi-region ingress.</li>
</ul></li>
<li>Nov. 12

<ul>
<li>Cannot create HA clusters in us-central1; same message as listed above.</li>
<li>Reached out via twitter and received a response.</li>
<li>Working with the <a href="https://kubernetes.io/docs/tasks/administer-federation/cluster/" rel="nofollow noreferrer">K8s guide to federation</a> to see if I can get multi-cluster running.  Most likely going to use <a href="https://github.com/kelseyhightower/kubernetes-cluster-federation" rel="nofollow noreferrer">Kelsey Hightowers approach</a></li>
<li>Only problem, can't spin up clusters to federate.</li>
</ul></li>
</ul>

<p><strong>Findings</strong></p>

<ul>
<li>Talked with google support, need a $150/mo. package to get a tech person to answer my questions.</li>
<li>Preemptible instances are not a good option for a primary node pool.  I did this because I'm cheap, it bit me hard.

<ul>
<li>The new architecture is a primary node pool with <a href="https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts" rel="nofollow noreferrer">committed use</a> VMs that do not autoscale, and a secondary node pool with preemptible instances for autoscale needs.  The secondary pool will have minimum nodes = 0 and max nodes = 5 (for right now); this cluster is regional so instances are across all zones.</li>
<li>Cost for an n1-standard-1 <a href="https://cloud.google.com/compute/docs/sustained-use-discounts" rel="nofollow noreferrer">sustained use</a> (assuming 24/7) a 30% discount off list.</li>
<li>Cost for a 1-year n1-standard-1 <a href="https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts" rel="nofollow noreferrer">committed use</a> is about ~37% discount off list.</li>
<li>Preemptible instances are re-provisioned every 24hrs., if they are not taken from you when resource needs spike in the region.</li>
<li>I believe I fell prey to a resource spike in the us-central1.</li>
</ul></li>
<li>A must-watch for people looking to federate K8s: <a href="https://www.youtube.com/watch?v=kwOvOLnFYck" rel="nofollow noreferrer">Kelsey Hightower - CNCF Keynote | Kubernetes Federation</a></li>
</ul>

<p>Issue appears to be resolved as of Nov 13th.</p>
