Nginx should bind to tcp6 as well as tcp4

[sajal]

I would be interested in having nginx listen to ipv6. I am using this with hostNetwork: true so I am not limited by lack of IPv6 support in kubernetes.

@thetechnick commented that they have "pull requests incoming for ipv6 binding", I would like to inquire of the status of that.

I think a good default is to listen on IPv6 by default. For PoC I turned on IPv6 by editing the template.

listen 80{{if $server.ProxyProtocol}} proxy_protocol{{end}};<br/>listen [::]:80{{if $server.ProxyProtocol}} proxy_protocol{{end}};<br/>

Is that the correct way to make nginx listen on both v4 and v6?

Aha! Link: https://nginx.aha.io/features/IC-112

[pleshakov]

@sajal
that's the correct way

[thetechnick]

@sajal

@thetechnick commented that they have "pull requests incoming for ipv6 binding", I would like to inquire of the status of that.

I am currently working on #77, which will change all variable names in the ingress template from $server to .Server. Because of that I want to postpone the pull request for ipv6 until this is merged, so we do not have to fix the otherwise occuring merge conflicts.

Edit:
The title of this issue is, that ipv6 binding should be the default.
@pleshakov whats your opinion on this matter?

[kaja-mohideen]

Any idea when this will be implemented?

I'm trying to use nginx for supporting both IPv4/Ipv6 to front a All-IPv4 K8S cluster.

Ref: https://serverfault.com/questions/969097/nginx-ingress-to-support-ipv4-and-ipv6-for-kubernetes-ipv4-cluster

[pleshakov]

@sajal we're not planning to support it yet.

as a workaround, you can customize the listen directives in the templates as shown in #96 (comment) Please also see https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/custom-templates You also need to configure hostNetwork: true in the IC pod templates. In this case, it is assumed that the clients will use public IPs of the nodes where the IC is running to connect to the Ingress Controller.

[github-actions]

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

[github-actions]

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

[unixfox]

Hello,

Why can't we just add this into the default template:

listen [::]80 {{if .ProxyProtocol}} proxy_protocol{{end}};
listen [::]443 ssl {{if .HTTP2}} http2{{end}}{{if .ProxyProtocol}} proxy_protocol{{end}};

?

It seems like a very easy fix and the community NGINX ingress is already supporting IPv6, so why is the NGINX ingress from NGINX inc lagging behind?

Would the members of the NGINX Inc accept my pull request if I add similar lines to the default template that would allow IPv6 support?

[Frankkkkk]

Related to #991

[github-actions]

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

[Frankkkkk]

/unstale

[github-actions]

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

[Frankkkkk]

Unless I'm mistaken, this has been fixed in #2576 ? 🎉 Ping @jjngx

[brianehlert]

It is. There were multiple ipv6 related issues.