-
Notifications
You must be signed in to change notification settings - Fork 411
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
Add ability to turn off descriptions for sub-objects #561
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hello,
I am currently building an operator that uses podTemplateSpec for each element of the system (users would have reasons to want to customize each of these elements.)
Unfortunately, when I attempt to install this feature I get the following error
This is because the entire description of podTemplateSpec gets imported into the yaml CRD.
Following kubernetes-sigs/kubebuilder#1140 , I was able to make this error disappear by setting my CRD_OPTIONS to
CRD_OPTIONS ?= "crd:trivialVersions=true,preserveUnknownFields=false,maxDescLen=0"
in theMakefile
. However, this means that none of the descriptions show up if I attempt to kubectl explain!It would be really great to have a kubebuilder tag that would allow a specific field to not propagate descriptions when generating the CRDS. Something like
This would allow us to keep descriptions where we can, while also staying within the bounds of k8s's limits.
Thank you!
The text was updated successfully, but these errors were encountered: