Add more detail in vgs/vgsc/vgsclass printed columns

[winrouter]

What type of PR is this?

/kind feature

What this PR does / why we need it:

add more detail printed columns when exec kubectl get vgs | vgsc | vgsclass

before

[root@node-1 deploy]# kubectl get vgsc
NAME                                                    AGE
groupsnapcontent-03314fd3-faa5-4aea-a14b-416b8b47ba86   4h24m

[root@node-1 deploy]# kubectl get vgs
NAME                AGE
hostpath-mock-vgs   4h24m

[root@node-1 deploy]# kubectl get vgsc
NAME                                                    AGE
groupsnapcontent-03314fd3-faa5-4aea-a14b-416b8b47ba86   4h24m

after

[root@node-1 new-crd]# kubectl get vgsclass
NAME                 DRIVER                DELETIONPOLICY   AGE
hostpath-mock-vgsc   hostpath.csi.ake.io   Delete           4d6h


[root@node-1 new-crd]# kubectl get vgs
NAME                READYTOUSE   VOLUMEGROUPSNAPSHOTCLASS   VOLUMEGROUPSNAPSHOTCONTENT                              CREATIONTIME   AGE
hostpath-mock-vgs   true         hostpath-mock-vgsc         groupsnapcontent-03314fd3-faa5-4aea-a14b-416b8b47ba86   4h19m          4h19m


[root@node-1 new-crd]# kubectl get vgsc
NAME                                                    READYTOUSE   DELETIONPOLICY   DRIVER                VOLUMEGROUPSNAPSHOTCLASS   VOLUMEGROUPSNAPSHOTNAMESPACE   VOLUMEGROUPSNAPSHOT   AGE
groupsnapcontent-03314fd3-faa5-4aea-a14b-416b8b47ba86   true         Delete           hostpath.csi.ake.io   hostpath-mock-vgsc         default                        hostpath-mock-vgs     4h20m

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@xing-yang @RaunakShah

help me check the feature is ok, thanks

Does this PR introduce a user-facing change?:

More detail printed columns output when get vgs/vgsc/vgsclass with kubectl

[k8s-ci-robot]

Welcome @winrouter!

It looks like this is your first PR to kubernetes-csi/external-snapshotter 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/external-snapshotter has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @winrouter. Thanks for your PR.

I'm waiting for a kubernetes-csi 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.

[carlory]

@winrouter please add a release note.

LGTM cc @xing-yang

/ok-to-test

[winrouter]

thanks for your review @carlory , your comment have been addressed.

[winrouter]

thanks for you review, I already fixed it. review again @RaunakShah

[RaunakShah]

/lgtm
/approve
Thanks for catching this!

[winrouter]

/assign @xing-yang

ping @xing-yang for approval

[xing-yang]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RaunakShah, winrouter, xing-yang

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 [xing-yang]

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