Brennan Tolman
07/05/2023, 9:14 PMReadiness probe failed: Get “http://<pod IP>:8088/healthcheck”: dial tcp <pod IP>:8088: connect: connection refused
Same error for the liveness probe. Has anyone ran into this before or does anyone have an idea of how to solve it?
Additionally, if I comment out the liveness and readiness probes, the installation will succeed, but when I try to access the 8088 port on the service or pod I get a ‘connection refused’ response.
Any ideasDavid Espejo (he/him)
07/05/2023, 9:51 PMBrennan Tolman
07/05/2023, 9:59 PMYee
Brennan Tolman
07/05/2023, 10:29 PMTommy Nam
07/06/2023, 6:47 AMkubectl logs deployment/<flyte-binary deployment name> -n <namespace of your flyte deployment>
And then see what the logs say. Whenever I run into an error message like that, it usually means some part of the service is failing due to a misconfigurationkubectl get events -A
to get a list of all events in the cluster and see what's happeningBrennan Tolman
07/06/2023, 4:24 PM