Merge pull request #20691 from alculquicondor/fix-2nd-scheduler

Add missing ClusterRoleBinding and leases permissions for running 2nd scheduler

content/en/docs/tasks/administer-cluster/configure-multiple-schedulers.md

@@ -108,20 +108,27 @@ my-scheduler-lnf4s-4744f                       1/1       Running   0          2m
 You should see a "Running" my-scheduler pod, in addition to the default kube-scheduler
 pod in this list.
 
+### Enable leader election
+
 To run multiple-scheduler with leader election enabled, you must do the following:
 
 First, update the following fields in your YAML file:
 
 * `--leader-elect=true`
-* `--lock-object-namespace=lock-object-namespace`
+* `--lock-object-namespace=<lock-object-namespace>`
-* `--lock-object-name=lock-object-name`
+* `--lock-object-name=<lock-object-name>`
 
-If RBAC is enabled on your cluster, you must update the `system:kube-scheduler` cluster role. Add your scheduler name to the resourceNames of the rule applied for endpoints resources, as in the following example:
+{{< note >}}
+The control plane creates the lock objects for you, but the namespace must already exist.
+You can use the `kube-system` namespace.
+{{< /note >}}
+
+If RBAC is enabled on your cluster, you must update the `system:kube-scheduler` cluster role. Add your scheduler name to the resourceNames of the rule applied for `endpoints` and `leases` resources, as in the following example:
 ```
 kubectl edit clusterrole system:kube-scheduler
 ```
 ```yaml
-- apiVersion: rbac.authorization.k8s.io/v1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
   annotations:
@@ -130,6 +137,22 @@ kubectl edit clusterrole system:kube-scheduler
     kubernetes.io/bootstrapping: rbac-defaults
   name: system:kube-scheduler
 rules:
+- apiGroups:
+  - coordination.k8s.io
+  resources:
+  - leases
+  verbs:
+  - create
+- apiGroups:
+  - coordination.k8s.io
+  resourceNames:
+  - kube-scheduler
+  - my-scheduler
+  resources:
+  - leases
+  verbs:
+  - get
+  - update
 - apiGroups:
   - ""
   resourceNames:

content/en/examples/admin/sched/my-scheduler.yaml

@@ -17,6 +17,19 @@ roleRef:
   name: system:kube-scheduler
   apiGroup: rbac.authorization.k8s.io
 ---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: my-scheduler-as-volume-scheduler
+subjects:
+- kind: ServiceAccount
+  name: my-scheduler
+  namespace: kube-system
+roleRef:
+  kind: ClusterRole
+  name: system:volume-scheduler
+  apiGroup: rbac.authorization.k8s.io
+---
 apiVersion: apps/v1
 kind: Deployment
 metadata: