c226b4e5cbbe1428733c9075c2b3f3c0b100680a
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`.
##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.
Description
Deploy a Production Ready Kubernetes Cluster
ansibleawsbare-metalgcehacktoberfesthigh-availabilityk8s-sig-cluster-lifecyclekuberneteskubernetes-clusterkubespray
Readme
147 MiB
Languages
Jinja
76.2%
HCL
12.1%
Python
5.5%
Shell
5.4%
Dockerfile
0.3%
Other
0.3%