Chris Laprun

Actually, 1.26 is using the commons-codec version of Charsets 🤦🏼 but that was changed in https://github.com/apache/commons-compress/commit/2d1b94ff3f3d8c6c5bb25b5be0d4c8e0fdd73a4b

Seems like adding the commons-codec optional dependency also addresses the native compilation issues.

The change made in https://issues.apache.org/jira/browse/COMPRESS-659 will make commons-compress dependent on commons-io, though, so we might need some equivalent fix here as well to add a commons-io dependency.

I've built 1.26.1-SNAPSHOT locally and confirmed that simply upgrading to it without other changes seems to address the native compilation issue I was seeing.

> It might be an ide to also support this in the CustomResource abstraction, currently all custom resource POJO has status, although in k8s this is not necessarily true. CRD...

I would like to reopen this as we're still seeing issues where such a functionality would be useful, in particular, for example when doing RBAC generation, being able to detect...

> It's unfortunately harder than it sounds - the code generation isn't really setup to understand things that are already defined by a base class. Yes, looking at what's involved,...

I think also that to support this, most of the code should probably be handled via jsonschema2pojo Annotators to be able to generate the needed Java code.

We could also use the Java generator from CRDs…

Do you have any ideas as to what could be used?