Closed jyotimahapatra closed 4 years ago
Looks like readiness probes fail
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 36m kubelet Readiness probe failed: Get http://10.43.181.59:6070/ready: read tcp 10.43.55.163:56620->10.43.181.59:6070: read: connection reset by peer
Warning Unhealthy 11m (x3 over 15h) kubelet Readiness probe failed: Get http://10.43.181.59:6070/ready: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Normal Started 10m (x6 over 15h) kubelet Started container xdsrelay-service-gojson
Warning Unhealthy 6m15s kubelet Readiness probe failed: Get http://10.43.181.59:6070/ready: read tcp 10.43.55.163:37882->10.43.181.59:6070: read: connection reset by peer
Warning BackOff 5m36s (x10 over 34m) kubelet Back-off restarting failed container
trying to fix using #194 and #195
While rolling in staging I noticed that there are too many container restarts
This can cause xdsrelay downtime if multiple containers restart at the same time.