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

kubectl explain --recursive --depth 5 #1659

Open
novellizator opened this issue Sep 24, 2024 · 2 comments · May be fixed by kubernetes/kubernetes#127820
Open

kubectl explain --recursive --depth 5 #1659

novellizator opened this issue Sep 24, 2024 · 2 comments · May be fixed by kubernetes/kubernetes#127820
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@novellizator
Copy link

What would you like to be added:
Setting the maximum depth of the recursion could be helpful at times.

Why is this needed:
when you kubectl explain complex objects such as pods, it goes way to much in detail, so having a shorter desc would be helpful.

@novellizator novellizator added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 24, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 24, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

@ak20102763
Copy link
Contributor

@novellizator I think this --depth <int> flag would be a good addition, along with --recursive and it will give better UX. User may want to see the first few levels of details to begin with and not the entire description of complex resources. I got the implementation for plaintext type of output, would like to take this up once it is triaged.

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. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants