Specify IP addresses the Ingress controller is listening on

[cluk1]

We are running k8s on bare metal. It would be great to specify the IP addresses the nginx ingress controller is listening on.

This would enable us

1. to route traffic for specific IPV4 IPs to k8s
2. also route (http) traffic for IPV6 addresses to k8s.

AFAIK 1) can be achieved by using a service in front of the ingress ctrl with external (IPV4) addresses. But currently we do not see any possibility to achieve 2).

Might be related to #131 .

Thanks a lot!

[euank]

2 is related to #34; I use a daemonset with net=host to manage ipv6 ingress

[bprashanth]

you probably want to specify the name of the interface instead of the actual ip? eg if you just want to listen on cbr0 or docker0 with net=host, so the system is free to manage ipam. The way the nodecontroller assigns cidrs to nodes today, you don't know the range a given node will get.

[cluk1]

@euank Thanks for the pointer. But isn't nginx listening on all IPV4 and IPV6 addresses which are available on the host in that setup? We are trying to migrate one IP at a time to k8s and keep the other IPs and services working outside of k8s.

[cluk1]

@bprashanth Thanks for the suggestion. We are using a fixed /28 subnet for our incoming traffic. Therefore it would be great to specify exact listen addresses for nginx. What would also work is using the hostnames from the ingress object for the nginx listen directives. Though my attempts using a custom nginx template doing that failed utterly. ;)

[euank]

@cluk33 indeed, it is for me. It's not ideal, but it's worked for me so far. Specifying only one ipv6 address would be saner.

[euank]

@bprashanth on the other hand, you don't necessarily want to listen on an interface for the case of eth0 or whatever since you've potentially got multiple different ips on it.

[TattiQ]

I also use bare metal and would be great to be able to assign an external IP for ingress
and thus use the hostnames from the ingress resource for the nginx listen directives.
Currently I am not sure how I can get this working - private docker registry (2 rc replica's, talking to the same redis deployment + the same filesystem (nfs mount to all kube nodes) ) behind a nginx controller + ingress resource points to a hostname docker-registry.bla.bla . My understanding is docker-registry.bla.bla should be pointing to the nginx external IP in DNS which in its turn redirects traffic to the endpoints in round robin. But we have no way to point it to nginx, have we ? Please correct me if I am wrong somewhere there, I am a newbie to kubernetes

[bowei]

This issue was moved to kubernetes/ingress-gce#24

[guoshimin]

@bowei Can we reopen this one? It was moved to ingress-gce and closed there as "irrelevant to gce".

[zerthimon]

I'd also like to have the possibility to specify the IP for the controller to listen on.
I'm using a daemonset with net=host.

[mentos1386]

@bowei can this be reopned? I'm also in need of specifying on which ip it should listen on, instead of just using 0.0.0.0.

[j-mahlke]

Is there a solution for this issue from 6 years ago?

[W1zzardTPU]

Same problem, switched to HAProxy ingress and was up and running within 15 minutes

[Tashows]

@bowei Can you please reopen this? As more people pointed out, this was never supposed to move to another project.

[bowei]

/reopen

Sorry about that

[k8s-ci-robot]

@bowei: Reopened this issue.

In response to this:

/reopen

Sorry about that

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-sigs/prow repository.

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

[longwuyuan]

ingress-nginx/charts/ingress-nginx/values.yaml

Line 508 in 01d0a20

externalIPs: []

[Tashows]

ingress-nginx/charts/ingress-nginx/values.yaml

Line 508 in 01d0a20
externalIPs: []

Tried this, but it just appends the externalIPs you set to the already discovered IPs. The desired effect would be to override them.

[strongjz]

Looks like it was answered in the other issue

https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/status/status.go#L74C1-L80C59

// statusSync keeps the status IP in each Ingress rule updated executing a periodic check
// in all the defined rules. To simplify the process leader election is used so the update
// is executed only in one node (Ingress controllers can be scaled to more than one)
// If the controller is running with the flag --publish-service (with a valid service)
// the IP address behind the service is used, if it is running with the flag
// --publish-status-address, the address specified in the flag is used, if neither of the
// two flags are set, the source is the IP/s of the node/s