Eirik A

There's __currently no support for that__ in here. It's a bit of a peripheral api, and it's also marked as alpha. It looks a bit involved, but not beyond the...

On the other hand, if it does, it would be more as part of proposed utilities.

@xrl did you get somewhere with this? it would still be a nice feature for the runtime :-)

Ah right! I thought we had unintentional support, but I guess not. Yeah, tame-oauth is probably the better place for it based on their description: > The only auth flow...

oof, yeah, this is pretty complicated! thanks for raising what you have here. the general plan here sounds reasonable; the default client should use something like this if the `proxy_url`...

Ah, this is great! Yeah, ssh dynamic forward is a SOCKS5 proxy, and forgot about this. Your SOCKS custom client works above perfectly though! It even works for me without...

Core types for this have been added in #999. Outstanding is integration with `kube-derive` to specify the how to do the conversion, which currently has to be done manually by...

Have updated/resolved Q1 here after realizing it's actually impossible for us to follow Kubernetes versioning. This means it's down to the new Q2 above; i.e. `is there a rush to...

> As an aside, for Q2, this only really concerns libraries that are part of our public API. > > Currently I believe that would be `backoff`, `tower`, `k8s-openapi` (with...

> Personally, the main thing I'd love to see for 1.0 would be to decouple kube-rs breakage from k8s-openapi breakage. Some of that could be viable. The traits crate idea...