44
55<!-- toc -->
66- [ Create a Kubernetes Cluster] ( #create-a-kubernetes-cluster )
7- - [ Install release v0.27 .8 and use Coscheduling] ( #install-release-v0278 -and-use-coscheduling )
7+ - [ Install release v0.28 .8 and use Coscheduling] ( #install-release-v0288 -and-use-coscheduling )
88 - [ As a second scheduler] ( #as-a-second-scheduler )
99 - [ As a single scheduler (replacing the vanilla default-scheduler)] ( #as-a-single-scheduler-replacing-the-vanilla-default-scheduler )
1010- [ Test Coscheduling] ( #test-coscheduling )
@@ -24,7 +24,7 @@ If you do not have a cluster yet, create one by using one of the following provi
2424* [ kubeadm] ( https://kubernetes.io/docs/reference/setup-tools/kubeadm/ )
2525* [ minikube] ( https://minikube.sigs.k8s.io/ )
2626
27- ## Install release v0.27 .8 and use Coscheduling
27+ ## Install release v0.28 .8 and use Coscheduling
2828
2929Note: we provide two ways to install the scheduler-plugin artifacts: as a second scheduler
3030and as a single scheduler. Their pros and cons are as below:
@@ -146,9 +146,9 @@ any vanilla Kubernetes scheduling capability. Instead, a lot of extra out-of-box
146146 - - --kubeconfig=/etc/kubernetes/scheduler.conf
147147 - - --leader-elect=true
148148 19,20c20
149- + image: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.27 .8
149+ + image: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.28 .8
150150 ---
151- - image: registry.k8s.io/kube-scheduler:v1.27 .8
151+ - image: registry.k8s.io/kube-scheduler:v1.28 .8
152152 50,52d49
153153 + - mountPath: /etc/kubernetes/sched-cc.yaml
154154 + name: sched-cc
@@ -160,14 +160,14 @@ any vanilla Kubernetes scheduling capability. Instead, a lot of extra out-of-box
160160 + name: sched-cc
161161 ` ` `
162162
163- 1. Verify that kube-scheduler pod is running properly with a correct image: ` registry.k8s.io/scheduler-plugins/kube-scheduler:v0.27 .8`
163+ 1. Verify that kube-scheduler pod is running properly with a correct image: ` registry.k8s.io/scheduler-plugins/kube-scheduler:v0.28 .8`
164164
165165 ` ` ` bash
166166 $ kubectl get pod -n kube-system | grep kube-scheduler
167167 kube-scheduler-kind-control-plane 1/1 Running 0 3m27s
168168
169169 $ kubectl get pods -l component=kube-scheduler -n kube-system -o=jsonpath=" {.items[0].spec.containers[0].image}{'\n'}"
170- registry.k8s.io/scheduler-plugins/kube-scheduler:v0.27 .8
170+ registry.k8s.io/scheduler-plugins/kube-scheduler:v0.28 .8
171171 ` ` `
172172
173173 > ** ⚠️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