Merge pull request #58975 from xenolinux/pod-affinity

OCPBUGS#9406: Use the unique combination of labels when configuring anti-affinity rules

Author: michaelryanpeter

modules/nodes-scheduler-pod-affinity-about.adoc

@@ -13,6 +13,11 @@ _Pod affinity_ and _pod anti-affinity_ allow you to constrain which nodes your p
 
 For example, using affinity rules, you could spread or pack pods within a service or relative to pods in other services. Anti-affinity rules allow you to prevent pods of a particular service  from scheduling  on the same nodes as pods of another service that are known to interfere with the performance of the pods of the first service. Or, you could spread the pods of a service across nodes, availability zones, or availability sets to reduce correlated failures.
 
+[NOTE]
+====
+A label selector might match pods with multiple pod deployments. Use unique combinations of labels when configuring anti-affinity rules to avoid matching pods.
+====
+
 There are two types of pod affinity rules: _required_ and _preferred_.
 
 Required rules *must* be met before a pod can be scheduled on a node. Preferred rules specify that, if the rule is met, the scheduler tries to enforce the rules, but does not guarantee enforcement.