Create NLB instead of CLB for bastion #14468
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bastions didn't work in IPv6 clusters because they were placed in the IPv6-only private networks, which the CLB couldn't talk to. IPv6 bastions are now placed in dualstack networks, where they can be instance targets.
While I was at it, I switched the bastion LB from CLB to NLB. If there are any subnets with IPv6 CIDRs, it makes the NLB dualstack and publishes an AAAA DNS record for it.
Doesn't delete the old CLB (yet).