nodeSelector sends Pods only to nodes with exact labels. Node affinity says more. Under requiredDuringSchedulingIgnoredDuringExecution, nodeSelectorTerms hold matchExpressions with operators In, NotIn, Exists, DoesNotExist, Gt and Lt; a node must satisfy one term. Under preferredDuringSchedulingIgnoredDuringExecution, each term has a weight from 1 to 100 that the scheduler adds to matching nodes' scores, and the Pod still runs elsewhere when none fits.
Use required rules for real constraints, such as data that must stay in a region, and preferred rules for wishes. A required rule that nothing satisfies leaves Pods Pending with didn't match Pod's node affinity/selector, often because of a typo in a value.
IgnoredDuringExecution means running Pods are not moved when labels change later. Node labels like topology.kubernetes.io/zone are usually set by the cloud provider; teams add their own with kubectl label node.
Only nodes in the south zone.