see my question on stack-overflow here - https://stackoverflow.com/questions/56025977/isito-ingress-controller-virtual-service-returning-503
because the response showing server: istio-envoy, the request at least made its way inside the cluster. What is not possible to tell from the info you posted in the SO question is the k8s service which is referenced from the VirtualService object, and the pods. Does your k8s exist and maps the pods properly? This can help to narrow down the problem:
kubectl describe svc club-finder -n club-finder-service-dev
kubectl describe pod club-finder-deployment-7dcf4479f7-8jlpc -n club-finder-service-dev
Thanks Olga. This is issue has been resolved. I had wrong VS configuration. I have another question on Networking if you dont mind please take a look at that.