Skip to content

Latest commit

 

History

History
76 lines (56 loc) · 2.96 KB

kube-scheduler.md

File metadata and controls

76 lines (56 loc) · 2.96 KB

WARNING WARNING WARNING WARNING WARNING

PLEASE NOTE: This document applies to the HEAD of the source tree

If you are using a released version of Kubernetes, you should refer to the docs that go with that version.

The latest 1.0.x release of this document can be found [here](http://releases.k8s.io/release-1.0/docs/admin/kube-scheduler.md).

Documentation for other releases can be found at releases.k8s.io.

kube-scheduler

Synopsis

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.

kube-scheduler

Options

      --address=127.0.0.1: The IP address to serve on (set to 0.0.0.0 for all interfaces)
      --algorithm-provider="DefaultProvider": The scheduling algorithm provider to use, one of: DefaultProvider
      --bind-pods-burst=100: Number of bindings per second scheduler is allowed to make during bursts
      --bind-pods-qps=50: Number of bindings per second scheduler is allowed to continuously make
      --google-json-key="": The Google Cloud Platform Service Account JSON Key to use for authentication.
      --kube-api-burst=100: Burst to use while talking with kubernetes apiserver
      --kube-api-qps=50: QPS to use while talking with kubernetes apiserver
      --kubeconfig="": Path to kubeconfig file with authorization and master location information.
      --log-flush-frequency=5s: Maximum number of seconds between log flushes
      --master="": The address of the Kubernetes API server (overrides any value in kubeconfig)
      --policy-config-file="": File with scheduler policy configuration
      --port=10251: The port that the scheduler's http service runs on
      --profiling[=true]: Enable profiling via web interface host:port/debug/pprof/
Auto generated by spf13/cobra on 13-Oct-2015

Analytics