Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS EKS IPv6 Cluster unable to use nginx ingress #11154

Open
rudian opened this issue Mar 23, 2024 · 4 comments
Open

AWS EKS IPv6 Cluster unable to use nginx ingress #11154

rudian opened this issue Mar 23, 2024 · 4 comments
Assignees
Labels
kind/support Categorizes issue or PR as a support question. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@rudian
Copy link

rudian commented Mar 23, 2024

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

@rudian rudian added the kind/bug Categorizes issue or PR as related to a bug. label Mar 23, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 23, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@longwuyuan
Copy link
Contributor

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

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it. and removed kind/bug Categorizes issue or PR as related to a bug. labels Mar 23, 2024
@strongjz strongjz self-assigned this Mar 28, 2024
Copy link

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.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Apr 28, 2024
@tinoejlerskov
Copy link

tinoejlerskov commented May 7, 2024

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

@github-actions github-actions bot removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Development

No branches or pull requests

5 participants