It is possible that your liveness/readiness probes are timing out prematurely before your application is fully in Ready state (started responding to health checks). The timeout setting for your liveness/readiness probes have to be decided based on your application expected performance.
timeoutSeconds period and see if the probes are successful. If they are, you can conclude that the reason for the timeouts is the result of probes prematurely timing out, and figure out why your application is unable to respond within the duration expected. If the probes still fail after increasing the
timeoutSeconds, it could be result of another underlying problem, and has to be dealt separately.
You can also try to increase the
initialDelaySeconds parameter to provide enough time for your application to startup, before starting the probes.
I hope this info is helpful to you. Please comment if you have further questions, and I will be happy to help!
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- EXPERTpublished 4 months ago
- EXPERTpublished 5 months ago