kubectl explain --recursive --depth 5

[novellizator]

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.

[k8s-ci-robot]

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]

@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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale