Skip to content
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 PodTopologySpread & NodePort in predicate #3895

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bibibox
Copy link
Contributor

@bibibox bibibox commented Dec 16, 2024

This is a supplement to #3840

@volcano-sh-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign k82cn
You can assign the PR to them by writing /assign @k82cn in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@volcano-sh-bot volcano-sh-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 16, 2024
@bibibox bibibox force-pushed the fix_predicate_podtopologyspread branch from 5f7c260 to 0be4606 Compare December 16, 2024 09:07
@volcano-sh-bot volcano-sh-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 16, 2024
@bibibox bibibox changed the title Fix PodTopologySpread in predicate Fix PodTopologySpread & NodePort in predicate Dec 16, 2024
// TODO: Currently, preemption is not supported when NodePort filtering fails.
// Once supported, the logic here should be removed.
// See https://github.com/volcano-sh/volcano/issues/3845
nodePortStatus.Code = api.UnschedulableAndUnresolvable
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does a node port not support preemption?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to inter-pod affinity, passing resource comparison during preemption does not guarantee that the pod occupying the node’s port will be preempted.

@bibibox bibibox force-pushed the fix_predicate_podtopologyspread branch from 0be4606 to 8088d0d Compare December 16, 2024 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants