Port sharing using Kestrel+YARP

[adityamandaleeka]

Story for tracking a port-sharing experience using Kestrel + YARP

• Fast local IPC (see Support for alternate transports microsoft/reverse-proxy#1504)
• Expose Http.Sys fast delegation proxying microsoft/reverse-proxy#1503
• Determine configuration options needed for port-sharing #39641
• Port-sharing configuration - mechanism/UX #39642

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[adityamandaleeka]

Configuration stuff can be incremental; we don't need to nail it down entirely for 7 since we can always add more later.

[rizi]

Any update on this?
br

[davidfowl]

Our goto solution for port sharing is YARP. We should have a sample somewhere on how to set it up (cc @Tratcher) but the end to end isn't as smooth as it could be. It still requires manual code and configuration, but it works.

[rizi]

Our goto solution for port sharing is YARP. We should have a sample somewhere on how to set it up (cc @Tratcher) but the end to end isn't as smooth as it could be. It still requires manual code and configuration, but it works.

@davidfowl thats great!
@Tratcher it would be great if you could direct me to the sample.

[Tratcher]

@rizi the general YARP docs are here: https://microsoft.github.io/reverse-proxy/articles/config-files.html. You don't have to do anything special from YARP's perspective for the port sharing scenario, just set up routes to decide which destination gets which requests (e.g. by host, path, etc.).

Would you want TLS/HTTPS enabled on the shared port using different host names / certificates? Then you'd need to configure Kestrel with multiple certs. https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/endpoints?view=aspnetcore-7.0#configure-endpoints-using-server-name-indication

[sebastienros]

This is the sample I worked on at some point https://github.com/sebastienros/udssample