diff options
| author | Piotr Szczesniak <pszczesniak@google.com> | 2015-10-08 07:19:07 +0200 |
|---|---|---|
| committer | Piotr Szczesniak <pszczesniak@google.com> | 2015-10-08 07:19:07 +0200 |
| commit | 2ff148ae5c6534a1dcabd49759cc5ebbb35df180 (patch) | |
| tree | cbe7009518431695de7530d40d1657fc6fe189b9 /rescheduler.md | |
| parent | 70ab6385596f0dc1de21bfdd03669133176c6de3 (diff) | |
Fixed formatting in rescheduler proposal
Diffstat (limited to 'rescheduler.md')
| -rw-r--r-- | rescheduler.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/rescheduler.md b/rescheduler.md index 88747d08..512064f2 100644 --- a/rescheduler.md +++ b/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) |