Natalie Klestrup Röijezon

> I appreciate where you are coming from, but I find it difficult to believe you can write anything non-trivial without any piece of shared state - at the very...

Personally, I'd lean towards [crate2nix](https://github.com/kolloch/crate2nix) and [`buildLayeredImage`](https://grahamc.com/blog/nix-and-layered-docker-images) because: 1. It has much better caching behaviour than Dockerfiles (since it caches each Rust package individually, just like Cargo) 2. It automatically...

Oh, that's interesting. The caching seems stronger than for the plain `Dockerfile` setup, but there doesn't seem to be much of a story for non-cargo build steps (seeing `apt` invoked...

> Remove unwrap from backgrounded Lease renewal tokio task (how do we report errors in this situation?) Hm, we also need some way to notify the user that the lease...

This looks like an underlying HTTP client issue, but it makes sense that `watcher` would be more likely to hit the issue. Intuitively I suspect that the issue is that...

It's also worth keeping in mind that Kube-rs 0.58.1 is pretty outdated. Can you confirm that this still happens on Kube-rs 0.64.0?

@xrl Cool! This seems like something that we ought to have in `kube_runtime`. Haven't had the time to go through all of it, but a few notes: > Poll for...

Personally, the main thing I'd love to see for 1.0 would be to decouple kube-rs breakage from k8s-openapi breakage. Given that we mostly interact with k8s-openapi via traits, maybe it...

I think that's also kind of required if we want to approach parity between k8s-openapi and k8s-pb at some point.

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 the caveats above),...