[V2] Storage Analysis Tool for Azure Disk CSI Driver V2

[hccheng72]

What type of PR is this?
/kind feature

What this PR does / why we need it:

1. This tool to facilitate analysis and debugging of the Azure Disk CSI Driver in Kubernetes cluster.
2. Reporting Azure Disk CSI Driver V2 persistent volumes information gathered by pod using information from its custom resources.
3. Reporting Azure Disk CSI Driver V2 volume attachments information gathered by pod/node/zone using information from its custom resources.

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:
Testing cases output:

az-analyze get

az-analyze get node

az-analyze get azv --pod <my-pod-name>
(if no specified namespace, default will be used)

az-analyze get azv
(show all azv in a table with a pod column)

az-analyze get azva --pod <my-pod-name>
(if no specified namespace, default will be used)

az-analyze get azva --node <my-node-name>
(if namespace is provided, it'll be ignored)

az-analyze get azva --zone <my-zone-name>
(if namespace is provided, it'll be ignored)

az-analyze get azva
(show all azva in a table with pod, node and zone as columns)

az-analyze get azva --pod
(empty argument for pod/node/zone flag will cause an error)

az-analyze -h

Release note:

none

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: hccheng72 (7e9e368, 45a433e, 39de770, 540b4d5)

[k8s-ci-robot]

Welcome @hccheng72!

It looks like this is your first PR to kubernetes-sigs/azuredisk-csi-driver 🎉. 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-sigs/azuredisk-csi-driver 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 @hccheng72. 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.

[andyzhangx]

/ok-to-test
could you add a unit test and build test in this PR?

[edreed]

/assign @nearora-msft

[nearora-msft]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hccheng72, nearora-msft

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 [nearora-msft]

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