-
Notifications
You must be signed in to change notification settings - Fork 166
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
modify open_timeout #163
Comments
@grosser could you please provide a specific code example with how you are trying to do this? |
|
if I understand correctly the issue here - you are trying to pass a parameter that is not recognized/ supported by kubeclient itself at the moment, (did you see somewhere documentation of kubeclient usage with this parameter?) , so it makes sense that it doesn't work at the moment. |
I saw that I cannot pass it in ... that's why I opened an issue :) On Tue, Apr 26, 2016 at 10:33 PM, abonas notifications@github.com wrote:
|
@grosser it was not clear from your issue that this is a feature request, but rather it sounded like reporting a bug. |
ah sorry, definitely a feature request :) |
@grosser I don't think I'll have the time to get this implemented in the near future, but perhaps some other community member can pick up the glove. |
I am ok to add these timeouts, but remember that watches are special: https://github.com/abonas/kubeclient/pull/24/files In the past I had to force the |
I want to pass in open_timeout and read_timeout since they both seem to be too big by default,
but passing them in results in
ArgumentError - unknown keyword: open_timeout:
any idea @msufa @abonas ?
The text was updated successfully, but these errors were encountered: