## Overview``The Kubernetes scheduler is a policy-rich, topology-aware, workload-specific function that significantly impacts availability, performance, and capacity. The scheduler needs to take into account individual and collective resource requirements, quality of service requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference, deadlines, and so on. Workload-specific requirements will be exposed through the API as necessary.``(the above synopsis is from: https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/).In order to view the list of options for running kube-scheduler, please refer to the "Options" section in the same documentation:https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/## Additional kube-scheduler resourcesThe official Kubernetes Reference documentation provides information on the Kubernetes Scheduler:* https://kubernetes.io/docs/concepts/scheduling-eviction/* https://github.com/kubernetes/kubernetes#readme## Downloading and building kube-scheduler from the Iron Bank1. Go to the webpage for kube-scheduler in the Iron Bank and download the latest tarball.2. Navigate to the location of the download and run `docker load -i *tarball.tar.gz* -t kube-scheduler:*tag*` or `podman load -i *tarball.tar.gz* -t kube-scheduler:*tag*`, substituting in the appropriate download name. This will build the image that will be used when the container runs. Provide a unique tag so that it is easy to reference the image later.## Notes:The default user for the container is set to 1000.The entrypoint for the container is `/usr/bin/kube-scheduler`.
