 This case can occur if the virtual service
actually blocks traffic by never routing traffic to the pod&rsquo;s subset. For
example:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ export REVIEWS_V2_POD=$(kubectl get pod -l app=reviews,version=v2 -o jsonpath=&#39;{.items[0].metadata.name}&#39;)
$ istioctl x describe pod $REVIEWS_V2_POD
...
VirtualService: reviews
   WARNING: No destinations match pod subsets (checked 1 HTTP routes)
      Route to non-matching subset v1 for (everyth