Azure-docs: Failed to create provisioner: Failed to get Azure Cloud Provider. GetCloudProvider returned <nil> instead

[soheilade]

following the guide here on a k8s the I installed on an azure VM myself, my PVC have this error and stays in pending mode, any idea how to resolve it?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a57e48b4-dc33-0b9d-b773-42ce7d2bffd0
• Version Independent ID: e912ac2d-cf6a-0b54-4697-1940b1270874
• Content: Dynamically create a Files volume for multiple pods in Azure Kubernetes Service (AKS)
• Content Source: articles/aks/azure-files-dynamic-pv.md
• Service: container-service
• GitHub Login: @mlearned
• Microsoft Alias: mlearned

[himanshusinha-msft]

Thanks for the ask . At this time we are reviewing the ask and we will reply back as soon as we can .

[VikasPullagura-MSFT]

@soheilade Can you please elaborate more on the issue.

Are you using AKS OR you have installed k8s on a Azure VM and trying the tutorial for creating a persistent volume claim.

[soheilade]

I have installed a k8s cluster myself on a vm and i am trying the tutorial for creating an storgaeclass and PVC. when I runkubectl get sc, it shows me that my storage class exist but when I run kubectl get pvc, they have pendingstatus and the error above is displayed when i describe the PVCs.

[VikasPullagura-MSFT]

@soheilade If it a AKS environment will have a Service Principle that will be used to allocate resources.

In your case as it is on VM, did you specify any Service principle for the cluster you have created.

[soheilade]

no, could you please advise how can I create this service principle?

[jakaruna-MSFT]

@soheilade Can you use AKS (managed kubernetes service from Azure)?
In AKS you will be charged only for the nodes which you run. Master (control plane) is free.

In AKS, These management activities are taken care

[VikasPullagura-MSFT]

@soheilade Using AKS is recommended, try using AKS and let us know if you run into any issues following the document.

We will close this issue now. If there are further questions on this, please tag my name in a comment. I will reopen the issue and we will be glad to assist you further on this.

[michaelelleby]

@VikasPullagura-MSFT I am seeing this same issue, with minikube on a physical Windows 10 version 1909 with Hyper-V.

> kubectl describe pvc
Name:          ps-pvc
Namespace:     default
StorageClass:  ps-sc
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/azure-file
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    <none>
Events:
  Type     Reason              Age                 From                         Message
  ----     ------              ----                ----                         -------
  Warning  ProvisioningFailed  28s (x9 over 4m5s)  persistentvolume-controller  Failed to create provisioner: Failed to get Azure Cloud Provider. GetCloudProvider returned <nil> instead

> kubectl describe sc
Name:            ps-sc
IsDefaultClass:  No
Annotations:     kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{},"name":"ps-sc"},"parameters":{"location":"eastus2","secretName":"volume-azurefile-storage-secret","skuName":"Standard_LRS","storageAccount":"dsta001persistentvolume"},"provisioner":"kubernetes.io/azure-file"}

Provisioner:           kubernetes.io/azure-file
Parameters:            location=eastus2,secretName=volume-azurefile-storage-secret,skuName=Standard_LRS,storageAccount=<edited out>
AllowVolumeExpansion:  <unset>
MountOptions:
  dir_mode=0777
  file_mode=0777
  uid=0
  gid=0
  mfsymlinks
  cache=strict
ReclaimPolicy:      Delete
VolumeBindingMode:  Immediate
Events:             <none>

> kubectl  describe secrets/volume-azurefile-storage-secret
Name:         volume-azurefile-storage-secret
Namespace:    default
Labels:       <none>
Annotations:
Type:         Opaque

Data
====
azurestorageaccountname:  23 bytes
azurestorageaccountkey:   88 bytes

> minikube version
minikube version: v1.11.0
commit: 57e2f55f47effe9ce396cea42a1e0eb4f611ebbd

> kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

> docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:23:10 2020
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:29:16 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

[avenda]

same issue here using rke and i cant change to aks cluster

[emiliocolo]

@VikasPullagura-MSFT same here,

Changing to AKS is not an option neither, our cluster is already deployed and we are looking into general storage cloud solution for that cluster, so in case that non AKS is not supported, probably will look into somewhere else.

[SQLHorizons]

@soheilade Can you use AKS (managed kubernetes service from Azure)?
In AKS you will be charged only for the nodes which you run. Master (control plane) is free.

In AKS, These management activities are taken care

we should be offered a solution to the problem, not work around as AKS may not be an option but using azure storage is an option wherever k8s cluster is hosted.

[kirankbee]

We have VM running on azure with our own implementation of Kubernetes with out AKS.The issue we are unable to connect Azure File storage our cluster for persistence , is AKS is the only option?