Shulou(Shulou.com)05/31 Report--

This article will explain the example analysis of kube-scheduler configuration for you in detail. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

Version: kubernetes 1.6.2

# # kube-scheduler Configuration

Here is the completed configuration of the kube-scheduler I combed:

Flag default valuecomments--address string0.0.0.0The IP address to serve on (set to 0.0.0.0 for all interfaces) (default "0.0.0.0")-- algorithm-provider stringDefaultProviderThe scheduling algorithm provider to use, one of: DefaultProvider--failure-domains stringkubernetes.io/hostname, failure-domain.beta.kubernetes.io/zone Failure-domain.beta.kubernetes.io/regionIndicate 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 int1RequiredDuringScheduling 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 value100Burst to use while talking with kubernetes apiserver (default 100)-- kube-api-content-type stringapplication/vnd.kubernetes.protobufContent type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf")-kube-api-qps value50QPS to use while talking with kubernetes apiserver (default 50)-kubeconfig string

Path to kubeconfig file with authorization and master location information.--leader-electtrueStart 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 duration15sThe 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 duration10sThe 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 duration2sThe 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 value10251The port that the scheduler's http service runs on (default 10251)-- profilingtrueEnable profiling via web interface host:port/debug/pprof/ (default true)-- scheduler-name stringdefault-schedulerName 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

Here are the configurations I have combed that I think I must pay attention to:

Flag default valuecomments--address string0.0.0.0The 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 value10251The port that the scheduler's http service runs on (default 10251)-- this is the end of the profilingtrueEnable profiling via web interface host:port/debug/pprof/ (default true) article on "sample Analysis of kube-scheduler configuration". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.