-
Notifications
You must be signed in to change notification settings - Fork 25
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
build: update to controller-tools 0.14.0. #263
Conversation
- Built-in "reserved" and "default" balloon types are no longer special cases. They can be configured with the same parameters as user-defined balloons. Before this change their configuration was limited to few parameters. - The reserved balloon inflates and deflates if required by containers and allowed by minCPUs and maxCPUs. - Default balloons (which can be numerous now) never share CPUs with the reserved balloon. - Overcommitting reserved CPU resources is no more possible. Creating reserved containers will fail if there are not enough CPUs in the reserved balloon. - Explicit ReservedResources cpuset no more defines exactly the CPUs allocated to the reserved balloon. Instead, they are strongly preferred for that purpose. This happens implicitly through the same mechanism as explicit preferCloseToDevices. - Fixes: AllocatorPriority did not have proper effect. Now it enables high-priority user-defined balloons to allocate CPUs even before the reserved balloon. - Fixes: AvailableResources and ReservedResources had effect only when the policy was started, but not on reconfiguration. Now they can be changed in reconfiguration. Signed-off-by: Antti Kervinen <[email protected]>
In addition to testing resising the reserved balloon, the basic placement test is changed because it relied on overcommitting reserved CPUs. Signed-off-by: Antti Kervinen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Update controller-tools to 0.14.0. It handles some errors better than simply throwing a panic, leaving the user with little to no hint about what is really wrong. Regenerate CRDs since this version also generates multiline YAML strings differently than 0.12.0. Signed-off-by: Krisztian Litkey <[email protected]>
76a7531
to
def905b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
But let's wait for #254 |
Update controller-tools to 0.14.0. It handles some errors better than simply throwing a panic, leaving the user with little to no hint about what is really wrong. Regenerate CRDs since this version also generates multiline YAML strings differently than 0.12.0.