Allow setting a custom timeout for k8s commands #25
Conversation
This file contains 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
danegsta
commented
Oct 2, 2023
| private static GroupVersion GroupVersion => Model.Dcp.GroupVersion; | ||
|
|
||
| private IKubernetes? _kubernetes; | ||
| private TimeSpan _maxRetryDuration = TimeSpan.FromMilliseconds(1000); |
There was a problem hiding this comment.
This will technically slightly increase the default command timeout; we may want to consider a smaller number.
karolz-ms
approved these changes
Oct 2, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Rather than a maximum number of retries, use a maximum retry duration (and allow overriding for a given client) to let us increase the timeout on our initial connection after launching DCP.