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")

kube-scheduler Configuration Best Practices

下面是我梳理的,个人认为必须关注的配置:

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的配置真是少啊!确实,也难怪scheduler是最简单的组件。

本文参与腾讯云自媒体分享计划,欢迎正在阅读的你也加入,一起分享。

发表于

我来说两句

0 条评论
登录 后参与评论

相关文章

来自专栏nummy

flume RPC 接口开发

24440
来自专栏Laoqi's Linux运维专列

MySQL高可用架构之MHA

56730
来自专栏闵开慧

ERROR security.UserGroupInformation: Priviledge...

"Failed to set permissions of path"问题 参考文献:https://issues.apache.org/jira/browse...

36790
来自专栏别先生

SpringMVC的初始

1:其实一开始对SSH和SSM并不是很熟悉的,对SSH可能熟悉些(Struts,Spring,Hibernate)这三个框架。但是由于框架的更新,和出现了更好的...

23290
来自专栏hbbliyong

完美卸载SQL Server 2008的方案

针对SQL数据库卸载不完全的现象,做了如下总结: 1,控制面板 卸载 首先,打开控制面板,按照“安装时间”进行排序,卸载SQL Server系列组件 ...

47870
来自专栏全栈架构

Spring Boot 与 Kotlin 处理Web表单提交

我们在做web开发的时候,肯定逃不过表单提交,这篇文章通过Spring Boot使用Kotlin 语言 创建和提交一个表单。

8320
来自专栏编程坑太多

springboot(13)国际化

20240
来自专栏乐沙弥的世界

MySQL PXC 5.7 invalid user‘@MYSQLD_USER@’

最近的PXC 5.7启动的时候收到一个无效用户的提示,invalid user ‘@MYSQLD_USER@’,这个问题还真是头一次碰到,而且这个MYSQLD_...

15030
来自专栏dalaoyang

服务链路追踪---Sleuth

Sleuth:日志收集工具包,封装了Dapper和log-based追踪以及Zipkin和HTrace操作,为SpringCloud应用实现了一种分布式追踪解决...

521160
来自专栏生信技能树

(15)基因组各种版本对应关系-生信菜鸟团博客2周年精选文章集

这是我的成名作: 首先是NCBI对应UCSC,对应ENSEMBL数据库: GRCh36 (hg18): ENSEMBL release_52. GRCh37 (...

52880

扫码关注云+社区

领取腾讯云代金券