@@ -8,7 +8,7 @@ weight: 1
8
8
9
9
<!-- toc -->
10
10
- [ Create a Kubernetes Cluster] ( #create-a-kubernetes-cluster )
11
- - [ Install release v0.27 .8 and use Coscheduling] ( #install-release-v0278 -and-use-coscheduling )
11
+ - [ Install release v0.28 .8 and use Coscheduling] ( #install-release-v0288 -and-use-coscheduling )
12
12
- [ As a second scheduler] ( #as-a-second-scheduler )
13
13
- [ As a single scheduler (replacing the vanilla default-scheduler)] ( #as-a-single-scheduler-replacing-the-vanilla-default-scheduler )
14
14
- [ Test Coscheduling] ( #test-coscheduling )
@@ -28,7 +28,7 @@ If you do not have a cluster yet, create one by using one of the following provi
28
28
* [ kubeadm] ( https://kubernetes.io/docs/reference/setup-tools/kubeadm/ )
29
29
* [ minikube] ( https://minikube.sigs.k8s.io/ )
30
30
31
- ## Install release v0.27 .8 and use Coscheduling
31
+ ## Install release v0.28 .8 and use Coscheduling
32
32
33
33
Note: we provide two ways to install the scheduler-plugin artifacts: as a second scheduler
34
34
and as a single scheduler. Their pros and cons are as below:
@@ -150,9 +150,9 @@ any vanilla Kubernetes scheduling capability. Instead, a lot of extra out-of-box
150
150
> - --kubeconfig=/etc/kubernetes/scheduler.conf
151
151
> - --leader-elect=true
152
152
19,20c20
153
- < image: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.27 .8
153
+ < image: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.28 .8
154
154
---
155
- > image: registry.k8s.io/kube-scheduler:v1.27 .8
155
+ > image: registry.k8s.io/kube-scheduler:v1.28 .8
156
156
50,52d49
157
157
< - mountPath: /etc/kubernetes/sched-cc.yaml
158
158
< name: sched-cc
@@ -164,14 +164,14 @@ any vanilla Kubernetes scheduling capability. Instead, a lot of extra out-of-box
164
164
< name: sched-cc
165
165
` ` `
166
166
167
- 1. Verify that kube-scheduler pod is running properly with a correct image: ` registry.k8s.io/scheduler-plugins/kube-scheduler:v0.27 .8`
167
+ 1. Verify that kube-scheduler pod is running properly with a correct image: ` registry.k8s.io/scheduler-plugins/kube-scheduler:v0.28 .8`
168
168
169
169
` ` ` bash
170
170
$ kubectl get pod -n kube-system | grep kube-scheduler
171
171
kube-scheduler-kind-control-plane 1/1 Running 0 3m27s
172
172
173
173
$ kubectl get pods -l component=kube-scheduler -n kube-system -o=jsonpath=" {.items[0].spec.containers[0].image}{'\n'}"
174
- registry.k8s.io/scheduler-plugins/kube-scheduler:v0.27 .8
174
+ registry.k8s.io/scheduler-plugins/kube-scheduler:v0.28 .8
175
175
` ` `
176
176
177
177
> ** ⚠️Troubleshooting:** If the kube-scheudler is not up, you may need to restart kubelet service inside the kind control plane (` systemctl restart kubelet.service` )
0 commit comments