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

[BUG] While scheduling a reservation, reservation-ignored pods should not be counted in the node requested #2214

Open
saintube opened this issue Sep 27, 2024 · 0 comments
Labels
area/koord-scheduler kind/bug Create a report to help us improve

Comments

@saintube
Copy link
Member

What happened:

In the current koord-scheduler, a reservation cannot ignore the reservation-ignored pods on a node. For the reservation, the reservation-ignored pods are counted in the node requested. So when the reservation preemption is enabled, the reservation event preempts the reservation-ignored pods to release the node resources, and then get allocated by the reservation-ignored pods recreated by workload controllers.

What you expected to happen:

While scheduling a reservation, reservation-ignored pods should not be counted in the node requested

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • App version:
  • Kubernetes version (use kubectl version):
  • Install details (e.g. helm install args):
  • Node environment (for koordlet/runtime-proxy issue):
    • Containerd/Docker version:
    • OS version:
    • Kernal version:
    • Cgroup driver: cgroupfs/systemd
  • Others:
@saintube saintube added area/koord-scheduler kind/bug Create a report to help us improve labels Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/koord-scheduler kind/bug Create a report to help us improve
Projects
None yet
Development

No branches or pull requests

1 participant