. You can constrain a Pod so that it can only run on particular set of node(s).

There are several ways to do this and the recommended approaches all use label selectors to facilitate the

selection.

2.

Generally such constraints are unnecessary, as the scheduler will automatically do a reasonable placement

(for example, spreading your Pods across nodes so as not place Pods on a node with insufficient free

resources).

3.

However, there are some circumstances where you may want to control which node the Pod deploys to, for

example, to ensure that a Pod ends up on a node with an SSD attached to it, or to co-locate Pods from two

different services that communicate a lot into the same availability zone.

4.

You can use any of the following methods to choose where Kubernetes schedules specific Pods:

a. Node-Selector

b. Affinity and Anti-Affinity

c. Nodename