IPv4 and IPv6 Listeners

[mpstefan]

The ask is to support IPv6 in addition to IPv4. The short path is to assume dual stack and not be exclusive to IPv4.

The customer should not be restricted to using only one IPFamily, they should simply be able to use the IPFamily of choice for either the client side or upstream side. For v1 the listener should default to both.

Community issue: #1893

Cluster needs to have IPv6 enabled or NGINX will fail to reload
Operating system for NGINX data plane needs to have IPv6 enabled to send and host on IPv6

Acceptance Criteria

• The user can configure if NGF to use IPv4 and/or IPv6 on installation.

Tasks

Preview Give feedback

1. IPv6 and IPv4 Configuration on Installation #2086
   area/nginx-configuration enhancement refined size/medium +4
   
2. Functional test for IP version support #2087
   refined size/medium tests +3
   

[akdor1154]

it seems i can't get nginx gateway to listen on ipv6 with v1.0.0, would it be right to assume I need to wait for this issue to be implemented if I want my nginx pod to listen on ipv6?

[pleshakov]

@akdor1154

would it be right to assume I need to wait for this issue to be implemented if I want my nginx pod to listen on ipv6?

that is correct. with its current configuration in NGINX Gateway Fabric, NGINX doesn't listen on ipv6.

[bjee19]

@akdor1154, is ipv6 something that you would like to see be implemented sooner than later / is it something that you're interested in using or is it just more of a curiosity / trying things out thing?

[akdor1154]

I chose to stick with ingress-nginx as a result of this, but the whole project is just a hobby non-production homelab.

[bjee19]

ok thanks for letting us know, hope you give us a try again in the future when we've got a bit more features!

[github-actions]

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.