Beni Cherniavsky-Paskin

Also worth mentioning I think we need #332 anyway. it'll expose _a_ way — though quite different and perhaps less friendly — to use one client with many groups, something...

I suspect it is but don't know for sure. - is rest-client thread-safe? - is http gem thread-safe? - I think the only Client mutation during use is lazy discovery....

I think we *want* it to become thread-safe. That's the only sane contract for a high-level library... Do you know details on problems you saw? Should discovery take a mutex,...

@mindfulmonk have you also seen this problem with create/get/update/delete, or only watch? (I'm asking because these use different HTTP libs.) I'm not able to reproduce the underlying problem this PR...

According to https://github.com/httprb/http/blob/256539edd9ad8acf0f8a424114ac9fae6fb44782/lib/http/request.rb#L199-L202 http gem also always set a host header (and if we want to set it ourselves we maybe should include non-default port as that code does?) Could...

Sorry, missed your reply and forgot about this. Fascinating. The log shows exactly same `Host: example-cluster.com` header sent before and after, yet the result is different. @ilackarms, you know http...

Thanks. I'm still reluctant to put in a "magic" fix if I can't explain what's the problem and how it helps... Trying to investigate more... Staring at `http` code, I...

Sorry fat finger. Are any of those useful for the 3 patch variants, or just for apply? (I'm not sure the pattern of kubeclient whitelisting query params per action is...

cc @shiramax. I believe your kubevirt VNC use case won't be helped by any _generic_ sub-resource functionality, which this issue is about; but #417 (params to do your own connection)...

#422 wants to patch `foo/status`, and I think we should instead allow all verbs on `foo/status`.