-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Track pods with required anti-affinity #94059
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b4d91da
to
a5dae7c
Compare
LGTM. Please squash. |
This is a performance optimization that reduces the overhead of inter-pod affinity PreFilter calculaitons. Basically eliminates that overhead when no pods in the cluster use required pod anti-affinity. This offered 20% improvement on 5k clusters for preferred anti-affinity benchmarks.
a5dae7c
to
a8873e1
Compare
done. |
/lgtm |
/priority important-longterm |
/kind bug |
…pshot. Cherry pick of kubernetes#94059 on release-1.19. This is fixes a performance regression in the cluster autoscaler which started to execute PreFilter explicitly since 1.18.
…upstream-release-1.19 Automated cherry pick of #94059: Track pods with required anti-affinity
cherry pick of #94059: Track pods with required anti-affinity
What type of PR is this?
/kind feature
What this PR does / why we need it:
This is a performance optimization that reduces the overhead of inter-pod affinity PreFilter calculaitons. Basically
eliminates that overhead when no pods in the cluster use required pod anti-affinity. This offered 20% improvement on 5k clusters for preferred anti-affinity benchmarks.
Does this PR introduce a user-facing change?: