AWS EKS IPv6 Cluster unable to use nginx ingress

[rudian]

Has anyone encountered the same issue as me?

I deployed an EKS IPv6 cluster and modified the IPv4 to IPv6 in the deploy.yaml file according to the documentation below in the ipFamilies section. The installation was successful, but the ingress applications deployed cannot be accessed. They just time out after waiting for a long time.

The same deploy.yaml file works perfectly fine when installed on an EKS IPv4 cluster. Has anyone encountered this issue? Also, the documentation seems a bit incomplete and does not provide deployment guidelines for EKS IPv6.

deploy.yaml: https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.10.0/deploy/static/provider/aws/deploy.yaml Ingress-Nginx Deployment: https://kubernetes.github.io/ingress-nginx/deploy/#network-load-balancer-nlb

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[longwuyuan]

The information you have posted is not enough to analyze the problem.

The template of a new bug report asks questions that help to collect data on a issue. Look at the template and answer those questions by editing your issue description.

/remove-kind bug /kind support /triage needs-information

[github-actions[bot]]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[tinoejlerskov]

Just a note that we have experienced similar issue, using a AWS EKS cluster IPv6 with ingress-nginx (ipFamilies: ["IPv6"]) Using curl we checked that service was present for a given deployment, and could see that the service was responding with valid output, however the ingress fails to pass the health check and targets in Load Balancer were not coming into healthy state. There is various components in play, and we a have not been able to pin-point issue to ingress-nginx (other than it was working fine using IPv4). Also realise this is not that helpful in terms of "steps to reproduce", but will update if I get time to look more into it, and also let me know if you need more info