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

Fix typo in CA FAQ. #458

Merged
merged 1 commit into from
Nov 9, 2017
+1 −1
Merged

Fix typo in CA FAQ. #458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion cluster-autoscaler/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,7 +201,7 @@ Nothing changes for Pods with priority greater or equal to cut off and pods with
Default priority cut off is 0. It can be changed using flag but we discourage it.
Cluster Autoscaler also don't trigger scale up if an unschedulable pod is waiting for lower priority pod preemption.

Prior 1.9 CA didn't take priorities into account.
Prior to 1.9 CA didn't take priorities into account.

More about Pod Priority and Preemption:
* [Priority in Kubernetes API](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/scheduling/pod-priority-api.md),
Expand Down