Readiness probe failed: probe returned not ready

Hi Team,
We are using Istio and Knative,When we enable a side-car the service deployment is failing with
Readiness probe failed: Get http://10.164.44.150:15021/healthz/ready: dial tcp 10.164.44.150:15021: connect: connection refused

Events:
Type Reason Age From Message


Normal Scheduled default-scheduler Successfully assigned dev/demo-impl-rest-7slcl-deployment-556fjhjkf to ip-10-164-44-64.ec2.internal
Normal Pulling 111s kubelet, ip-10-164-44-64.ec2.internal Pulling image “docker.artifactory.test.com/istio/proxyv2:1.6.12
Normal Pulled 111s kubelet, ip-10-164-44-64.ec2.internal Successfully pulled image “docker.artifactory.test.com/istio/proxyv2:1.6.12
Normal Created 109s kubelet, ip-10-164-44-64.ec2.internal Created container istio-init
Normal Started 106s kubelet, ip-10-164-44-64.ec2.internal Started container istio-init
Normal Pulling 97s kubelet, ip-10-164-44-64.ec2.internal Pulling image “docker.artifactory.test.com/demo-impl-rest@sha256:7bf356a13e4e47910772632214ad86bd8142041b642e93a1eac6393648dc0bad
Normal Pulled 85s kubelet, ip-10-164-44-64.ec2.internal Successfully pulled image “docker.artifactory.test.com/demo-impl-rest@sha256:7bf356a13e4e47910772632214ad86bd8142041b642e93a1eac6393648dc0bad
Normal Created 83s kubelet, ip-10-164-44-64.ec2.internal Created container demo-impl-rest
Normal Started 80s kubelet, ip-10-164-44-64.ec2.internal Started container demo-impl-rest
Normal Pulled 80s kubelet, ip-10-164-44-64.ec2.internal Container image “gcr.io/knative-releases/knative.dev/serving/cmd/queue@sha256:bba041b926e31e9d5da2cb799001b31fce4c519037334db3751eb5f69d0f227f” already present on machine
Normal Created 78s kubelet, ip-10-164-44-64.ec2.internal Created container queue-proxy
Normal Started 76s kubelet, ip-10-164-44-64.ec2.internal Started container queue-proxy
Normal Pulling 76s kubelet, ip-10-164-44-64.ec2.internal Pulling image “docker.artifactory.test.com/istio/proxyv2:1.6.12
Normal Pulled 76s kubelet, ip-10-164-44-64.ec2.internal Successfully pulled image “docker.artifactory.test.com/istio/proxyv2:1.6.12
Normal Created 75s kubelet, ip-10-164-44-64.ec2.internal Created container istio-proxy
Normal Started 74s kubelet, ip-10-164-44-64.ec2.internal Started container istio-proxy
Warning Unhealthy 69s (x2 over 71s) kubelet, ip-10-164-44-64.ec2.internal Readiness probe failed: Get http://10.164.44.150:15021/healthz/ready: dial tcp 10.164.44.150:15021: connect: connection refused

Hello,

I’m currently facing the same issue. Have you found any solution ?

Thank you !