Chris Laprun

As long as we don't need to import the full client library to use what's in `CustomResource`, I'm fine with it.

That means that the default use case where there's only one version will be more cumbersome, though.

I feel the current way is more natural: you start with one version. It's stored. You add a new version: you usually deactivate the old one and store the new...

We should take a decision on this so that it's addressed for 5.2.

That feels like too magical. The rules need to be simple, imo, and people need to make explicit decisions on which version is stored so I really feel it's natural...

Can we close this issue, @iocanel ?

Damn! 😓

No, this hasn't been fixed but not sure how important it is

We could put the `@NotNull` annotation on the `spec` field of `CustomResource`, though that might be a little heavy-handed…

Would like to re-open this as this should still be addressed, imo.