Deploy a Production Ready Kubernetes Cluster
 
 
 
 
 
Go to file
Paul Czarkowski c226b4e5cb fixes issue #258
Kubernetes API server has an option:

```
--advertise-address=<nil>: The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used.
```

kargo does not set --bind-address, thus it binds to eth0, in vagrant and similar
environments this causes issues because nodes cannot talk to eachother over eth0.

This sets `--advertise-address` to `ip` if its set, otherwise the default behavior
of is persisted by using `ansible_default_ipv4.address`.
2016-05-22 13:48:16 -05:00
inventory Use correct google ns for dns upstream 2016-05-17 13:19:13 +02:00
roles fixes issue #258 2016-05-22 13:48:16 -05:00
scripts upgrade k8s vers, and add a script for future upgrades 2016-05-12 15:56:30 +02:00
tests upgrade k8s vers, and add a script for future upgrades 2016-05-12 15:56:30 +02:00
.gitignore set vm box to be hashicorp hosted trusty 2016-05-20 17:04:03 -05:00
.gitmodules Remove submodules 2016-03-04 16:14:01 +01:00
.travis.yml upgrade k8s vers, and add a script for future upgrades 2016-05-12 15:56:30 +02:00
LICENSE Create LICENSE 2016-03-01 15:37:01 +01:00
README.md race condition in download role under vagrant 2016-05-20 17:04:38 -05:00
Vagrantfile race condition in download role under vagrant 2016-05-20 17:04:38 -05:00
ansible.cfg Add complete test integration 2016-02-10 22:58:57 +01:00
cluster.yml Dnsmasq runs on all nodes 2016-03-21 11:37:35 +01:00
coreos-bootstrap.yml first version of CoreOS on GCE 2016-02-21 00:06:36 +01:00
requirements.txt Add native Vagrant support 2016-05-08 10:17:11 -05:00
requirements.yml upgrade calico v0.19.0, calico-cni v1.2.1 2016-04-19 18:28:45 +02:00
uploads.yml Upload files to a separate storage 2016-03-04 17:39:02 +01:00

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

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 SlackStatus

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