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

docs: adding clarification to HighNodeUtilization's purpose #592

Merged
merged 2 commits into from
Aug 13, 2021
Merged

docs: adding clarification to HighNodeUtilization's purpose #592

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
448dbce
docs: adding clarification to HighNodeUtilization's purpose
chrisjohnson00 Jun 24, 2021
d4fa83f
chore: PR feedback
chrisjohnson00 Jun 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,9 +267,11 @@ under utilized frequently or for a short period of time. By default, `numberOfNo

### HighNodeUtilization

This strategy finds nodes that are under utilized and evicts pods in the hope that these pods will be scheduled compactly into fewer nodes.
This strategy **must** be used with the
scheduler strategy `MostRequestedPriority`. The parameters of this strategy are configured under `nodeResourceUtilizationThresholds`.
This strategy finds nodes that are under utilized and evicts pods from the node in the hope that these pods will be
chrisjohnson00 marked this conversation as resolved.
Show resolved Hide resolved
scheduled onto other nodes. Used in conjunction with node auto-scaling, this strategy is intended to help trigger down
scaling of under utilized nodes.
This strategy **must** be used with the scheduler strategy `MostRequestedPriority`. The parameters of this strategy are
configured under `nodeResourceUtilizationThresholds`.

The under utilization of nodes is determined by a configurable threshold `thresholds`. The threshold
`thresholds` can be configured for cpu, memory, number of pods, and extended resources in terms of percentage. The percentage is
Expand Down