I did help with this after verifying I had the same issue. A workable solution was to use a modified reviews-v3.yaml from the example (I pulled the pieces from the current booking.yaml) and the had to force an update by applying the default destination rules and then deleting them (when the DRs were in place the app failed to work).
I do want to create an issue for this, maybe two since I think we want to update the docs with the new yaml, and probably need some investigation why the config update doesn’t happen until the apply/delete of the DRs happen…
{“id”: “1”,“reviews”: [{ “reviewer”: “Reviewer1”, “text”: “An extremely entertaining play by Shakespeare. The slapstick humour is refreshing!”, “rating”: {“stars”: 5, “color”: “red”}},{ “reviewer”: “Reviewer2”, “text”: “Absolutely fun and entertaining. The play lacks thematic depth when compared to other plays by Shakespeare.”, “rating”: {“stars”: 4, “color”: “red”}}]}/
istio-proxy logs
GET /reviews/1 HTTP/1.1
Host: reviews:9080
User-Agent: curl/7.63.0
Accept: /
end-user:jason
< HTTP/1.1 503 Service Unavailable
HTTP/1.1 503 Service Unavailable
< content-length: 95
content-length: 95
< content-type: text/plain
content-type: text/plain
< date: Thu, 07 May 2020 07:05:47 GMT
date: Thu, 07 May 2020 07:05:47 GMT
< server: envoy
server: envoy
<
Connection #0 to host reviews left intact
upstream connect error or disconnect/reset before headers. reset reason: connection termination/
istio-proxy logs