Tye picked random ports while the project app config already specified ports. https://github.com/dotnet/tye/issues/178
Even with next to no configuration or additional work on your API Swagger already provides great insights into your API.
A Route is the inbound URL which the reverse proxy is going to act on. The cluster is a list of potential destination URLs.
In Part one we setup the health check endpoints, now to add a frontend.
This follows on from my previous post Secure ASP.NET Core Health Checks to a specific port and assumes that you already have your service running over 2 ports and have specified a
ManagementPort in the appsettings.json file.
To secure Health Checks it is possible to make them available on internal addresses only and on a different port to the publicly served pages/API endpoints.