The ingress addon is not listening on minikube ip:80

[victor-sudakov]

On minikube version: v1.24.0, commit: 76b94fb-dirty, Manjaro Linux:

when I enable the ingress addon, it's not listening on ports 80 or 443:

$ minikube addons enable ingress
  - Using image k8s.gcr.io/ingress-nginx/controller:v1.0.4
  - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
  - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
* Verifying ingress addon...
* The 'ingress' addon is enabled
$ telnet `minikube ip` 80
Trying 192.168.49.2...
telnet: Unable to connect to remote host: Connection refused

kubectl get pods -A shows that the ingress-nginx-controller-* pod is running. Should not it start listening immediately?

My minikube start command was:

minikube start  --disk-size=50g  --nodes=2 --insecure-registry "192.168.88.0/24" --mount --mount-string ~/.volumes:/volumes

I'm attaching the ingress-controller pod log
ingress-controller.txt

[victor-sudakov]

I had to do some guesswork. This should be documented somehow in https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/:

$ minikube node list
minikube	192.168.49.2
minikube-m02	192.168.49.3
$
$ telnet `minikube ip -n minikube-m02` 80
Trying 192.168.49.3...
Connected to 192.168.49.3.
Escape character is '^]'.

That''s where my ingress is listening: on the second node.

[medyagh]

I believe implentation of ingress assumes u recieve traffic only on control plane
do u mind sharing what driver or OS you are using ?

[victor-sudakov]

do u mind sharing what driver or OS you are using ?

Manjaro Linux, docker driver
Linux vrs11 5.14.18-1-MANJARO #1 SMP PREEMPT Fri Nov 12 20:24:59 UTC 2021 x86_64 GNU/Linux

[sharifelgamal]

This might be a bug in our ingress addon for multinode clusters. I would like to take a closer look at this, or have someone who's ingress-savvy take a look at it.

cc @prezha

[victor-sudakov]

This might be a bug in our ingress addon for multinode clusters

Where is the ingress addon supposed to run, on the master (control-plane) node or on one of the minikube-m* worker nodes?

[iam-veeramalla]

I will be happy to contribute to this. Please let me know if you can assign this issue to me.
@medyagh

[victor-sudakov]

make sure that ingress is always deployed on the 1st node in multi-node cluster (referenced by minikube ip)

Oh, thanks a lot!