- 新しい順
- 投票が多い順
- コメントが多い順
Hello hvb,
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.
Increase the 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公式更新しました 2年前
Thanks for the update. To my other question, do you know if there are any known occurrences of readiness/liveness timeouts within EKS due to the target containers being out of memory?