I know it's late, but somebody might have similar situation.

In my case, problem was next:

When executing curl command:

curl http://<ip-address>:<k8s-svc-port> -H 'Host:foo.com'

HTTP request looks something like:

GET / HTTP/1.1
Host: foo.com
User-Agent: curl/7.64.0
Accept: */*

When executing in browser, http request looks something like this: firefox http request example

Host: foo.com:32009
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
...

And that's the difference, because haproxy ingress controller looks for host field of http request. In this case,
- curl sets header Host:foo.com
- browser sets header Host:foo.com:32009, which is not recognized by haproxy
(haproxy expects foo.com and gets foo.com:32009)

So, ingress controller works fine, it's the browsers http request that's making problem.

I hope this can be helpful.

Upon looking at your YAML file, I can see that you do not have a 'default backend' in the Ingress service. The 'default backend' will define the rules to take if the page results in an error 404.

The ‘default backend’ is different from the backend under the path. The default backend has to be right under the spec.

For more information on the default backend, you may read through the k8s documentation

This is the how you should define a default backend in your YAML file.

spec:
   backend:

For the same reason, it is not working on the chrome browser. There is no 'default backend'.