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
..
BUILD.bazel	gazelle updates with new bazel version	2017-11-05 17:41:53 -07:00
config.go	Refactor kubeconfig into its own package	2017-01-15 18:19:39 -05:00
create_kubecfg.go	Don't use ELB DNS name for internal ELBs	2018-03-21 20:12:15 -04:00
kubecfg_builder.go	kops not Kops	2017-11-29 00:38:49 -07:00