From 5dac62b1875f24ae45d8886aea9869acfcd1e81d Mon Sep 17 00:00:00 2001 From: Piotr Szczesniak Date: Thu, 8 Oct 2015 07:19:07 +0200 Subject: [PATCH] Fixed formatting in rescheduler proposal --- docs/proposals/rescheduler.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/proposals/rescheduler.md b/docs/proposals/rescheduler.md index 88747d0806..512064f27a 100644 --- a/docs/proposals/rescheduler.md +++ b/docs/proposals/rescheduler.md @@ -144,6 +144,7 @@ A key design question for a Rescheduler is how much knowledge it needs about the ## Appendix: Integrating rescheduler with cluster auto-scaler (scale up) For scaling up the cluster, a reasonable workflow might be: + 1. pod horizontal auto-scaler decides to add one or more Pods to a service, based on the metrics it is observing 1. the Pod goes PENDING due to lack of a suitable node with sufficient resources 1. rescheduler notices the PENDING Pod and determines that the Pod cannot schedule just by rearranging existing Pods (while respecting SLOs)