kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Automated way of cluster setup added 

With the purpose of easier deployment of libvirt-coreos Kubernetes cluster with the default settings, the way of installing using the automated script from https://get.k8s.io/ has been added.
This commit is contained in:
Ihor Dvoretskyi 2016-03-07 17:38:03 -08:00
parent 9d579763ff
commit 7657bf367a
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/getting-started-guides/libvirt-coreos.md
View File

@ -117,6 +117,26 @@ setfacl -m g:kvm:--x ~
By default, the libvirt-coreos setup will create a single Kubernetes master and 3 Kubernetes nodes. Because the VM drives use Copy-on-Write and because of memory ballooning and KSM, there is a lot of resource over-allocation.
There are two major ways of how-to run and configure the libvirt-based Kubernetes cluster on CoreOS instances:
#### Automated setup
To start and setup your local CoreOS-Kubernetes cluster the following command might be easily runned:
`export KUBERNETES_PROVIDER=libvirt-coreos; wget -q -O - https://get.k8s.io | bash`
or, in favor of curl:
`export KUBERNETES_PROVIDER=libvirt-coreos; curl -sS https://get.k8s.io | bash`
Just wait a few minutes, the tarball with the latest Kubernetes release will be downloaded; CoreOS instances will be spawned and Kubernetes cluster on them will be launched.
Cluster configuration will be the following: 4 KVM/QEMU instances, where 1 instance will act as a Kubernetes Master node and 3 as Minion nodes.
If you'd like to run this cluster with customized settings, run it in a manual way:
#### Manual setup
To start your local cluster, open a shell and run:
```shell
@ -135,6 +155,8 @@ The `KUBE_PUSH` environment variable may be set to specify which Kubernetes bina
* `release` (default if `KUBE_PUSH` is not set) will deploy the binaries of `_output/release-tars/kubernetes-server-….tar.gz`. This is built with `make release` or `make release-skip-tests`.
* `local` will deploy the binaries of `_output/local/go/bin`. These are built with `make`.
### Management
You can check that your machines are there and running with:
```shell
@ -291,4 +313,4 @@ usermod -a -G libvirtd $USER
#### error: Out of memory initializing network (virsh net-create...)
Ensure libvirtd has been restarted since ebtables was installed.
Ensure libvirtd has been restarted since ebtables was installed.