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] NodeNUMAResource should support allocating reserved cpus when CPU amplification enabled #2158

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

Comments

@saintube
Copy link
Member

saintube commented Aug 6, 2024

What happened:

The fine-grained cpu orchestration has already supported allocating reserved CPUs for the owner pods when the node does not enable the cpu amplification. But when the cpu amplification is enabled, the owner pod can fail to allocate the reserved CPUs because of insufficient CPUs.

What you expected to happen:

Both when the cpu amplification is disabled and it is enabled, the owner pods can allocate the reserved CPUs correctly.

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

Anything else we need to know?:

Environment:

  • App version: v1.5.0
  • 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 Aug 6, 2024
@songtao98 songtao98 added this to the someday milestone Aug 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

2 participants