New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Generate List Class for CRD using java-generator-maven-plugin #5936
Comments
Can you give an example? @manusa thanks! |
@fengyinqiao : Could you please check if this helps? Lines 101 to 110 in eaf7cff
|
new KubernetesListBuilder()
.addToItems(new ElasticSearchBuilder()
// ....
.build())
.build() KubernetesResourceList<ElasticSearch> res = client.resources(ElasticSearch.class).list(); |
It does help, but is cronTabClient singleton? Whether I can use it globally after initialization, whether it has a race mode that can be used concurrently? @rohanKanojia thanks! |
From the java-generator I think we never generated the "Kubernetes Resource List". This should be sufficient for all the use-cases I'm aware of: @fengyinqiao what are you trying to achieve? |
I am new to fabric8-k8s-client and use client-go/controller-runtime before.
I thought there was only the first way to list CR, what‘s the difference between them? @andreaTP |
Describe the bug
Hello,
I'm using the Fabric8 Kubernetes Client (version 6.12.0) to automatically generate Java classes from a CRD. The generation process successfully creates the individual resource class (
ElasticSearch.class
), but it does not generate the corresponding list class (ElasticSearchList.class
).Environment
Issue Description
When I run the Maven generation plugin (
java-generator-maven-plugin
), it only generates theElasticSearch.class
and not theElasticSearchList.class
. My Maven plugin configuration is as follows:Fabric8 Kubernetes Client version
6.12.1
Steps to reproduce
Expected behavior
generates both the
ElasticSearch.class
and theElasticSearchList.class
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
other (please specify in additional context)
Environment
macOS
Fabric8 Kubernetes Client Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: