Getting Readiness probe failed when using cert-manager-istio-csr

[PrashantGSIN]

I am using cert-manager's external plugin to get the certificate. I am successfully able to get the cert through the external plugin. I am getting readiness probe failed error shown below:

Events:
Type Reason Age From Message

---

Normal Scheduled 69s default-scheduler Successfully assigned cert-manager/cert-manager-istio-csr-76f6f8c4f-fkwct to ip-192-168-52-136.eu-west-1.compute.internal
Normal Pulled 68s kubelet Container image "quay.io/jetstack/cert-manager-istio-csr:v0.8.1" already present on machine
Normal Created 68s kubelet Created container cert-manager-istio-csr
Normal Started 68s kubelet Started container cert-manager-istio-csr
Warning Unhealthy 6s (x9 over 62s) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500

The cert-manager-istio-csr pod is failing its health checks because the tls_provider and grpc_server are reported as "not ready."

This means that the application inside the container is not able to pass its health checks and is therefore not ready to serve traffic.

Can anyone guide me to overcome this error ?

[PrashantGSIN]

So, I have investigated further and found that when using the external issuer the cert-manager-istio-csr pod is failing because of the tls_provider and grpc_server. As they are not getting ready in any situation. So I have tried with the self signed certificate and it is working smoothly. Any ideas about this why it is not working with external issuer of cert-manager ?