<p>While this question might seem duplicate at first, I would ask people to go through it once. I have checked SO, for all similar questions before posting this.</p>
<p>I have an ALB ingress controller which has a registered Target Group for an application that I am trying to access via the ALB.
However the target group binding is not getting created for the application due to which the &quot;registered targets&quot; under the target group always comes as 0.
Also the LoadBalancerAssociated also comes as None.
This can be seen from the image below.</p>
<p>I have the checked the ALB pod logs and there is no error w.r.t creating the targetgroupbinding.</p>
<p>Based on some documentation here :</p>
<p><a href="https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.1/guide/targetgroupbinding/targetgroupbinding/" rel="nofollow noreferrer">https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.1/guide/targetgroupbinding/targetgroupbinding/</a></p>
<p>I see that the ALB is supposed to create the targetgroupbinding itself:</p>
<p><code>The AWS LoadBalancer controller internally used TargetGroupBinding to support the functionality for Ingress and Service resource as well. It automatically creates TargetGroupBinding in the same namespace of the Service used.</code></p>
<p>Since there is no error in the pod logs, I am wondering how can I debug this issue?</p>
<p><a href="https://i.stack.imgur.com/yz4g2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/yz4g2.png" alt="enter image description here" /></a>Any help would be appreciated.</p>
<p>Update 1 (Current scenario) :
The ALB is supposed to load balance a number of applications. So the ingress has many services under it.
The targetgroupbindings have been created for all the service except the one mentioned above.</p>

Radioactive
<p>I was able to fix the issue by adding below annotation</p>
<pre><code>&quot;alb.ingress.kubernetes.io/target-type&quot;: ip
</code></pre>
<p>Referece - <a href="https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1695" rel="nofollow noreferrer">1695</a></p>
