<p>I'm trying to deploy a docker image (<a href="https://hub.docker.com/r/digitorus/eramba-db" rel="nofollow noreferrer">https://hub.docker.com/r/digitorus/eramba-db</a>) to Kubernetes. My workflow is using <code>docker pull digitorus/eramba-db</code> to pull the image and using the below .yaml file to deploy to a separate namespace (eramba-1)</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: eramba
  namespace: eramba-1
  labels:
     app: eramba               
spec:
  replicas: 1
  selector:
    matchLabels:
      app: eramba
  template:
    metadata:
      labels:
        app: eramba
    spec:
      containers:
      - name: eramba
        image: docker.io/digitorus/eramba:latest
        ports:
        - containerPort: 80
</code></pre>
<p>The master node has a status of (notReady) and the pod is pending.</p>

Bryan
<pre><code>Taints:             node.kubernetes.io/not-ready:NoSchedule
...
Namespace                 Name
---------                 ----
kube-system               etcd-osboxes
kube-system               kube-apiserver-osboxes
kube-system               kube-controller-manager-osboxes
kube-system               kube-proxy-hhgwr
kube-system               kube-scheduler-osboxes
...
</code></pre>
<p>After you ran kubeadm that installed core k8s components, your cluster needs to have network plugin installed and functioning so your node can be ready for workload deployment. Then you can remove the &quot;master&quot; taint <code>kubectl taint nodes --all node-role.kubernetes.io/master-</code> so that pod can be deploy on this single node.</p>
