github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #18421 from zhengguoyong/small_typo 

Auto commit by PR queue bot
pull/6/head
k8s-merge-robot 2015-12-09 21:46:01 -08:00
parent c6cb9d7201 360e8de81a
commit 15a20bd96a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/proposals/rescheduler.md
View File

@ -107,7 +107,7 @@ antagonism and ask the rescheduler to move one of the antagonists to a new node.
The vast majority of users probably only care about rescheduling for three scenarios: The vast majority of users probably only care about rescheduling for three scenarios:
1. Move Pods around to get a PENDING Pod to schedule 1. Move Pods around to get a PENDING Pod to schedule
1. Redistribute Pods onto new nodes added by a cluster auto-scaler when ther are no PENDING Pods 1. Redistribute Pods onto new nodes added by a cluster auto-scaler when there are no PENDING Pods
1. Move Pods around when CPU starvation is detected on a node 1. Move Pods around when CPU starvation is detected on a node
## Design considerations and design space ## Design considerations and design space