这篇文章将为大家详细讲解有关kube-scheduler配置的示例分析，小编觉得挺实用的，因此分享给大家做个参考，希望大家阅读完这篇文章后可以有所收获。
version: kubernetes 1.6.2
##kube-scheduler Configuration
下面是我梳理的kube-scheduler的完成配置：
| flag | default value | comments |
|---|---|---|
| --address string | 0.0.0.0 | The IP address to serve on (set to 0.0.0.0 for all interfaces) (default "0.0.0.0") |
| --algorithm-provider string | DefaultProvider | The scheduling algorithm provider to use, one of: DefaultProvider |
| --failure-domains string | kubernetes.io/hostname,<br/> failure-domain.beta.kubernetes.io/zone,<br/> failure-domain.beta.kubernetes.io/region | Indicate the "all topologies" set for an empty topologyKey when it's used for PreferredDuringScheduling pod anti-affinity. (default "kubernetes.io/hostname,failure-domain.beta.kubernetes.io/zone,failure-domain.beta.kubernetes.io/region") |
| --feature-gates value | A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: <br/> AllAlpha=true | |
| --google-json-key string | The Google Cloud Platform Service Account JSON Key to use for authentication. | |
| --hard-pod-affinity-symmetric-weight int | 1 | RequiredDuringScheduling affinity is not symmetric, but there is an implicit PreferredDuringScheduling affinity rule corresponding to every RequiredDuringScheduling affinity rule. --hard-pod-affinity-symmetric-weight represents the weight of implicit PreferredDuringScheduling affinity rule. (default 1) |
| --kube-api-burst value | 100 | Burst to use while talking with kubernetes apiserver (default 100) |
| --kube-api-content-type string | application/vnd.kubernetes.protobuf | Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") |
| --kube-api-qps value | 50 | QPS to use while talking with kubernetes apiserver (default 50) |
| --kubeconfig string | Path to kubeconfig file with authorization and master location information. | |
| --leader-elect | true | Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability. (default true) |
| --leader-elect-lease-duration duration | 15s | The duration that non-leader candidates will wait after observing a leadership renewal until attempting to acquire leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be stopped before it is replaced by another candidate. This is only applicable if leader election is enabled. (default 15s) |
| --leader-elect-renew-deadline duration | 10s | The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must be less than or equal to the lease duration. This is only applicable if leader election is enabled. (default 10s) |
| --leader-elect-retry-period duration | 2s | The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled. (default 2s) |
| --master string | The address of the Kubernetes API server (overrides any value in kubeconfig) | |
| --policy-config-file string | File with scheduler policy configuration | |
| --port value | 10251 | The port that the scheduler's http service runs on (default 10251) |
| --profiling | true | Enable profiling via web interface host:port/debug/pprof/ (default true) |
| --scheduler-name string | default-scheduler | Name of the scheduler, used to select which pods will be processed by this scheduler, based on pod's annotation with key 'scheduler.alpha.kubernetes.io/name' (default "default-scheduler") |
下面是我梳理的，个人认为必须关注的配置：
| flag | default value | comments |
|---|---|---|
| --address string | 0.0.0.0 | The IP address to serve on (set to 0.0.0.0 for all interfaces) (default "0.0.0.0") |
| --kubeconfig string | Path to kubeconfig file with authorization and master location information. | |
| --master string | The address of the Kubernetes API server (overrides any value in kubeconfig) | |
| --policy-config-file string | File with scheduler policy configuration | |
| --port value | 10251 | The port that the scheduler's http service runs on (default 10251) |
| --profiling | true | Enable profiling via web interface host:port/debug/pprof/ (default true) |
关于“kube-scheduler配置的示例分析”这篇文章就分享到这里了，希望以上内容可以对大家有一定的帮助，使各位可以学到更多知识，如果觉得文章不错，请把它分享出去让更多的人看到。
免责声明：本站发布的内容（图片、视频和文字）以原创、转载和分享为主，文章观点不代表本网站立场，如果涉及侵权请联系站长邮箱：is@yisu.com进行举报，并提供相关证据，一经查实，将立刻删除涉嫌侵权内容。
