Cloud provider not initialized properly

4/5/2020

I created storageclass and persistentvolumeclaim in the vSphere infrastructure. However, I am getting an error when I checked persistentvolumeclaim using kubectl describe pvc pvc-name command:

[root@kube-master-01 ~]# kubectl describe pvc jenkins-claim -n kube-jenkins
Name:          jenkins-claim
Namespace:     kube-jenkins
StorageClass:  fast
Status:        Pending
Volume:
Labels:        <none>
Annotations:   kubectl.kubernetes.io/last-applied-configuration:
                 {"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{"volume.beta.kubernetes.io/storage-class":"fast"},"name":"jen...
               volume.beta.kubernetes.io/storage-class: fast
               volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/vsphere-volume
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    <none>
Events:
  Type     Reason              Age                    From                         Message
  ----     ------              ----                   ----                         -------
  Warning  ProvisioningFailed  2m42s (x701 over 26h)  persistentvolume-controller  Failed to provision volume with StorageClass "fast": Cloud provider not initialized properly

The storageclass.yml and persistentvolumeclaim.yml used is as followings:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast
provisioner: kubernetes.io/vsphere-volume
parameters:
  datastore: VSANDatastore
  diskformat: thin
  fstype: xfs

The persistentvolumeclaim.yml:

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: jenkins-claim
  annotations:
    volume.beta.kubernetes.io/storage-class: fast
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5G

This problem occurs frequently in VMware vSphere environment.

-- thenextgeneration
kubernetes
persistent-volume-claims
persistent-volumes
vmware
vsphere

0 Answers