You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The affinity weight ca be between 1 and 100 for each instance of
the preferredDuringSchedulingIgnoredDuringExecution affinity type.
When the scheduler finds nodes that meet all the other scheduling
requirements of the Pod, the scheduler iterates through every
preferred rule that the node satisfies and adds the value of the
weight for that expression to a sum.
To make the pods better spread bump the weight to the max. Still
the anti affinty is "this Pod should not run in an X if that X is
already running one or more Pods that meet rule Y", which means
if there are less nodes, but enough resources, the pods get
scheduled there.
Related: https://issues.redhat.com/browse/OSPRH-8870
(cherry picked from commit c61e750)
0 commit comments