https://github.com/elementtech/kube-arch-scheduler
An architecture-aware Kubernetes scheduler plugin
https://github.com/elementtech/kube-arch-scheduler
kubernetes kubernetes-controller kubernetes-operator plugin scheduler scheduler-plugin schedulers
Last synced: 10 months ago
JSON representation
An architecture-aware Kubernetes scheduler plugin
- Host: GitHub
- URL: https://github.com/elementtech/kube-arch-scheduler
- Owner: ElementTech
- License: apache-2.0
- Created: 2023-06-09T08:13:36.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-05-03T20:58:33.000Z (about 2 years ago)
- Last Synced: 2024-06-22T19:08:34.516Z (almost 2 years ago)
- Topics: kubernetes, kubernetes-controller, kubernetes-operator, plugin, scheduler, scheduler-plugin, schedulers
- Language: Go
- Homepage: https://elementtech.github.io/kube-arch-scheduler/
- Size: 30.1 MB
- Stars: 31
- Watchers: 2
- Forks: 8
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Kubernetes Architecture Scheduler Plugin
An image architecture aware Kubernetes scheduler plugin
**kube-arch-scheduler** is a kubernetes scheduler filter plugin that will filter nodes by the compatibility of the container image architectures (platforms) present in a Pod. It can also assign weight to each architecture, so that pods can prefer sitting on a specific one.
## Deploy - Helm
```bash
helm repo add kube-arch-scheduler https://elementtech.github.io/kube-arch-scheduler/
helm repo update
helm install -n kube-system kube-arch-scheduler/kube-arch-scheduler
```
**Core Values:**
```yaml
# While enabled, this will add the scheduler to the default scheduler plugins,
# this will make it affect all pods in the cluster.
addToDefaultScheduler: true
# If addToDefaultScheduler if false, this will be the name of the scheduler,
# and it will only affect pods with: [schedulerName: kube-arch-scheduler].
nonDefaultSchedulerName: kube-arch-scheduler
# This is relevant if your Kubernetes pod does not have permissions to your private registries.
# dockerconfig.json is a base64 encoded docker config file, it will be used
# to pull the image manifests. The pod needs to have the secret mounted at
# /root/.docker/config.json. This is only needed if you are using a private
# registry. If you are using a public registry, you can leave this empty.
dockerConfigSecretName: ""
# The weight of each architecture,
# if a pod can sit on both, it will prefer the one with the higher weight.
# The default weight of undefined architectures is 0, meaning none will have
# any particular preference.
weight:
amd64: 0
arm64: 0
arm: 0
ppc64le: 0
s390x: 0
riscv64: 0
```
## Development
Use this command to run the scheduler locally while connected to your Kubernetes cluster's context:
```shell
go run main.go --authentication-kubeconfig ~/.kube/config --authorization-kubeconfig ~/.kube/config --config=./example/scheduler-config.yaml --v=2
```
You can use the [example deployment](example/busybox.yaml) in order to test the scheduler on a live pod:
```
kubectl deploy -f example/busybox.yaml
```
## Support
