Reputation: 3069
I have a need to communicate from services (hosted in azure service fabric) to communicate with our on-premises resources. I would like all outgoing traffic from azure to have a static ip address so that on-premises network team can create a firewall incoming firewall rule based on this static ip address.
Since the service(s) hosted in service fabric can move from node to node (without user's intervention) and auto-scale feature can add new nodes or tear down existing nodes, I am guessing I have to use something with configuration step. So I would like to know following:
1) What needs to be modified in the fabric cluster so that all outgoing traffic has static ip address? 2) How do I modify it at configuration step so that I don't worry about node to node switch as well as auto-scale feature?
Upvotes: 1
Views: 1504
Reputation: 3776
All nodes get the same outbound IP address, the same public IP that is assigned to your cluster/load balances in Azure. You can specify the public IP address by using an ARM template to deploy your cluster, you specify a name of the public IP (and that public IP is assigned to your subscription and is then referenced in the ARM template for the cluster).
Upvotes: 3