Available dynamic provisioning plug-ins
Fusion Data Foundation provides provisioner plugins, which have generic implementations for dynamic provisioning that use the cluster’s configured provider’s API to create new storage resources.
Table 1 details the provided Fusion Data Foundation provisioner plugins.
| Storage type | Provisioner plug-in name | Notes |
|---|---|---|
| OpenStack Cinder |
kubernetes.io/cinder
|
|
| AWS Elastic Block Store (EBS) |
kubernetes.io/aws-ebs
|
For dynamic provisioning when using multiple clusters in different zones, tag each node with
Key=kubernetes.io/cluster/<cluster_name>,Value=<cluster_id> where
<cluster_name> and <cluster_id> are unique per
cluster. |
| AWS Elastic File System (EFS) | Dynamic provisioning is accomplished through the EFS provisioner pod and not through a provisioner plug-in. | |
| Azure Disk |
kubernetes.io/azure-disk
|
|
| Azure File |
kubernetes.io/azure-file
|
The persistent-volume-binder ServiceAccount requires permissions to create
and get Secrets to store the Azure storage account and keys. |
| GCE Persistent Disk (gcePD) |
kubernetes.io/gce-pd
|
In multi-zone configurations, it is advisable to run one Fusion Data Foundation cluster per GCE project to avoid PVs from being created in zones where no node in the current cluster exists. |
| VMware vSphere |
kubernetes.io/vsphere-volume
|
Important: Any chosen provisioner plug-in also requires configuration for the relevant
cloud, host, or third-party provider as per the relevant documentation.