Add Kestrel section to appsettings and remove other URL settings

[tjololo]

Reverts #155

removing Kestrel section from appsettings.json results in applications trying to start on port 80 once deployed.
Ports below 1024 are marked as privileged on linux and non-root users are not allowed to bind to these ports leading to application crash on startup

Add config in appsettings back and remove applicationUrl from launchSettings and remove value of ASPNETCORE_URLS in docker image to remove warning both locally and in docker

Fixes #163

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[ivarne]

Nice! I guess the restarts wasn’t because of port 80 being privileged, but because the health check running on 5005 killed it.

I think the correct approach would be to override ASPNETCORE_URLS in the cluster, but that is a really minor point.

[tjololo]

It was an actual privilege problem, first part of the error thrown at startup:

Unhandled exception. System.Net.Sockets.SocketException (13): Permission denied
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)

The health check would be the next to fail if we granted the container more privileges than we need (bind to privileged ports).
By keeping the configuration in appsettings.json we do not force the app developer to run their app on 5005 if they for some reason don't want too without us needing to check if they have overridden the port in appsettings or in some other manor, as they can change de port in the kubernetes helm-chart if they want to

[RonnyB71]

🕹️