From 6ec90297d02a546c51ea89411896a650927cd3df Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 13:31:18 +0530 Subject: [PATCH] Update multiple scheduler deployment guide --- .../configure-multiple-schedulers.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) 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 d44e6897b0..468f4b5b1b 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -71,15 +71,24 @@ config. Save it as `my-scheduler.yaml`: {{< codenew file="admin/sched/my-scheduler.yaml" >}} -An important thing to note here is that the name of the scheduler specified as an -argument to the scheduler command in the container spec 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. +In the above manifest, we have used a [Scheduler Configuration](/docs/reference/scheduling/config/) +to customize the behavior of your scheduler implementation. This configuration has been passed to +the `kube-scheduler` during initialization via its `--config` command line argument. + +In the aforementioned Scheduler Configuration, your scheduler implementation has been represented via +a [KubeSchedulerProfile](/docs/reference/config-api/kube-scheduler-config.v1beta2/#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerProfile). +An important thing to note here is that the name of the scheduler specified via `schedulerName` field of the defined `KubeSchedulerProfile`, +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 `system:kube-scheduler` to it so that it can acquire the same privileges as `kube-scheduler`. Please see the [kube-scheduler documentation](/docs/reference/command-line-tools-reference/kube-scheduler/) for -detailed description of other command line arguments. +detailed description of other command line arguments and +[Scheduler Configuration reference](https://kubernetes.io/docs/reference/config-api/kube-scheduler-config.v1beta2/) for +detailed description of other customizable `kube-scheduler` configurations. ## Run the second scheduler in the cluster