on the cluster. 6. Perform static or dynamic provisioning of PVs using the CSI plugin as the provisioner. For details on how  to provision volumes for your specific storage provider, refer to the storage provider’s user manual. +### Certified CSI drivers+The following table lists the UCP certified CSI drivers.++| Partner name | Kubernetes on Docker Enterprise 3.0 |+|--------------|-------------------------------------|+| NetApp       | Certified (Trident - CSI)           |+| EMC/Dell     | Certified (VxFlexOS CSI driver)     |+| VMware       | Certified (CSI)                     |+| Portworx     | Certified (CSI)                     |+| Nexenta      | Certified (CSI)                     |+| Blockbridge  | Certified (CSI)                     |+| Storidge     | Certified (CSI)                     |

 Docker Enterprise 3.0 supports version 1.0+ of the CSI specification. Therefore,  ![Kubernetes and CSI components](/ee/ucp/images/csi-plugins.png){: .with-border} -**Note**: Docker Enterprise does not provide CSI drivers. CSI drivers are provided by enterprise storage vendors. -Kubernetes does not enforce a specific procedure for how Storage Providers (SP) should bundle and distribute CSI drivers.+> Note+>+> Docker Enterprise does not provide CSI drivers. CSI drivers are provided by enterprise storage vendors. Kubernetes does not enforce a specific procedure for how Storage Providers (SP) should bundle and distribute CSI drivers.  Review the [Kubernetes CSI Developer Documentation](https://kubernetes-csi.github.io/docs/) for CSI architecture,  security, and deployment details.  ## Prerequisites -1. Select a storage provider from the list of [available CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html) -or as documented by your storage vendor. +1. Select a CSI driver to use with Kubernetes. Contact Docker for a list of certified drivers.

+---+title: Configuring vSphere Volumes for Kubernetes+description: Learn how to add persistent storage to your Docker Enterprise clusters using vSphere Volumes.+keywords: Universal Control Plane, UCP, Docker Enterprise, Kubernetes, storage, volume+---++The [vSphere Storage for Kubernetes driver](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/index.html) enables customers to address persistent storage requirements for Kubernetes pods  in vSphere environments. The driver allows you to create a persistent  volume on a Virtual Machine File System (VMFS), and use it to manage persistent storage requirements independent of pod and VM lifecycle.++> Note+>+> Of the three main storage backends offered by vSphere on Kubernetes (VMFS, vSAN, and NFS), we support VMFS.++You can use vSphere Cloud Provider to manage storage with Kubernetes in UCP 3.1 and later. This includes support for :++* Volumes+* Persistent volumes+* Storage classes and provisioning volumes+++## Prerequisites+* Ensure that vsphere.conf is populated per the [vSphere Cloud Provider Configuration Deployment Guide](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html#create-the-vsphere-cloud-config-file-vsphereconf).+* `disk.EnableUUID` value on the worker VMs must be set to `True`.++## Configure for Kubernetes++Kubernetes cloud providers provide a method of provisioning cloud resources through Kubernetes via the `--cloud-provider` option. This is to ensure that the kubelet is aware that it must be initialized by ucp-kube-controller-manager before it is scheduled any work.++```bash+docker container run --rm -it --name ucp -e REGISTRY_USERNAME=$REGISTRY_USERNAME -e REGISTRY_PASSWORD=$REGISTRY_PASSWORD \+  -v /var/run/docker.sock:/var/run/docker.sock \+  "dockereng/ucp:3.1.0-tp2" \+  install \+  --host-address <HOST_ADDR> \+  --admin-username admin \+  --admin-password XXXXXXXX \+  --cloud-provider=vsphere \+  --image-version latest:+```++## Create a StorageClass++1. Create a StorageClass with a user specified disk format.+```bash+apiVersion: storage.k8s.io/v1+kind: StorageClass+metadata:+  name: fast+provisioner: kubernetes.io/vsphere-volume+parameters:+  diskformat: zeroedthick+```+For example, `diskformat` can be `thin`, `zeroedthick`, or `eagerzeroedthick`. The default format is `thin`.+2. Create a StorageClass with a disk format on a user specified datastore.+```bash+apiVersion: storage.k8s.io/v1+kind: StorageClass+metadata:+  name: fast+provisioner: kubernetes.io/vsphere-volume+parameters:+    diskformat: zeroedthick+    datastore: VSANDatastore+```+You can also specify the `datastore` in the StorageClass. The volume will be created on the datastore specified in the storage class, which in this case is `VSANDatastore`. This field is optional. If the datastore is not specified, then the volume will be created on the datastore specified in the vSphere config file used to initialize the vSphere Cloud Provider.++For more information on Kubernetes Storage Classes, see [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/).++## Deploy vSphere Volumes++After you create a StorageClass, you can create [PersistentVolumes (PV)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#introduction) that deploy volumes attached to hosts and mounted inside pods. A PersistentVolumeClaim (PVC) is a claim for storage resources that are bound to a PV when storage resources are granted. ++We recommend that you use the StorageClass and PVC resources as these abstraction layers provide more portability as well as control over the storage layer across environments.++To deploy vSphere volumes:++1. [Create a PVC from the plugin](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html). When you define a PVC to use the storage class, a PV is created and bound.+2. [Refer to the PVC from the Pod](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html).

 Docker Enterprise 3.0 supports version 1.0+ of the CSI specification. Therefore,  ![Kubernetes and CSI components](/ee/ucp/images/csi-plugins.png){: .with-border} -**Note**: Docker Enterprise does not provide CSI drivers. CSI drivers are provided by enterprise storage vendors. -Kubernetes does not enforce a specific procedure for how Storage Providers (SP) should bundle and distribute CSI drivers.+> Note+>+> Docker Enterprise does not provide CSI drivers. CSI drivers are provided by enterprise storage vendors. Kubernetes does not enforce a specific procedure for how Storage Providers (SP) should bundle and distribute CSI drivers.  Review the [Kubernetes CSI Developer Documentation](https://kubernetes-csi.github.io/docs/) for CSI architecture,  security, and deployment details.  ## Prerequisites -1. Select a storage provider from the list of [available CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html) -or as documented by your storage vendor. +1. Select a CSI driver to use with Kubernetes. Contact Docker for a list of certified drivers.

+kind: PersistentVolumeClaim+apiVersion: v1+metadata:+  name: myclaim+  annotations:+    volume.beta.kubernetes.io/storage-class: "iscsi-targetd-vg-targetd"

 func (p *iscsiProvisioner) getAccessModes() []v1.PersistentVolumeAccessMode { 	} } +func createPVSource(options controller.VolumeOptions, portals []string, lun int32) v1.PersistentVolumeSource {+	if options.PVC.Annotations["os"] == "windows" {+		return v1.PersistentVolumeSource{+			FlexVolume: &v1.FlexPersistentVolumeSource{+				Driver: "microsoft.com/iscsi.cmd",