nodePlacement provides explicit control over the scheduling of DNS pods.
Generally, it is useful to run a DNS pod on every node so that DNS queries are always handled by a local DNS pod instead of going over the network to a DNS pod on another node. However, security policies may require restricting the placement of DNS pods to specific nodes. For example, if a security policy prohibits pods on arbitrary nodes from communicating with the api, a node selector can be specified to restrict DNS pods to nodes that are permitted to communicate with the api. Conversely, if running DNS pods on nodes with a particular taint is desired, a toleration can be specified for that taint.
If unset, defaults are used. See nodePlacement for more details.