Readiness probe failed

[jatin30naudiyal]

Error I got: Readiness probe failed: Get "http://ip:port/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Readiness probe failed: Get "http://ip:port/": dial tcp ip:port: i/o timeout (Client.Timeout exceeded while awaiting headers)

This error I am getting in the error logs and I checked the pods in the workloads, and it seems pods getting restarted again and again but my application is working fine.

My only concern is that if everything is fine then my GCP creates these logs and it creates in every minutes so this affects my project costing.

If anyone has any observations, please share it with me.

Thanks

[dionv]

Hello jatin30naudiyal,

What might solve this issue is increasing the periodSeconds or timeoutSeconds to give the application a longer window of time to respond. More information about how you can adjust these parameters and what they do can be found here. You might also want to check more about health checks with readiness and liveness probes here.

[sangngocle]

I have the same issue with Readiness Probe and Liveness Probe.
Increased the timeout did not do the trick. Warning still occurs. The probes are below:

 readinessProbe:
  failureThreshold: 10
  httpGet:
   path: /v1/healthz
   port: 8080
   scheme: HTTP
   periodSeconds: 60
   timeoutSeconds: 40
livenessProbe:
 failureThreshold: 10
 httpGet:
  path: /v1/healthz
  port: 8080
  scheme: HTTP
  initialDelaySeconds: 70
  periodSeconds: 60
  timeoutSeconds: 40

Really appreciate if you can help me on this.