<p>I entered the below command to create a cluster, but I get an error stating
gcloud container clusters create kubia --num-nodes=3 --machine-type=f1-micro</p>

<p>The above command throws the below error.</p>

<blockquote>
  <p>ERROR: (gcloud.container.clusters.create) ResponseError: code=403,
  message=Insufficient regional quota to satisfy request: resource
  "IN_USE_ADDRESSES": request requires '9.0' and is short '1.0'. project
  has a quota of '8.0' with '8.0' available. View and manage quotas at
  <a href="https://console.cloud.google.com/iam-admin/quotas?usage=USED&amp;project=k8s-demo-263903" rel="nofollow noreferrer">https://console.cloud.google.com/iam-admin/quotas?usage=USED&amp;project=k8s-demo-263903</a>.</p>
</blockquote>

<p>Then I chose to set the number of nodes to 2</p>

<p>The command created 6 nodes</p>

<p>NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS kubia asia-south1 1.13.11-gke.14 35.200.140.153 f1-micro 1.13.11-gke.14 <strong><em>6</em></strong> RUNNING</p>

<p>NAME</p>

<pre><code>gke-kubia-default-pool-46a198b9-qdg2
gke-kubia-default-pool-46a198b9-s3xn
gke-kubia-default-pool-72fd11ff-mddd
gke-kubia-default-pool-72fd11ff-qrds
gke-kubia-default-pool-75ecb3b2-1wfq
gke-kubia-default-pool-75ecb3b2-j4cz
</code></pre>

<p>Why is that the number of node is getting multiplied with 3 for the nodes mentioned in the command?</p>

zilcuanu
<p>This is an old request, so hopefully you have found your way past it by now, so this is mainly aimed at anyone else who happens across this issue.</p>
<p>It looks like you are following the examples in the Manning Kubernetes in Action (version 1).</p>
<p>I understand that the problem is caused by setting the default compute/zone to a region (e.g. europe-west4) and not to a zone (e.g. europe-west4-a).  This results in the effect that @Stefan Neacsu mentioned above.  When you launch the cluster, it starts three nodes in each zone (e.g. europe-west4-a, europe-west4-b and europe-west4-c), hence the multiple of three.  This is great for stability when you get to deployment, but not what you want when you are just experimenting.</p>
<p>The solution therefore is to use the command:
gcloud config set compute/zone &lt;zone_id&gt;
where zone_id is the name of a zone and not a region.</p>
<p>See <a href="https://cloud.google.com/compute/docs/regions-zones" rel="nofollow noreferrer">this</a> for a list of zones and regions.</p>
