Istio Give 503 error with no healthy upstream when pods get evicted

Istio Give 503 error with no healthy upstream when pods get evicted. Ideally pods goes down and come up when there are lack of resources on individual nodes to other nodes. During this time when it happens across multiple times and incase if it is taking a while for pod to come up, istio is still giving “no healthy upstream” error on browser when the external url for the pod is hit. Can anyone help me with this. Do I need to add any external flag or do I need to do any application level change. One solution I found is virtualService have retry strategies like attempts and perTryTimeout. But I don’t feel this is the right way to be implemented in production, either it should be something can be implemented in istio-proxy or istio-ingressgateway to get ride of this.