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
Setting nodeAntiAffinity prevents running steps on the same host when pod retries.
This is configured by patching requiredDuringSchedulingIgnoredDuringExecution filter out hostnode in the pod affinity.
However, we could encounter a situation where retry exhausts all the hostnodes.
We want this configuration to be more flexible,
e.g. supports preferredDuringSchedulingIgnoredDuringExecution
e.g. supports configuring maximum number of hosts excluded
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
What change needs making?
Setting
nodeAntiAffinity
prevents running steps on the same host when pod retries.This is configured by patching
requiredDuringSchedulingIgnoredDuringExecution
filter out hostnode in the pod affinity.However, we could encounter a situation where retry exhausts all the hostnodes.
We want this configuration to be more flexible,
e.g. supports
preferredDuringSchedulingIgnoredDuringExecution
e.g. supports configuring maximum number of hosts excluded
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: