contrib/vagrant: enable hubble listener on :4244 (TCP) by default #11618
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
Hubble-relay needs to connect to hubble peers for multi-node support. Enabling hubble server on :4244 makes working on hubble-relay easier as one does not need to perform an extra step to reconfigure every VM on a locally deployed vagrant k8s cluster to start playing with hubble-relay. Signed-off-by: Robin Hahling <[email protected]>
rolinh
added
kind/enhancement
tklauser
approved these changes
May 20, 2020
gandro
approved these changes
May 20, 2020
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.
Hubble-relay needs to connect to hubble peers for multi-node support.
Enabling hubble server on :4244 makes working on hubble-relay easier as
one does not need to perform an extra step to reconfigure every VM on a
locally deployed vagrant k8s cluster to start playing with hubble-relay.