@TaviTruman-4790 Apologies for the delay in response and all the incovinience caused by the issue.
There are a couple options available for load balancing TCP connections to service fabric. You can create a helper discovery service which is available over HTTP. The client application will first connect to the discovery service and retrieve an externally reachable TCP endpoint for one of the instances of your TCP service. The client then connects directly to the TCP service without going through the L7 reverse proxy.
Your discovery service should be Service Fabric aware and implement RegisterServicePartitionResolution ChangeHandler to keep track of the TCP endpoints available.
You can read more about it here.
Another option is to introduce a dedicated L4 reverse-proxy/load-balancer (e.g. nginx, traefik, haproxy) between your client and TCP service. If your TCP service is stateful, this option is trickier as you will need a mechanism to determine the appropriate service endpoint based on partition hash and you need to keep track of any scaling events. For stateful TCP service, you'd need much of the same implementation as the discovery service, but the Service Fabric details would feed into the configuration of the proxy rather than being returned to the client. Traefik has a service fabric plug-in which you might be able to leverage to get you started if you choose to run your L4 reverse-proxy inside the ASF cluster.
Hope it helps.
Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics.