You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Paul Czarkowski 5240465f39 set vm box to be hashicorp hosted trusty 8 years ago
inventory Use correct google ns for dns upstream 8 years ago
roles Fix issue with check_certs playbook 8 years ago
scripts upgrade k8s vers, and add a script for future upgrades 8 years ago
tests upgrade k8s vers, and add a script for future upgrades 8 years ago
.gitignore set vm box to be hashicorp hosted trusty 8 years ago
.gitmodules Remove submodules 8 years ago
.travis.yml upgrade k8s vers, and add a script for future upgrades 8 years ago
LICENSE Create LICENSE 8 years ago
README.md set vm box to be hashicorp hosted trusty 8 years ago
Vagrantfile set vm box to be hashicorp hosted trusty 8 years ago
ansible.cfg Add complete test integration 8 years ago
cluster.yml Dnsmasq runs on all nodes 8 years ago
coreos-bootstrap.yml first version of CoreOS on GCE 8 years ago
requirements.txt Add native Vagrant support 8 years ago
requirements.yml upgrade calico v0.19.0, calico-cni v1.2.1 8 years ago
uploads.yml Upload files to a separate storage 8 years ago

README.md

Kubespray Logo

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

Getting Started

To deploy the cluster you can use :

kargo-cli

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

A complete documentation can be found here

if you have any question you can chat with us SlackStatus

Build Status
CI tests sponsored by Google (GCE), and teuto.net for OpenStack.