Why There is No Kubernetes Pod on the Master Node

You may have noticed that the Scheduler doesn’t schedule any Pod to master node. Only worker nodes have pods. Let’s take a look at why.

The reason

When the Kubernetes cluster is first set up, a Taint is set on the master node. This automatically prevents any pods from being scheduled on this node. You can see this as well as modify this behavior if required. However, a best practice is not to deploy application workloads on a master server. To see this taint, run a kubectl describe node command with kubemaster which has the node name and look for the “Taint” section. You will see a Taint set to not schedule any pod on the master node.

Taints on Master Node