<p>I have a picture below of my mac.</p>

<ul>
<li>K8S Cluster(on VirtualBox, 1*master, 2*workers)</li>
<li>OS Ubuntu 15.04</li>
<li>K8S version 1.1.1</li>
</ul>

<p>When I try to create a pod "busybox.yaml" it goes to pending status.
How can I resolve it?</p>

<p>I pasted the online status below for understanding with a picture (kubectl describe node).</p>

<ul>
<li><p>Status
kubectl get nodes
192.168.56.11   kubernetes.io/hostname=192.168.56.11   Ready      7d
192.168.56.12   kubernetes.io/hostname=192.168.56.12   Ready      7d</p></li>
<li><p>kubectl get ev
1h  39s  217  busybox Pod  FailedScheduling {scheduler } no nodes available to schedule pods</p></li>
<li><p>kubectl get pods
NAME      READY     STATUS    RESTARTS   AGE
busybox   0/1       Pending   0          1h</p></li>
</ul>

<p>And I also added one more status.
<a href="https://i.stack.imgur.com/vTqc2.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/vTqc2.jpg" alt="enter image description here"></a></p>

TedJung
<p>"kubectl describe pod busybox" or "kubectl get pod busybox -o yaml" output could be useful.</p>

<p>Since you didn't specify, I assume that the busybox pod was created in the default namespace, and that no resource requirements nor nodeSelectors were specified. </p>

<p>In many cluster setups, including vagrant, we create a LimitRange for the default namespace to request a nominal amount of CPU for each pod (.1 cores). You should be able to confirm that this is the case using "kubectl get pod busybox -o yaml".</p>

<p>We also create a number of system pods automatically. You should be able to see them using "kubectl get pods --all-namespaces -o wide".</p>

<p>It is possible for nodes with sufficiently small capacity to fill up with just system pods, though I wouldn't expect this to happen with 2-core nodes.</p>

<p>If the busybox pod were created before the nodes were registered, that could be another reason for that event, though I would expect to see a subsequent event for the reason that the pod remained pending even after nodes were created.</p>

<p>Please take a look at the troubleshooting guide for more troubleshooting tips, and follow up here on on slack (slack.k8s.io) with more information.</p>

<p><a href="http://kubernetes.io/v1.1/docs/troubleshooting.html" rel="nofollow">http://kubernetes.io/v1.1/docs/troubleshooting.html</a></p>
