New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Liveness probe #76
Liveness probe #76
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Build succeeded. ✔️ pre-commit SUCCESS in 1m 36s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙏
Could the modification time of the file be used instead of writing the timestamp in the file? I.e.: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is really nice: modern smart pidfiles
I hope that openshift will let us know once exit(1) happens
Good point! PTAL @csomh |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 36s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💲 bash 💻
LIVENESS_FILE is touched upon each received message. The liveness probe checks how much time has passed since it and if it's more than LIVENESS_TIMEOUT (5min), returns 1.
Build succeeded. ✔️ pre-commit SUCCESS in 1m 51s |
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 35s |
Fedmsg liveness probe Related to packit/packit-service-fedmsg#76 Reviewed-by: None <None>
LIVENESS_FILE
is touched upon each received message.The liveness probe checks how much time has passed since it and if it's more than
LIVENESS_TIMEOUT
(5min), returns 1.