When to add a new model (Flux CD)

[jonesbusy]

Hi,

I did not find any guideline or contributing quide on when to add a new model of CR

I'm currently writting an operator (JOSDK + Quarkus) and I need to create Flux CD dependent CR (like OCIRepositories https://fluxcd.io/flux/components/source/ocirepositories/)

Should a new module be created and CR generated on the Kubernetes Client? Is there any interest? Or such classes need to be packaged in my own code?

I would argue that FluxCD is a well know and stable CNCF project. All CR are in 'v1' now

Thanks

[manusa]

You should package the classes in your own project by using the java-generator.

Check the documentation here: https://github.com/fabric8io/kubernetes-client/blob/main/doc/java-generation-from-CRD.md

If you're using the Quarkus Operator SDK extension, the CRD generation for the project is integrated.
I'm not sure that the java-generation is integrated too (@metacosm ?), however, the Java Generator Maven plugin should work.

[metacosm]

The Quarkus Operator SDK extension focused on the java-to-CRD direction but there is no reason why the reverse wouldn't work. There's an option, for example, to avoid generating CRDs for CRs in that situation.

[jonesbusy]

Thanks. This can be closed.

Using https://github.com/fabric8io/kubernetes-client/blob/main/doc/java-generation-from-CRD.md works very well for my use case to get Flux CRD as Java Object