-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] run networking stack on Windows #51280
Conversation
3d197ac
to
7f8b0b3
Compare
9503952
to
70fb809
Compare
7f8b0b3
to
375602d
Compare
7779e33
to
a3eda59
Compare
5486ab6
to
a80b639
Compare
a3eda59
to
0c5517f
Compare
a80b639
to
6086c59
Compare
6644c87
to
e46225e
Compare
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.
lgtm with comments
// TODO(nklaassen): implement process authentication. | ||
return nil |
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.
Should we return trace.NotImplemented
for now?
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.
this is all a work in progress, for now i'd like to leave it as nil so i can actually see the process running and not just immediately exiting with an error
type OSUpstreamNameserverSource struct{} | ||
|
||
func NewOSUpstreamNameserverSource() (*OSUpstreamNameserverSource, error) { | ||
return &OSUpstreamNameserverSource{}, nil | ||
} | ||
|
||
func (s *OSUpstreamNameserverSource) UpstreamNameservers(ctx context.Context) ([]string, error) { |
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.
Where are these used?
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.
added some comments
f34a5a6
to
7ad0064
Compare
e46225e
to
493aaf0
Compare
71320a1
to
26899bf
Compare
@nklaassen See the table below for backport results.
|
Backport #51280 to branch/v17
Backport #51280 to branch/v17
Backport #51280 to branch/v17
* [vnet] run networking stack on Windows * respond to review comments
Part of RFD 195.
This PR builds on top of the remote app provider added in #51279 to create the gRPC connection between the windows service and the user process/client application, and use the remote app provider to start the VNet networking stack on Windows.
I'm not yet configuring any routing or DNS resolvers on Windows, so it doesn't actually do anything, but it's one step in the process.