Jaegar using ingress for deployment

Bug

Description

Currently Rancher is using ingress for deployment. With the recent transition to 1.10, Jaeger has also begun to use ingress for deployment which overrides rancher. Therefore, it is not possible to access Rancher. I am curious as to why Jaeger is using ingress, when it used to be operating on Istio. Are there any recommendations in fixing this bug?

BigBang Version

1.10

kubectl get ingress -A NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE cattle-system rancher * 10.192.86.49,10.192.87.125,10.192.87.187 80 3h51m jaeger jaeger-query * 10.192.86.49,10.192.87.125,10.192.87.187 80 75m

via the deployed umbrella git tag

kubectl get gitrepository -n bigbang 1.10