You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2020. It is now read-only.
here gp2 is the default storage class which has kubernetes.io/aws-ebs set 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.
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
The text was updated successfully, but these errors were encountered:
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.
here gp2 is the default storage class which has
kubernetes.io/aws-ebs
set 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
The text was updated successfully, but these errors were encountered: