Pod reports readiness probe failing on container "istio-proxy"

Our Production pods are getting restarted 2x a week and we don’t know what’s causing it. We are seeing the following diagnostics when we research the issue. ’ -Pod reports readiness probe failing on container “istio-proxy”:

Line 918: Jun 01 00:31:49 aks-agentpool3-23355474-vmss000003 kubelet[3484]: I0601 00:31:49.747275 3484 prober.go:116] “Probe failed” probeType=“Readiness” pod=“acq-prod2/tokenization-dep-v1-5b468c7d88-xfcwg” podUID=37201ae8-662c-4e00-9bb0-f7f477d4e61e containerName=“istio-proxy” probeResult=failure output=“Get [http://xxxxxxxxx:xxxxxx/healthz/ready](https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2F172.21.0.78%3A15021%2Fhealthz%2Fready%2F&data=05|01|CAPORRAS%40microsoftsupport.com|ffa5c119cfb64f6f40f808da47be5210|b4c546a47dac46a6a7dded822a11efd3|0|0|637901180000274007|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=P5OYhOByhmWHgI4O3cT8Ra%2F3lByibYq8gtMXM8seZF0%3D&reserved=0): dial tcp xxxxxxxxx:xxxxx: connect: connection refused”’. Has someone experienced this before and what is the reason or root cause? We are running ISTI) version 1.13.1 with AKS version 1.22.