3 ms·
You can use ConfigMap instead of volume for providing the config (it is also nice since you can merge the application settings with the deployment manifest). F
by neonsunset 2y ago
You can use ConfigMap instead of volume for providing the config (it is also nice since you can merge the application settings with the deployment manifest).
For certificates, you can retrieve them from whatever vault solution you have on hand, or you can, indeed, access a volume. I do not understand the difficulties with volume mounting however which is a standard practice.
Configuring Kestrel programmatically is really straightforward too: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/endpoints?view=aspnetcore-9.0#configure-https-in-code https://learn.microsoft.com/en-us/aspnet/core/fundamentals/s...
I'm not saying just using Nginx is a bad choice, but, much like using Redis for things that have no business using Redis, I've seen a fair share of the same misuse with Nginx.
- stackskipton 2y agoIf you have ConfigMap, you have Kubernetes so Ingress is solved for you. ;) > Configuring Kestrel programmatically is really straightforward too Sure, but Developers tend to not want to futz with it. My use case is our application lives in a container, most of time we host it but occasionally a customer demands they host it so we give them the container. Some host it on Windows (we do build a Windows container of our application :vomit:) and some on Linux. In any case, we require them to use reverse proxy because HTTPS with Kestrel was becoming too high of support so we require they provide HTTPS proxy. We recommend IIS ARR for Windows users, and CaddyServer for Linux but Linux users tend to not need our advice. EDIT: Our hosting platform is Azure Kubernetes Service, 100% Linux Nodes.
- neonsunset 2y agoCaddy :( Might've as well shipped NativeAOT-compiled (or single-file trimmed JIT) build of YARP. Faster than Envoy which is faster than Caddy. Only Nginx and HAProxy are faster than YARP. (also bumped https://github.com/dotnet/yarp/issues/261 https://github.com/dotnet/yarp/issues/261)