add azure disk modifier

[handlerww]

What problem does this PR solve?

This PR introduces the Azure Disk Modifier. As of Kubernetes 1.31, the VolumeModifyClass feature remains in beta and is not enabled by default on Azure. As a workaround, we have implemented the Azure Disk Modifier by drawing inspiration from this project's AWS disk modifier implementation. This enhancement allows for disk modification capabilities on Azure, aligning with the existing functionality available for AWS.

This feature will use the kubelet identity of AKS, you should grant kubelet identity permission to modify the disk.

What is changed and how does it work?

Code changes

• Has Go code change
• Has CI related scripts change

Tests

• Unit test
• E2E test
• Manual test
• No code

Side effects

• Breaking backward compatibility
• Other side effects:

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation

Release Notes

Please refer to Release Notes Language Style Guide before writing the release note.

Manual test

kubectl create -f - <<EOF
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
   name: premium2-4000-1000
parameters:
   cachingMode: None
   skuName: PremiumV2_LRS
   DiskIOPSReadWrite: "4000"
   DiskMBpsReadWrite: "1000"
provisioner: disk.csi.azure.com
reclaimPolicy: Delete
volumeBindingMode: Immediate
allowVolumeExpansion: true
EOF

kubectl create -f - <<EOF
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
   name: premium2-4000-800
parameters:
   cachingMode: None
   skuName: PremiumV2_LRS
   DiskIOPSReadWrite: "4000"
   DiskMBpsReadWrite: "800"
provisioner: disk.csi.azure.com
reclaimPolicy: Delete
volumeBindingMode: Immediate
allowVolumeExpansion: true
EOF

kubectl apply -f - <<EOF
apiVersion: pingcap.com/v1alpha1
kind: TidbCluster
metadata:
  name: basic
  namespace: tidb-cluster
spec:
  version: v8.1.0
  timezone: UTC
  pvReclaimPolicy: Delete
  enableDynamicConfiguration: true
  configUpdateStrategy: RollingUpdate
  discovery: {}
  helper:
    image: alpine:3.16.0
  pd:
    baseImage: pingcap/pd
    maxFailoverCount: 0
    replicas: 1
    storageClassName: premium2-4000-1000
    requests:
      storage: "10Gi"
    config: {}
  tikv:
    baseImage: pingcap/tikv
    maxFailoverCount: 0
    evictLeaderTimeout: 1m
    replicas: 1
    storageClassName: premium2-4000-1000
    requests:
      storage: "10Gi"
    config:
      storage:
        reserve-space: "0MB"
      rocksdb:
        max-open-files: 256
      raftdb:
        max-open-files: 256
  tidb:
    baseImage: pingcap/tidb
    maxFailoverCount: 0
    replicas: 1
    service:
      type: ClusterIP
    config: {}
EOF

Modify the storage request and storage class name, then on Azure portal the disk properties changed as expected.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from handlerww, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 56.08466% with 83 lines in your changes missing coverage. Please review.

Project coverage is 56.98%. Comparing base (a16b2e8) to head (3cdbac0).
Report is 9 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5958      +/-   ##
==========================================
- Coverage   57.19%   56.98%   -0.21%     
==========================================
  Files         259      260       +1     
  Lines       33233    45024   +11791     
==========================================
+ Hits        19008    25658    +6650     
- Misses      12291    17382    +5091     
- Partials     1934     1984      +50     

Flag	Coverage Δ
unittest	56.98% <56.08%> (-0.21%)	⬇️

[csuzhangxc]

Can we use a newer version for these modules? then it can reduce the bump in the future.

[csuzhangxc]

Do we need to check extract if len(parts) = 9 above, or should we use strings.SplitN hear?

[csuzhangxc]

What's the behavior without an Azure config? can we do the same check as we did for AWS in dependences.go?

[csuzhangxc]

Do these statuses exist for Azure?