Skip to content
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 kubectl explain crd ,how can I know all fields in crd #4001

Closed
13567436138 opened this issue Jun 4, 2021 · 6 comments
Closed

add kubectl explain crd ,how can I know all fields in crd #4001

13567436138 opened this issue Jun 4, 2021 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@13567436138
Copy link

Feature request

add kubectl explain crd

Use case

@13567436138 13567436138 added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 4, 2021
@13567436138
Copy link
Author

not good enough

@afrittoli
Copy link
Member

@13567436138 Would you care to provide a bit more context?
Why is the answer from @nikhil-thomas not sufficient?
What are your use cases (they are missing in the feature request)?
Thank you

@13567436138
Copy link
Author

ok,I surrender.but I still hope somebody will provider explain command's content.

@vdemeester
Copy link
Member

@13567436138 the problem we have right now is that, kubectl explain looks at the embedded openapi schema in the CRD. But, if we add those in our CRD, we are hitting the object limit of etcd (in most/default kubernetes setup).

@liangyuanpeng
Copy link

liangyuanpeng commented Jul 15, 2021

@13567436138 the problem we have right now is that, kubectl explain looks at the embedded openapi schema in the CRD. But, if we add those in our CRD, we are hitting the object limit of etcd (in most/default kubernetes setup).

So we just no idea to let Tekton working for kubectl explain,right? It's frustrating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

5 participants