`kubectl get pv` is not listing dynamically created PVs by vSphere CSI Driver about cloud-provider-vsphere

[dvonthenen]

I just ran the commands using the latest (which is code changes that include this PR #136) and I don't see the problem. There were some updates to the YAML that affected permissions which could account for this. Recommend re-verifying after the PR gets merged.

[vonthd@k8smaster csi]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:39:04Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:31:33Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
[vonthd@k8smaster csi]$ kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                     STORAGECLASS   REASON   AGE
pvc-fba35f4e-296d-11e9-84f7-005056a741a8   5Gi        RWO            Delete           Bound    default/vsphere-csi-pvc   vsphere-fcd             13s
[vonthd@k8smaster csi]$ kubectl describe pv
Name:            pvc-fba35f4e-296d-11e9-84f7-005056a741a8
Labels:          <none>
Annotations:     pv.kubernetes.io/provisioned-by: io.k8s.cloud-provider-vsphere.vsphere
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    vsphere-fcd
Status:          Bound
Claim:           default/vsphere-csi-pvc
Reclaim Policy:  Delete
Access Modes:    RWO
VolumeMode:      Filesystem
Capacity:        5Gi
Node Affinity:   <none>
Message:         
Source:
    Type:              CSI (a Container Storage Interface (CSI) volume source)
    Driver:            io.k8s.cloud-provider-vsphere.vsphere
    VolumeHandle:      50bdf1e7-3545-4751-8370-7c724c4339aa
    ReadOnly:          false
    VolumeAttributes:      datacenter=vic1dc
                           name=pvc-fba35f4e-296d-11e9-84f7-005056a741a8
                           owning_datastore=shared-iscsi1-datastore-2
                           parent_name=iscsi1-cluster
                           parent_type=DatastoreCluster
                           storage.kubernetes.io/csiProvisionerIdentity=1549388801939-8081-io.k8s.cloud-provider-vsphere.vsphere
                           type=First Class Disk
                           vcenter=10.161.60.78
Events:                <none>
[vonthd@k8smaster csi]$ 

[dvonthenen]

/assign dvonthenen

[dvonthenen]

PR #136 was merged a few days ago. Please give it a try and see if it fixes your issue. Note the instructions below.

1. reinstall the CSI driver by grabbing/updating the YAML (fixed permissions) in its deployment
2. the YAML deploys v0.1.1 of the driver… so you will need to change the image to latest within the YAML in 2 places until a new tag becomes available
3. fairly detailed documentation was created for multi-vc/dc and zones support: https://github.com/kubernetes/cloud-provider-vsphere/blob/master/docs/deploying_ccm_and_csi_with_multi_dc_vc_aka_zones.md

[divyenpatel]

After applying fix mentioned at #135 (comment)

I am able to retrive pv and pvc using kubectl get

# kubectl get pvc
NAME                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS           AGE
my-vsphere-csi-pvc   Bound    pvc-48a3a1e3-3177-11e9-a630-00505690e9f4   5Gi        RWO            my-vsphere-fcd-class   14m

# kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                        STORAGECLASS           REASON   AGE
pvc-48a3a1e3-3177-11e9-a630-00505690e9f4   5Gi        RWO            Delete           Bound    default/my-vsphere-csi-pvc   my-vsphere-fcd-class            13m