Add a config listener to Gorouter #523
Draft
+429
−0
Conversation
This file contains hidden or 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
cf-foundation-community-automation
bot
moved this to Inbox
in Application Runtime Platform Working Group
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
** This is a draft PR implementation for a new /config endpoint on the gorouter **
Summary
The gorouter config that is applied through a Bosh Tile is not visible externally and hence troubleshooting failures has become a challenge. The failures such as an App route registered on a Gorouter when it should not be, and vice-versa. Also, it is hard to co-relate whether the compute and network isolation intended by the customer and provided through the Tile deployment has really taken effect on the gorouters.
This PR is to introduce a new
/configendpoint to the gorouters which will return information as below.(1) What segment(s) the router instance group was deployed for.
(2) Which segment(s) the router forwards traffic to.
(3) Few compute isolation config.
(4) Few network isolation config.
(5) Load Balancer config.
Backward Compatibility
Breaking Change? No