Conflict in VirtualService host when we have routes with same name (of different namespace)

[lichuqiang]

Expected Behavior

Value of Host should be unique across VirtualServices

Actual Behavior

When we have two routes (kservice) of same name in two namespaces. we will end up see same host value (route name) in their VirtualServices.

Steps to Reproduce the Problem

1. create kservice square in namespace foo
2. create kservice square in namespace bar
3. check the hosts value in their VirtualServices

Additional Info

We probably want to remove the base host name to avoid this issue
We might also need a way to distinguish altnames vs hosts

[mattmoor]

/kind good-first-issue

[lichuqiang]

As users can easily hit the issue (especially during debugging, say deploy helloworld demo in two namespaces), and currently the route name specified in hosts is not taking effect.
I'd like to remove it first, and leave the issue open, to see if we'll need other update later

[mattmoor]

@tcnghia why not close this?