<p>I am trying to deploy my microservices into Kubernetes cluster. My cluster having one master and one worker node. I created this cluster for my R&amp;D of Kubernetes deployment. When I am trying to deploy I am getting the even error message like the following,</p>

<pre><code>Events:
 Type     Reason            Age        From               Message
  ----     ------            ----       ----               -------
 Warning  FailedScheduling  &lt;unknown&gt;  default-scheduler  0/2 nodes are available: 2 node(s) had taints that the pod didn't tolerate
</code></pre>

<p><strong>My attempt</strong></p>

<p>When I am exploring about the error, I found some comments in forums for restarting the docker in the node etc. So after that I restarted Docker. But still the error is the same.</p>

<p>When I tried the command <code>kubectl get nodes</code> it showing like that both nodes are master and both are <code>ready</code> state.</p>

<pre><code>NAME           STATUS   ROLES    AGE     VERSION
 mildevkub020   Ready    master   6d19h   v1.17.0
 mildevkub040   Ready    master   6d19h   v1.17.0
</code></pre>

<p>I did not found worker node here. I created one master (mildevkub020) and one worker node (mildev040) with one load balancer. And I followed the official documentation of Kubernetes from the following link,</p>

<p><a href="https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/" rel="noreferrer">https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/</a></p>

<p><strong>My question</strong></p>

<p>Is this error is because of the cluster problem? Because I am not finding the cluster worker node. Only master node.</p>

<p>You can run below command to remove the taint from master node and then you should be able to deploy your pod on that node</p>

<pre><code>kubectl taint nodes  mildevkub020 node-role.kubernetes.io/master-
kubectl taint nodes  mildevkub040 node-role.kubernetes.io/master-
</code></pre>

<p>Now regarding why its showing as master node check the command you ran to join the node with kubeadm. There are separate commands for master and worker node joining.</p>
