Added readiness probe to seb webservice#35
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Readiness probe tests if pod responds, as liveness probe does already.
A failed Liveness probe will stop a pod, and Kubernetes restarts it. Readiness probe will not stop a pod, but prohibit any new requests to this probe.
The readiness probe triggers first. This will allow longer lasting requests to hopefully terminate correctly. After 5 failures or 25 seconds, the pod is considered dead and will be restarted. Currently, a pod gets restarted after 5 seconds by the liveness probe.