CODEWITHSUNDEEP
azureazure-service-fabric
Horia Toma
Horia Toma

Reputation: 1129

Endpoint configuration for Service Fabric

I deployed an app on Service Fabric and there's an HTTP listener spawned inside. How can I configure the listening URL in relation to app/cluster? More precisely, is there any way to build this URL inside the app by retrieving some environment/role parameter ?

Suppose my cluster is called "test", then it will be available at: test.northeurope.cloudapp.azure.com. If I have an app called "Sample" for which I configured an endpoint called "SampleTypeEndpoint" inside ServiceManifest.xml, what would be the complete URL my app would listen to?

Upvotes: 0

Views: 6282

Answers (1)

Vaclav Turecek
Vaclav Turecek

Reputation: 9050

The endpoints you configure in ServiceManifest.xml right now fulfill two purposes:

  1. Allow Service Fabric to provide a unique port from an application port range, if you don't need a well-known port.
  2. When opening a web server that uses http.sys, allow Service Fabric to set up URL ACLs for a random port or a well-known port (80, 443, etc) and certificate ACLs for HTTPS.

That's basically it. The actual address on which you open a listener is up to you to determine. Typically, you open a listener on the node IP and use a NAT for ingress traffic on a domain name. In Azure, the NAT is the Azure Load Balancer which is automatically configured to accept traffic on your cluster's VIP as well as the .region.cloudapp.azure.com domain.

Here's a more thorough overview of how this works on Service Fabric cluster in Azure: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-connect-and-communicate-with-services/

Upvotes: 6

Related Questions