Create tunnels per namespace/service #281
Merged
+20
−9
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
|
@nikolay-ngrok Thanks Nikolay — does this address some of what's called out in #267? If so, can we please call that out descriptively so stakeholders can track the progress? 🙏 |
|
@CK-Ward I don't think its addressing anything specifically, more like an issue I noticed. |
jonstacks
approved these changes
Jul 12, 2023
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
Its moving from globally unique tunnels (e.g. combo of "service-port") to ones that are only unique in their respective namespace.
How
Don't merge based on
service-port, but include the namespace too.Breaking Changes
None