Add HTTP request timeout option to KubeClientSettings #2383
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.
Proposed changes
The HTTP client used to communicate with the Kubernetes server has a default timeout of 32 seconds. In some cases, this timeout is too low, and causes failures during provider initialization. Add an option to override this timeout value. The timeout value can be overridden in the following ways, in order of precedence:
kubeClientSettings:timeout
parameter for the ProviderNote that this is distinct from the timeouts resource option, which controls how long Pulumi will wait for a resource operation to complete.
Related issues (optional)
Fix #1839