kube-controller-manager最佳配置
kubernetes version: 1.6.2
Kube-controller-manager Configuration
kube-controller-manager一共有72個flag配置,具體如下:
flag | value | default value | comments |
---|---|---|---|
–address ip | 0.0.0.0 | The IP address to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0) | |
–allocate-node-cidrs | Should CIDRs for Pods be allocated and set on the cloud provider. | ||
–attach-detach-reconcile-sync-period duration | 1m0s | The reconciler sync wait time between volume attach detach. This duration must be larger than one second, and increasing this value from the default may allow for volumes to be mismatched with pods. (default 1m0s) | |
–azure-container-registry-config string | Path to the file container Azure container registry configuration information. | ||
–cloud-config string | The path to the cloud provider configuration file. Empty string for no configuration file. | ||
–cloud-provider string | The provider for cloud services. Empty string for no provider. | ||
–cluster-cidr string | CIDR Range for Pods in cluster. | ||
–cluster-name string | kubernetes | The instance prefix for the cluster (default “kubernetes”) | |
–cluster-signing-cert-file string | /etc/kubernetes/ca/ca.pem | Filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates (default “/etc/kubernetes/ca/ca.pem”) | |
–cluster-signing-key-file string | /etc/kubernetes/ca/ca.key | Filename containing a PEM-encoded RSA or ECDSA private key used to sign cluster-scoped certificates (default “/etc/kubernetes/ca/ca.key”) | |
–concurrent-deployment-syncs int32 | 5 | The number of deployment objects that are allowed to sync concurrently. Larger number = more responsive deployments, but more CPU (and network) load (default 5) | |
–concurrent-endpoint-syncs int32 | 5 | The number of endpoint syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load (default 5) | |
–concurrent-gc-syncs int32 | 20 | The number of garbage collector workers that are allowed to sync concurrently. (default 20) | |
–concurrent-namespace-syncs int32 | 2 | The number of namespace objects that are allowed to sync concurrently. Larger number = more responsive namespace termination, but more CPU (and network) load (default 2) | |
–concurrent-replicaset-syncs int32 | 5 | The number of replica sets that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load (default 5) | |
–concurrent-resource-quota-syncs int32 | 5 | The number of resource quotas that are allowed to sync concurrently. Larger number = more responsive quota management, but more CPU (and network) load (default 5) | |
–concurrent-service-syncs int32 | 1 | The number of services that are allowed to sync concurrently. Larger number = more responsive service management, but more CPU (and network) load (default 1) | |
–concurrent-serviceaccount-token-syncs int32 | 5 | The number of service account token objects that are allowed to sync concurrently. Larger number = more responsive token generation, but more CPU (and network) load (default 5) | |
–concurrent-rc-syncs int32 | 5 | The number of replication controllers that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load (default 5) | |
–configure-cloud-routes | true | Should CIDRs allocated by allocate-node-cidrs be configured on the cloud provider. (default true) | |
–contention-profiling | Enable lock contention profiling, if profiling is enabled | ||
–controller-start-interval duration | Interval between starting controller managers. | ||
–controllers stringSlice | * | A list of controllers to enable. ‘*’ enables all on-by-default controllers, ‘foo’ enables the controller named ‘foo’, ‘-foo’ disables the controller named ‘foo’. All controllers: attachdetach, bootstrapsigner, certificatesigningrequests, cronjob, daemonset, deployment, disruption, endpoint, garbagecollector, horizontalpodautoscaling, job, namespace, node, persistentvolume-binder, podgc, replicaset, replicationcontroller, resourcequota, route, service, serviceaccount, serviceaccount-token, statefuleset, tokencleaner, ttl Disabled-by-default controllers: bootstrapsigner, tokencleaner (default [*]) |
|
–deployment-controller-sync-period duration | 30s | Period for syncing the deployments. (default 30s) | |
–disable-attach-detach-reconcile-sync | Disable volume attach detach reconciler sync. Disabling this may cause volumes to be mismatched with pods. Use wisely. | ||
–enable-dynamic-provisioning | true | Enable dynamic provisioning for environments that support it. (default true) | |
–enable-garbage-collector | true | Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-apiserver. (default true) | |
–enable-hostpath-provisioner | Enable HostPath PV provisioning when running without a cloud provider. This allows testing and development of provisioning features. HostPath provisioning is not supported in any way, won’t work in a multi-node cluster, and should not be used for anything other than testing or development. | ||
–enable-taint-manager | true | WARNING: Beta feature. If set to true, enables NoExecute Taints and will evict all not-tolerating Pods running on Nodes tainted with these kinds of Taints. (default true) | |
–feature-gates mapStringBool | A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: Accelerators=true |
||
–flex-volume-plugin-dir string | /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ | Full path of the directory in which the flex volume plugin should search for additional third party volume plugins. (default “/usr/libexec/kubernetes/kubelet-plugins/volume/exec/”) | |
–google-json-key string | The Google Cloud Platform Service Account JSON Key to use for authentication. | ||
–horizontal-pod-autoscaler-sync-period duration | 30s | The period for syncing the number of pods in horizontal pod autoscaler. (default 30s) | |
–horizontal-pod-autoscaler-use-rest-clients | WARNING: alpha feature. If set to true, causes the horizontal pod autoscaler controller to use REST clients through the kube-aggregator, instead of using the legacy metrics client through the API server proxy. This is required for custom metrics support in the horizonal pod autoscaler. | ||
–insecure-experimental-approve-all-kubelet-csrs-for-group string | The group for which the controller-manager will auto approve all CSRs for kubelet client certificates. | ||
–kube-api-burst int32 | 30 | Burst to use while talking with kubernetes apiserver (default 30) | |
–kube-api-content-type string | application/vnd.kubernetes.protobuf | Content type of requests sent to apiserver. (default “application/vnd.kubernetes.protobuf”) | |
–kube-api-qps float32 | 20 | QPS to use while talking with kubernetes apiserver (default 20) | |
–kubeconfig string | Path to kubeconfig file with authorization and master location information. | ||
–large-cluster-size-threshold int32 | 50 | Number of nodes from which NodeController treats the cluster as large for the eviction logic purposes. –secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller. (default 50) | |
–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) | ||
–min-resync-period duration | 12h0m0 | The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod (default 12h0m0s) | |
–namespace-sync-period duration | 5m0s | The period for syncing namespace life-cycle updates (default 5m0s) | |
–node-cidr-mask-size int32 | 24 | Mask size for node cidr in cluster. (default 24) | |
–node-eviction-rate float32 | 0.1 | Number of nodes per second on which pods are deleted in case of node failure when a zone is healthy (see –unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. (default 0.1) | |
–node-monitor-grace-period duration | 40s | Amount of time which we allow running Node to be unresponsive before marking it unhealthy. Must be N times more than kubelet’s nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status. (default 40s) | |
–node-monitor-period duration | 5s | The period for syncing NodeStatus in NodeController. (default 5s) | |
–node-startup-grace-period duration | 1m0s | Amount of time which we allow starting Node to be unresponsive before marking it unhealthy. (default 1m0s) | |
–pod-eviction-timeout duration | 5m0s | The grace period for deleting pods on failed nodes. (default 5m0s) | |
–port int32 | 10252 | The port that the controller-manager’s http service runs on (default 10252) | |
–profiling | true | Enable profiling via web interface host:port/debug/pprof/ (default true) | |
–pv-recycler-increment-timeout-nfs int32 | 30 | the increment of time added per Gi to ActiveDeadlineSeconds for an NFS scrubber pod (default 30) | |
–pv-recycler-minimum-timeout-hostpath int32 | 60 | The minimum ActiveDeadlineSeconds to use for a HostPath Recycler pod. This is for development and testing only and will not work in a multi-node cluster. (default 60) | |
–pv-recycler-minimum-timeout-nfs int32 | 300 | The minimum ActiveDeadlineSeconds to use for an NFS Recycler pod (default 300) | |
–pv-recycler-pod-template-filepath-hostpath string | The file path to a pod definition used as a template for HostPath persistent volume recycling. This is for development and testing only and will not work in a multi-node cluster. | ||
–pv-recycler-pod-template-filepath-nfs string | The file path to a pod definition used as a template for NFS persistent volume recycling | ||
–pv-recycler-timeout-increment-hostpath int32 | 30 | the increment of time added per Gi to ActiveDeadlineSeconds for a HostPath scrubber pod. This is for development and testing only and will not work in a multi-node cluster. (default 30) | |
–pvclaimbinder-sync-period duration | 15s | The period for syncing persistent volumes and persistent volume claims (default 15s) | |
–resource-quota-sync-period duration | 5m0s | The period for syncing quota usage status in the system (default 5m0s) | |
–root-ca-file string | If set, this root certificate authority will be included in service account’s token secret. This must be a valid PEM-encoded CA bundle. | ||
–route-reconciliation-period duration | 10s | The period for reconciling routes created for Nodes by cloud provider. (default 10s) | |
–secondary-node-eviction-rate float32 | 0.01 | Number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy (see –unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. This value is implicitly overridden to 0 if the cluster size is smaller than –large-cluster-size-threshold. (default 0.01) | |
–service-account-private-key-file string | Filename containing a PEM-encoded private RSA or ECDSA key used to sign service account tokens. | ||
–service-cluster-ip-range string | CIDR Range for Services in cluster. | ||
–service-sync-period duration | 5m0s | The period for syncing services with their external load balancers (default 5m0s) | |
–terminated-pod-gc-threshold int32 | 12500 | Number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If <= 0, the terminated pod garbage collector is disabled. (default 12500) | |
–unhealthy-zone-threshold float32 | 0.55 | Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy. (default 0.55) | |
–use-service-account-credentials | If true, use individual service account credentials for each controller. |
kube-controller-manager Configuration We Should First Care About
在72個flag中,我梳理出了我們私有云環境需要注意或配置的項,如下表所示。
flag | value | default value | comments |
---|---|---|---|
–address ip | 0.0.0.0 | The IP address to serve on (set to 0.0.0.0 for all interfaces) (default 0.0.0.0) | |
–attach-detach-reconcile-sync-period duration | 1m0s | The reconciler sync wait time between volume attach detach. This duration must be larger than one second, and increasing this value from the default may allow for volumes to be mismatched with pods. (default 1m0s) | |
–cluster-cidr string | CIDR Range for Pods in cluster. | ||
–cluster-name string | kubernetes | The instance prefix for the cluster (default “kubernetes”) | |
–cluster-signing-cert-file string | /etc/kubernetes/ca/ca.pem | Filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates (default “/etc/kubernetes/ca/ca.pem”) | |
–cluster-signing-key-file string | /etc/kubernetes/ca/ca.key | Filename containing a PEM-encoded RSA or ECDSA private key used to sign cluster-scoped certificates (default “/etc/kubernetes/ca/ca.key”) | |
–contention-profiling | Enable lock contention profiling, if profiling is enabled | ||
–enable-garbage-collector | true | Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-apiserver. (default true) | |
–flex-volume-plugin-dir string | /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ | Full path of the directory in which the flex volume plugin should search for additional third party volume plugins. (default “/usr/libexec/kubernetes/kubelet-plugins/volume/exec/”) | |
–kubeconfig string | Path to kubeconfig file with authorization and master location information. | ||
–large-cluster-size-threshold int32 | 50 | Number of nodes from which NodeController treats the cluster as large for the eviction logic purposes. –secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller. (default 50) | |
–master string | The address of the Kubernetes API server (overrides any value in kubeconfig) | ||
–node-cidr-mask-size int32 | 24 | Mask size for node cidr in cluster. (default 24) | |
–node-eviction-rate float32 | 0.1 | Number of nodes per second on which pods are deleted in case of node failure when a zone is healthy (see –unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. (default 0.1) | |
–node-monitor-grace-period duration | 40s | Amount of time which we allow running Node to be unresponsive before marking it unhealthy. Must be N times more than kubelet’s nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status. (default 40s) | |
–node-startup-grace-period duration | 1m0s ? | Amount of time which we allow starting Node to be unresponsive before marking it unhealthy. (default 1m0s) | |
–pod-eviction-timeout duration | 5m0s | The grace period for deleting pods on failed nodes. (default 5m0s) | |
–port int32 | 10252 | The port that the controller-manager’s http service runs on (default 10252) | |
–resource-quota-sync-period duration | 5m0s | The period for syncing quota usage status in the system (default 5m0s) | |
–root-ca-file string | If set, this root certificate authority will be included in service account’s token secret. This must be a valid PEM-encoded CA bundle. | ||
–secondary-node-eviction-rate float32 | 0.01 | Number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy (see –unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. This value is implicitly overridden to 0 if the cluster size is smaller than –large-cluster-size-threshold. (default 0.01) | |
–service-account-private-key-file string | Filename containing a PEM-encoded private RSA or ECDSA key used to sign service account tokens. | ||
–service-cluster-ip-range string | CIDR Range for Services in cluster. | ||
–terminated-pod-gc-threshold int32 | 12500 | Number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If <= 0, the terminated pod garbage collector is disabled. (default 12500) | |
–unhealthy-zone-threshold float32 | 0.55 | Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy. (default 0.55) |
相關文章
- Kubernetes: kube-controller-manager 原始碼分析Controller原始碼
- JVM最佳化配置JVM
- GitLab 配置最佳化Gitlab
- Zend OPcache 最佳實踐配置opcache
- Webpack 4 配置最佳實踐Web
- postgresql配置引數最佳化SQL
- SpringCloud之配置WebSocket的最佳方式SpringGCCloudWeb
- Nacos配置管理最佳實踐
- RMQ的SSL配置最佳實踐MQ
- MySQL 高併發配置最佳化MySql
- 【DATAGUARD】Dataguard遠端同步配置最佳實踐
- 提高安全性的最佳 Nginx 配置Nginx
- Kafka - 配置檔案引數最佳化方案Kafka
- [轉帖]JVM記憶體配置最佳實踐JVM記憶體
- Spring Cloud+Nacos+KMS 動態配置最佳實踐SpringCloud
- SSL證書安裝配置最佳化建議
- MySQL效能最佳化之Open_Table配置引數的合理配置建議MySql
- 容器化環境中,JVM最佳引數配置實踐JVM
- Jtti:如何最佳化大資料伺服器配置?Jtti大資料伺服器
- 【BEST】Oracle 資料庫19c配置最佳實踐Oracle資料庫
- 配置sysctl.conf檔案來最佳化系統
- ArkTS 中的記憶體調優與配置:最佳實踐記憶體
- 最佳化配置Little Snitch for Mac的規則和設定Mac
- OceanBase學習之路48|最佳效能引數的配置參考
- 高流量站點NGINX與PHP-fpm配置最佳化NginxPHP
- 服務發現與配置管理高可用最佳實踐
- SpringBoot最佳化之——1.Thymeleaf 配置等注意事項Spring Boot
- Ubuntu 下 Oh My Zsh 的最佳實踐「安裝及配置」Ubuntu
- 從青銅到王者,揭秘 Serverless 自動化函式最佳配置Server函式
- tomcat自帶連線池dbcp配置以及最佳化說明Tomcat
- 實戰Nginx與PHP(FastCGI)的安裝、配置與最佳化NginxPHPAST
- eslint-config-alloy配置個性化ESLint規則的最佳參考EsLint
- 彈性配置為構建提速 - CODING & 騰訊雲 CVM 最佳實踐
- MySQL-配置檔案my.cnf引數最佳化詳解MySql
- 如何配置Nginx壓縮實現效能最佳化?Linux主要學什麼NginxLinux
- Artifactory中Maven倉庫配置最佳化——提升Virtual倉庫下載速度Maven
- 【雙層模型】分散式光伏儲能系統的最佳化配置方法模型分散式
- 避免 OOMKilled:在 Kubernetes 環境中最佳化 Java 程序的記憶體配置OOMJava記憶體
- ECS彈性網路卡+彈性公網IP配置最佳實踐之策略路由路由