public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-27 13:38:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

language cleanup

Browse Source
This commit is contained in:
Mark Bishop
2018-07-05 11:49:48 -07:00
parent aab90da136
commit 8d6c8a6998
1 changed files with 5 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md
+5 -9
View File
@@ -20,12 +20,9 @@ Storage Classes allow you to create PVCs dynamically without having to create PV
### Storage and Cloud Providers ### Storage and Cloud Providers
<<<<<<< HEAD Each storage class contains the fields `provisioner`, `parameters`, and `reclaimPolicy`, which are used when a persistent volume that belongs to the class needs to be dynamically provisioned.
Kubernetes (and therefore, Rancher) supports a wide variety of storage volume plugins, both on premise and in the cloud.
=======
Each storage class contains the fields `provisioner`, `parameters`, and `reclaimPolicy`, which are used when a PersistentVolume belonging to the class needs to be dynamically provisioned.
The `provisioner` determine which volume plugin will be used to provision the persistent volumes, Rancher allows the user to define storage classes for the following provisioners: The `provisioner` determines which volume plugin is used to provision the persistent volumes. You can define storage classes for the following provisioners:
- Amazon EBS Disk - Amazon EBS Disk
- AzureFile - AzureFile
@@ -41,12 +38,11 @@ The `provisioner` determine which volume plugin will be used to provision the pe
- StorageOS - StorageOS
- Vmware vSphere Volume - Vmware vSphere Volume
In addition to customizing each provisioner options for the storage class, Rancher allows the user to specify the `reclaimPolicy` of the volume, there are two options available: In addition to customizing each provisioner's options for the storage class, you can also define the volume `reclaimPolicy`. There are two options available:
- Delete volumes and underlying device when released by workloads. - Delete volumes and underlying device when released by workloads.
- Retain the volume for manual cleanup. - Retain the volume for manual cleanup.
Rancher also allow the user to specify custom `MountOptions` for the persistent volume created. Finally, you can define custom `MountOptions` for the persistent volume created.
`parameters` are specific to each cloud storage provisioners, for full information about the storage classes provisioners parameters please refer to the official [Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters) `parameters` are specific to each cloud storage provisioner. For full information about the storage classes provisioner parameters, refer to the official [Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters).
>>>>>>> Storage Classes with cloud provisioner