What does the Kube-scheduler configuration parameter mean?

This article mainly shows you "what is the meaning of Kube-scheduler configuration parameters", the content is easy to understand, clear, hope to help you solve your doubts, let the editor lead you to study and learn "what is the meaning of Kube-scheduler configuration parameters" this article.

Here are all the configurations of Kube-scheduler version 1.12.0, of which the yellow background is the Flag that is not recommended, and the highlight and bold is the Flag that I think you need to pay attention to.

FlagComments--addresskube-scheduler listening address. Default 0.0.0.0 means to listen on all network interfaces used by the algorithm-provider scheduling algorithm provider. The value ClusterAutoscalerProvider or DefaultProvide--azure-container-registry-config contains the path of the Azure container registry configuration file-the path of the config configuration file. Flags overrides the values in this file-- contention-profiling enables lock contention analysis-- feature-gates, if profiling is enabled-- a set of key-value pairs that describe the features of the alpha/ experiment. -- burst pulse when kube-api-burst interacts with Kubernetes apiserver. Default value: 100--kube-api-content-type.

The type of request text sent to apiserver. Default value:

"application/vnd.kubernetes.protobuf"

-- QPS when kube-api-qps interacts with Kubernetes apiserver. Default value: kubeconfig configuration file path of 50--kubeconfig containing authentication and Master location information-- leader-elect

Before executing the main loop, start a leader election client and obtain leader rights.

Enable this feature when running replicated components for high availability. Default: true

-- leader-elect-lease-duration

This is actually the maximum time a Leader can be stopped before it is replaced by another candidate.

This parameter applies only when the-- leader-elect parameter is enabled

-- leader-elect-resource-lock

The types used to lock resources during leader elections, the supported options are:

Endpoints (default) and configmaps.

-- leader-elect-retry-period

The customer is trying to get the wait time between the leader and the replacement.

This parameter applies only when the-- leader-elect parameter is enabled

-- lock-object-name defines the name of the lock object. Default: kube-scheduler--lock-object-namespace defines the namespace of the lock object, and default: the maximum number of seconds between kube-system--log-flush-frequency log refreshes. Default value: address of 5s--masterKubernetes api server (overrides any value in kubeconfig)-policy-config-file

-- use this file when use-legacy-policy-config=true

-- policy-configmap

The name of the ConfigMap object that contains the scheduling policy configuration. If

-- use-legacy-policy-config=false, then it must be initialized in the scheduler

Previously existed in system namespace. The configuration must be used as a 'Data' map

The element key='policy.cfg' provides

-- policy-configmap-namespace

The namespace in which the scheduling policy ConfigMap is located. If the parameter is not provided

Or it is empty, then kube-system namespace will be used.

-- port

An insecure HTTP port that is not authenticated and authorized.

-- profiling enables profiling through web host interface: port/debug/pprof/-- scheduler-name

The name of the scheduler, which is used to select the scheduler based on the "spec.scheduler. Name" of pod

The pods processed by the scheduler

-- when use-legacy-policy-config is set to true, the scheduler will ignore policy configmap and use the policy configuration file-- if write-config-to is set, write the configuration value to this file and exit all of the above article "what is the meaning of Kube-scheduler configuration parameters?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!