Closed dmitri-d closed 6 years ago
+1
I just fixed this issue. Wait for tonight's nightly and try it out again. Please let me know if things still don't work.
@rshriram: could you link to the PR here please?
Issue moved to istio/istio #6570 via ZenHub
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
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. No auth, installed using helm template per documentation
What happened: I have both bookinfo and httpbin example applications are installed, and both have gateways defined, the former via
istioctl create -f samples/bookinfo/routing/bookinfo-gateway.yaml
, the latter as explained in https://preliminary.istio.io/docs/tasks/traffic-management/ingress/#configuring-ingress-using-an-istio-gateway. Only one gateway is being used: the first one that was created.What you expected to happen: I would expect that gateway precedence would be from most specific to least specific and in accordance with
host
sections of gataway and virtual service definitions. In the example above, I would expect that all traffic tohttpbin.example.com
would be handled byhttpbin-gateway
, and the rest of the traffic would go tobookinfo-gateway
. How to reproduce it: Install both bookinfo and httpbin examples, observe that only one of the examples (the first that was installed) is accessible, all attempts to reach the other one come back with "404" errors.Feature Request: N
Describe the feature: