<p>I got OutOfcpu in kubernetes on googlecloud what does it mean? My pods seem to be working now, however there there were pods in this same revision which got OutOfcpu.</p>

<p>It means that the <a href="https://kubernetes.io/docs/concepts/scheduling/kube-scheduler/#kube-scheduler" rel="noreferrer">kube-scheduler</a> can't find any node with available CPU to schedule your pods:</p>

<blockquote>
  <p>kube-scheduler selects a node for the pod in a 2-step operation:</p>
  
  <ol>
  <li>Filtering</li>
  <li>Scoring</li>
  </ol>
  
  <p>The <em>filtering</em> step finds the set of Nodes where it’s feasible to
  schedule the Pod. For example, the <code>PodFitsResources</code> filter checks
  whether a candidate Node has enough available resource to meet a Pod’s
  specific resource requests.<br>
  [...]<br>
  <code>PodFitsResources</code>: Checks if the
  Node has free resources (eg, CPU and Memory) to meet the requirement
  of the Pod.</p>
</blockquote>

<p>Also, as per <a href="https://kubernetes.io/docs/concepts/configuration/assign-pod-node/" rel="noreferrer">Assigning Pods to Nodes</a>:</p>

<blockquote>
  <p>If the named node does not have the resources to accommodate the pod,
  the pod will fail and its reason will indicate why, e.g. OutOfmemory
  or <strong>OutOfcpu</strong>.</p>
</blockquote>
