Beni Cherniavsky-Paskin

An alternative could be to not provide these [for now] as generated method names, first as generic method taking the kind of object as parameter. That is, implement at least...

Oh i now remembered there is a starightforward way to add *full* set of operations on these `foo/status` sub-resources: I believe we're already getting them listed in discovery, and we're...

Sorry, I effectively blocked this by saying "there is a better way" but never implementing it :-| I won't have time to work on this until 5.0 release (#435). Why...

> The PUT and POST verbs on objects MUST ignore the "status" values, to avoid accidentally overwriting the status in read-modify-write scenarios. A /status subresource MUST be provided to enable...

Thanks. Can you help us map out the current situation? A PR with just tests for current kubeclient behavior would be wonderful (but manual "this worked and this didn't" is...

Also, is current kubeclient API adequate if you're willing to parse env vars yourself? https://github.com/abonas/kubeclient#proxies — you can set `http_proxy_uri` but can't specify a no_proxy set of hosts, right? Ooh,...

`label_selector: 'foo=1'` works, right? This would be just sugar? There are 4 selector operators, `=`, `!=`, `in`, `notin`. How would you represent the other types?

I believe the same also applies to percent-encoded username. RFC doesn't talk of password specifically; AFAICT it says percent encoding applies to any component, and syntax for whole whole userinfo...

I don't think backward compatibility is a blocker. That's the beauty of RFCs :-) If we're confident we understood the RFC right (I'm satisfied), then `http://user:%ab@...` is simply wrong URL...

Yes and no :-) Easiest case is something like this: ```ruby deployment = Kubeclient::Resource.new(YAML.safe_load(File.read('path/to/deployment.yaml'))) client.create_deployment(deployment) ``` - kubeclient currently disregards `kind` and `apiVersion` inside the Kubeclient::Resource (#208). - if you...