Change bookinfo to use Gateway instead of Ingress#5103
Change bookinfo to use Gateway instead of Ingress#5103
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@frankbu: The following tests failed, say
DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
The problem is that we read the Here's a snippet of the generated config: $ curl -v http://192.168.99.100:31380/login -H "Host: foo.com"
* Trying 192.168.99.100...
* TCP_NODELAY set
* Connected to 192.168.99.100 (192.168.99.100) port 31380 (#0)
> GET /login HTTP/1.1
> Host: foo.com
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< date: Fri, 20 Apr 2018 22:32:32 GMT
< server: envoy
< content-length: 0
<
* Connection #0 to host 192.168.99.100 left intact
$ curl -v http://192.168.99.100:31380/login -H "Host: foo.default.svc.cluster.local"
* Trying 192.168.99.100...
* TCP_NODELAY set
* Connected to 192.168.99.100 (192.168.99.100) port 31380 (#0)
> GET /login HTTP/1.1
> Host: foo.default.svc.cluster.local
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 200 OK
< date: Fri, 20 Apr 2018 22:34:34 GMT
< content-length: 27
< content-type: text/plain; charset=utf-8
< x-envoy-upstream-service-time: 1
< server: envoy
<
* Connection #0 to host 192.168.99.100 left intact
default handler echoing: ""%I'll get a fix out shortly. |
| @@ -0,0 +1,38 @@ | |||
| apiVersion: networking.istio.io/v1alpha3 | |||
There was a problem hiding this comment.
doesn't this have to be used in some script to do the actual testing?
There was a problem hiding this comment.
yes, it has to, let me submit a separate PR for that.
|
@frankbu Could you please move the old Ingress definition into samples/bookinfo/kube/bookinfo-gateway.yaml? It should be used in v1alpha1 documentation and tests, until v1alpha1 is removed. |
|
@frankbu Thanks for the initial cut and the example gateway config. This helped us fix a big bug (thanks @ZackButcher ). |
This is a WIP first pass at trying to use a Gateway, instead of Ingress, to access the Bookinfo app. It doesn't work yet.
@rshriram @vadimeisenbergibm : I'm not sure if the problem is just that my environment is not configured correctly for envoyv2/v1alpha3, or something else, but here's what I tried:
I'm creating a Gateway and corresponding VirtualService in the
defaultnamespace, which is using aselectorto try to use the istio-ingressgateway implementation pod running inistio-system. I'm wondering if this might be the problem. How can we do cross-namespace referencing?