kubernetes.io/aws-ebs is set as default volume provisioner on fresh setup

[divyenpatel]

Observed tests failure on nightly CI job.

Cluster is deployed using

+ .build/dist/linux/amd64/kops create cluster kubernetes.skydns.local --cloud=vsphere --zones=vmware-zone --dns-zone=skydns.local --networking=flannel --vsphere-server=10.162.12.94 --vsphere-datacenter=vcqaDC --vsphere-resource-pool=cluster-vsan-1 --vsphere-datastore=vsanDatastore --dns private --vsphere-coredns-server=http://10.162.26.195:2379 --image=kops_ubuntu_16_04 --yes

Observed AWS storage classes on the freshly deployed kubernetes cluster.

+ kubectl describe storageclasses --all-namespaces
Name:       default
IsDefaultClass: No
Annotations:    kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1beta1","kind":"StorageClass","metadata":{"annotations":{},"labels":{"k8s-addon":"storage-aws.addons.k8s.io"},"name":"default","namespace":""},"parameters":{"type":"gp2"},"provisioner":"kubernetes.io/aws-ebs"}

Provisioner:    kubernetes.io/aws-ebs
Parameters: type=gp2
Events:     <none>

Name:       gp2
IsDefaultClass: Yes
Annotations:    kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1beta1","kind":"StorageClass","metadata":{"annotations":{"storageclass.beta.kubernetes.io/is-default-class":"true"},"labels":{"k8s-addon":"storage-aws.addons.k8s.io"},"name":"gp2","namespace":""},"parameters":{"type":"gp2"},"provisioner":"kubernetes.io/aws-ebs"}
,storageclass.beta.kubernetes.io/is-default-class=true
Provisioner:    kubernetes.io/aws-ebs
Parameters: type=gp2
Events:     <none>

here gp2 is the default storage class which has kubernetes.io/aws-ebsset as provisioner, this is causing failure for some of the e2e test cases, when we have static PVs, and then test creates PVCs to bind with these PVs.

Failed Test Specs: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/pvc_label_selector.go

After deleting stoage class gp2, test passed. Expected: This storage class should be present after deployment or default provisoner should be set to kubernetes.io/vsphere-volume

[fabulous-gopher]

This issue was moved to kubernetes/kops#2732