-
Notifications
You must be signed in to change notification settings - Fork 630
Objects don't have a description via kubectl explain #3054
Copy link
Copy link
Closed
Labels
area/apikind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/good-first-issueDenotes an issue ready for a new contributor.Denotes an issue ready for a new contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Metadata
Metadata
Assignees
Labels
area/apikind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/good-first-issueDenotes an issue ready for a new contributor.Denotes an issue ready for a new contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Describe the bug
No description when running
kubectl explainExpected behavior
I expected a description like all other k8s objects.
Maybe it comes from the
kubectlcode and we cannot getexplainto work on CRDs.