github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make periodic sync nodes from cloud provider optional.

Browse Source 
--sync_nodes=false gives user flexibility to add/remove nodes in the
cluster using REST api/kubectl cli and at the same time can use
cloud provider for other resources like persistent disks, etc.
This commit is contained in:
Ravi Sankar Penta
2015-01-14 17:05:48 -08:00
parent a84e94574f
commit 3a5ef05f64
7 changed files with 30 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -36,7 +36,7 @@ The kube-controller-manager has several options.
The provider for cloud services. Empty string for no provider.
**--minion_regexp**=""
If non empty, and -cloud_provider is specified, a regular expression for matching minion VMs.
If non empty, and --cloud_provider is specified, a regular expression for matching minion VMs.
**--insecure_skip_tls_verify**=false
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.
@@ -56,6 +56,9 @@ The kube-controller-manager has several options.
**--machines**=[]
List of machines to schedule onto, comma separated.
**--sync_nodes**=true
If true, and --cloud_provider is specified, sync nodes from the cloud provider. Default true.
**--master**=""
The address of the Kubernetes API server.

6
docs/node.md
View File

@@ -110,9 +110,11 @@ any binary; therefore, to
join Kubernetes cluster, you as an admin need to make sure proper services are
running in the node. In the future, we plan to automatically provision some node
services. In case of no cloud provider, Node Controller simply registers all
machines from `-machines` flag, any futher interactions need to be done manually
by using `kubectl`. If you are paranoid, leave `-machines` empty and create all
machines from `--machines` flag, any futher interactions need to be done manually
by using `kubectl`. If you are paranoid, leave `--machines` empty and create all
machines from `kubectl` one by one - the two approaches are equivalent.
Optionally you can skip cluster-wide node synchronization with
'--sync_nodes=false' and can use REST api/kubectl cli to add/remove nodes.
Node life-cycle management in the Node Controller is still under development, it
is supposed to manage the Node Status Specification defined above.