<p><strong>Update: it says &quot;0 of 0 instances in service&quot; in the Basic Configuration of my AWS Loadbalancer</strong></p>
<p>I know, this is a duplicate of several other questions with the same title, but there a almost no answers, so I am asking this myself:</p>
<p>I have followed this tutorial to the letter (twice)
<a href="https://kubernetes.io/docs/tutorials/stateless-application/expose-external-ip-address/" rel="nofollow noreferrer">https://kubernetes.io/docs/tutorials/stateless-application/expose-external-ip-address/</a></p>
<p>I use the managed kubernetes by aws based on fargate.</p>
<p>All I get when calling the url in the browser is an empty response. I have checked that the loadbalancer has the correct permissions and ports. Everything is fine there (all automatically setup by AWS).</p>
<p>I have verified that all pods are running, and that the service is running. Aditionally, this does not seem to be a problem concerning this specific tutorial and its setup. Actually I had this &quot;empty-response&quot;-problem with another hello-world-deployment (from the aws-tutorial) yesterday.</p>
<p>There seems to be something fundamentally wrong. Maybe I forgot a step in the setup of my kubernetes cluster? It is all managed though...</p>
<p>Thanks for any pointers!</p>

<p>When using Fargate withg an EKS cluster, you don't have access to nodes instances. this means that Fargate doesn't support CLB/NLB.</p>
<p>With Fargate it is recommended to use the <a href="https://aws.amazon.com/blogs/containers/using-alb-ingress-controller-with-amazon-eks-on-fargate/" rel="noreferrer">ALB Ingress Controller</a></p>
<p>example of ingress rule:</p>
<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/scheme: internet-facing
    kubernetes.io/ingress.class: alb
  labels:
    app: hello-world
  name: hello-world
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: my-service
          servicePort: 8080
        path: /*
</code></pre>
<p>Note: If your EKS cluster has a mix of Fargate and EC2 instances, then you'll ma able to uses the classic loadbalancing, that will first reach EC2 eks instances, then it will be forwarded to your Fargate pods using internal Kubernetes routing.</p>
