EKS: Why can't a target behind my Network Load Balancer connect to its own Network Load Balancer?

With v0.44.0 of the nginx ingress controller, NLB using instance target-type will be deployed. Hair pinning is not supported in this configuration. Services hosted behing the same NLB won't be able to talk to each other going through the same loadbalancer.

After reading this piece of documentation: https://aws.amazon.com/premiumsupport/knowledge-center/target-connection-fails-load-balancer/

using IP target-type could solve this issue.

Kind: Service` should have that annotation to support "hairpinning": `service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip