From 067f8a937058108930bdf1746d47a79db873a0e4 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 12:49:55 +0530 Subject: [PATCH 01/16] Update custom scheduler example for v1.22+ Remove invalid scheduler args, add new scheduler args and add new Scheduler Configuration for defining scheduler name --- .../en/examples/admin/sched/my-scheduler.yaml | 32 ++++++++++++++++--- 1 file changed, 27 insertions(+), 5 deletions(-) diff --git a/content/en/examples/admin/sched/my-scheduler.yaml b/content/en/examples/admin/sched/my-scheduler.yaml index 800595862b..56e82dd4b1 100644 --- a/content/en/examples/admin/sched/my-scheduler.yaml +++ b/content/en/examples/admin/sched/my-scheduler.yaml @@ -30,6 +30,22 @@ roleRef: name: system:volume-scheduler apiGroup: rbac.authorization.k8s.io --- + +apiVersion: v1 +data: + my-scheduler-config.yaml: | + apiVersion: kubescheduler.config.k8s.io/v1beta2 + kind: KubeSchedulerConfiguration + profiles: + - schedulerName: my-scheduler + leaderElection: + leaderElect: false +kind: ConfigMap +metadata: + name: my-scheduler-config + namespace: kube-system + +--- apiVersion: apps/v1 kind: Deployment metadata: @@ -55,9 +71,8 @@ spec: containers: - command: - /usr/local/bin/kube-scheduler - - --address=0.0.0.0 - - --leader-elect=false - - --scheduler-name=my-scheduler + - --bind-address=0.0.0.0 + - --config=/etc/kubernetes/my-scheduler/my-scheduler-config.yaml image: gcr.io/my-gcp-project/my-kube-scheduler:1.0 livenessProbe: httpGet: @@ -74,7 +89,14 @@ spec: cpu: '0.1' securityContext: privileged: false - volumeMounts: [] + volumeMounts: + - name: config-volume + mountPath: /etc/kubernetes/my-scheduler hostNetwork: false hostPID: false - volumes: [] + volumes: + - name: config-volume + configMap: + # Provide the name of the ConfigMap containing the files you want + # to add to the container + name: my-scheduler-config From 0add8b4a53e5d94635185b378dde840265633b2d Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 13:30:24 +0530 Subject: [PATCH 02/16] Remove --bind-address kube-scheduler argument Defaults to 0.0.0.0 --- content/en/examples/admin/sched/my-scheduler.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/examples/admin/sched/my-scheduler.yaml b/content/en/examples/admin/sched/my-scheduler.yaml index 56e82dd4b1..2e179a3edc 100644 --- a/content/en/examples/admin/sched/my-scheduler.yaml +++ b/content/en/examples/admin/sched/my-scheduler.yaml @@ -71,7 +71,6 @@ spec: containers: - command: - /usr/local/bin/kube-scheduler - - --bind-address=0.0.0.0 - --config=/etc/kubernetes/my-scheduler/my-scheduler-config.yaml image: gcr.io/my-gcp-project/my-kube-scheduler:1.0 livenessProbe: From 6ec90297d02a546c51ea89411896a650927cd3df Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 13:31:18 +0530 Subject: [PATCH 03/16] 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 From 95be4e5e657787fea30a8059f97110ab693631d3 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 14:55:30 +0530 Subject: [PATCH 04/16] Update multiple scheduler with HA guide --- .../extend-kubernetes/configure-multiple-schedulers.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 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 468f4b5b1b..5069053283 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -119,11 +119,11 @@ pod in this list. To run multiple-scheduler with leader election enabled, you must do the following: -First, update the following fields in your YAML file: +First, update the following fields in the Scheduler Configuration of your YAML file: -* `--leader-elect=true` -* `--lock-object-namespace=` -* `--lock-object-name=` +* `leaderElection.leaderElect` to `true` +* `leaderElection.resourceNamespace` to `` +* `leaderElection.resourceName` to `` {{< note >}} The control plane creates the lock objects for you, but the namespace must already exist. From 8e250cf405ad9dedb1bee5f874c7f15e590db7d9 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 15:02:45 +0530 Subject: [PATCH 05/16] Update references to invalid --scheduler-name arg --- .../extend-kubernetes/configure-multiple-schedulers.md | 6 +++--- 1 file changed, 3 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 5069053283..721722041a 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -73,7 +73,7 @@ config. Save it as `my-scheduler.yaml`: 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. +the `kube-scheduler` during its initialization via `--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). @@ -177,8 +177,8 @@ scheduler in that pod spec. Let's look at three examples. {{< codenew file="admin/sched/pod3.yaml" >}} In this case, we specify that this pod should be scheduled using the scheduler that we - deployed - `my-scheduler`. Note that the value of `spec.schedulerName` should match the name supplied to the scheduler - command as an argument in the deployment config for the scheduler. + deployed - `my-scheduler`. Note that the value of `spec.schedulerName` should match the name supplied for the scheduler + in the `schedulerName` field of the mapping `KubeSchedulerProfile` of the scheduler. Save this file as `pod3.yaml` and submit it to the Kubernetes cluster. From b06baf8f8013903329edf28a1ea2288135309c84 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 16 Oct 2021 21:52:09 +0530 Subject: [PATCH 06/16] Re-order ConfigMap definition --- content/en/examples/admin/sched/my-scheduler.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/examples/admin/sched/my-scheduler.yaml b/content/en/examples/admin/sched/my-scheduler.yaml index 2e179a3edc..d8a5f669a7 100644 --- a/content/en/examples/admin/sched/my-scheduler.yaml +++ b/content/en/examples/admin/sched/my-scheduler.yaml @@ -32,6 +32,10 @@ roleRef: --- apiVersion: v1 +kind: ConfigMap +metadata: + name: my-scheduler-config + namespace: kube-system data: my-scheduler-config.yaml: | apiVersion: kubescheduler.config.k8s.io/v1beta2 @@ -40,10 +44,6 @@ data: - schedulerName: my-scheduler leaderElection: leaderElect: false -kind: ConfigMap -metadata: - name: my-scheduler-config - namespace: kube-system --- apiVersion: apps/v1 From 10846473acd1c8e38572730184dc051cf9467f0b Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Mon, 18 Oct 2021 10:21:13 +0530 Subject: [PATCH 07/16] Add reference to the created scheduler configuration CM Co-authored-by: Tim Bannister --- .../extend-kubernetes/configure-multiple-schedulers.md | 6 +++++- 1 file changed, 5 insertions(+), 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 721722041a..98c4aeb984 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -119,7 +119,11 @@ pod in this list. To run multiple-scheduler with leader election enabled, you must do the following: -First, update the following fields in the Scheduler Configuration of your YAML file: +First, update the scheduler configuration (earlier you applied a +`my-scheduler.yaml` file that included a ConfigMap named `my-scheduler-config`; the +scheduler configuration is in YAML format, within the `data` field of that ConfigMap). + +The fields to change in the inner KubeSchedulerConfiguration are: * `leaderElection.leaderElect` to `true` * `leaderElection.resourceNamespace` to `` From 9a0f0e25ea697fe6f978956ab4681599c1928917 Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Mon, 18 Oct 2021 20:28:17 +0530 Subject: [PATCH 08/16] 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 From dcbf15211824b608c10aa93b2702951271de1b5c Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Mon, 18 Oct 2021 20:29:53 +0530 Subject: [PATCH 09/16] Remove unnecessary reference to scheduler Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com> --- .../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 81c7bdf59e..2cb1e20dc6 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -182,7 +182,7 @@ scheduler in that pod spec. Let's look at three examples. In this case, we specify that this pod should be scheduled using the scheduler that we deployed - `my-scheduler`. Note that the value of `spec.schedulerName` should match the name supplied for the scheduler - in the `schedulerName` field of the mapping `KubeSchedulerProfile` of the scheduler. + in the `schedulerName` field of the mapping `KubeSchedulerProfile`. Save this file as `pod3.yaml` and submit it to the Kubernetes cluster. From fc257531188d38245d38de67b59c2be91777fdd0 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Mon, 18 Oct 2021 20:32:38 +0530 Subject: [PATCH 10/16] Remove unnecessary comment --- content/en/examples/admin/sched/my-scheduler.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/examples/admin/sched/my-scheduler.yaml b/content/en/examples/admin/sched/my-scheduler.yaml index d8a5f669a7..b44123b61a 100644 --- a/content/en/examples/admin/sched/my-scheduler.yaml +++ b/content/en/examples/admin/sched/my-scheduler.yaml @@ -96,6 +96,4 @@ spec: volumes: - name: config-volume configMap: - # Provide the name of the ConfigMap containing the files you want - # to add to the container name: my-scheduler-config From 35525d17b5d8dba54399fb4419364426b2f8df61 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Mon, 18 Oct 2021 20:44:13 +0530 Subject: [PATCH 11/16] Add extra details for clarity --- .../extend-kubernetes/configure-multiple-schedulers.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 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 2cb1e20dc6..f65cb29628 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -73,12 +73,14 @@ config. Save it as `my-scheduler.yaml`: 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 its initialization via `--config` command line argument. +the `kube-scheduler` during its initialization via `--config` command line argument. The configuration +file has been embedded within the ConfigMap `my-scheduler-config` which has been injected to the scheduler +Deployment via a volume. 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 +should be unique among all schedulers running in the cluster. 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. Also, note that we created a dedicated service account `my-scheduler` and bound the cluster role From eedbfd5724d41a79c478b570c653b5c3fc6d746d Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Tue, 2 Nov 2021 10:28:51 +0530 Subject: [PATCH 12/16] Add content best practices Co-authored-by: Rey Lejano --- .../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 f65cb29628..39f0f342c7 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -71,7 +71,7 @@ config. Save it as `my-scheduler.yaml`: {{< codenew file="admin/sched/my-scheduler.yaml" >}} -In the above manifest, we have used a [Scheduler Configuration](/docs/reference/scheduling/config/) +In the above manifest, you use 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 its initialization via `--config` command line argument. The configuration file has been embedded within the ConfigMap `my-scheduler-config` which has been injected to the scheduler From 514db9eb70568db913fb6deab5c3c19a234c5895 Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Tue, 2 Nov 2021 10:31:38 +0530 Subject: [PATCH 13/16] Improve and reorder the wording Co-authored-by: Rey Lejano --- .../tasks/extend-kubernetes/configure-multiple-schedulers.md | 4 +--- 1 file changed, 1 insertion(+), 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 39f0f342c7..f1f919e936 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -73,9 +73,7 @@ config. Save it as `my-scheduler.yaml`: In the above manifest, you use 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 its initialization via `--config` command line argument. The configuration -file has been embedded within the ConfigMap `my-scheduler-config` which has been injected to the scheduler -Deployment via a volume. +the `kube-scheduler` during initialization with the `--config` option. The `my-scheduler-config` ConfigMap stores the configuration file. The Pod of the`my-scheduler` Deployment mounts the `my-scheduler-config` ConfigMap as a volume. 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). From 7b6d84ec7c4efb6dec2747758ed64b7e1945e887 Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Tue, 2 Nov 2021 13:59:24 +0530 Subject: [PATCH 14/16] Use note short code to highlight the content Co-authored-by: Rey Lejano --- .../configure-multiple-schedulers.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 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 f1f919e936..700ef82480 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -75,13 +75,15 @@ In the above manifest, you use a [Scheduler Configuration](/docs/reference/sched to customize the behavior of your scheduler implementation. This configuration has been passed to the `kube-scheduler` during initialization with the `--config` option. The `my-scheduler-config` ConfigMap stores the configuration file. The Pod of the`my-scheduler` Deployment mounts the `my-scheduler-config` ConfigMap as a volume. -In the aforementioned Scheduler Configuration, your scheduler implementation has been represented via +In the aforementioned Scheduler Configuration, your scheduler implementation is 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 among all schedulers running in the cluster. 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 >}} +To determine if a scheduler is responsible for scheduling a specific Pod, the `spec.schedulerName` field in a +PodTemplate or Pod manifest must match the `schedulerName` field of the `KubeSchedulerProfile`. +All schedulers running in the cluster must have unique names. +{{< /note >}} -Also, note that we created a dedicated service account `my-scheduler` and bound the cluster role +Also, note that you create a dedicated service account `my-scheduler` and bind the ClusterRole `system:kube-scheduler` to it so that it can acquire the same privileges as `kube-scheduler`. Please see the From c5cb03ab13e4e101875e03a61689cad458ec782f Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Tue, 2 Nov 2021 14:01:35 +0530 Subject: [PATCH 15/16] Shorten the description on field updating Co-authored-by: Rey Lejano --- .../extend-kubernetes/configure-multiple-schedulers.md | 6 +----- 1 file changed, 1 insertion(+), 5 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 700ef82480..6fac32e1cf 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -121,11 +121,7 @@ pod in this list. To run multiple-scheduler with leader election enabled, you must do the following: -First, update the scheduler configuration (earlier you applied a -`my-scheduler.yaml` file that included a ConfigMap named `my-scheduler-config`; the -scheduler configuration is in YAML format, within the `data` field of that ConfigMap). - -The fields to change in the inner KubeSchedulerConfiguration are: +Update the following fields for the KubeSchedulerConfiguration in the `my-scheduler-config` ConfigMap in your YAML file: * `leaderElection.leaderElect` to `true` * `leaderElection.resourceNamespace` to `` From 7449bb36a0eaa7f2983fa8fae005e00f06496fa8 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Tue, 2 Nov 2021 19:56:21 +0530 Subject: [PATCH 16/16] Update config refs to KubeSchedulerConfiguration --- .../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 6fac32e1cf..bed250a170 100644 --- a/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md +++ b/content/en/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md @@ -71,7 +71,7 @@ config. Save it as `my-scheduler.yaml`: {{< codenew file="admin/sched/my-scheduler.yaml" >}} -In the above manifest, you use a [Scheduler Configuration](/docs/reference/scheduling/config/) +In the above manifest, you use a [KubeSchedulerConfiguration](/docs/reference/scheduling/config/) to customize the behavior of your scheduler implementation. This configuration has been passed to the `kube-scheduler` during initialization with the `--config` option. The `my-scheduler-config` ConfigMap stores the configuration file. The Pod of the`my-scheduler` Deployment mounts the `my-scheduler-config` ConfigMap as a volume.