fix azure disk create failure due to sdk upgrade

[andyzhangx]

What this PR does / why we need it:
fix azure storage account creation failure, this happens only on unmanaged k8s cluster on Azure.

This bug is due to azure-sdk-for-go API change introduced in v1.11:
https://github.com/Azure/azure-sdk-for-go/blob/fbe7db0e3f9793ba3e5704efbab84f51436c136e/services/storage/mgmt/2017-10-01/storage/models.go#L381-L382

there is a new field Kind which is required, so any sdk upgrade from and old version would break the storage account creation since old code won't use Kind. I have filed an issue to azure-sdk-for-go: Azure/azure-sdk-for-go#2182
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #67234

Special notes for your reviewer:

Release note:

fix azure disk create failure due to sdk upgrade

/kind bug
/sig azure

/assign @feiskyer
FYI @khenidak @brendandburns

[andyzhangx]

FYI @weherdh

[weherdh]

@andyzhangx So PR #65846 did not fully fix the issue?

[andyzhangx]

@weherdh PR #65846 fixes the azure file creation issue, while this PR fixes azure unmanaged disk creation issue although fix is similar.

[weherdh]

What about the managed disk? Does this PR also fix that? Or we need separated issue and fix.

[andyzhangx]

What about the managed disk? Does this PR also fix that? Or we need separated issue and fix.

managed disk don't need storage account, it won't have such issue.

[feiskyer]

/lgtm
/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, feiskyer

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:

• pkg/cloudprovider/providers/azure/OWNERS [andyzhangx,feiskyer]

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

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 66984, 67236, 67216, 62721, 67106). If you want to cherry-pick this change to another branch, please follow the instructions here.

[andyzhangx]

This issue only happens on k8s version: 1.11.0 ~1.11.2
workaround:

1. create a V2 storage account with Standard_LRS or Premium_LRS (depends on storageAccountType in azure file storage class)
2. use azure file storage class:

---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: azurefile
provisioner: kubernetes.io/azure-file
parameters:
  storageAccount: EXISTING_STORAGE_ACCOUNT
  skuName: Standard_LRS  #available values: Standard_LRS, Standard_GRS, Standard_RAGRS, (and Premium_LRS are supported from k8s v1.13.0)