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

rm-wg feedback changes #2

Closed

Conversation

sjenning
Copy link

NoExecute that prevents BestEffort and Burstable QoS class pods from
running on the node. BestEffort and Burstable QoS class pods are
evicted from the node.
1. The CPU manager sets a `CPUPressure` node condition to `true`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

state why this is preferred versus reserving some slack cpu for scavengers? i agree with this approach, but woudl like to explain that we dont think the complexity to support scavengers on nodes with this configuration is worth it.

ConnorDoyle pushed a commit that referenced this pull request Aug 2, 2017
ConnorDoyle pushed a commit that referenced this pull request Aug 2, 2017
Wrong link to sig lead github page - Take #2
@sjenning sjenning closed this Aug 23, 2017
@ConnorDoyle
Copy link
Owner

Sorry @sjenning if this should have been merged, totally missed it. Ping in PR if you make a new one against upstream and I will review ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants