feat: use CRD generator#350
Conversation
|
Code looks good, but when I tried to use it in the memcached operator I'm getting this error: |
| ``` | ||
|
|
||
| The CRD will be generated in `target/classes/META-INF/fabric8` (or | ||
| in `target/test-classes/META-INF/fabric8`, if you use the `test` scope) with the CRD name suffixed |
There was a problem hiding this comment.
I'm wondering if this is the best place to put the generated files... Why here? Why not in resources or even in the kubernetes directory next to the generated deployment yaml?
There was a problem hiding this comment.
Because that's where fabric8 tools have traditionally put their generated files. Also, worth noting that the deployment manifest is generated by a different process (I'm assuming you're talking about the manifests generated by the quarkus extension, here) and, while it would be nice for every tool to generate things at the same spot, these tools are not supposed to know about one another and could evolve separately.
I agree, though, that it would be nice if everything was generated at the same spot. Can you please open a fabric8 ticket for this?
There was a problem hiding this comment.
There was a problem hiding this comment.
I see you already did, thanks!
Let me check but I suspect that's because the memcached operator uses a mix of different fabric8 client versions… How did you add the |
|
OK, that is indeed an issue. It's possible to work around it but we need to address this more cleanly. See java-operator-sdk/memcached-operator-sample#2 |
|
I've created an issue to simplify the dependencies: fabric8io/kubernetes-client#2840 |
| <artifactId>crd-generator</artifactId> | ||
| <scope>compile</scope> | ||
| </dependency> | ||
| ``` |
There was a problem hiding this comment.
Shouldn't we add the dependency on <dependency> <groupId>io.fabric8</groupId> <artifactId>kubernetes-model-common</artifactId> </dependency> here?
There was a problem hiding this comment.
Done. Can we merge this now?
|
added one more comment, otherwise all looks good! |
Fixes #110.