Eirik A

Oh, right. For some reason I forgot you could just factor out closures :dumpling: That's definitely pretty similar in the base case :thinking: The `secrets_syncer` example writes them all inline...

A trait similar to this this would also be useful for the scale subresource, allowing us to could help close #142. Though I suspect either of these would have to...

Another annoying point; subresources may need two versions by the look of the [APIResource struct](https://github.com/kubernetes/apimachinery/blob/945d4ebf362b3bbbc070e89371e69f9394737676/pkg/apis/meta/v1/types.go#L1011-L1013)

We have had traits for this for a while; `HasSpec` and `HasStatus` (convenience for `Object`), but we are actually filling these out in `k8s-pb`: https://github.com/kube-rs/k8s-pb/issues/4 so this can be solved...

Naming-wise, it's also possible we should call the worker here the `Elector`, and the params `ElectorParams` to avoid confusion with the existing `Lease` object.

Another question here; how large is the set of CRDs that you are listing? Side-note; we are working on a problem to add backoff to the internal mechanisms here, because...

I think we probably want to have a page on [kube.rs](https://kube.rs) on the controller guide dedicated to this. Have linked this issue from https://github.com/kube-rs/website/issues/5

Hehe fair. That makes sense. A schemars fork makes a lot of sense, agree with the points. I had considered getting a light-weight thing inside the derive macro crate at...

Bringing back this discussion a bit. Hid some of the previous comments because they were off-topic or outdated. The example created in #432 solves the basic need by providing a...

Hey, thanks a lot for all of this! I think this makes sense to include a lot of this in kube, and will come back in a day or two...