Commit Graph

6 Commits

Author SHA1 Message Date
Justin Santa Barbara 45bc6a559d Don't use ELB DNS name for internal ELBs
We introduced some new heuristics in #3941 that meant we would access
private DNS names via the ELB's name, just as we do with gossip names.

But it's also possible to set up a VPN or DirectConnect and access a
private HostedZone directly, and in this case we don't want to use the
ELB DNS Name.  We recognize this case because the ELB can be set to
Internal (and probably should be, for minimal attack surface!)

We'll probably have to introduce a field for this, but hopefully this
heuristic is sufficient to unblock the release.
2018-03-21 20:12:15 -04:00
chrislovecnm c13b952cd3 Updating legacy Keyset to newer Keyset API Objects
Creating the keypair.yaml file if it does not exist.

If the Keypair is not found kops creates a new keyset file.  We are
setting the Keyset Task Format to 'Keypair', which denotes that we do
not have a keypair.yaml file.

This commit enables upgrading from kops 1.8 -> 1.9 while upgrading an
existing cluster.  Clusters built with kops 1.8 do not have the keypair
file, and these code changes allow the creation of that file.
2018-03-09 13:14:25 -07:00
Arto Jantunen 7639487e4f Use ELB hostname in the generated kubeconfig when using private DNS 2017-11-29 15:12:58 +02:00
chrislovecnm 1e418c3e13 more goimport updates 2017-11-04 10:03:02 -06:00
Justin Santa Barbara eddd73549c Use LB IP address for private dns 2017-04-25 01:32:27 -04:00
Justin Santa Barbara 2817e49bd6 Refactor kubeconfig building 2017-03-28 10:10:14 -04:00