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.

Sign up for GitHub

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

Jump to bottom

Report dual stack Node IPs instead of just the first #10756

Open
akdor1154 opened this issue Dec 13, 2023 · 1 comment · May be fixed by #10757
Open

Report dual stack Node IPs instead of just the first #10756

akdor1154 opened this issue Dec 13, 2023 · 1 comment · May be fixed by #10757
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@akdor1154
Copy link

If I have ingress-nginx running

  • with no service
  • on hostNetwork
  • on a dual stack node

then currently it reports only the first IP of the node as the resulting Ingresses' IPs.

I would like it to set the Ingresses' IPs to both the IPv4 and IPv6 addresses of the node.

I'm preparing a PR with a straightforward approach to this.
@akdor1154 akdor1154 added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 13, 2023
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 13, 2023
@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.

@akdor1154 akdor1154 linked a pull request Dec 13, 2023 that will close this issue
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
[SIG Network] Ingress NGINX
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

return multiple IPs for nodes when reporting ingress status akdor1154/ingress-nginx
2 participants
@akdor1154 @k8s-ci-robot