title: AWS Fargate backed EKS application not reachable over loadbalancer service
body: <p>I have created a Fargate backed EKS cluster and deployed an application listening to 9090. Remember I am using a label &quot;worker: fargate&quot; so that my apps are created in fagrate nodes and not on EKS worker nodes.</p>
  <p>I have made sure the application is listening to ::9090 and respond well when performing with a curl localhost 9090</p>
  <p>I then created a service of type loadbalancer with the below definition:</p>
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-js lang-js prettyprint-override"><code>apiVersion: v1
  kind: Service
  metadata:
    name: mytestapp
  spec:
    type: LoadBalancer
    selector:
      app: mytestapp
      worker: fargate
    ports:
      - protocol: TCP
        port: 9090
        targetPort: 9090</code></pre>
  </div>
  </div>
  </p>
  <p>I can see this has created a classic load balancer, under listener I see 9090 port and a random Nodeport.</p>
  <p>The Loadbalancer backend health state shows &quot;Outofservice&quot; and telnet to the LB endpoint and port 9090 does not work.</p>
  <p>I am confused what is wrong here. Note that I have opened security groups both inbound and outbound as well in the custer.</p>