kube-scheduler最佳配置

Posted 2022-12-15 WaltonWang

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, failure-domain.beta.kubernetes.io/zone, 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: 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)