Istio Ingress Controller - Throwing HTTP 503

#1

see my question on stack-overflow here - https://stackoverflow.com/questions/56025977/isito-ingress-controller-virtual-service-returning-503

#2

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