Merge pull request #1046 from pnovotnak/pnovotnak/feat/volume-claim-exclusivity-and-namespacing

noted exclusivity of volume claims, namespacing particularities
reviewable/pr1045/r1
Phillip Wittrock 2016-08-17 15:17:54 -07:00 committed by GitHub
commit 504987e204
1 changed files with 5 additions and 1 deletions

View File

@ -33,7 +33,7 @@ A cluster administrator will create a number of PVs. They carry the details of t
### Binding
A user creates a `PersistentVolumeClaim` with a specific amount of storage requested and with certain access modes. A control loop in the master watches for new PVCs, finds a matching PV (if possible), and binds them together. The user will always get at least what they asked for, but the volume may be in excess of what was requested.
A user creates a `PersistentVolumeClaim` with a specific amount of storage requested and with certain access modes. A control loop in the master watches for new PVCs, finds a matching PV (if possible), and binds them together. The user will always get at least what they asked for, but the volume may be in excess of what was requested. Once bound, `PersistentVolumeClaim` binds are exclusive, regardless of the mode used to bind them.
Claims will remain unbound indefinitely if a matching volume does not exist. Claims will be bound as matching volumes become available. For example, a cluster provisioned with many 50Gi PVs would not match a PVC requesting 100Gi. The PVC can be bound when a 100Gi PV is added to the cluster.
@ -212,3 +212,7 @@ spec:
persistentVolumeClaim:
claimName: myclaim
```
### A Note on Namespaces
`PersistentVolumes` binds are exclusive, and since `PersistentVolumeClaims` are namespaced objects, mounting claims with "Many" modes (`ROX`, `RWX`) is only possible within one namespace.