-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Config / RequestConfig rollingTimeout is unused #4826
Milestone
Comments
getUploadConnectionTimeout is no longer used, the more general getWebsocketTimeout is used instead. |
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Feb 14, 2023
this means there's no reason to keep the rollingTimeout RequestConfig option
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Feb 14, 2023
this means there's no reason to keep the rollingTimeout RequestConfig option
11 tasks
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Feb 15, 2023
this means there's no reason to keep the rollingTimeout RequestConfig option
manusa
pushed a commit
to shawkins/kubernetes-client
that referenced
this issue
Feb 20, 2023
this means there's no reason to keep the rollingTimeout RequestConfig option
manusa
pushed a commit
that referenced
this issue
Feb 20, 2023
this means there's no reason to keep the rollingTimeout RequestConfig option
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Feb 20, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This appears to predate the recent changes to aggregate some of the timeout logic and blocking delete. It should be used in the event that the context timeout is unset and passed to the rolling update.
The text was updated successfully, but these errors were encountered: