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 PodToplogySpread plugin violates maxSkew #2929
Conversation
node.AddPod(pod) | ||
klog.V(4).Infof("node order, update pod %s/%s allocate to node [%s]", pod.Namespace, pod.Name, nodeName) | ||
} | ||
}, | ||
DeallocateFunc: func(event *framework.Event) { |
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.
@Monokaix Don't we need to remove the DeallocateFunc?
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.
yeah it should be removed too.
@Monokaix please take a look at the e2e failure case |
Signed-off-by: Xuzheng Chang <changxuzheng@huawei.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: william-wang 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 |
This pr #2606 refact nodeorder and predict plugin and move
util.NewPodListerFromNode(ssn)
from plugin local to global variable, so we just need add pod into cache once at eventHandler.fix #2928