From 360e8de81aae8503ae13e0361c75d7a63d4d87a2 Mon Sep 17 00:00:00 2001 From: zhengguoyong Date: Wed, 9 Dec 2015 16:35:48 +0800 Subject: [PATCH] Fix small typo --- docs/proposals/rescheduler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/proposals/rescheduler.md b/docs/proposals/rescheduler.md index 550c227052..f10eb6d38f 100644 --- a/docs/proposals/rescheduler.md +++ b/docs/proposals/rescheduler.md @@ -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: 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 ## Design considerations and design space