I am currently experimenting the Naming Service resolution on my 5-nodes local cluster and encountering some resistance :). Here is the deal:
My Local Cluster Manifest defines an endpoint & protocol for the Reverse Proxy on each "fake" node. The entry is HttpApplicationGatewayEndpoint.
If I browse through the explorer on port 19080, I can find my running Stateless Service (Kestrel Swagger API) at this URL: http://localhost:8145/7303da82-4ed2-4548-996d-1b5e8f49c7c9/131574695524899694/swagger/
If I try to use the Reverse Proxy Gateway with the service full-name I get:
http://localhost:19081/SHRec.SF.App/SHRec.SF.Front.ClientAPI/swagger
Which gets translated to:
http://localhost:19081/7303da82-4ed2-4548-996d-1b5e8f49c7c9/131574695524899694/swagger/
Where one can detect that the port is incorrect for a direct connection and that normally one should not be able to see the internal address...
Any Idea ?
Best :)
Cf last comment, everything runs smoothly locally and on the Cloud :)