User-configurable request timeouts #970
Merged
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.
What this PR does / why we need it:
Add an option (
--request-timeout
) to allow the user to specify the KUDO client's requesttimeout. The hardcoded default of 3 seconds causes problems for users whose connectivity to a target service involves relatively significant amounts of latency.
Mirror the behaviour of
kubectl
by copying the option itself and setting this to by default to 0 (no timeout).Fixes #955