subnet discovery: new flag to enable prioritization by availability-zone locale #3585
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.
Issue
N/A
Description
Draft PR to gather opinions about adding a flag to enable different algorithms for the subnet selection from multiple qualified ones when they all come from the same availability zone. The sorting by subnet IDs remains the default. A new sorting alogrithm
azfirst
is added to prioritizeavailability-zone
locale over other locales. This change may help to reduce the random aspect of the subnet selection when multiple locales are used in a cluster.Example of where this can be helpful:
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯