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 categories to kubectl api-resources wide output and add --categories flag #111096
Add categories to kubectl api-resources wide output and add --categories flag #111096
Conversation
Add categories column to show which categories each resource type belongs to. Add --categories flag to allow filtering the output to a specific category or set of categories. Change verbs column to display verbs in a comma-delimited list, consistent with other multi-value columns in the output.
/hold |
/retest |
1 similar comment
/retest |
The Kubernetes project currently lacks enough 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 stale |
/triage accepted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good--thanks for adding this functionality. One small nit-pick: is it possible to update the Release Notes to display the two items (-o wide
& --categories
) instead of one long item. I think the new --categories
would be more discoverable.
/remove-lifecycle stale |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brianpursley, seans3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks, @seans3 I updated the release notes... I assume it is OK to have two separate lines in the release note block. PTAL and let me know if you have any improvements to suggest. |
/hold cancel |
/lgtm |
What type of PR is this?
/kind feature
/kind cleanup
What this PR does / why we need it:
Some resources have one or more categories to which they belong (ie. all, api-extensions). However, there is not a good way for people to discover those categories.
Additionally, this leads to confusion about commands like
kubectl get all
where it seems that theall
is some kind of magic keyword, when in reality it is simply a category name that is being resolved.This PR does the following:
kubectl api-resources -o wide
)--categories
flag that lets you filter on category, just like you can filter on verb.Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: