<p>I’m trying to set up <code>argocd</code> in EKS cluster using helm. I want to use ALB as a load balancer.  The UI is reachable through <code>http://node_ip:8080</code>, but not through the ALB or the LB that was created.</p>
<p>Here is my configuration:</p>
<pre><code>  ingress:
    enabled: true
    annotations:
      kubernetes.io/ingress.class: alb
      alb.ingress.kubernetes.io/backend-protocol: HTTPS
      alb.ingress.kubernetes.io/listen-ports: '[{&quot;HTTP&quot;: 80}, {&quot;HTTPS&quot;:443}]'
      alb.ingress.kubernetes.io/scheme: internal
      alb.ingress.kubernetes.io/target-type: IP
      alb.ingress.kubernetes.io/certificate-arn: &quot;${cert}&quot;
      alb.ingress.kubernetes.io/ssl-policy: ELBSecurityPolicy-FS-1-2-Res-2020-10
</code></pre>
<p>Here is the ingress that was created:</p>
<pre><code>kubectl get ing -n argocd

NAME            CLASS    HOSTS                         ADDRESS                                                          PORTS   AGE
argocd-server   &lt;none&gt;   eks-test-alb-argocd.abc.com   internal-k8s-argocd-argocdse-111.222.us-east-1.elb.amazonaws.com   80      9h
</code></pre>
<p>Here is what i get when trying to use the DNS or the LB address:</p>
<pre><code>curl internal-k8s-argocd-argocdse-111-222.us-east-1.elb.amazonaws.com

&lt;html&gt;
&lt;head&gt;&lt;title&gt;502 Bad Gateway&lt;/title&gt;&lt;/head&gt;
&lt;body&gt;
&lt;center&gt;&lt;h1&gt;502 Bad Gateway&lt;/h1&gt;&lt;/center&gt;
&lt;/body&gt;
&lt;/html&gt;
</code></pre>
<p>What could be the issue?</p>

<p>Well, I have found the issue, and it was much simple than i thought.</p>
<p>Since the pods are listening to port 80, all I had to do is to change the <code>backend-protocol</code> to <code>HTTP</code>. That's it.</p>
