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
fix(*):inter pod affinity default min score is zero #98096
Conversation
Hi @leileiwan. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
edit: actually, nevermind, this wouldn't change the ordering, just the score values |
/triage accepted This PR makes the differentiation between inter-pod affinity scores stronger, and so resulting in higher impact of inter-pod affinity scores on the final ordering. This bug seems to exist since the inception of the feature, it is worth a release note: "Scores from InterPodAffinity have stronger differentiation." |
@@ -252,7 +253,8 @@ func (pl *InterPodAffinity) NormalizeScore(ctx context.Context, cycleState *fram | |||
return nil | |||
} | |||
|
|||
var maxCount, minCount int64 | |||
var minCount int64 = math.MaxInt64 | |||
var maxCount int64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should initialize maxCount to -math.MaxInt64 since anti-affinity scores are in the negative.
please update the release note in the description with "Scores from InterPodAffinity have stronger differentiation." |
ok, done |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, leileiwan 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: