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
{{ message }}
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
Affinity rules present more expressive and flexible way to select nodes for pod scheduling, compared to nodeSelector. This is useful in more heterogeneous environments. The charts should allow configuring both hard and soft affinity.
Anti-affinity rules allow flexible scaling while avoiding scheduling to e.g. nodes that already have a pod that meets a certain rule. This is useful to avoid contention, emulate DaemonSet behaviour (while keeping dynamic scaling), etc.
Affinity rules present more expressive and flexible way to select nodes for pod scheduling, compared to
nodeSelector
. This is useful in more heterogeneous environments. The charts should allow configuring both hard and soft affinity.Anti-affinity rules allow flexible scaling while avoiding scheduling to e.g. nodes that already have a pod that meets a certain rule. This is useful to avoid contention, emulate
DaemonSet
behaviour (while keeping dynamic scaling), etc.See k8s docs for more info:
https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
The text was updated successfully, but these errors were encountered: