Getting the VMware vSphere Provider Working In Kubernetes

GettingTheVMwarevSphereProviderWorkingInKubernetes.md

Configuring the vSphere Cloud Provider

• Follow the steps here: https://kubernetes.io/docs/getting-started-guides/vsphere/#getting-started-with-the-vsphere-cloud-provider
• When you get to "Step-5", I originally put my vsphere.conf file at /etc/kubernetes, but I ran into this issue: kubernetes/kubeadm#484. I moved it to /etc/kubernetes/pki temporarily, and I was able to get things working.
• My /etc/kubernetes/pki/vsphere.conf file:

[Global]
        user = "[email protected]"
        password = "MYSUPERSECRETPASSWORD"
        server = "MYVCENTERSERVER.MYDOMAIN.com"
        port = "443" #Optional
        insecure-flag = "1" #set to 1 if the vCenter uses a self-signed cert
        datacenter = "MYDATACENTER"
        datastore = "MYDATASTORE" #Datastore to use for provisioning volumes using storage classes/dynamic provisioning
        working-dir = "Kubernetes"
        vm-name = "kubemaster" #Optional
[Disk]
    scsicontrollertype = pvscsi

• Add the following lines to /etc/kubernetes/manifests/kube-apiserver.yaml on the Master server under the spec > containers > command section

    - --cloud-provider=vsphere
    - --cloud-config=/etc/kubernetes/pki/vsphere.conf

• Add the following lines to /etc/kubernetes/manifests/kube-controller-manager.yaml on the Master server under the spec > containers > command section

    - --cloud-provider=vsphere
    - --cloud-config=/etc/kubernetes/pki/vsphere.conf

• Reload the systemctl config and restart the kubelet service

sudo systemctl daemon-reload
sudo systemctl restart kubelet.service

Testing

• Create a StorageClass for our new vsphere volume

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: thin-disk
provisioner: kubernetes.io/vsphere-volume
parameters:
    diskformat: thin

• Create a test persistent volume claim. If everything was successful, you should see this created in VMWAre

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test-disk
  annotations:
    volume.beta.kubernetes.io/storage-class: thin-disk
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi

I do all the things as above. Every thing is seems ok but after all i got following error.

Jan 23 13:57:44 centos-master-01 journal: E0123 10:27:44.354815 1 vsphere_util.go:199] Kubernetes node nodeVmDetail details is empty. nodeVmDetails : []
Jan 23 13:57:44 centos-master-01 journal: E0123 10:27:44.354855 1 vsphere.go:1059] Failed to get shared datastore: Kubernetes node nodeVmDetail details is empty. nodeVmDetails : []
Jan 23 13:57:44 centos-master-01 journal: I0123 10:27:44.354972 1 event.go:218] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-disk", UID:"aa0a426e-0027-11e8-8e6d-005056ae5f45", APIVersion:"v1", ResourceVersion:"5956", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' Failed to provision volume with StorageClass "thin-disk": Kubernetes node nodeVmDetail details is empty. nodeVmDetails : []
Jan 23 13:57:45 centos-master-01 journal: E0123 10:27:45.229122 1 reflector.go:205] k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vsphere.go:227: Failed to list *v1.Node: nodes is forbidden: User "system:serviceaccount:kube-system:vsphere-cloud-provider" cannot list nodes at the cluster scope

any solutions for this problem? I'm having the same problem as you.

Thanks

I have the same problem