kops/tests/integration/update_cluster/bastionadditional_user-data
Justin Santa Barbara 1c3949bdfe Don't assume that we only have one subnet per AZ
I made a mistaken assumption in
dde2100a19 that we only had one subnet
per AZ, but as demonstrated in #5587 this was not the case.

What I was trying to achieve was not to include the cluster name, so
for the case of subnets this commit just uses the subnet name from the
cluster spec, which should be unique and stable.  That is hopefully at
least as meaningful.

Thankfully we hadn't released a version with the erroneous naming.

Fix #5587
2018-08-13 13:15:03 -04:00
..
data Add support for bastion aws user-data 2018-02-19 08:52:10 -05:00
id_rsa.pub Add support for bastion aws user-data 2018-02-19 08:52:10 -05:00
in-v1alpha2.yaml Add support for bastion aws user-data 2018-02-19 08:52:10 -05:00
kubernetes.tf Don't assume that we only have one subnet per AZ 2018-08-13 13:15:03 -04:00