5 Commits

Author	SHA1	Message	Date
Adam Sunderland	75674e7f4b	Fetch AWS PrivateDNSName for route recon	2015-07-31 10:57:38 -05:00
Justin Santa Barbara	5ae7c13ad3	AWS: Use private dns name for node name again ... This is a partial reversion of #9728, and should fix #10612. 9728 used the AWS instance id as the node name. But proxy, logs and exec all used the node name as the host name for contacting the minion. It is possible to resolve a host to the IP, and this fixes logs. But exec and proxy also require an SSL certificate match on the hostname, and this is harder to fix. So the sensible fix seems to be a minimal reversion of the changes in #9728, and we can revisit this post 1.0.	2015-07-03 01:23:51 -04:00
Justin Santa Barbara	2a5ed2f086	AWS: Use auto-scaling group to run minions ... This uses the dynamic CIDR work, and we set source-dest-check to false when we configure the route (which kind-of makes sense)	2015-06-19 10:22:15 -04:00
Justin Santa Barbara	0ad16a187d	Refactor findRouteTable to be less verbose ... Thanks for the suggestion @cjcullen	2015-06-18 17:08:32 -07:00
Justin Santa Barbara	a4e15cdf3e	AWS: Configure minion routes dynamically ... We need to implement the Routes interface, and then enable the functionality in the cluster scripts.	2015-06-18 14:59:37 -07:00