k8s-scheduler-extender-example's Introduction

k8s-scheduler-extender-example

This is an example of Kubernetes Scheduler Extender

How to

0. checkout the repo

$ git clone [email protected]:everpeace/k8s-scheduler-extender-example.git
$ cd k8s-scheduler-extender-example
$ git submodule update --init

1. buid a docker image

$ IMAGE=YOUR_ORG/YOUR_IMAGE:YOUR_TAG

$ docker build . -t "${IMAGE}"
$ docker push "${IMAGE}"

2. deploy `my-scheduler` in `kube-system` namespace

please see ConfigMap in extender.yaml for scheduler policy json which includes scheduler extender config.

# bring up the kube-scheduler along with the extender image you've just built
$ sed 's/a\/b:c/'$(echo "${IMAGE}" | sed 's/\//\\\//')'/' extender.yaml | kubectl apply -f -

For ease of observation, start streaming logs from the extender:

$ kubectl -n kube-system logs deploy/my-scheduler -c my-scheduler-extender-ctr -f
[  warn ] 2018/11/07 08:41:40 main.go:84: LOG_LEVEL="" is empty or invalid, fallling back to "INFO".
[  info ] 2018/11/07 08:41:40 main.go:98: Log level was set to INFO
[  info ] 2018/11/07 08:41:40 main.go:116: server starting on the port :80

Open up an another termianl and proceed.

3. schedule test pod

you will see test-pod will be scheduled by my-scheduler.

$ kubectl create -f test-pod.yaml

$ kubectl describe pod test-pod
Name:         test-pod
...
Events:
  Type    Reason                 Age   From               Message
  ----    ------                 ----  ----               -------
  Normal  Scheduled              25s   my-scheduler       Successfully assigned test-pod to minikube
  Normal  SuccessfulMountVolume  25s   kubelet, minikube  MountVolume.SetUp succeeded for volume "default-token-wrk5s"
  Normal  Pulling                24s   kubelet, minikube  pulling image "nginx"
  Normal  Pulled                 8s    kubelet, minikube  Successfully pulled image "nginx"
  Normal  Created                8s    kubelet, minikube  Created container
  Normal  Started                8s    kubelet, minikube  Started container

License

Copyright 2018 Shingo Omura <https://github.com/everpeace>

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

k8s-scheduler-extender-example's Issues

If don't define schedulerName in the Application defination, whether the default scheduler could call the extender auto?

Hi,
I have a question about the scheduler extender example, in the guide, it requests the Application to add schedulerName in the Application yaml defination.

spec:
      schedulerName: my-scheduler

I want to ask, whether there is method users need NOT to set the schedulerName and the default scheduler will call the scheduler extender auto?

Thanks

Unable to see Priority call

Hi,

Thanks for sharing this example. I do have a question about priority. I try to observe priority api call by adding some debug logging, but I am not able to see these code has been hit. For example,

Func: func(_ v1.Pod, nodes []v1.Node) (schedulerapi.HostPriorityList, error) {
log.Print("*************** Available Node for Priority ***********")
...

It looks like the api call has not been reached to that function. Do you have any suggestions?

Thanks.

Dependency management and ease the import

The packages used by [email protected] can be easily managed by dep.
The shared go files, such as
predicate.go
preemption.go
prioritize.go
routes.go
bind.go
and some variables can be grouped into a package for others to import easily.

Recommend Projects

everpeace / k8s-scheduler-extender-example Goto Github PK