Natalie Klestrup Röijezon
Natalie Klestrup Röijezon
> I'm more inclined to hard depend on the latest version supported by either k8s-pb or k8s-openapi via kube and use the standard [compatibility matrix approach instead](https://github.com/kubernetes/client-go#compatibility-matrix). That still won't...
One downside of this PR is that it worsens the ergonomics of error policies that differ depending on the error case...
> Assume you have 10 owned resources for each resource, and 10 managed resources. That makes 100 events and thus 100 reconciliations on the startup of an operator. No, the...
In that case, the old queue entry should be reused. Is `hawkbit_operator` public?
> i was originally thinking we could explore a guard type pattern that we run users code inside (so that we would hold off until a lease has been reacquired),...
I'm putting this on hold for now, the corner cases are driving me slightly insane. I still want to have this eventually, but I'm not sure this is quite it...
Yeah, my first plan was to add it as a separate option, but the cartesian explosion is already getting pretty bad...
Feels like we're starting to come full circle back to the old `applier` API.. :P
I've been looking at implementing an `error_policy` on top of `backoff`. It mostly seems to work, just need to get around to hooking it all together.
Won't the docs-only feature break people who run `cargo doc` from their own workspaces?