Eirik A

An idea for how to do this that I have been thinking about: **We could explore changing the `Controller::new`, `Controller::owns`, et al to accept watcher streams** Users could then apply...

> Won't the docs-only feature break people who run `cargo doc` from their own workspaces? That's kind of already broken. You really need to run the big string in `make...

> This is not quite what was recommended in [Only use necessary futures components #900 (comment)](https://github.com/kube-rs/kube-rs/pull/900#discussion_r868303411); I could not get rid of the warnings during my attempt to implement the...

> In that case, would it be acceptable to refer to `futures_util` for the crate links but keep `futures` in the doctests? This would obviate the need for the internal...

> That is unexpected... I just tried `make doc` on a clean copy of my branch, and everything resolved without issue. I am running Ubuntu 20.04 server; are you running...

Yep, tested with `#[allow(unused_imports)] use futures_util;` in `watcher.rs`. Works.

yeah, that one seems to not work no matter what i try. it's not like `select` is even hidden behind any features :confused: we could maybe put it down to...

Another possibly interesting point. The current local build seems to sometimes resolve better than what docs.rs does. Case in point: [WatchStreamExt::backoff](https://docs.rs/kube/latest/kube/runtime/trait.WatchStreamExt.html#method.backoff) resolves locally, but did not resolve in the last...

I believe you find this error by setting debug trace levels on kube/kube_runtime. But regardless. RBAC errors should bubble up to the controller. It should probably crash the controller. I...

Well, turns out this is incredibly complicated to do as a trait. Was trying something along the lines of: ```rust pub trait RuntimeApiExt { type R: Resource + Clone +...