Beni Cherniavsky-Paskin

See my comment https://github.com/abonas/kubeclient/pull/293#issuecomment-467421832 on similar attempt. I think we do want a base class (or module) that will cover all our exception non-http errors too. However, it's good time...

Summary of current signatures wrt. name & namespace: ``` get_foos(namespace: 'namespace', **opts) # namespaced collection get_foos(**opts) # all namespaces or global collection get_foo('name', 'namespace', opts) # namespaced get_foo('name', nil, opts)...

I don't want to break comaptibility, especially as this would affect almost every call. I'll consider *allowing* name too as keyword. Though it's not optional. See also #332 that proposes...

BTW, there is a small discrepancy between what k8s documents and what client-go does, related to rare issue https://github.com/kubernetes/kubernetes/issues/40973 where the env vars are not always set. See previous discussion...

I think it'll make sense to extract config & auth parts from kubeclient + https://github.com/kubernetes-client/ruby/ into a new gem and make both projects use it. They already have `InClusterConfig` class,...

Kubernetes plans to change service account tokens to short-lived: https://github.com/kubernetes/kubernetes/issues/70679 This even simple in-cluster config will require on-the fly auth updates (#393)

I'm not sure about `preferredVersion`. As APIs progress alpha->beta->v1->v2..., some of the data structure and the semantics will change. In the simplest case, code performing specific requests was written against...

Now we have 2 options: 1. #389 — generic support for GET on arbitrary path, which I think is worth adding anyway. 2. Add native API for this. Do we...

Indeed :+1: Concrete API proposals and/or PRs welcome.

To take a step back, this is related (but not same) to #388 which was about info from `/apis` (list of groups) and/or `/apis/GROUP` (list versions of given group). Here...