From 9a0f0e25ea697fe6f978956ab4681599c1928917 Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Mon, 18 Oct 2021 20:28:17 +0530 Subject: [PATCH] Rearrange words for better meaning Co-authored-by: Deepak Gupta --- .../tasks/extend-kubernetes/configure-multiple-schedulers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md index 98c4aeb984..81c7bdf59e 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -81,7 +81,7 @@ An important thing to note here is that the name of the scheduler specified via should be unique. This is the name that is matched against the value of the optional `spec.schedulerName` on pods, to determine whether this scheduler is responsible for scheduling a particular pod. -Note also that we created a dedicated service account `my-scheduler` and bind the cluster role +Also, note that we created a dedicated service account `my-scheduler` and bound the cluster role `system:kube-scheduler` to it so that it can acquire the same privileges as `kube-scheduler`. Please see the