Chapter 8 – Pod Placement Controls

1. Node Selectors can be used to match against Node labels and multiple Nodes can fulfill the requirements. Using a Node name means that you specify the single Node where the Pod must be placed.
2. Kubernetes implements some default taints to ensure that Pods do not get scheduled on Nodes that are malfunctioning or lack resources. In addition, Kubernetes taints the master Nodes to prevent scheduling of user applications on the masters.
3. Too many affinities and anti-affinities can slow down the scheduler or cause it to become unresponsive. Determining Pod placement in cases with a lot of affinities or anti-affinities is very compute-heavy.
4. Using anti-affinities, you could prevent Pods from co-existing with like Pods in the same failure domain. Nodes in the same failure domain would be labeled with a failure domain or zone identifier. Anti-affinity would look for Pods matching the specific tier of the application level in the same failure...