<p>I'm new to kubernetes and I'm struggling with starting my frist pods.
I installed kubernetes on my Ubuntu virtual machine, proceeded with </p>

<pre><code>kubeadm init
</code></pre>

<p>followed by other instuctions </p>

<pre><code>mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/
</code></pre>

<p>I can see that the node is up and running </p>

<pre><code>kubectl get nodes
NAME      STATUS    ROLES     AGE       VERSION
vm24740   Ready     master    12m       v1.10.0
</code></pre>

<p>Nevertheless my pods won't start:</p>

<pre><code>kubectl get pods
NAME                               READY     STATUS    RESTARTS   AGE
myappdeployment-588bc8ddf4-28jzj   0/1       Pending   0          11m
myappdeployment-588bc8ddf4-9bbb9   0/1       Pending   0          11m
myappdeployment-588bc8ddf4-fptft   0/1       Pending   0          11m
myappdeployment-588bc8ddf4-lxj8p   0/1       Pending   0          11m
myappdeployment-588bc8ddf4-xhg5f   0/1       Pending   0          11m
</code></pre>

<p>This is a detailed view on a pod:</p>

<pre><code>kubectl describe pod myappdeployment-588bc8ddf4-28jzj
Name:           myappdeployment-588bc8ddf4-28jzj
Namespace:      default
Node:           &lt;none&gt;
Labels:         app=myapp
                pod-template-hash=1446748890
Annotations:    &lt;none&gt;
Status:         Pending
IP:
Controlled By:  ReplicaSet/myappdeployment-588bc8ddf4
Containers:
  myapp:
    Image:        jamesquigley/exampleapp:v1.0.0
    Port:         9000/TCP
    Host Port:    0/TCP
    Environment:  &lt;none&gt;
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-6rcjb (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  default-token-6rcjb:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-6rcjb
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  1m (x37 over 11m)  default-scheduler  0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate.
</code></pre>

<p>Would somebody more experienced than me know, why the pods don't start?</p>

<p>Seem like you are running single node (master) k8s: </p>

<p>From <a href="https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/" rel="noreferrer">Documentation</a>: </p>

<blockquote>
  <p>Master Isolation </p>
  
  <p>By default, your cluster will not schedule pods on
  the master for security reasons. If you want to be able to schedule
  pods on the master, e.g. for a single-machine Kubernetes cluster for
  development, run:</p>
  
  <p><code>kubectl taint nodes --all node-role.kubernetes.io/master-</code> </p>
  
  <p>With output looking something like:</p>
  
  <p><code>node "test-01" untainted
   taint key="dedicated" and effect="" not found.
   taint key="dedicated" and effect="" not found</code>. </p>
  
  <p>This will remove <code>the node-role.kubernetes.io/master</code> taint from any nodes that have it,
  including the master node, meaning that the scheduler will then be
  able to schedule pods everywhere.</p>
</blockquote>
