From a3c0cc68e800d7aa4f90d7f337d7e8bcaff09072 Mon Sep 17 00:00:00 2001 From: "David M. Lentz" Date: Wed, 15 Jan 2020 02:15:32 -0700 Subject: [PATCH] Update kube-scheduler.md (#18133) Fix typo. --- content/en/docs/concepts/scheduling/kube-scheduler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/scheduling/kube-scheduler.md b/content/en/docs/concepts/scheduling/kube-scheduler.md index ce5e4253ce..0fc46e48ee 100644 --- a/content/en/docs/concepts/scheduling/kube-scheduler.md +++ b/content/en/docs/concepts/scheduling/kube-scheduler.md @@ -35,7 +35,7 @@ kube-scheduler is designed so that, if you want and need to, you can write your own scheduling component and use that instead. For every newly created pod or other unscheduled pods, kube-scheduler -selects a optimal node for them to run on. However, every container in +selects an optimal node for them to run on. However, every container in pods has different requirements for resources and every pod also has different requirements. Therefore, existing nodes need to be filtered according to the specific scheduling requirements.