Eirik A

I think the difficulty here is whether or not we should force this behavior on the `Controller`. We would have to use a lot more reflectors (or something smarter) at...

Coming back to this, this is probably the next thing I'd like to improve. Want to investigate whether we can inject some kind of event filter at the very end...

another option: if we can make the use of a local kubeconfig opt-in for in-cluster use, then the burden of sanitising will fall on the app. that we we are...

> Relying on the Kubeconfig itself to decide this would solve nothing, no? yeah, it's a big `if`; it won't solve anything unless we have a foolproof way. i can't...

Yeah, that is a good assessment, and possibly the `ResourceExt::name` case has probably gone a bit far for convenience internally. We probably should not use it in the general case...

> For guidance on what to do instead, one somewhat more ergonomic way would be to define a common helper struct with the fields you need, and a `TryFrom`. That...

Yeah, it doesn't really help with panic policies, but it avoids the need to do any unwraps (since the event api only takes options as input). That's probably not a...

Have had a veeery quick go at adding something about this in https://github.com/kube-rs/website/pull/21 . This is less important now that we've dealt with the more egregious problem-child `ResourceExt::name` in favour...

Yeah, helpers like that would be very much appreciated! I think we have some logic like this already [inside the finalizer helper](https://github.com/kube-rs/kube-rs/blob/0e70871e10160f7ffa0c19c6003202e942537ff1/kube-runtime/src/finalizer.rs#L154-L172) that is utilizing jsonpatches. I personally always wanted...

Ah, that type of module would also probably work inside core, not what I expected, but it's probably easier than combining json patches, and it's a clever signature.