-
Notifications
You must be signed in to change notification settings - Fork 881
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
Add configurable probe values #387
Conversation
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.
LGTM
Co-authored-by: Tom Proctor <[email protected]>
Co-authored-by: Tom Proctor <[email protected]>
Co-authored-by: Theron Voran <[email protected]>
# How often (in seconds) to perform the probe | ||
periodSeconds: 5 | ||
# Minimum consecutive successes for the probe to be considered successful after having failed | ||
successThreshold: 1 | ||
# Number of seconds after which the probe times out. | ||
timeoutSeconds: 3 |
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.
was this desired to swap period and timeout values? It was timeout:5 and period:3 before that PR.
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.
Yeah, as discussed here: #387 (comment)
This makes hardcoded probe values configurable with some defaults out of the box so users can configure readiness/liveness probes for their environment.