【kubernetes/k8s概念】kube-controller-manager启动参数

小鱼儿 2022-03-28 20:46 594阅读 0赞

kubernetes 1.12.1版本

# **Desc** #

>       The Kubernetes controller manager is a daemon that embeds the core control loops shipped with Kubernetes. In applications of robotics and automation, a control loop is a non-terminating loop that regulates the state of the system. In Kubernetes, a ontroller is a control loop that watches the shared state of the cluster through the apiserver and makes changes attempting to move the current state towards the desired state. Examples of controllers that ship with Kubernetes today are the replication controller, endpoints controller, namespace controller, and serviceaccounts controller.

/usr/bin/kube-controller-manager \
      --address=127.0.0.1 \
      --master=http://127.0.0.1:8080 \
      --allocate-node-cidrs=true \
      --service-cluster-ip-range=10.254.0.0/16 \
      --cluster-cidr=172.30.0.0/16 \
      --cluster-name=kubernetes \
      --cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem \
      --cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem \
      --service-account-private-key-file=/etc/kubernetes/ssl/ca-key.pem \
      --root-ca-file=/etc/kubernetes/ssl/ca.pem \
      --leader-elect=false \
      --log-dir=/var/log/kubernetes/kube-controller-manager \
      --v=2

# kube-controller-manager启动参数详解 #

Usage:  
  kube-controller-manager \[flags\]

Debugging flags:

<table> 
 <tbody> 
  <tr> 
   <td> <p><strong>参数</strong></p> </td> 
   <td> <p><strong>描述</strong></p> </td> 
  </tr> 
  <tr> 
   <td>--contention-profiling</td> 
   <td>启用了 profiling，则启用锁争用性分析</td> 
  </tr> 
  <tr> 
   <td>--profiling</td> 
   <td>开启profilling，通过web接口host:port/debug/pprof/分析性能</td> 
  </tr> 
 </tbody> 
</table>

Generic flags:

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--allocate-node-cidrs</td> 
   <td>是否应在云提供商上分配和设置Pod的CIDR</td> 
  </tr> 
  <tr> 
   <td>--cidr-allocator-type string</td> 
   <td>CIDR分配器的类型&nbsp;(default "RangeAllocator")</td> 
  </tr> 
  <tr> 
   <td><span style="color:#86ca5e;">--cloud-config string</span></td> 
   <td>云提供商配置文件路径，空代表没有配置文件</td> 
  </tr> 
  <tr> 
   <td><span style="color:#86ca5e;">--cloud-provider string</span></td> 
   <td>云提供商，空代表没有云提供商</td> 
  </tr> 
  <tr> 
   <td>--cluster-cidr string</td> 
   <td>集群中Pod的CIDR范围，要求--allocate-node-cidrs为true</td> 
  </tr> 
  <tr> 
   <td>--cluster-name string</td> 
   <td>集群的实例前缀(default "kubernetes")</td> 
  </tr> 
  <tr> 
   <td>--configure-cloud-routes</td> 
   <td>是否在云提供商上配置allocate-node-cidrs分配的CIDR(default true)</td> 
  </tr> 
  <tr> 
   <td>--controller-start-interval duration</td> 
   <td>启动controller manager的间隔时间</td> 
  </tr> 
  <tr> 
   <td>--controllers strings</td> 
   <td> <p>需要开启的controller列表，*代表开启所有（默认），‘foo’代表开启foo controller，‘-foo’代表禁止foo controller</p> <p>所有的controller如下：</p> 
    <ul> 
     <li>&nbsp; attachdetach, bootstrapsigner, clusterrole-aggregation,</li> 
     <li>&nbsp; cronjob, csrapproving, csrcleaner, csrsigning, daemonset,</li> 
     <li>&nbsp; deployment, disruption, endpoint, garbagecollector,</li> 
     <li>&nbsp; horizontalpodautoscaling, job, namespace, nodeipam, nodelifecycle,&nbsp; &nbsp; &nbsp;</li> 
     <li>&nbsp; persistentvolume-binder, persistentvolume-expander, podgc, pv-protection,</li> 
     <li>&nbsp; pvc-protection, replicaset, replicationcontroller,</li> 
     <li>&nbsp; resourcequota, route, service, serviceaccount, serviceaccount-token,</li> 
     <li>&nbsp; statefulset, tokencleaner, ttl,ttl-after-finished</li> 
    </ul></td> 
  </tr> 
  <tr> 
   <td>--feature-gates mapStringBool</td> 
   <td>key = value对，用于试验</td> 
  </tr> 
  <tr> 
   <td>--kube-api-burst int32</td> 
   <td>发送到kube-apiserver每秒请求量 （default 100）</td> 
  </tr> 
  <tr> 
   <td>--kube-api-content-type string</td> 
   <td>发送到kube-apiserver请求内容类型（default "application/vnd.kubernetes.protobuf"）</td> 
  </tr> 
  <tr> 
   <td>--kube-api-qps float32</td> 
   <td>与kube-apiserver通信的qps（default 50）</td> 
  </tr> 
  <tr> 
   <td>--leader-elect</td> 
   <td>多个master情况设置为true保证高可用，进行leader选举</td> 
  </tr> 
  <tr> 
   <td>--leader-elect-lease-duration duration</td> 
   <td>当leader-elect设置为true生效，选举过程中非leader候选等待选举的时间间隔（default 15s）</td> 
  </tr> 
  <tr> 
   <td>--leader-elect-renew-deadline duration</td> 
   <td>eader选举过程中在停止leading，再次renew时间间隔，小于或者等于leader-elect-lease-duration duration，也是leader-elect设置为true生效（default 10s）</td> 
  </tr> 
  <tr> 
   <td>--leader-elect-retry-period duration</td> 
   <td>当leader-elect设置为true生效，获取leader或者重新选举的等待间隔（default 2s）</td> 
  </tr> 
  <tr> 
   <td>--min-resync-period duration</td> 
   <td>重新同步周期,在 [MinResyncPeriod-2 * MinResyncPeriod]间取随机值(default 12h0m0s)</td> 
  </tr> 
  <tr> 
   <td>--node-monitor-period duration</td> 
   <td>NodeController同步NodeStatus的时间间隔(default 5s)</td> 
  </tr> 
  <tr> 
   <td><span style="color:#86ca5e;">--route-reconciliation-period duration</span></td> 
   <td>协调由云提供商为节点创建的路由的时间间隔&nbsp;(default 10s)</td> 
  </tr> 
  <tr> 
   <td>--use-service-account-credentials</td> 
   <td>设置true为每个控制器使用单个service account</td> 
  </tr> 
  <tr> 
   <td>&nbsp;</td> 
   <td>&nbsp;</td> 
  </tr> 
 </tbody> 
</table>

Service controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-service-syncs int32</td> 
   <td>允许同时同步的 service 数量。 数字越大=服务管理响应越快，但消耗更多 CPU 和网络资源</td> 
  </tr> 
  <tr> 
   <td>&nbsp;</td> 
   <td>&nbsp;</td> 
  </tr> 
 </tbody> 
</table>

Secure serving flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--bind-address ip</td> 
   <td>监听--secure-port端口的IP地址(default 0.0.0.0)</td> 
  </tr> 
  <tr> 
   <td>-cert-dir string</td> 
   <td>TLS证书所在的目录。如果提供了--tls-cert-file和--tls-private-key-file，则将忽略此标志(default "/var/run/kubernetes")</td> 
  </tr> 
  <tr> 
   <td>--http2-max-streams-per-connection int</td> 
   <td>api server 提供给 client&nbsp; 的HTTP / 2最大 stream 连接数。0 用golang的默认值</td> 
  </tr> 
  <tr> 
   <td>--secure-port int</td> 
   <td>使用身份验证和授权提供服务的HTTPS端口。0禁用HTTPS</td> 
  </tr> 
  <tr> 
   <td>--tls-cert-file string</td> 
   <td> <p>文件包含HTTPS的默认x509证书的文件。 （如果有CA证书，在服务器证书之后级联）。如果启用了HTTPS服务，但是 --tls-cert-file和--tls-private-key-file 未设置，则会为公共地址生成自签名证书和密钥，并将其保存到--cert-dir的目录中</p> </td> 
  </tr> 
  <tr> 
   <td>--tls-cipher-suites strings</td> 
   <td>逗号分隔的cipher suites列表。如果省略则使用默认的Go&nbsp;cipher suites</td> 
  </tr> 
  <tr> 
   <td>--tls-min-version string</td> 
   <td>支持最低TLS版本。 主要有：VersionTLS10，VersionTLS11，VersionTLS12</td> 
  </tr> 
  <tr> 
   <td>--tls-private-key-file string&nbsp;</td> 
   <td>文件包括与 --tls-cert-file 匹配的默认x509私钥</td> 
  </tr> 
  <tr> 
   <td>--tls-sni-cert-key namedCertKey</td> 
   <td>x509证书和私钥对的文件路径(default [])&nbsp;Examples: "example.crt,example.key" or&nbsp;"foo.crt,foo.key:*.foo.com,foo.com"</td> 
  </tr> 
 </tbody> 
</table>

Authentication flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--authentication-kubeconfig string</td> 
   <td>kubeconfig文件指向有权力创建tokenaccessreviews.authentication.k8s.io的核心kubernetes server，如果未设置所有的token请求被视为匿名的，在集群中也不查找client CA</td> 
  </tr> 
  <tr> 
   <td>--authentication-skip-lookup</td> 
   <td>如果设置false，authentication-kubeconfig用来在集群中查找缺失的authentication配置</td> 
  </tr> 
  <tr> 
   <td>--authentication-token-webhook-cache-ttl duration</td> 
   <td>来自webhook token验证器的缓存响应时间 (default 10s)</td> 
  </tr> 
  <tr> 
   <td>--client-ca-file string</td> 
   <td>如果设置任何请求必须提供其中一个客户端证书签名。则用其中的 Common Name 作为请求的用户名验证</td> 
  </tr> 
  <tr> 
   <td>--requestheader-allowed-names strings</td> 
   <td>List of client certificate common names to allow to provide usernames in headers specified by&nbsp;--requestheader-username-headers. If empty, any client certificate validated by the authorities in&nbsp;--requestheader-client-ca-file is allowed.</td> 
  </tr> 
  <tr> 
   <td>--requestheader-client-ca-file string</td> 
   <td>Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers. WARNING: generally do not depend on authorization being already done for incoming requests.</td> 
  </tr> 
  <tr> 
   <td>--requestheader-extra-headers-prefix strings</td> 
   <td>List of request header prefixes to inspect. X-Remote-Extra- is suggested. (default [x-remote-extra-])</td> 
  </tr> 
  <tr> 
   <td>--requestheader-group-headers strings</td> 
   <td>List of request headers to inspect for groups. X-Remote-Group is suggested. (default [x-remote-group])</td> 
  </tr> 
  <tr> 
   <td>--requestheader-username-headers strings</td> 
   <td>List of request headers to inspect for usernames. X-Remote-User is common. (default [x-remote-user])</td> 
  </tr> 
 </tbody> 
</table>

Authorization flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--authorization-always-allow-paths strings</td> 
   <td>授权期间要跳过的HTTP路径列表，这些路径是经过授权、无须与'核心'kubernetes服务通信(default [/healthz])</td> 
  </tr> 
  <tr> 
   <td>--authorization-kubeconfig string</td> 
   <td>kubeconfig指向核心的kubernetes服务拥有足够的权力来创建subjectaccessreviews.authorization.k8s.io，也是可选项，如果未设置，则所有请求将被禁止</td> 
  </tr> 
  <tr> 
   <td>--authorization-webhook-cache-authorized-ttl duration</td> 
   <td>从webhook授权器对于cache验证响应时间(default 10s)</td> 
  </tr> 
  <tr> 
   <td>--authorization-webhook-cache-unauthorized-ttl duration</td> 
   <td>从webhook授权器对于cache验证未响应时间(default 10s)</td> 
  </tr> 
 </tbody> 
</table>

Attachdetach controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--attach-detach-reconcile-sync-period duration</td> 
   <td>在volume attach detach调整同步等待时间，时间间隔必须大于1s，增加默认值可能导致volume与pod不匹配(default 1m0s)</td> 
  </tr> 
  <tr> 
   <td>--disable-attach-detach-reconcile-sync</td> 
   <td>禁止volume attach detach 调整同步，禁用此功能可能会导致卷与 pod 不匹配</td> 
  </tr> 
 </tbody> 
</table>

Csrsigning controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--cluster-signing-cert-file string</td> 
   <td>Filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates (default&nbsp;"/etc/kubernetes/ca/ca.pem")</td> 
  </tr> 
  <tr> 
   <td>--cluster-signing-key-file string</td> 
   <td>Filename containing a PEM-encoded RSA or ECDSA private key used to sign cluster-scoped certificates&nbsp;(default "/etc/kubernetes/ca/ca.key")</td> 
  </tr> 
  <tr> 
   <td>--experimental-cluster-signing-duration duration</td> 
   <td>The length of duration signed certificates will be given. (default 8760h0m0s)</td> 
  </tr> 
 </tbody> 
</table>

Deployment controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-deployment-syncs int32</td> 
   <td>允许同时同步的deployment对象的数量，部署数量越大需要的CPU网络load也多(default 5)</td> 
  </tr> 
  <tr> 
   <td>--deployment-controller-sync-period duration</td> 
   <td>同步deployment的周期(default 30s)</td> 
  </tr> 
 </tbody> 
</table>

Endpoint controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-endpoint-syncs int32</td> 
   <td>同时同步endpoint的数量，也是数量越多需要越多的CPU和network(default 5)</td> 
  </tr> 
 </tbody> 
</table>

Garbagecollector controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td> <p><strong>描述</strong></p> </td> 
  </tr> 
  <tr> 
   <td>--concurrent-gc-syncs int32</td> 
   <td>允许同时同步的garbage collector workers数量(default 20)</td> 
  </tr> 
  <tr> 
   <td>--enable-garbage-collector&nbsp;</td> 
   <td>启用通用垃圾收集器，必须与kube-apiserver的相应参数一起使用(default true)</td> 
  </tr> 
  <tr> 
   <td>&nbsp;</td> 
   <td>&nbsp;</td> 
  </tr> 
 </tbody> 
</table>

Horizontalpodautoscaling controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--horizontal-pod-autoscaler-cpu-initialization-period duration</td> 
   <td>当CPU samples略过，在pod启动之后的周期(default 5m0s)</td> 
  </tr> 
  <tr> 
   <td>--horizontal-pod-autoscaler-downscale-stabilization duration</td> 
   <td>The period for which autoscaler will look backwards and not scale down below any recommendation it made during that period(default 5m0s)</td> 
  </tr> 
  <tr> 
   <td>--horizontal-pod-autoscaler-initial-readiness-delay duration</td> 
   <td>The period after pod start during which readiness changes will be treated as initial readiness(default 30s)</td> 
  </tr> 
  <tr> 
   <td>--horizontal-pod-autoscaler-sync-period duration</td> 
   <td>The period for syncing the number of pods in horizontal pod autoscaler. (default 15s)</td> 
  </tr> 
  <tr> 
   <td>--horizontal-pod-autoscaler-tolerance float</td> 
   <td>The minimum change (from 1.0) in the desired-to-actual metrics ratio for the horizontal pod autoscaler to&nbsp;consider scaling. (default 0.1)</td> 
  </tr> 
 </tbody> 
</table>

Namespace controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td> <p><strong>描述</strong></p> </td> 
  </tr> 
  <tr> 
   <td>--concurrent-namespace-syncs int32</td> 
   <td>The number of namespace objects that are allowed to sync concurrently. Larger number = more responsive namespace termination, but more CPU (and network) load (default 10)</td> 
  </tr> 
  <tr> 
   <td>--namespace-sync-period duration</td> 
   <td>同步namespace生命周期更新的周期(default 5m0s)</td> 
  </tr> 
 </tbody> 
</table>

Nodeipam controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--node-cidr-mask-size int32</td> 
   <td>集群中节点子网掩码打小(default 24)</td> 
  </tr> 
  <tr> 
   <td>--service-cluster-ip-range string&nbsp;</td> 
   <td>集群service的cidr范围，需要--allocate-node-cidrs设置为true</td> 
  </tr> 
 </tbody> 
</table>

Nodelifecycle controller flags:

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--enable-taint-manager</td> 
   <td>如果设置为true则开启NoExecute Taints，将驱逐所有节点上（拥有这种污点的节点）不容忍运行pod (default true)</td> 
  </tr> 
  <tr> 
   <td>--large-cluster-size-threshold int32</td> 
   <td>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)</td> 
  </tr> 
  <tr> 
   <td>--node-eviction-rate float32</td> 
   <td>当zone健康node失败情况，删除节点上的pod的速率&nbsp;(default 0.1)</td> 
  </tr> 
  <tr> 
   <td>--node-monitor-grace-period duration</td> 
   <td>在标记节点不健康之前，允许运行节点不响应的时间，必须是n倍的kubelet's nodeStatusUpdateFrequency，N意味着kubelet报告node状态重试的次数(default 40s)</td> 
  </tr> 
  <tr> 
   <td>--node-startup-grace-period duration</td> 
   <td>在标记节点不健康之前，允许开始节点不响应的时间 (default 1m0s)</td> 
  </tr> 
  <tr> 
   <td>--pod-eviction-timeout duration</td> 
   <td>在失败的节点上删除pod的宽限时间&nbsp;&nbsp;(default 5m0s)</td> 
  </tr> 
  <tr> 
   <td>--secondary-node-eviction-rate float32</td> 
   <td>当zone不健康node失败情况，删除节点上的pod的速率，如果集群大小小于 large-cluster-size-threshold，则隐式地将设置为0。(default 0.01)</td> 
  </tr> 
  <tr> 
   <td>--unhealthy-zone-threshold float32</td> 
   <td>not ready 节点（至少3个）的比例达到该值时，将 Zone 标记为不健康 (default 0.55)</td> 
  </tr> 
  <tr> 
   <td>&nbsp;</td> 
   <td>&nbsp;</td> 
  </tr> 
 </tbody> 
</table>

Persistentvolume-binder controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--enable-dynamic-provisioning</td> 
   <td>为支持它的环境启用动态配置&nbsp;(default true)</td> 
  </tr> 
  <tr> 
   <td>--enable-hostpath-provisioner</td> 
   <td>当没有云提供商运行时开启host path pv配置，这主要适合测试以及开发配置features，host path配置不支持多点集群</td> 
  </tr> 
  <tr> 
   <td>--flex-volume-plugin-dir string</td> 
   <td>第三方插件路径&nbsp;(default "/usr/libexec/kubernetes/kubelet-plugins/volume/exec/")</td> 
  </tr> 
  <tr> 
   <td>--pv-recycler-increment-timeout-nfs int32</td> 
   <td>NFS scrubber pod添加每Gi到ActiveDeadlineSeconds的时间增量(default 30)</td> 
  </tr> 
  <tr> 
   <td>--pv-recycler-minimum-timeout-hostpath int32</td> 
   <td>对于HostPath Recycler pod的最小ActiveDeadlineSeconds，仅使用于测试于开发，不使用于多几点集群&nbsp;(default 60)</td> 
  </tr> 
  <tr> 
   <td>--pv-recycler-minimum-timeout-nfs int32</td> 
   <td>对于NFS Recycler pod的最小ActiveDeadlineSeconds&nbsp;(default 300)</td> 
  </tr> 
  <tr> 
   <td>--pv-recycler-pod-template-filepath-hostpath string</td> 
   <td>对于hostpaht持久卷重使用定义的模板路径，仅使用于测试于开发，不使用于多几点集群&nbsp;</td> 
  </tr> 
  <tr> 
   <td>--pv-recycler-timeout-increment-hostpath int32</td> 
   <td>对于HostPath scrubber pod每增加Gi到ActiveDeadlineSeconds的时间增量，仅使用于测试于开发，不使用于多几点集群&nbsp;(default 30)</td> 
  </tr> 
  <tr> 
   <td>--pvclaimbinder-sync-period duration</td> 
   <td>同步pv以及pvc的周期 (default 15s)</td> 
  </tr> 
 </tbody> 
</table>

Podgc controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--terminated-pod-gc-threshold int32</td> 
   <td>当终止的pod达到该值时，pod garbage collector开始删除终止pod，如果设置&lt;=0，关闭pod garbage collector&nbsp;(default 12500)</td> 
  </tr> 
 </tbody> 
</table>

Replicaset controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-replicaset-syncs int32</td> 
   <td>允许同时同步的rs数量，Larger number = more responsive replica<br> management, but more CPU (and network) load (default 5)</td> 
  </tr> 
 </tbody> 
</table>

Replicationcontroller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent_rc_syncs int32</td> 
   <td>The number of replication controllers that are allowed to sync concurrently. Larger number = more&nbsp;responsive replica management, but more CPU (and network) load (default 5)</td> 
  </tr> 
 </tbody> 
</table>

Resourcequota controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-resource-quota-syncs int32</td> 
   <td>The number of resource quotas that are allowed to sync concurrently. Larger number = more responsive&nbsp;quota management, but more CPU (and network) load (default 5)</td> 
  </tr> 
  <tr> 
   <td>--resource-quota-sync-period duration</td> 
   <td>在系统中同步配额使用状态的周期&nbsp;(default 5m0s)</td> 
  </tr> 
 </tbody> 
</table>

Serviceaccount controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-serviceaccount-token-syncs int32</td> 
   <td>The number of service account token objects that are allowed to sync concurrently. Larger number = more&nbsp;responsive token generation, but more CPU (and network) load (default 5)</td> 
  </tr> 
  <tr> 
   <td>--root-ca-file string</td> 
   <td>根CA 证书文件路径，如果设置的话将被用于 Service Account 的 token secret 中</td> 
  </tr> 
  <tr> 
   <td>--service-account-private-key-file string</td> 
   <td>Filename containing a PEM-encoded private RSA or ECDSA key used to sign service account tokens</td> 
  </tr> 
 </tbody> 
</table>

Ttl-after-finished controller flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--concurrent-ttl-after-finished-syncs int32</td> 
   <td>The number of TTL-after-finished controller workers that are allowed to sync concurrently. (default 5)</td> 
  </tr> 
 </tbody> 
</table>

Misc flags

<table> 
 <tbody> 
  <tr> 
   <td><strong>参数</strong></td> 
   <td><strong>描述</strong></td> 
  </tr> 
  <tr> 
   <td>--insecure-experimental-approve-all-kubelet-csrs-for-group string</td> 
   <td>This flag does nothing.</td> 
  </tr> 
  <tr> 
   <td>--kubeconfig string</td> 
   <td>kubeconfig文件路径，带有验证以及master信息</td> 
  </tr> 
  <tr> 
   <td>--master string</td> 
   <td>kubernetes api server的地址，将会覆盖kubeconfig设置的值</td> 
  </tr> 
 </tbody> 
</table>