Commit Graph

5 Commits (b4bddcc99892761b239d17f14606b7bc3d335346)

Author SHA1 Message Date
Wang Guoliang b8526cd077 -Add scheduler optimization options, short circuit all predicates if one predicate fails 2018-01-13 18:18:55 +08:00
Haoran Wang 31d2f452d2 move hardPodAffinitySymmetricWeight to scheduler policy config 2017-05-26 14:04:37 +08:00
tanshanshan a61b5f2490 PodFitsPorts has been replaced by PodFitsHostPorts 2017-01-11 14:52:45 +08:00
Justin Santa Barbara f9a6ac077e Ubernetes Lite: Volumes can dictate zone scheduling
For AWS EBS, a volume can only be attached to a node in the same AZ.
The scheduler must therefore detect if a volume is being attached to a
pod, and ensure that the pod is scheduled on a node in the same AZ as
the volume.

So that the scheduler need not query the cloud provider every time, and
to support decoupled operation (e.g. bare metal) we tag the volume with
our placement labels.  This is done automatically by means of an
admission controller on AWS when a PersistentVolume is created backed by
an EBS volume.

Support for tagging GCE PVs will follow.

Pods that specify a volume directly (i.e. without using a
PersistentVolumeClaim) will not currently be scheduled correctly (i.e.
they will be scheduled without zone-awareness).
2015-12-31 12:27:01 -05:00
dingh 88c5f3f0a7 Example for policy config file for scheduler
Add a json file which can be used with --policy-config-file argument when starting kube-scheduler.

This file serves as an example for new Kubernetes users so that they can quickly understand how to
use '--policy-config-file' argument and have a brief idea about the scheduler policy.
2015-06-24 11:10:27 +08:00