Pod and PVC will be in a pending state when using kubernetes.io/vsphere-volume as the provisioner in Enterprise PKS
search cancel

Pod and PVC will be in a pending state when using kubernetes.io/vsphere-volume as the provisioner in Enterprise PKS

book

Article ID: 316810

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • You see a message similar to the following on a vSphere provisioned volume type when running describe pvc <pvc name>:
Failed to provision volume with StorageClass "thin-disk": invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce] are supported
  • You see a message similar to the following on a pod using a vSphere provisioned volume type when running describe pod <pod name>:
pod has unbound immediate PersistentVolumeClaims (repeated 3 times)


Environment

VMware PKS 1.x

Cause

ReadWriteMany access mode is not supported by the vSphere Cloud Provider. ReadWriteOnce must be used as the accessMode when using kubernetes.io/vsphere-volume.

Resolution

This is a known issue affecting Enterprise PKS. There is currently no resolution.

Workaround:
Set the accessMode for the pvc to ReadWriteOnce.

Additional Information

Is ReadWriteMany volume supported with vSphere Cloud Provider?

Define the PersistentVolumeClaim 


Powered by Wolken Software