Fix for multiple subnets per zone when creating load balancers #632
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.
We configure multiple subnets for each AZ for a number of reasons. On an ASG it just works, but an ELB still only allows selection of one subnet per zone. Our strategy is to just to randomly pick one subnet from the available set.
This change also includes as a separate commit deletion of a swath of unused methods in the
SubnetAnalyzer
class. That was lift-n-shifted from the Asgard codebase without paring out the bits that we don't care about.@spinnaker/netflix-reviewers PTAL