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
2016-05-22 13:48:16 -05:00
2016-03-04 16:14:01 +01:00
2016-02-10 22:58:57 +01:00
2016-03-21 11:37:35 +01:00
2016-03-01 15:37:01 +01:00
2016-05-08 10:17:11 -05:00
2016-03-04 17:39:02 +01:00

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.

Languages
Jinja 76.2%
HCL 12.1%
Python 5.5%
Shell 5.4%
Dockerfile 0.3%
Other 0.3%