/test istio-pilot-e2e-envoyv2-v1alpha3-master

cc @nrjpoddar

@mandarjog no, I don't think there is test added yet. I can add one.

Can you link the issue about what got broken? I was suspicious about setting the attribute for passthrough routes.

@kyessenov I don't think setting destination.service.host to BlackHole/Passthrough broke anything. This PR makes that field just more useful by making the default more reasonable.

Ok thanks for explaining. I wasn't sure if there is an issue or not.

@bianpengyuan is something blocking its merge?

In response to a cherrypick label: new pull request created: #16949

Folks should I be expecting this in the current 1.3 release? if so, it doesn't appear to be working:

{destination_app="unknown",destination_service="unknown",destination_service_name="unknown",destination_service_namespace="unknown",destination_version="unknown",destination_workload="unknown",destination_workload_namespace="unknown",instance="10.198.17.85:42422",job="istio-mesh",reporter="source",request_protocol="http",response_code="502",response_flags="-",source_app="sauron-web",source_version="unknown",source_workload="sauron-web",source_workload_namespace="sauron-web"}

@Stono It is in 1.3.1, and it needs proxy to be upgraded to 1.3.1.

@Stono here's a blog istio/istio.io#5027 I wrote on this topic. The PR will be merged once 1.3.1 is released.

Netlify link might be better for reading: https://deploy-preview-5027--preliminary-istio.netlify.com/blog/2019/monitoring-external-service-traffic/

Thank you :-) looking forward to 1.3.1 then

Confirmed this is working 1.3.1 pre-release #17385

We might need to revisit this in light of the discovery made recently (#18818).