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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[vnet][5] app proxying #41033
[vnet][5] app proxying #41033
Changes from all commits
160f4f3
0aeb933
e6292f8
65b4f60
f194ba0
80f66cc
22c21f3
49eb7c4
f951fc6
5a154cf
3914632
19375ae
bc63550
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's possible to extract local VNet app address from
net.Conn
, it'd be beneficial to include it here. When I was adding telemetry, I ran into an issue where I cannot tell the user which app they were trying to access, becausetypes.Application
alone doesn't have this info obviously.OTOH, wouldn't
net.Conn
here in the context of VNet be the connection between a local proxy and the proxy service? 🤔 So it still wouldn't tell us whether someone tried to openapp.cluster.com
orapp.custom-dns-zone.com
.Anyway, I can handle adding this down the line when I'll be working on showing recent connections in Connect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean "I cannot tell the user which app they were trying to access, because types.Application alone doesn't have this info obviously"? Seems like you have all the info you'd need about which app is being accessed here #41587
but no, i don't think you could get any extra info from the
net.Conn
here other than the client-side and vnet IP address, but I don't see why we'd need those. We wouldn't be able to get the DNS name the user is trying to connect to from the connThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I should've said "which DNS name" and not "which app they were trying to access".
Displaying the DNS name will be useful once I get around to showing connections in the UI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the only valid DNS name is the app's public_addr though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about edge cases such as an app with a custom
public_addr
, sayexample.com
, being accessed overapp.cluster.com
anyways – this should still work, right? In that,types.Application.GetPublicAddr
would returnexample.com
instead ofapp.cluster.com
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That won't work, we only query for apps by their public_addr