Show HierarchicalResourceQuota status by kubectl-hns

[mochizuki875]

What type of PR is this?:

/kind feature

What this PR does / why we need it:

As #274, there is no way to know the quota and consumption of resource in the HierarchicalResourceQuota other than check the detail.
So I added new sub-command to show HierarchicalResourceQuota status as below.

$ kubectl hns hrq -n test
NAME         AGE     REQUEST                                              LIMIT
test-hrq     2m37s   requests.cpu: 500m/1, requests.memory: 100Mi/200Mi   limits.cpu: 500m/2, limits.memory: 100Mi/500Mi
test-hrq-2   4m6s    requests.memory: 100Mi/300Mi                         limits.cpu: 500m/1

$ kubectl hns hrq test-hrq -n test
NAME       AGE     REQUEST                                              LIMIT
test-hrq   2m43s   requests.cpu: 500m/1, requests.memory: 100Mi/200Mi   limits.cpu: 500m/2, limits.memory: 100Mi/500Mi

$ kubectl hns hrq --all-namespaces
NAMESPACE   NAME         AGE     REQUEST                                              LIMIT
test        test-hrq     2m49s   requests.cpu: 500m/1, requests.memory: 100Mi/200Mi   limits.cpu: 500m/2, limits.memory: 100Mi/500Mi
test        test-hrq-2   4m18s   requests.memory: 100Mi/300Mi                         limits.cpu: 500m/1

Tested:

Unit and E2E tests has passed.
I also added test case to HRQ E2E test which is now Pending.

Which issue(s) this PR fixes:

#274

Special notes for your reviewer:

In this case, if there is a .status.hard.<requests/limits>.<resource> field in HierarchicalResourceQuota, the corresponding content should appear in REQUEST and LIMIT.

I tried using JsonPath with HierarchicalResourceQuota's CustomResourceDefinition(.spec.versions.additionalPrinterColumns field), but I couldn't come up with an expression to control what is displayed.

So in this PR, I propose a new sub-command of kubectl-hns in the following format to view the status of HierarchicalResourceQuota

kubectl-hns hrq [NAME] [flags]

If you have better ideas for doing that, please let me know and I'll fix it.

[k8s-ci-robot]

Hi @mochizuki875. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[adrianludwin]

This looks amazing. No notes, thank you for doing this!

Can you please also cherry-pick this to the v1.1 branch?

/ok-to-test
/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrianludwin, mochizuki875

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:

• OWNERS [adrianludwin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment