<p>I have self hosted a .NET framework 4.x version of WCF with net.tcp binding console app, which is running in Azure k8s contianer, as a selfhosted wcf service</p>
<p>exposed as <a href="http://net.tcp://CONTAINERIP:5000/WCFServiceName" rel="nofollow noreferrer">net.tcp://CONTAINERIP:5000/WCFServiceName</a></p>
<p>and the port 5000 is exposed via Loadbalancer type ingress service</p>
<p>so the client will be accessing this service like below</p>
<p><a href="http://net.tcp://LoadBalancerIP:5000/containerAppName/WCFServiceName" rel="nofollow noreferrer">net.tcp://LoadBalancerIP:5000/containerAppName/WCFServiceName</a></p>
<p>But using the loadbalancer ip is not forwarding the request to container - getting the error.</p>
<p>'There was no endpoint listening at net.tcp://LoadBalancerIp:5000/ContainerAppName/WCFServiceName that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.'</p>
<p>LB Yaml</p>
<pre><code>spec:
  clusterIP: IP.ADDRESS.OF.CLUSTER
  externalTrafficPolicy: Cluster
  ports:
  - name: nettcp
    nodePort: 30412
    port: 5000
    protocol: TCP
    targetPort: 5000
  selector:
    app: CONTAINERAPPNAME
  sessionAffinity: None
  type: LoadBalancer
status:
  loadBalancer:
    ingress:
    - ip: LB.PUBLIC.IP.ADDRESS
</code></pre>
<p>Any idea or suggesions ??</p>

<p>Guys thanks for the inputs,</p>
<p>Found the reason for the issue, since the app is deployed using the LoadBalancer type service, its not required to provide APP Name in the URL.</p>
<p>when the outside world access the service :</p>
<p><a href="http://net.tcp://LoadBalancerIP:5000/containerAppName/WCFServiceName" rel="nofollow noreferrer">net.tcp://LoadBalancerIP:5000/containerAppName/WCFServiceName</a> - WONT WORK</p>
<p><a href="http://net.tcp://LoadBalancerIP:5000/WCFServiceName" rel="nofollow noreferrer">net.tcp://LoadBalancerIP:5000/WCFServiceName</a> - THIS WORKS !!! (Solution)</p>
<p>or</p>
<p>when we do the self hosting we need to include the app name in the URI framing to host the WCF TCP Service.</p>
