Skip to content

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

@ppalucki

Description

@ppalucki

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions