I understand and agree with your sentiment but .net core on windows is definitely not rare. What's rare is asp.net windows developers knowing what a reverse proxy is (they typically install the asp.net core hosting packages).
Wait, wait, so reverse proxy functionality is available in ASP.NET?
If I'm deploying an app to a K8s cluster, I assume I would still opt for an ingress rather than making my app handle that bit of functionality? Where's the cutoff here?
Also, how do I handle discovering what ASP.NET offers in terms of functionality? Is there an overview somewhere that I missed?
RP has nothing to do with any programming language or framework, if a web server exists, you can put a reverse proxy in front of it.
In this case, asp.net core has a built-in web server named Kestrel. IIS can be used as a reverse proxy so you can have IIS forward requests to web servers bound to local host.
Personally, I think its quite hilarious that you went straight to k8's. The vast majority of asp.net code is running on servers (bare metal or otherwise).
> Personally, I think its quite hilarious that you went straight to k8's.
I work in a production environment with some 1.5mil loc that runs in a k8s cluster, so that's what I know. I'm not sure which reverse proxy we use in our ingress. I'd have to check with devops.
I feel that it's actually quite rare to run modern .NET apps on Windows Server now.