kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add some missing PVs and a capability overview

pull/727/head
Tolleiv Nietsch 2016-06-25 13:04:54 +02:00
parent f82d9e61d1
commit 429028dc54
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/user-guide/persistent-volumes/index.md
View File

@ -51,10 +51,15 @@ The reclaim policy for a `PersistentVolume` tells the cluster what to do with th
* GCEPersistentDisk * GCEPersistentDisk
* AWSElasticBlockStore * AWSElasticBlockStore
* AzureFile
* FC (Fibre Channel)
* NFS * NFS
* iSCSI * iSCSI
* RBD (Ceph Block Device) * RBD (Ceph Block Device)
* CephFS
* Cinder (OpenStack block storage)
* Glusterfs * Glusterfs
* VsphereVolume
* HostPath (single node testing only -- local storage is not supported in any way and WILL NOT WORK in a multi-node cluster) * HostPath (single node testing only -- local storage is not supported in any way and WILL NOT WORK in a multi-node cluster)
@ -86,7 +91,7 @@ Currently, storage size is the only resource that can be set or requested. Futu
### Access Modes ### Access Modes
A `PersistentVolume` can be mounted on a host in any way supported by the resource provider. Providers will have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV's capabilities. A `PersistentVolume` can be mounted on a host in any way supported by the resource provider. As shown in the table below, providers will have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV's capabilities.
The access modes are: The access modes are:
@ -103,6 +108,23 @@ In the CLI, the access modes are abbreviated to:
> __Important!__ A volume can only be mounted using one access mode at a time, even if it supports many. For example, a GCEPersistentDisk can be mounted as ReadWriteOnce by a single node or ReadOnlyMany by many nodes, but not at the same time. > __Important!__ A volume can only be mounted using one access mode at a time, even if it supports many. For example, a GCEPersistentDisk can be mounted as ReadWriteOnce by a single node or ReadOnlyMany by many nodes, but not at the same time.
| | ReadWriteOnce| ReadOnlyMany| ReadWriteMany|
| :--- | :---: | :---: | :---: |
| AWSElasticBlockStore | x | - | - |
| AzureFile | x | x | x |
| CephFS | x | x | x |
| Cinder | x | - | - |
| FC | x | x | - |
| FlexVolume | x | x | - |
| GCEPersistentDisk | x | x | - |
| Glusterfs | x | x | x |
| HostPath | x | - | - |
| iSCSI | x | x | - |
| NFS | x | x | x |
| RDB | x | x | - |
| VsphereVolume | x | - | - |
### Recycling Policy ### Recycling Policy
Current recycling policies are: Current recycling policies are: