Add AZ to registry message #29
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrussett
approved these changes
Oct 27, 2023
|
Approved but will not merge until all permutations of the unit tests pass. |
|
Is this okay to merge in? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is this change about?
Route Emitter sends availability zone that it received in BBS events in the Registry Message to the Gorouter.
What problem it is trying to solve?
This will Gorouter to make decisions based on balancing algorithm.
How should this change be described in diego-release release notes?
[Feature] Diego advertises the availability zone of an LRP to enable clever intra-AZ routing
Please provide any contextual information.
tracker story
issue
Thank you!