Cluster Pod is Running but not Ready.

KevinH

Hello Dataiku Community,

I'm running into an issue where Pods within a active Cluster are 'Running' but not 'Ready'.

This seems to cause issues with any services that are associated with these pods.

Here's information provided within the Describe of one of these pods.

Events:

  Type     Reason     Age                        From     Message

  ----     ------     ----                       ----     -------

  Warning  Unhealthy  20m (x624 over 2d20h)      kubelet  Readiness probe failed: Get "myURL": dial tcp myIP: connect: connection refused

  Normal   Pulled     15m (x456 over 2d20h)      kubelet  Container image "myImage" already present on machine

  Warning  Unhealthy  5m40s (x12870 over 2d20h)  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 502

  Warning  BackOff    55s (x9291 over 2d20h)     kubelet  Back-off restarting failed container apinode-container in pod dku-myContainer

Any help or suggestions is greatly appreciated. Thank you.