github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 14:37:00 +00:00
Code Issues Projects Releases Wiki Activity

Add node sync period flag

Browse Source
This commit is contained in:
Deyuan Deng 2015-01-20 20:31:21 -05:00
parent 6db42eda4e
commit c263a79d3e
3 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
cmd/kube-controller-manager/controller-manager.go
View File

@ -49,7 +49,10 @@ var (
cloudProvider = flag.String("cloud_provider", "", "The provider for cloud services. Empty string for no provider.")
cloudConfigFile = flag.String("cloud_config", "", "The path to the cloud provider configuration file. Empty string for no configuration file.")
minionRegexp = flag.String("minion_regexp", "", "If non empty, and -cloud_provider is specified, a regular expression for matching minion VMs.")
machineList util.StringList
nodeSyncPeriod = flag.Duration("node_sync_period", 10*time.Second, ""+
"The period for syncing nodes from cloudprovider. Longer periods will result in "+
"fewer calls to cloud provider, but may delay addition of new nodes to cluster.")
machineList util.StringList
// TODO: Discover these by pinging the host machines, and rip out these flags.
// TODO: in the meantime, use resource.QuantityFlag() instead of these
nodeMilliCPU = flag.Int64("node_milli_cpu", 1000, "The amount of MilliCPU provisioned on each node")
@ -107,7 +110,7 @@ func main() {
},
}
nodeController := nodeControllerPkg.NewNodeController(cloud, *minionRegexp, machineList, nodeResources, kubeClient)
nodeController.Run(10 * time.Second)
nodeController.Run(*nodeSyncPeriod)
select {}
}

5
docs/man/kube-controller-manager.1.md
View File

@ -54,11 +54,14 @@ The kube-controller-manager has several options.
log to standard error instead of files.
**--machines**=[]
List of machines to schedule onto, comma separated.
List of machines to schedule onto, comma separated.
**--master**=""
The address of the Kubernetes API server.
**--node_sync_peroid**=10s
The period for syncing nodes from cloudprovider.
**--port**=10252
The port that the controller-manager's http service runs on.

3
docs/node.md
View File

@ -58,7 +58,8 @@ objects. It performs two major functions: cluster-wide node synchronization
and single node life-cycle management.
Node controller has a sync loop that creates/deletes `Node`s from Kubernetes
based on all matching VM instances listed from cloud provider. If a new instance
based on all matching VM instances listed from cloud provider. The sync period
can be controlled via flag "--node_sync_period". If a new instance
gets created, Node Controller creates a representation for it. If an existing
instance gets deleted, Node Controller deletes the representation. Note however,
Node Controller is unable to provision the node for you, i.e. it won't install