-
Notifications
You must be signed in to change notification settings - Fork 717
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
Allow user to override readiness timeout #2260
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
@@ -30,7 +30,7 @@ const ReadinessProbeScriptConfigKey = "readiness-probe-script.sh" | |||
const ReadinessProbeScript string = ` | |||
#!/usr/bin/env bash | |||
# Consider a node to be healthy if it responds to a simple GET on "/_cat/nodes?local" | |||
CURL_TIMEOUT=3 | |||
CURL_TIMEOUT=${CURL_TIMEOUT:=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.
I feel like this env var name should be more explicit: READINESS_CURL_TIMEOUT
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.
READINESS_PROBE_TIMEOUT
?
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.
Agreed, I'll open a new PR
Relates to #2259
Default the readiness timeout 3s, but allow the user to set an env var to override the timeout for clusters that are under load. Currently it is hardcoded so changing the timeout means you need to change the whole readiness probe