Open davidxia opened 1 year ago
Is crd-model-gen image meant to be public or internal to this repo only?
is it a public open image
If it's meant to be public, any way to support x-kubernetes-validation or to disable this validation?
looks like there's a typo in that property, it should be x-kubernetes-validations
rather than singular form in your yaml. can you try that again?
Any plans to support generating classes from CRD YAMLs with x-kubernetes-validation?
at the moment, it's not in our roadmap. but we're definitely open to receive PR to add this piece. thanks!
looks like there's a typo in that property
Oh I accidentally typed it wrong (updated previous messages), but I used the plural in my YAML and the error message shows the plural also doesn't work.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
This is still definitely an issue.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
This is still definitely an issue.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
No change afaik
For future reference, I managed to find a workaround to get it working by launching a bash terminal instead of the generation script, then patching /generate.sh
to include a --validate=false
flag to the kubectl apply
command.
$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v "$(pwd)":"$(pwd)" -it --network host ghcr.io/kubernetes-client/java/crd-model-gen:v1.0.6 bash
$ sed -i 's|kubectl apply -f "$url"|kubectl apply -f "$url" --validate=false|g' /generate.sh
$ /generate.sh ...
Hopefully this helps someone else that runs into this...
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Hi, I'm using
ghcr.io/kubernetes-client/java/crd-model-gen:v1.0.6
to generate Java classes from K8s CRD YAMLs. My YAML hasx-kubernetes-validations
. Currently I'm getting the following error.I tried adding
--validate=false
to thedocker run
args, but it looks like the executable in the image only supports the following args based on this new error.my questions
crd-model-gen
image meant to be public or internal to this repo only?x-kubernetes-validations
or to disable this validation?x-kubernetes-validations
?