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
..
kube-apiserver.manifest.j2	fixes issue #258	2016-05-22 13:48:16 -05:00
kube-controller-manager.manifest.j2	Changed path to hosts ssl certs from /usr/share/ca-certificates to /etc/ssl/certs/ which fixes https problems in kube-controller-manager and kube-apiserver (#189) caused by the lack of certificates on debian and redhat based systems.	2016-04-01 09:34:28 +02:00
kube-scheduler.manifest.j2	use master election option instead of podmaster	2016-03-21 22:25:09 +01:00