mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 15:46:57 +01:00
c5d64426e7
xrefs aren't allowed in modules:
$ grep -A1 'You must not include xrefs' modules/mod-docs-ocp-conventions.adoc
You must not include xrefs in modules or create an xref to a module. You can
only use xrefs to link from one assembly to another.
And we can't move this module out into an assembly directory, because
it is consumed from two places:
$ git --no-pager grep dynamic-provisioning-available-plugins
post_installation_configuration/storage-configuration.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+3]
storage/dynamic-provisioning.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+1]
We could:
a. Trim down post_installation_configuration to just xref the storage
assembly, instead of duping so much of it's content via modules.
b. Drop the module and instead inline (some of) it with copy/paste in
both assemblies.
c. Remove the xref.
With this commit, I'm going with (c), removing the xref which was
added in 57961f1117 ([STOR] Include section on the OpenStack Manila
CSI Driver, 2020-05-12, #22199).
83 lines
2.3 KiB
Plaintext
83 lines
2.3 KiB
Plaintext
// Module included in the following assemblies
|
|
//
|
|
// * storage/dynamic-provisioning.adoc
|
|
// * post_installation_configuration/storage-configuration.adoc
|
|
|
|
[id="available-plug-ins_{context}"]
|
|
= Available dynamic provisioning plug-ins
|
|
|
|
{product-title} provides the following provisioner plug-ins, which have
|
|
generic implementations for dynamic provisioning that use the cluster's
|
|
configured provider's API to create new storage resources:
|
|
|
|
|
|
[options="header",cols="1,1,1"]
|
|
|===
|
|
|
|
|Storage type
|
|
|Provisioner plug-in name
|
|
|Notes
|
|
|
|
|{rh-openstack-first} Cinder
|
|
|`kubernetes.io/cinder`
|
|
|
|
|
|
|
|{rh-openstack} Manila Container Storage Interface (CSI)
|
|
|`manila.csi.openstack.org`
|
|
|Once installed, the OpenStack Manila CSI Driver Operator and ManilaDriver automatically create the required storage classes for all available Manila share types needed for dynamic provisioning.
|
|
|
|
|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 {product-title}
|
|
cluster per GCE project to avoid PVs from being created in zones where
|
|
no node in the current cluster exists.
|
|
|
|
//|GlusterFS
|
|
//|`kubernetes.io/glusterfs`
|
|
//|
|
|
|
|
//|Ceph RBD
|
|
//|`kubernetes.io/rbd`
|
|
//|
|
|
|
|
//|Trident from NetApp
|
|
//|`netapp.io/trident`
|
|
//|Storage orchestrator for NetApp ONTAP, SolidFire, and E-Series storage.
|
|
|
|
|link:https://www.vmware.com/support/vsphere.html[VMware vSphere]
|
|
|`kubernetes.io/vsphere-volume`
|
|
|
|
|
|
|
//|HPE Nimble Storage
|
|
//|`hpe.com/nimble`
|
|
//|Dynamic provisioning of HPE Nimble Storage resources using the
|
|
//HPE Nimble Kube Storage Controller.
|
|
|
|
|===
|
|
|
|
[IMPORTANT]
|
|
====
|
|
Any chosen provisioner plug-in also requires configuration for the relevant
|
|
cloud, host, or third-party provider as per the relevant documentation.
|
|
====
|