ansibleawsbare-metalgcehacktoberfesthigh-availabilityk8s-sig-cluster-lifecyclekuberneteskubernetes-clusterkubespray
ba615ff94e
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. |
||
---|---|---|
inventory | ||
roles | ||
scripts | ||
tests | ||
.gitignore | ||
.gitmodules | ||
.travis.yml | ||
LICENSE | ||
README.md | ||
Vagrantfile | ||
ansible.cfg | ||
cluster.yml | ||
coreos-bootstrap.yml | ||
requirements.txt | ||
requirements.yml | ||
uploads.yml |
README.md
##Deploy a production ready kubernetes cluster
- Can be deployed on AWS, GCE, OpenStack or Baremetal
- High available cluster
- Composable (Choice of the network plugin for instance)
- Support most popular Linux distributions
- Continuous integration tests
To deploy the cluster you can use :
- kargo-cli
- vagrant by simply running
vagrant up
- Ansible usual commands
A complete documentation can be found here
if you have any question you can chat with us
CI tests sponsored by Google (GCE), and teuto.net for OpenStack.