kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Don't try to configure a bastion DNS name in gossip mode 

It can't be done anyway; instead we make it work (as far as we can),
and we document the workaround (which is to access it via the ELB DNS
name).

In future we could make it easier to discover this DNS name!

Issue #2881
This commit is contained in:
Justin Santa Barbara 2020-02-16 11:27:05 -05:00 committed by Justin SB
parent d4c847cfe8
commit 1e69835693
No known key found for this signature in database
GPG Key ID: 8DEC5C8217494E37
2 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
cmd/kops/create_cluster.go
View File

@ -1144,10 +1144,11 @@ func RunCreateCluster(f *util.Factory, out io.Writer, c *CreateClusterOptions) e
bastionGroup.Spec.Image = c.Image
instanceGroups = append(instanceGroups, bastionGroup)
cluster.Spec.Topology.Bastion = &api.BastionSpec{
BastionPublicName: "bastion." + clusterName,
if !dns.IsGossipHostname(clusterName) {
cluster.Spec.Topology.Bastion = &api.BastionSpec{
BastionPublicName: "bastion." + clusterName,
}
}
}
default:

13
docs/bastion.md
View File

@ -73,6 +73,19 @@ spec:
bastionPublicName: bastion.mycluster.example.com
```
### Access when using gossip (k8s.local)
When using gossip mode, there is no DNS zone where we can configure a
CNAME for the bastion. Because bastions are fronted with a load
balancer, you can instead use the endpoint of the load balancer to
reach your bastion.
On AWS, an easy way to find this DNS name is with kops toolbox:
```
kops toolbox dump -ojson | grep 'bastion.*elb.amazonaws.com'
```
### Using SSH agent to access your bastion
Verify your local agent is configured correctly