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.

Sign up for GitHub

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

Jump to bottom

Balloons policy reserved cpuset is not validated against actually available cpus #904

Open
ppalucki opened this issue Oct 14, 2022 · 0 comments
Open

Balloons policy reserved cpuset is not validated against actually available cpus #904

ppalucki opened this issue Oct 14, 2022 · 0 comments

Comments

@ppalucki
Copy link
Contributor

Describe the bug
Configuration for balloons policy set Reserved cpuset=15 but machine has only 8 cpus - my pods stuck in CrashLoopBackOff state

I had this fallback.cfg
image

and applied default configuraiton:
image

now my pods:
image

Expected behavior
Reject configuration because Reserved CPU = 15 is out of available cpus (max is 7)

To Reproduce
set reserved cpu > availabe cpus

Environment
VM: m4.2xlarge
has only 8 cpus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ppalucki