How does Kubernetes' scheduler work? What I mean is that Kubernetes' scheduler appears to be very simple?
My initial thought is that this scheduler is just a simple admission control system, not a real scheduler. Is it that correct?
I found a short description, but it is not terribly informative:
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.