Tomas Aschan

/remove-lifecycle stale /lifecycle frozen

@alvaroaleman I ran into this myself but was able to verify that this PR solves it well enough for my own needs at least. Is there anything I can do...

@fsommar I think there's an old (probably closed PR, or intermediate step later refactored away) attempt at using this to test repo-enabler, if you're curious to test it on a...

Here's the corresponding client-go fake issue, for reference: https://github.com/kubernetes/kubernetes/issues/133549

I agree this would be better to add to `conditions` rather than `errors`. Not quite sure how `errors` is used today, though, but I feel like whatever it _is_ used...

Fwiw, this relates to #190.

I don't know if the project has actually made any decisions in this direction, but I think we _should_ 😸 I base this mostly on [the Kubernetes API Conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status) guide,...

/ok-to-test

@justinsb This is (at least part of) the problem I mentioned in controller-runtime compat.

@justinsb a less hacky way to accomplish this would be to build a linter that can emit recommendations when obsolete methods are used - or to find one that already...