Is this a BUG or FEATURE REQUEST?:

Did you review https://istio.io/help/ and existing issues to identify if this is already solved or being worked on?:

Bug:
Y

What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details

istioctl version 0.7.1
kubectl version 1.9.1

Is Istio Auth enabled or not ?
Did you install the stable istio.yaml, istio-auth.yaml.... or if using the Helm chart please provide full command line input.
Y
What happened:

Istio pilot is dropping route rules for ingress in release 0.7.1.

What you expected to happen:

I expect that istio-ingress will preserve all route rules in precedence order as is done for sidecars.

How to reproduce it:

Follow the steps in exercise 10 of the following workshop - https://github.com/retroryan/istio-workshop/tree/master/exercise-10

When you get the step to apply the route-rule-user-mobile.yaml then a curl using -A mobile will work but if you remove -A mobile then the curl command returns a 404 error. It is expected that the weighted 80/20 would be used. Looking at both the pilot and istio-ingress configurations I can see that the lower precedence route rules are not being preserved for ingress but they are for sidecar.

While this may not be fixed in the 0.7.1 release, please ensure that the same problem does not exist with the new v2 routing format for 0.8