host: ingress-nginx setting fallback to default ingress-controller backend service

[calvinxu1526]

Hi,

Just wondering any enhancement in 1.12 of ingress controller change behavior of -host setting for the ingress object, in 1.11.5 the setting of host: ingress-nginx works, while upgraded to 1.12.1, it does not work anymore unless it replaced by the fqdn(point to ingress ip), if accessing the same without updating it, it will redirect to default backend service.
rules:
- host: ingress-nginx

for example, in 1.11.5 deployment, we are able to access https://host.xxx.yyy.com/test (where host.xxx.yyy.com point yo the ingress ip) with above rules setting; while upgrade to 1.12.1, when access https://host.xxx.yyy.com/test, it fall back to the default backend service https://host.xxx.yyy.com, after update
rules:
- host: host.xxx.yyy.com
access to https://host.xxx.yyy.com/test work again.

[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.