External-Mirrors/kubespray
2
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kubespray.git synced 2026-03-06 19:21:12 -03:30
Code Issues Packages Projects Releases Wiki Activity

race condition in download role under vagrant

Browse Source 
using a shared folder can cause race conditions for the download
role as it tries to download files on all the nodes to the same
shared path.  This adds a flag to run the tasks in the download
role on just one node.
This commit is contained in:
Paul Czarkowski
2016-05-17 23:30:01 -05:00
parent 5240465f39
commit ba615ff94e
4 changed files with 14 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
README.md
View File

@@ -2,7 +2,7 @@
![Kubespray Logo](http://s9.postimg.org/md5dyjl67/kubespray_logoandkubespray_small.png)
# Deploy a production ready kubernetes cluster
##Deploy a production ready kubernetes cluster
- Can be deployed on **AWS, GCE, OpenStack or Baremetal**
- **High available** cluster
@@ -10,61 +10,12 @@
- Support most popular **Linux distributions**
- **Continuous integration tests**
# Getting Started
To deploy the cluster you can use :
## kargo-cli
[**kargo-cli**](https://github.com/kubespray/kargo-cli)
## Vagrant
Assuming you have Vagrant (1.8+) installed with virtualbox (it may work
with vmware, but is untested) you should be able to launch a 3 node
Kubernetes cluster by simply running `$ vagrant up`.
This will spin up 3 VMs and install kubernetes on them. Once they are
completed you can connect to any of them by running
`$ vagrant ssh k8s-0[1..3]`.
```
$ vagrant up
Bringing machine 'k8s-01' up with 'virtualbox' provider...
Bringing machine 'k8s-02' up with 'virtualbox' provider...
Bringing machine 'k8s-03' up with 'virtualbox' provider...
==> k8s-01: Box 'bento/ubuntu-14.04' could not be found. Attempting to find and install...
...
...
k8s-03: Running ansible-playbook...
PLAY [k8s-cluster] *************************************************************
TASK [setup] *******************************************************************
ok: [k8s-03]
ok: [k8s-01]
ok: [k8s-02]
...
...
PLAY RECAP *********************************************************************
k8s-01 : ok=157 changed=66 unreachable=0 failed=0
k8s-02 : ok=137 changed=59 unreachable=0 failed=0
k8s-03 : ok=86 changed=51 unreachable=0 failed=0
$ vagrant ssh k8s-01
vagrant@k8s-01:~$ kubectl get nodes
NAME STATUS AGE
k8s-01 Ready 45s
k8s-02 Ready 45s
k8s-03 Ready 45s
```
## Ansible
**Ansible** usual commands
# Further Reading
* [**kargo-cli**](https://github.com/kubespray/kargo-cli)
* **vagrant** by simply running `vagrant up`
* **Ansible** usual commands
A complete **documentation** can be found [**here**](https://docs.kubespray.io)