@@ -8,7 +8,7 @@ weight: 1
88
99<!-- toc -->
1010- [ Create a Kubernetes Cluster] ( #create-a-kubernetes-cluster )
11- - [ Install release v0.32.7 and use Coscheduling] ( #install-release-v0327 -and-use-coscheduling )
11+ - [ Install release v0.33.5 and use Coscheduling] ( #install-release-v0335 -and-use-coscheduling )
1212 - [ As a second scheduler] ( #as-a-second-scheduler )
1313 - [ As a single scheduler (replacing the vanilla default-scheduler)] ( #as-a-single-scheduler-replacing-the-vanilla-default-scheduler )
1414- [ 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
2828* [ kubeadm] ( https://kubernetes.io/docs/reference/setup-tools/kubeadm/ )
2929* [ minikube] ( https://minikube.sigs.k8s.io/ )
3030
31- ## Install release v0.32.7 and use Coscheduling
31+ ## Install release v0.33.5 and use Coscheduling
3232
3333Note: we provide two ways to install the scheduler-plugin artifacts: as a second scheduler
3434and as a single scheduler. Their pros and cons are as below:
@@ -150,7 +150,7 @@ any vanilla Kubernetes scheduling capability. Instead, a lot of extra out-of-box
150150 > - --kubeconfig=/etc/kubernetes/scheduler.conf
151151 > - --leader-elect=true
152152 19,20c20
153- < image: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.32.7
153+ < image: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.33.5
154154 ---
155155 > image: registry.k8s.io/kube-scheduler:v1.28.9
156156 50,52d49
@@ -164,14 +164,14 @@ any vanilla Kubernetes scheduling capability. Instead, a lot of extra out-of-box
164164 < name: sched-cc
165165 ` ` `
166166
167- 1. Verify that kube-scheduler pod is running properly with a correct image: ` registry.k8s.io/scheduler-plugins/kube-scheduler:v0.32.7 `
167+ 1. Verify that kube-scheduler pod is running properly with a correct image: ` registry.k8s.io/scheduler-plugins/kube-scheduler:v0.33.5 `
168168
169169 ` ` ` bash
170170 $ kubectl get pod -n kube-system | grep kube-scheduler
171171 kube-scheduler-kind-control-plane 1/1 Running 0 3m27s
172172
173173 $ 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.32.7
174+ registry.k8s.io/scheduler-plugins/kube-scheduler:v0.33.5
175175 ` ` `
176176
177177 > ** ⚠️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