Mooli Tayer

Hi @achille-roussel. I affraid not, any time soon, sorry.

This is opened following https://github.com/abonas/kubeclient/pull/116#issuecomment-135472512

+1

Does not sound like a desired behavior. Might be related to https://github.com/abonas/kubeclient/blob/1e7e4f4db3c3f79985651db298d60f6ca31be778/lib/kubeclient/common.rb#L302. @Ryan-Rose-Bose can you add a reproducer? I could not reproduce with master: ``` client = Kubeclient::Client.new( 'https://:8443/api', 'v1',...

Not currently on my road map. Designing the API (as well as backward compatibility) for this might prove somewhat complex. for example this proposal describes put requests, but what is...

see https://github.com/abonas/kubeclient/pull/254

Based on the link @cben [posted](https://github.com/rest-client/rest-client/blob/8874463a4/lib/restclient/request.rb#L751) I think we should catch OpenSSL::SSL::SSLError to keep the behavior we have (or thought we had). Introducing a new subclass sound good but I'd...

Some test code and different exceptions I got ### test code ```ruby require 'kubeclient' cert_store = OpenSSL::X509::Store.new cert_store.add_cert(OpenSSL::X509::Certificate.new(IO.read('ca_bad.crt'))) ssl_options = { cert_store: cert_store, verify_ssl: OpenSSL::SSL::VERIFY_PEER } client = Kubeclient::Client.new( 'https://vm-48-131.eng.lab.tlv.redhat.com:8443',...

> Is there an issue reported on this to rest client repo? https://github.com/rest-client/rest-client/issues/168 (from 2013) This might also be related: https://github.com/rest-client/rest-client/issues/286

I've seen this happening with curl after little over an hour in kubernetes v1.7.6+a08f5eeb62 ``` $ time curl -k -s -H "Authorization: Bearer $OSH_TOKEN" https://$OSH_HOST:8443/api/v1/pods?watch=139024 ... ... ... real 71m49.189s...