title: How do I avoid unschedulable pods when running an autoscale-enabled Google Container/Kubernetes Engine cluster?
body: <p>I'm running into an issue where I seem to max out my Container Engine (Kubernetes Engine) cluster at 9 nodes (or 9 vCPUs). For context, I'm trying to run around 50 or so web scrapers as Kubernetes <a href="https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/" rel="noreferrer">Cron Jobs</a>. Here is the <code>gcloud</code> command I am using to create the cluster in the <code>us-east1-c</code> zone:</p>
  
  <pre><code>gcloud beta container clusters create my-example-cluster \
    --cluster-version=1.8.1-gke.1 \
    --machine-type=f1-micro \
    --enable-autoscaling \
    --min-nodes=1 \
    --max-nodes=60
  </code></pre>
  
  <p>When I checked out <a href="https://console.cloud.google.com/iam-admin/quotas" rel="noreferrer">IAM &amp; Admin > Quotas</a>, it looked like I was possibly maxing out on in-use IP addresses (max=8).</p>
  
  <p>After launching all the scrapers, I'm ending up around 35 pods that are unschedulable (seemingly because I can't exceed 9 nodes?).</p>
  
  <p>Has anyone run into a similar situation and come up with a solution? Is there a way, perhaps via Kubernetes config, to not count against IP address usage since these nodes do not need to be accessible externally (if that's even the issue)? Also open to other setups if anyone has recommendations.</p>
  
  <p>Thanks for all the help!</p>
  
  <p>P.S. I do have billing enabled</p>